Privacy Policy
What we collect, why, who it reaches, and what you can ask us to do with it.
Last updated: 31 October 2026
This policy describes the data the platform actually handles. It is written to be checkable against the product: where a data category is stored, the policy says what is stored and what is not.
1. Who is responsible for your data
The data controller is MaxonForge, Surat, Gujarat, India. For privacy requests, contact support@maxonforge.com. See Contact & Support for response expectations.
2. What we collect
Account data. Your email address, a securely hashed password (we never store the password itself), your account status, and — where email verification is in use — a timestamp showing when the address was verified. Verification codes are stored only as hashes and are single-use.
API keys. A key label, a prefix used to identify the key, and a hash of the key. The full key is shown to you once at creation and is not recoverable afterwards.
Usage metadata. For each request we store the model, token counts (input, output, cached), the amount charged, HTTP status, latency, whether the response was streamed, a request id, and which of your keys made the request. We do not store the text of your prompts or the model’s responses in your usage history.
Billing data. Top-ups, plan purchases, charges and corrections, recorded in an append-only ledger with payment references. We do not store your full card number or CVV; card data is handled by the payment provider.
Technical and security data. IP address and request metadata used for rate limiting, abuse prevention and security logging. Logs are written through a redaction layer that strips keys, tokens and request bodies.
Analytics and marketing data — collected automatically on your visits (see §6): page views and interaction events, an anonymous identifier, referral/attribution parameters, device and browser information, and approximate location derived from your IP by the analytics provider. This measurement is on by default; you can opt out at any time from the Cookie Policy page.
3. What happens to the content you send to models
When you call a model, your prompt and any content you include are transmitted to the third-party AI provider that serves that request. This is inherent to how the Service works: the model runs on the provider’s infrastructure, not ours.
- That provider processes your content under its own terms and privacy policy, which may include retention for abuse monitoring or service operation. Review the provider’s policy for the model you use.
- Our internal routing traces are sanitised: they record routing decisions, never prompt text, API keys or provider credentials.
- Do not send personal data, confidential business information, or special-category data to a model unless you are permitted to disclose it to that third party.
4. Why we use it (purposes and lawful bases)
- To provide the Service — authenticate you, route requests, meter usage, bill correctly. Lawful basis: performance of our contract with you.
- To secure the Service — rate limiting, fraud and abuse prevention, detecting credential misuse. Lawful basis: our legitimate interests and, where applicable, legal obligation.
- To meet legal and accounting duties — retaining billing and tax records. Lawful basis: legal obligation.
- To improve the product and measure marketing — analytics, attribution and advertising measurement. Lawful basis: our legitimate interests in understanding usage and measuring our advertising. You can opt out at any time (see §6).
- To contact you about your account — verification codes, security notices, material service or policy changes. Lawful basis: contract and legal obligation. These are not marketing messages.
5. Who we share data with
We share data only as needed to run the Service:
- AI model providers — the request content needed to answer your call (see §3).
- Payment providers — to process a top-up or plan purchase and to receive settlement confirmations.
- Email delivery providers — to send verification codes and transactional account email.
- Hosting, database and infrastructure providers — to run the website, API and ledger.
- Analytics and advertising measurement providers — Google (Tag Manager, Analytics 4 and Google Ads measurement), Meta, and OpenAI Ads, which load automatically as described in §6.
- Professional advisers, auditors, or authorities — where legally required or necessary to establish or defend legal claims.
We do not sell your personal data. We do not share your prompts with other customers. Administrative access to customer data is permission-gated and audited.
7. How long we keep data
- Account data — while your account is open, and for a short period afterwards so the account can be recovered if closure was accidental.
- Usage metadata — retained for a limited window so you can review your history and so billing can be reconciled.
- Billing and ledger records — retained for as long as accounting and tax law requires. These records are append-only and cannot be edited, which is why they may outlast your account.
- Verification codes — short-lived, and unusable once expired or consumed.
- Security logs — retained for a limited period for incident investigation.
8. Your rights
Depending on where you live, you may have the right to:
- access the personal data we hold about you;
- correct inaccurate data;
- delete your data (see Account & Data Deletion);
- restrict or object to certain processing;
- receive a portable copy of the data you provided;
- withdraw consent for analytics or marketing at any time; and
- complain to your local data protection authority.
To exercise a right, contact support@maxonforge.com. We may need to verify your identity first. Some rights are limited where we must keep records for legal or accounting reasons, and we will explain any such limit in our response.
9. International transfers
Our own processing takes place in India, and the providers we use may process data in countries other than yours. Where required, transfers are covered by an appropriate safeguard such as standard contractual clauses. Because your prompts go directly to the provider serving the request, that provider’s processing location is governed by its own policy.
10. How we protect data
- Passwords and verification codes are stored as hashes, never in plain text.
- API keys are shown once and stored as hashes.
- Administrative access is role-gated by permission and recorded in an audit trail.
- Application logs pass through a redaction layer that removes keys, tokens and request bodies.
- Transport to the Service and to providers is encrypted in transit.
No system is perfectly secure. If we become aware of a breach affecting your personal data, we will notify you and the relevant authority where the law requires it.
11. Children
The Service is not intended for anyone under 18 and we do not knowingly collect data from children. If you believe a child has created an account, contact us and we will close it.
12. Changes to this policy
We may update this policy. The “last updated” date above identifies the current version. Material changes will be announced on the site or by email before they take effect.