Effective and updated: September 4, 2026
This policy describes Project Ledger by Tervalum, a public service operated by Tervalum Systems. It applies to Project Ledger account data and service use.
Information processed
- Account and authentication data: account identifiers and authentication information needed to sign you in through Auth0 and associate access with your Project Ledger account. Do not submit sign-in credentials as project content.
- Intentional project content: non-sensitive facts, decisions, handoffs, superseded facts and verified failure lessons you choose to provide through the service.
- Minimal audit and security data: records needed to associate service actions with an account, inspect audit history and investigate errors or misuse.
- Support communications: your email address and the information you choose to include when contacting support.
Why we process information
We use this information to authenticate access, isolate users' records, store and retrieve project state, carry out requested updates and handoffs, provide audit history, process exports and deletion, respond to support requests and protect service operation.
Service providers and client platforms
- Tervalum Systems: operates Project Ledger and handles service support.
- Railway: provides hosting for the Project Ledger service and its datastore.
- Auth0: provides OAuth authentication.
- OpenAI: provides the client platform when you use Project Ledger through ChatGPT or another OpenAI surface. Your requests and returned tool content are processed in that client context, subject to the platform's own terms, privacy policy and settings.
Project Ledger does not use your information for advertising, sell personal data or perform behavioral profiling. These public Project Ledger pages do not add advertising, analytics, tracking cookies or third-party scripts.
Prohibited sensitive data
Do not store passwords, API keys, tokens, MFA codes, private keys, payment-card data, protected health information, government identifiers or full chat transcripts. Use Project Ledger only for non-sensitive project information. Project Ledger rejects restricted credential and sensitive-data storage. Review content before submitting it rather than relying solely on those checks.
Retention and deletion
Active project content is retained until you delete it or request account-data deletion. Superseding a fact preserves the distinction between earlier and updated information; it is not deletion.
Deleted data is removed from the primary Project Ledger datastore. No scheduled backups are presently configured for the Project Ledger production volume on Railway. We make no backup-retention or recovery-period promise.
Project Ledger account-data deletion does not delete copies you exported, support emails or records retained separately by client and authentication providers. Manage those copies and provider accounts separately, or contact us for help with information held by Tervalum Systems.
Your controls
You can export account data and delete account data through the authenticated service. Both controls have been remotely tested successfully. See Project Ledger Support for guidance. Keep independent copies of information you need before requesting deletion.
Security
Project Ledger uses HTTPS, OAuth authentication through Auth0 and per-user tenant isolation. Live two-user isolation testing has passed. These measures reduce risk but do not guarantee absolute security. Protect your account, review information before submitting it and safeguard exported copies.
Policy changes and contact
We may update this policy as the service changes; the date above identifies the current version. For privacy questions, support or help exercising your data controls, contact info@tervalum.com.