Security
Trackument handles employee discipline documentation, which means it handles information that matters. Here is how that information is protected, in plain language.
All traffic between your browser and Trackument runs over HTTPS, so anything moving between your device and the server is encrypted in transit, whether you're on a district network or a home wifi connection. Any data stored in Trackument's database is encrypted at rest by default through Railway, the platform Trackument runs on.
Before any facts are sent to generate a document, employee names and other identifying details go through a pseudonymization process. The AI model that drafts your document never sees a real name. It works from the facts of the situation, not from an identity, so the most sensitive detail in any discipline case is kept out of the process entirely.
Trackument does not store generated documents after your session ends. Once you download a document, it's yours, and it isn't sitting in a database somewhere that could later be breached, subpoenaed, or simply forgotten about. Your documentation belongs in your district's own systems, not in a third-party archive.
Trackument works with two subprocessors: Railway, which hosts the application and its database, and Anthropic, which provides the AI model that drafts your documents. That's the complete list. No hidden analytics vendors, no data brokers, no unnecessary third parties with access to district information.
API keys and credentials are stored as environment variables on the hosting platform, never written into the codebase itself. The codebase lives in a private repository accessible only to the developer. Access to the application itself is currently limited through a password-protected gate while Trackument is in beta, with broader access controls planned as the product grows.
Log in to access your account, or reach out to sign up.
