Straight answers about what Trackument collects, where it lives, and who can see it.
The facts you enter about an incident: what happened, when, and the employee's position and classification. Names and other identifying details are replaced with placeholders before they ever leave your browser.
No. Nothing your district enters is used to train any AI model. Your data is used only to generate your documentation, and for nothing else.
Trackument runs on Railway, hosted in the United States. Anything stored in the database is encrypted at rest.
All traffic between your browser and Trackument is encrypted in transit over HTTPS. Data at rest is encrypted by default through Railway.
API keys and credentials are stored as environment variables, never in the codebase. The codebase lives in a private repository. Application access is currently limited by a password gate during beta, with broader role-based access controls planned as Trackument grows.
Trackument does not store generated documents after your session ends. Once you download a document, it's yours to keep in your district's own systems, not in a third-party archive.
A small, disclosed list, each limited to what its specific function needs:
No. Trackument does not work with analytics vendors, ad networks, or data brokers of any kind.
Your district's stored settings and account data are deleted from Trackument's systems. Since generated documents are never retained after a session, there is nothing further to delete there. Contact help@trackument.com to confirm your specific offboarding timeline.
See how Trackument can work for your district.