Privacy policy

Last updated: October 13, 2026

This policy explains how Jev AI (“we”, “us”) handles personal data when you use Jev AI.

Information we collect

Account data. If you sign in with Google, Google provides your account identifier, name, email address and profile image. If you sign in with an emailed link, we store your email address and a record of the link we sent. We store these so you can access your account and history.

Product data. We store prompts, lyrics and other submitted text, generation settings, model choices, status, credit usage, and result links. Do not submit sensitive personal information in prompts, lyrics, or reference media.

Temporary browser drafts and request recovery. When you start sign-in with an editing or generation form open, its current text, settings, and already-uploaded media references can be kept in this browser for up to 30 minutes so they can be restored after authentication or when you return without signing in. Sign-in drafts are removed when restored, and expired drafts are removed by the open page or on a later visit. Raw files selected from your device are not copied into this sign-in storage.

Billing data. Dodo Payments, Waffo Pancake or NOWPayments (cryptocurrency) processes payment details, depending on the method you choose at checkout. We receive customer, subscription, invoice, payment-status, country, tax and transaction identifiers, but not full card numbers or wallet keys. If you are in the European Economic Area, United Kingdom and Switzerland, we record your consent to immediate supply (time, country and wording version) with the purchase.

Technical and analytics data. Essential logs may include IP address, browser details, timestamps, security events, and errors. Google Analytics 4 runs cookie-less until you allow analytics cookies. Microsoft Clarity may collect page use, interaction, device and session data for privacy-filtered session replay and heatmaps (form inputs are masked): outside the European Economic Area, the United Kingdom and Switzerland it runs by default and “Essential only” on the cookie policy page turns it off; inside those regions it runs only after you choose “Allow analytics”.

Checkout diagnostics. We record limited first-party checkout stages even when optional analytics is declined, using a new random reference for each attempt. These records may include the payment provider, plan, quantity, elapsed time, status code, country and a fixed page category. They contain no account or visitor identifier, email, IP address, page query, prompt, payment details or raw error text. The reference is not saved in browser storage, and these events are not sent to analytics or advertising providers.

If you choose Waffo checkout, we share your account email, an internal purchase reference, selected plan, and purchase amount with Waffo Pancake to provide checkout, tax calculation, receipts, subscription management, fraud prevention, and refunds. Waffo handles payment information on its hosted checkout; we do not receive full card numbers. We retain transaction identifiers and payment status for accounting, support, and applicable legal obligations.

For Dodo Payments checkout, we share your email, selected purchase, amount and an internal purchase reference with Dodo Payments for payment processing, tax, receipts, subscription management, fraud prevention and refunds. Card details are collected on its hosted checkout; we do not receive full card numbers. We retain payment identifiers and status for delivery, support, accounting and legal obligations.

If you choose crypto checkout through NOWPayments, we share an internal purchase reference, selected plan, purchase amount, and currency with the crypto payment provider to create the payment invoice. We receive invoice and transaction identifiers, payment amounts, and payment status to confirm the purchase and maintain your credit balance. We retain these billing records for accounting, support, and applicable legal obligations.

How and why we use data

We use data to provide and secure accounts, process generation and payments, maintain credit balances, prevent abuse, troubleshoot failures, support customers, measure product performance, and meet legal or tax obligations. Where applicable, our legal bases include performing our contract, legitimate interests in security and service improvement, consent for optional analytics, and compliance with law.

Processing partners and international transfers

We share only what is needed with Google for authentication and optional analytics, Dodo Payments, Waffo Pancake or NOWPayments (cryptocurrency) for billing, Microsoft for optional Clarity analytics, and the hosting, database, and generation-processing partners needed to operate the service. These partners may process data in other countries under their terms and legally recognized transfer safeguards.

For Jev AI, the text and questions you submit are processed by TypeSafe, which provides the Jev model, and by a fallback inference provider when one is needed. When you use Live Web Context, your question and search query are sent to Exa to run the web search. Do not include personal or confidential information in web search questions.

Retention

Account and product records are kept while your account is active. Generation result links can expire under storage rules. Security logs are normally kept only as long as operationally needed. Billing and tax records may be retained for the period required by law. After a valid deletion request, we delete or anonymize data that is not legally required.

Cookies and controls

Essential cookies maintain your session and choices. Optional GA4 cookies and, in the EEA, UK and Switzerland, Clarity measurement are off until you choose “Allow analytics” in the Cookies notice or cookie policy; elsewhere Clarity session analytics runs by default on approved public pages and “Essential only” on the cookie policy page turns it off. That choice enables GA4 on approved public pages and limited product events, including new registrations and confirmed purchases, and Google advertising storage for conversion attribution. GA4 events use a sign-in method or an opaque transaction reference, actual paid amount and currency; they exclude email, account IDs, API keys, prompts and results. Private account, admin, batch and judge pages do not load these analytics. Clarity remains restricted to approved clean public URLs.

Google Ads conversion measurement. When you complete a first purchase, our server can send Google Ads the Google click identifier from the ad visit that brought you to the site (if any), a SHA-256 hash of your account email address (Google enhanced conversions), the purchase time, amount, currency and an order reference. Google uses this to measure which ads lead to purchases; we do not send prompts, results or payment details, and ad personalization is disabled. In the European Economic Area, the United Kingdom and Switzerland we send this only after you choose “Allow analytics”. Elsewhere it is on by default and you can opt out at any time by choosing “Essential only”, which also removes purchases that have not yet been sent. Renewals are not sent. See how Google uses data from sites that use its services.

Where Clarity is enabled, with your analytics consent we associate signed-in visits on approved public pages with a site-prefixed internal account ID to understand visits across devices. Clarity hashes this identifier before transmission. We do not supply your email or name through this feature. Signing out or switching accounts ends the current recording and clears Clarity cookies. Private pages remain excluded. You can withdraw analytics consent in Cookie preferences.

Your rights

Depending on where you live, you may request access, correction, deletion, portability, restriction, or objection, and may withdraw analytics consent. You can submit deletion from the account page or email [email protected]. We may need to verify your identity. You may also complain to your local data-protection authority.

Children

The service is not directed to children under 13, and users must be old enough to enter a binding contract in their jurisdiction.

Security and changes

We use access controls, secured session cookies, server-side credentials, signed payment-provider webhooks, and encrypted transport. No system is completely secure. Material policy changes will be posted here with a new effective date.

Contact

Data controller: Jev AI. Privacy questions: [email protected].

Abuse prevention and account security

To limit free offers and keep accounts secure, an essential first-party browser cookie lasts up to one year, and our server stores a hashed random browser identifier so a welcome offer is given once per browser per site.

When you sign up, sign in, check in or claim a free-credit offer, we also record a keyed hash of the network you connect from (your IPv4 address, or the /64 block of an IPv6 address), together with your country and browser type. We never store the raw address. We use these records to give welcome credits once per network across our sites, give the daily check-in reward once per network per day, detect several accounts operating from one network, and investigate abuse, fraud and chargebacks; authorized administrators can see which accounts used the same network. Our legal basis is our legitimate interest in preventing abuse and fraud. The records are kept while your account exists and as long as needed to resolve abuse or payment disputes. Contact support if you believe an offer was withheld in error.