Security
What we do with your data, in plain terms.
You are handing us the full picture of a family’s wealth. These are the questions we’d ask in your position, answered as specifically as we can. If something you need isn’t here, ask us directly.
Your data
- How is our data encrypted?
- Data is encrypted in transit and at rest. Each portfolio is encrypted under its own key in AWS Key Management Service, so one customer's data is never protected by another customer's key.
- Can Trac employees see our data?
- Trac staff can access customer data when supporting an account, and we don't pretend otherwise. What we do is record it, by person and by portfolio. How that record is kept is under Access and audit, below.
- Where is our data stored?
- On Amazon Web Services, in the United States. That covers the database, your uploaded documents, backups and logs. The production database is continuously backed up with point-in-time recovery.
Access and audit
- Do you store our bank or brokerage logins?
- No. Trac links bank and brokerage accounts through Plaid, which handles the institution's login on your behalf. Trac never sees or stores your banking credentials.
- Who can get into our portfolio?
- Sign-up is by invitation, so an account exists only because someone at your office was added to it. Access inside a portfolio is by role, and the roles are enforced on the server for every request, not just hidden in the interface.
- Is there a record of who changed what?
- Yes. Changes inside a portfolio are written to an audit trail: what was created, changed or deleted, the values before and after, when, and who did it, whether that was a person, a rule or the system. You can open it for a holding, for a rule, or for one user to see everything they did.
- Is Trac's own access to our data logged?
- Yes. Every portfolio is encrypted under its own key, so when a person at Trac unlocks a portfolio's data, AWS records who it was, which portfolio and when. Trac collects those records every hour into an access log covering the last 90 days, which its team can read by person and by portfolio. If you ask who has opened your portfolio, that log is what we answer from.
- How do we know nothing was changed after the fact?
- A reconciled period is locked: its activities become read-only. Reports keep a version history, and a published edition doesn't change afterward.
Traci and AI
- Where does Traci send our data?
- Traci's reasoning runs on Amazon Bedrock inside Trac's own AWS account. Bedrock does not store the content of your requests or its responses. To meet demand, AWS may process an individual request in another of its commercial regions; nothing is retained there.
- What about voice?
- If you dictate to Traci or have a reply read aloud, that audio or text is processed by OpenAI to transcribe or voice it. Typing instead keeps the conversation on Bedrock.
- Can Traci change our books on its own?
- Changes to your ledger, such as activities, prices and deletions, are always proposed as a review card and applied only when you approve. Traci works through the same screens and permissions you do; it has no separate path into your books.
The documents behind this page
The contractual versions of everything above, including the vendors that process data on our behalf.
Report a vulnerability
Found something? Write to security@trac.bot.