Account & billing
Privacy & data
What data Contral collects and never collects, how long it's kept, and how to use your privacy rights.
This page summarizes how Contral handles your data. The Privacy Policy is the binding document; if anything here differs from it, the Privacy Policy wins.
What data Contral collects#
Contral collects three kinds of data:
- Account data. Your email address, display name and sign-in information (Google, GitHub, or email and password), managed through Firebase Authentication.
- Usage data. Counts of feature use, such as build messages, explanations and deep dives. Contral needs these counts to enforce your plan's limits, so they're collected for every account.
- Telemetry (only with your consent). Anonymized analytics: which model was used for a request, how long it took and whether it succeeded, session events (create, delete, switch), mode changes (Fast, Plan, Deep), and error types. Telemetry never includes your code or prompts. If you decline telemetry, Contral records only aggregate feature counts with no metadata, device identifiers or session information.
Contral also keeps a one-way hashed device ID and IP information to detect multi-account abuse of the free tier.
What Contral never collects#
According to the Privacy Policy, Contral never collects or stores:
- Your source code or project files
- File contents, file names or directory structures
- Clipboard contents or screenshots
- Keystrokes or input patterns
Contral is local-first: your code stays on your machine, and Contral doesn't store your source code on its servers.
How your code and prompts reach AI models#
To answer a request, Contral sends your prompt and the relevant code context to an AI model provider. With Contral's hosted models, those providers are NVIDIA NIM, OpenAI and OpenRouter, accessed through their APIs; the Privacy Policy states your data isn't used for training. The policy also says Contral doesn't keep your prompts or AI conversations.
When you bring your own key, requests go to the provider you chose, under that provider's terms.
How long Contral keeps data#
| Data | Kept for |
|---|---|
| Telemetry events | 90 days, then deleted automatically |
| Usage snapshots | 2 years |
| Account data | Until you delete your account |
| Payment records | As long as the law requires (typically 7 years) |
Data is stored in Google Cloud Firestore (Firebase), encrypted at rest.
Your privacy rights and how to use them#
You can:
- Access or export your data. Email contact@contral.ai to request a copy (exported as JSON).
- Delete your data. Delete your whole account from Dashboard → Account → Danger Zone. See Delete your account.
- Withdraw telemetry consent. Click Decline on the consent banner in the IDE, or change the telemetry setting in the IDE settings.
Contral responds to privacy requests within 30 days. Users in the EU (GDPR), California (CCPA) and India (DPDP Act) have the additional rights listed in the Privacy Policy. Contral doesn't sell your personal information.
Service providers Contral uses#
- Firebase (Google): sign-in and database
- AI model providers (NVIDIA NIM, OpenAI, OpenRouter): generating responses
- Payment processor: payments for subscriptions bought on contral.ai (Contral doesn't store your card or bank details)
- Website hosting and analytics
AppSumo purchases are processed by AppSumo under AppSumo's own privacy policy.
Privacy questions#
Email contact@contral.ai with any privacy question or request. Read the full Privacy Policy and Terms of Service.
Still stuck? Ask the support assistant in the corner of this page, or open a support ticket.