Privacy Policy

1. Who we are and what this covers

Trimml ("we") provides a prompt-compression API and the console at this site. This policy covers the data we handle when you use either. Contact for anything privacy-related: support@trimml.com.

2. Prompt data — the part that matters most

The content you send to POST /v1/compress is the most sensitive thing we touch, so here is exactly what happens to it:

• Processed transiently. Your prompt is held in memory only long enough to run compression and return the result in the API response.
• Never stored. We do not write prompt text (or the compressed output) to disk, databases, or logs.
• Never used for training. Our models are trained on our own corpora, not on customer traffic.
• What we do keep: per-request metering — the original token count, the compressed token count, processing latency, a timestamp, and which API key made the request. These numbers are what your dashboard and invoices are computed from; they contain no prompt content.

3. Data we collect

• Account information: name, email address, optional company name, and your password (held by our authentication provider in hashed form — we never see or store the plaintext).
• API keys: we store only a SHA-256 hash of each key and its first 8 characters for display. The full secret is shown once at creation and cannot be recovered by us.
• Usage metering: the per-request token counts and latency described above, aggregated per key and per day.
• Billing records: monthly invoices derived from metering (token totals, savings value, fee). When card payments are enabled they are processed by Stripe — we never hold card numbers.
• Security log: key lifecycle events (issue, rename, revoke) and account actions, with the requesting IP address, kept for abuse prevention and auditability.
• Support correspondence: whatever you send to support@trimml.com.

We do not run advertising or sell personal data, and we collect no analytics about your browsing today. If we enable analytics, it will be a cookieless, aggregate-only service (no cross-site tracking, no personal identifiers) and this policy will say so.

4. Cookies

The app sets exactly two first-party cookies, both functional. There are no analytics, advertising, or third-party cookies, which is why you don't see a consent banner — both cookies below are strictly necessary for, or a direct consequence of, an action you take. If we ever add non-essential cookies, we will ask first.

5. Subprocessors

We share data only with the providers that run the service:

• Google Cloud — authentication (Identity Platform) and database hosting / Cloud SQL (account profiles, key hashes, metering, invoices, audit log).
• Stripe — payment processing, once card billing is enabled (billing contact and payment details; Stripe is the controller of card data).

We may also disclose data where the law requires it. We will keep this list current as the infrastructure changes.

6. Retention

• Prompt text: not retained at all (see section 2).
• Account data and key records: kept while your account exists.
• Metering: kept while your account exists, because your bill must remain reproducible from it; usage history is removed when you delete your account (the amounts already billed are frozen into the invoices below).
• Invoices: issued invoices are financial records, so we retain them even after you delete your account — detached from your profile and reduced to the minimal bill-to (legal name and email) needed for a valid record — to meet bookkeeping and tax record-keeping obligations. They are purged after the applicable legal retention window. [Counsel/ops to set the exact retention window (commonly ~7 years for tax records) before GA.]
• Security log: the audit log of sign-ins, password/account changes, billing changes, and key lifecycle events (with the requesting IP) is retained for 12 months and then automatically deleted by a scheduled job, which also bounds how long IP addresses are kept. It is retained for abuse prevention and account security, including after account deletion.

7. Your rights and controls

• Access and correction: your profile is editable in the console's settings page; for a copy of everything we hold about you, email us.
• Deletion: you can delete your account yourself in the console (Settings → Delete account), which removes your profile, API keys, and usage history. Issued invoices are retained as anonymized financial records for the legal retention window (see the retention notes above), not deleted with the account.
• Complaints: depending on where you live (e.g. the EU/UK under GDPR, or California under CCPA) you may have additional statutory rights — to object, restrict, or port data, and to complain to a supervisory authority. Email us and we will honor them. [Counsel to finalize jurisdictional specifics and legal bases.]

8. Security

Traffic is encrypted in transit (TLS). API keys are stored only as one-way hashes. Console sessions use HttpOnly, host-locked cookies. Passwords are hashed by our authentication provider. No measure is perfect — report suspected vulnerabilities to support@trimml.com.

9. Changes

We will post updates here and, for material changes, notify account holders by email or in the console. The "Last updated" date above reflects the current version.

10. Contact

support@trimml.com — or see the Terms of Service for the agreement that governs use of the service.