Project Ledger helps you search and maintain non-sensitive project facts, decisions, handoffs and verified failure lessons across work sessions. You can supersede outdated facts and inspect audit history.
What not to store
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. Restricted credential and sensitive-data storage is rejected, but you remain responsible for reviewing what you submit.
Connect or reconnect
- Open your client platform's app or connector settings and use its supported MCP connection flow for
https://ledger.tervalum.com/mcp. - Complete the Auth0 sign-in and authorization flow using the account whose Project Ledger data you want to access.
- If access expires or authorization fails, use the client's reconnect or reauthorize control. If necessary, disconnect the connection and add it again, then sign in to the same account.
- If records appear missing, check that you signed in to the intended account and searched the intended project. Different users' records are isolated.
Client menus and connection availability vary. If a connection still fails, email info@tervalum.com with the client name, approximate time and a redacted error message. Never send credentials or access tokens.
Supersede outdated information
Search for the existing fact, check that it is the record you intend to correct, then ask Project Ledger to supersede it with the updated non-sensitive information. Review the returned result and audit history. Superseding information records a correction; it is not the same as deleting account data.
Export account data
While connected and signed in, ask Project Ledger to export your account data. Review the tool result and save the export in storage you control. If export fails, contact support with a redacted description of the failure.
Delete account data
While connected and signed in, explicitly request deletion of your Project Ledger account data and follow any confirmation presented. Export first if you need a copy. Check the returned result before treating deletion as complete. Account-data deletion removes deleted data from the primary Project Ledger datastore; disconnecting a client alone does not delete that data.
Copies already exported or held in your client platform must be managed separately. If you cannot access the account or need help with deletion, contact info@tervalum.com.
Privacy and security reporting
Send privacy questions or reports of a suspected security issue to info@tervalum.com. Include a concise description and redacted reproduction steps where possible. Do not include sensitive project content, credentials or another user's data.