Privacy Policy

Last updated: August 4, 2026

1. Overview

This policy explains what information Tempr LLC ("Tempr," "we," "us") collects through the Tempr Visual Studio extension and customer portal, why we collect it, and the choices you have. Tempr is a bring-your-own-key (BYOK) product: your AI provider requests are relayed using your own API key, not routed through a shared pool we control.

2. Information we collect

We collect the following categories of information:

• Account & license data — your email address, license key, subscription tier, and activation history, used to authenticate you and enforce plan entitlements.
• Provider API keys — the API key(s) you add for AI providers you choose to use. Keys are stored encrypted and used only to relay your own requests to the provider you configured them for.
• Billing data — subscription and payment details are handled by Stripe, our payment processor. We don't store your full payment card details ourselves.
• Usage & entitlement data — token counts, estimated cost, and request metadata (for example which model or feature was used, and how many agent-loop steps a request took), used for usage reporting, tier enforcement, and optional spend-alert budgets.
• Chat sessions and configuration, if you enable cloud sync — on plans that include it, chat session content, tool preferences, and custom persona configuration are stored so they can sync across your devices. If you don't enable sync, this data stays local to your machine.
• Code index data, if you use semantic search — using the semantic code search feature creates embeddings (numeric representations) of chunks of your codebase to power search; these are stored to make the feature work and are not used to train shared models.
• Feature requests and support communications — anything you submit through the in-product feature request form or send to our support address.

We don't proxy your AI provider requests through a shared pool, and we don't store your prompts or code beyond what's needed to relay the request and enforce your license tier and any features you've opted into (like cloud sync or semantic search).

3. How we use information

• To provide, maintain, and secure the Service, including authenticating your license and relaying your AI provider requests.
• To process payments and manage subscriptions through Stripe.
• To enforce plan limits (for example agent-loop step limits and model access windows) and provide usage reporting and budget alerts.
• To respond to support requests and feature requests.
• To send license-related and billing-related emails (for example your license key after checkout, or a monthly budget alert).
• To improve the Service.

4. How information is shared

• AI providers you configure — when you use a model, your request is relayed to the provider you added a key for (for example OpenAI, Anthropic, or OpenRouter), using your own key. That provider's own privacy policy governs how they handle the request.
• Stripe — for billing, subscription management, and payment processing.
• Service providers — infrastructure and email-delivery vendors that help us operate the Service, bound by confidentiality obligations.
• Legal requirements — if required to comply with law, legal process, or to protect the rights, property, or safety of Tempr or others.

We don't sell your personal information.

5. Data security

Provider API keys and other sensitive data are stored encrypted at rest, and traffic to and from the Service is encrypted in transit. No method of storage or transmission is 100% secure, so we can't guarantee absolute security.

6. Data retention

We keep account, license, and billing data for as long as your account is active and as needed to comply with legal and tax obligations. You can ask us to delete your account data at any time, subject to what we're legally required to retain (for example billing records).

7. Your choices and rights

• You can remove a provider API key from your account at any time, which stops future relayed requests from using it.
• You can disable cloud sync and semantic search if you don't want that data stored.
• You can request access to, correction of, or deletion of your personal data by contacting us.
• If you're in the EEA, UK, or Switzerland, you have rights under the GDPR to access, correct, delete, restrict, or port your data, to object to processing, and to lodge a complaint with your local data protection authority.
• If you're a California resident, you have rights under the CCPA/CPRA to know what personal information we collect, request its deletion or correction, opt out of the sale or sharing of personal information (we don't sell or share personal information), and not be discriminated against for exercising these rights.

8. Children's privacy

The Service is not directed to children, and we don't knowingly collect personal information from anyone under 16.

9. Changes to this policy

We may update this policy from time to time. If we make material changes, we'll update the "Last updated" date above and, where appropriate, notify you.

10. Contact

Questions about this policy, or want to exercise a data right? Contact us at contact@temprhq.io.