policies
Privacy policy
We do not store or log the content of your requests or the model’s responses. Here is what we do keep, and why.
- Title
- Privacy policy
- Effective
- 13 October 2026
- Sections
- 9
- Questions
- support@ultracode.in
The short version
- We do not store or log the content of your requests — your prompts, code, files, images and tool results — or the model’s responses.
- We keep only what it takes to run your account: who you are, your keys, what you bought, and how much you used.
- We do not sell your data. Our public pages load one advertising pixel so we can tell whether our own ads are worth running; it is never on the pages you work in, and your prompts and responses are never part of it.
What we keep
- Your account — your name and email address. Your password is kept only as a one-way hash that cannot be turned back into the password. If you sign in with Google, we keep the name, email address and account id Google shares with us.
- Your API keys — stored encrypted, so that your dashboard can show a key again when you ask for it.
- Your purchases — the plan, the amount, and Razorpay’s order and payment references. Card, UPI and bank details are entered with Razorpay and never reach us.
- Your usage — for each request: which key made it, the model tier, the number of tokens, and the time. Your limits, your dashboard and your receipts are built from this.
- Network information — the IP address a request comes from, used for rate limits and to protect the service from abuse.
What we do not keep
The content of your requests and the model’s responses is used only to answer your requests, and is not stored or logged by us — not in our database, not in our server logs, and not in files.
Who else handles your data
- Razorpay processes your payments.
- Google, only if you choose to sign in with Google.
- Our email provider, to deliver receipts and password-reset links.
- The infrastructure that runs the model tiers, which receives each request only to produce its answer.
- Authorities, when Indian law requires us to share information.
How long we keep it
- Your account, keys and usage records — for as long as your account exists.
- Purchase records — for as long as accounting and tax law requires.
- Server logs — only as long as they are needed to run and protect the service. They never contain the content of your requests.
Security
Passwords are hashed, keys are encrypted, and every connection to UltraCode uses HTTPS.
Cookies and browser storage
Your browser keeps your sign-in session and your light or dark theme in its local storage. Signing in with Google sets one short-lived cookie that protects the sign-in.
Our public pages — the home page, pricing, models, docs, status, and these policy pages — also load Meta’s advertising pixel, which sets its own cookie and tells Meta that a browser visited the page. We use it only to measure our own advertising. It is not loaded on your dashboard, on checkout, on the usage checker or on any signed-in page, so what you do inside UltraCode is not part of it, and neither are your prompts, your responses or your keys. Blocking it, with any ad blocker or your browser’s own setting, changes nothing about how UltraCode works for you.
Your choices
You can see and change your details on your dashboard. To delete your account, write to support@ultracode.in from the address on it; we delete the account and its keys, keeping only the purchase records the law requires us to keep.
UltraCode is not intended for anyone under 18.
Changes and contact
If this policy changes, the date at the top of the page changes with it. Questions about your data: support@ultracode.in.
next document
Refunds & cancellation
When money comes back.
Every document is set out here in full.