Privacy Policy

Last updated: September 23, 2026

This Policy explains what jevtypesafeai.com (the “Service”) collects, why, and who it is shared with. The Service is operated by CODEFASHION TECH LTD (“we”, “us”). It is an independent developer platform and is not affiliated with or endorsed by TypeSafe AI. By using the Service you agree to this Policy; if you do not agree, do not use the Service.

1. What we collect

• Account — when you sign in, our authentication provider (Clerk) gives us your email address and a user ID. We do not receive or store your password.
• Billing — payments are processed by Stripe. We store an order record (amount, credits granted, Stripe session ID, timestamp) and your credit balance. We never receive or store your card number; card details are handled entirely by Stripe.
• API keys — we store only a one-way hash of each key plus a short non-secret prefix, so we can authenticate calls without holding the key itself.
• Usage metadata — for each API call we store its shape: the endpoint, which question types were used, token counts, cost, latency and status. We do not store the request body — your state and questions are not written to our database.
• Free playground / anti-abuse — for unauthenticated free-tool calls we log the IP address and a coarse request category to detect and rate-limit abuse of the shared key.
• Analytics — we use Plausible, a privacy-friendly analytics tool that does not use cookies and does not collect personal or cross-site identifiers.

2. How your request content is handled

When you call the API, we forward your request (state and questions) to the upstream model provider (TypeSafe AI, and, as a failover, an AI gateway) to obtain the answer, then return it to you. That content is processed by the upstream provider under their own terms and privacy practices, which are outside our control. We pass it through unchanged and do not retain the request body ourselves. Do not send data through the Service that you are not authorized to share with an upstream processor.

3. How we use data

• To provide the Service: authenticate you, meter usage, and bill your prepaid balance.
• To keep the Service secure and prevent abuse (e.g. rate-limiting the free tier).
• To understand aggregate usage and improve the product.
• To contact you about your account, a purchase, or a refund.

We do not sell your personal data, and we do not use your request content to train models.

4. Who we share it with

We share data only with the processors needed to run the Service:

• Clerk — authentication.
• Stripe — payments.
• Supabase — our database and hosting of the data described above.
• TypeSafe AI (and an AI gateway as failover) — to process your API requests.
• Plausible — cookieless analytics.
• Our hosting/CDN and email routing providers (e.g. Railway, Cloudflare).

We may also disclose data if required by law, or to protect our rights, users, or the Service.

5. Cookies

We use only the cookies necessary to keep you signed in (set by our authentication provider). Our analytics are cookieless. We do not use advertising or cross-site tracking cookies.

6. Retention

We keep account, billing and usage-metadata records for as long as your account is active and as needed for legal, accounting and anti-fraud purposes. Aggregate, non-identifying analytics may be kept indefinitely. Because we do not store request bodies, there is nothing of that content for us to retain.

7. Your choices

• You can access or update your account details from your dashboard.
• You can revoke API keys at any time in your dashboard.
• You can request a copy or deletion of your personal data by emailing contact@jevtypesafeai.com. Some records (e.g. completed payment records) may be retained where required by law.

8. Security

We use industry-standard measures to protect data in transit and at rest, store API keys only as hashes, and never store card numbers. No method of transmission or storage is perfectly secure, so we cannot guarantee absolute security. Keep your API keys secret and server-side.

9. International users & children

The Service may be operated from, and data processed in, jurisdictions different from yours. The Service is intended for developers and is not directed to children under 16; we do not knowingly collect data from them.

10. Changes

We may update this Policy from time to time; material changes will be reflected by the “last updated” date above. Continued use after a change means you accept the updated Policy.

11. Contact

Questions or data requests: contact@jevtypesafeai.com. See also our Terms of Service and Refund Policy.