TrueMend is operated by 2435316 Ontario Inc. ("TrueMend," "we," "us," or "our"), a corporation incorporated in Ontario, Canada. This policy covers every place TrueMend touches your data: the truemend.ai website and account, billing, license validation, and the CLI's optional networked features. If you only ever run the CLI locally without a license or a truemend login session, none of this applies to you: no TrueMend component makes a network call in that mode, and Section 5 explains exactly how we verified that.
1. Scope
TrueMend is a locally-installed code analysis tool. Analysis, metric computation, and report generation happen entirely on your own infrastructure, whether or not you have an account. This policy applies to the parts of the product that do talk to a server:
- The truemend.ai website: creating an account, billing, team management, and license issuance.
- License validation from the CLI.
- The optional
truemend login/ definitions-feed flow. - The optional license seat fingerprint check.
- The optional
--ci --batchflag, which sends code to a third party (Anthropic) at your explicit request and using your own API key.
Nothing else in TrueMend talks to a server. Section 5 lists what we verified this against directly, not merely assert.
2. Information We Collect
2.1 Account information
When you create a truemend.ai account, we collect and store: email address, organization name, and a password. Your password is handled entirely by our authentication provider (Supabase Auth); we never see or store it in plain text, only a salted hash Supabase manages on our behalf.
2.2 Billing information
Payment is handled by Stripe through Stripe's own hosted checkout. We never receive or store your card number, expiry date, or CVC. What we store on our side is limited to: your Stripe customer ID, your subscription tier (Free, Pro, Max, or Teams), and your seat count.
2.3 Team information
If you invite a team member on the Teams tier, we store that person's email address, an optional display name, their role (owner, admin, or member), and whether their invitation is pending or accepted. We do not require or collect any information about a team member beyond what is needed to grant and manage their seat.
2.4 License records
Every signed license key we issue is recorded against your account: the license ID, organization name, tier, seat count, issue date, expiry date, and whether it has since been revoked. Revoked keys are marked revoked, not deleted, so that license verification and your own audit trail stay accurate.
2.5 License validation (CLI)
The license validation service transmits only: license key, timestamp of the request, software version, and operating system and architecture (for example linux/amd64). That is the complete list. No source code, file names, metrics, or analysis results are ever part of a validation request.
2.6 Definitions feed login (optional, truemend login)
If you run truemend login, your CLI receives and stores locally (~/.truemend/token.json, file permissions 0600) a Supabase session: an access token, a refresh token, and a snapshot of your account profile (email, organization name, subscription tier). Each truemend definitions --update afterward sends that access token to fetch current anti-pattern definitions; we log which account fetched which update, and when. No source code, file paths, or analysis results are ever part of this flow.
This credential is a real session for your account, not a narrow read-only token: anyone who obtains ~/.truemend/token.json can use it for anything your account can otherwise do on truemend.ai until the session is revoked. truemend logout deletes the local copy; if you believe the file itself was exposed, also change your password or contact us (Section 12) to revoke the session server-side, since deleting the local file alone does not do that.
2.7 License seat fingerprint counting (optional)
If you hold a paid license, the CLI computes a one-way hash of local hardware and OS identifiers on your machine and sends that hash, alongside your license key, so your account can show seat usage. The raw values being hashed (hostname, MAC address, username) are never transmitted, only the hash: this was verified directly by inspecting the fingerprinting function's real output, not merely asserted. On Pro and Max, this transmission is mandatory: it is how seat visibility works on those tiers. On Teams, it is opt-out.
We store, per license: the hashed fingerprint, the license ID it belongs to, and first-seen/last-seen timestamps. Nothing else: no hostname, no IP address beyond what any HTTP request incidentally carries, no additional account data. This count is informational only. It does not block validation, does not lock you out, and is not enforced against your declared seat count by any code path today.
2.8 The in-browser demo
The Playground demo on truemend.ai analyzes whatever code you paste directly in the request and returns findings. It keeps nothing: no logging of the source you submit, no persistence, no association with your account even if you are signed in. This was verified directly against the handler's implementation, not merely asserted.
2.9 Session storage
We do not use cookies for authentication, or at all: this website sets none. Signing in stores a bearer token in your browser's local storage, scoped to your device and cleared when you sign out. This is a deliberate architectural choice, not an oversight, and Section 10 discloses the tradeoff it carries.
2.10 What we explicitly do not collect
To be specific rather than reassuring: TrueMend does not collect your source code, file contents, file paths, directory structure, analysis results, scores, API keys, credentials, secrets, or repository metadata (commit hashes, branch names, authors), through any of the flows above. The one narrow exception, Section 4, is the optional --ci --batch flag, which you must explicitly enable and which is governed by our Responsible AI Policy.
3. How We Use Information
We use the information in Section 2 only to: authenticate you and maintain your session; process billing and enforce subscription tier and seat limits; validate and track license usage; manage team invitations and roles; operate the definitions feed and its per-tier freshness rules; respond to support requests; and meet legal and tax recordkeeping obligations. We do not use your data for advertising, do not build advertising or behavioral profiles, and do not run any analytics or tracking scripts on this site: there are none in the codebase, verified directly rather than assumed.
4. The Opt-In Batch API
If you explicitly enable the --ci --batch flag, the engine sends code fragments to Anthropic's API using your own ANTHROPIC_API_KEY, for LLM-assisted review. This is the only scenario, anywhere in TrueMend, where your source code leaves your own infrastructure by design. It is off by default and requires you to provide your own credential. Before transmission, common secret patterns (API keys, tokens, AWS credentials, JSON web tokens, password-like strings) are automatically redacted. Full detail on what this flow does and does not do, and the human-in-the-loop guarantees around every fix it proposes, is in our Responsible AI Policy.
5. What We Verified Directly
Every claim in this policy about what the codebase does or does not do was checked against the actual implementation, not assumed from a design document: the license validation and definitions-feed payloads (Sections 2.5-2.6), the fingerprint hash containing no raw hardware identifiers (Section 2.7), the Playground handler discarding submitted code (Section 2.8), the absence of any cookie usage anywhere in the site (Section 2.9), the absence of any analytics or tracking script in the codebase (Section 3), and the secrets-redaction function actually running on every field of a Batch API request before it is sent (Section 4).
6. Who We Share Information With
We do not sell your data, to anyone, under any circumstances. We share data only with the service providers necessary to run TrueMend, each bound by their own data protection obligations:
- Supabase: authentication and database hosting for your account, team, and license records.
- Stripe: payment processing. See Stripe's privacy policy for how they handle payment data directly.
- Vercel: website and API hosting.
- Anthropic: only if and when you explicitly enable the
--ci --batchflag (Section 4), and only for the code fragments that flag transmits.
We may also disclose information if required by law, or to protect the rights, property, or safety of TrueMend, our users, or the public.
7. Data Retention
License validation logs are retained for 90 days, then permanently deleted. Account, billing, team, and license-activation records are retained for as long as your account is active, plus a reasonable period afterward for legal, tax, and dispute-resolution purposes. Deletion requests are honored within 30 days of a verified request (Section 12).
8. Your Rights
Depending on where you live, you may have some or all of the following rights over your personal information, and can exercise any of them by contacting us (Section 12):
- Access: a copy of the personal information we hold about you.
- Correction: fix inaccurate or incomplete information.
- Deletion: request we delete your personal information, subject to Section 7's retention needs.
- Portability: receive your data in a portable format, where applicable.
- Objection and restriction: object to, or ask us to restrict, certain processing.
Canada (PIPEDA). As an Ontario corporation, we are subject to Canada's Personal Information Protection and Electronic Documents Act. You may access and request correction of your personal information, and challenge our compliance with this policy, by contacting us. If you are not satisfied with our response, you may file a complaint with the Office of the Privacy Commissioner of Canada.
EU/UK (GDPR). If you are in the European Economic Area or the UK, the legal bases we rely on are: performance of a contract (running your account and license), legitimate interest (security, fraud prevention, and product operation), and consent where we ask for it. You have the rights listed above in full, plus the right to lodge a complaint with your local supervisory authority.
California (CCPA/CPRA). California residents have the right to know what personal information we collect and why, to delete it, to correct it, and to non-discrimination for exercising these rights. We do not sell or share personal information for cross-context behavioral advertising, so there is no opt-out to exercise: there is nothing being sold.
9. International Data Transfers
Our infrastructure providers (Supabase, Stripe, Vercel) may process data outside of Canada, including in the United States. Where required, we rely on the safeguards those providers maintain for cross-border transfer (such as standard contractual clauses).
10. Data Security and Session Storage
We rely on our infrastructure providers' encryption in transit (TLS) and at rest, and restrict internal access to authorized personnel only. As noted in Section 2.9, authentication uses a bearer token in browser local storage rather than a cookie. We disclose the tradeoff plainly: local storage is readable by any script running on the page, so a successful cross-site-scripting attack could expose a session token the same way it could expose cookie-based sessions lacking HttpOnly protection. Our full security practices, and how to report a vulnerability, are in our Security Policy.
11. Children's Privacy
TrueMend is not directed at, and we do not knowingly collect personal information from, anyone under 16. If you believe a child has provided us personal information, contact us and we will delete it.
12. Offline and Air-Gap Mode
TrueMend supports fully offline operation for environments that prohibit external network access. License validation can run entirely offline using signed license files issued at purchase or renewal, cryptographically signed and validated locally against a bundled public key. In offline mode, zero license-related data is transmitted. If you have also never run truemend login, no TrueMend component makes any network call, full stop. If you have run truemend login and later use truemend definitions --update, that specific opt-in command still transmits the data Section 2.6 describes, independent of your license mode.
13. Changes to This Policy
We will notify active account holders of material changes by email at least 30 days before they take effect. Non-material clarifications, such as rewording without changing meaning, may be made without notice. The current version is always at truemend.ai/privacy.
14. Contact
2435316 Ontario Inc., operating as TrueMend, Ontario, Canada.
For questions, concerns, or to exercise any right listed in Section 8: hello@truemend.ai