Privacy Policy
Most privacy policies are written to protect the company. This one is written to be read. Every formal section has a plain-language summary beside it, and if the two ever seem to disagree, tell us, because they shouldn't.
01What we collect
The transactions you add, and the minimum needed to run your account: an email and a password. No tracking, no ad profiles.
We collect the financial transactions you choose to add to TrackFin, whether through an uploaded CSV or OFX file, a scanned receipt, or manual entry. We also collect the account credentials you provide: an email address and a password, which is stored only as a salted hash.
We do not use third-party advertising trackers, and we do not build an advertising profile of you. We collect basic, aggregate operational metrics (such as error rates and response times) that never contain your transaction contents.
What we never collect
- Bank credentials or full account numbers
- Biometric data
- Your location
- Advertising identifiers or tracking pixels
- Any data sold to advertisers, data brokers, or ad networks
02How the AI uses your data
Analysis runs through an inference provider under a no-retention arrangement, then the data is dropped. Your data never trains a model and is never sold.
When you request an insight, budget analysis, or anomaly check, the relevant transactions are sent to our AI service over an encrypted connection and held in memory for the duration of that single request. Inference is performed by a third-party provider (currently Groq) under a no-retention, no-training arrangement: they receive the transactions only for the duration of that request and do not keep them. We will update this policy if that provider changes.
Your transactions are never used to train or fine-tune any model. When the request completes, the in-memory data is released. This behavior is verifiable: we share the AI service code on request, and you can read the architecture or run it yourself.
03What we store
Your ledger is stored, encrypted, so you can see it across sessions. The AI service stores nothing: no transaction logs, ever.
To show you your data across sessions, your transaction ledger is stored in an encrypted database associated with your account. This is data you can export or delete at any time. Your password is stored only as a salted hash and is never recoverable in plain text.
The AI processing service stores nothing. It writes no transaction data to disk and emits no log lines containing your transaction contents. The place where other apps keep an analysis history does not exist in our architecture.
05Your rights
Export everything yourself, anytime. Ask us to delete your account and we erase it permanently, not "flagged as deleted."
You can export the entirety of your data at any time from the Account page, in a portable format, without a support request or a waiting period. To delete your account, email us and we will permanently erase it and every associated record; deletion is a hard delete, not a soft flag.
Depending on where you live, you may have additional statutory rights (such as under GDPR or CCPA) to access, correct, or restrict processing of your data. We honor these rights for all users regardless of location, because they describe how the product already works.
06Security
Encrypted in transit (TLS 1.3) and at rest. The service code is available on request, so you can verify our claims rather than trust them.
Data in transit is protected with TLS. Data at rest is encrypted, and passwords are stored only as bcrypt hashes, never recoverable in plain text. Authentication uses an httpOnly session cookie, so your session token is not readable by JavaScript. Access to production systems is tightly restricted.
Because we share the AI service code on request, our most important security claim, that your transactions are never stored or logged during analysis, is independently auditable.
08Changes to this policy
If we change something material, we'll tell you before it takes effect, not quietly in a diff.
If we make a material change to this policy, we will notify account holders by email before the change takes effect, and we will keep prior versions available for comparison. Continued use after a change takes effect constitutes acceptance of the updated policy.
09Contact
Questions about this policy or your data? Reach us at privacy@trackfin.app. We read every message, and privacy questions go to a human, not a queue.