The policy states an effective date of September 10th, 2026
The privacy policy gives September 10th, 2026 as its effective date.
Supporting quotations
Effective: September 10th, 2026
Not stated here
The supplied text does not say how future changes to the policy will be announced or whether earlier versions remain available.
Legal Rights & Agreement Rules · Context
Anlatan Inc. is the controller of the personal data described
Anlatan Inc., of Boston, Massachusetts, United States, is named as the controller of the personal data this policy describes. Questions can be sent to support@novelai.net.
Supporting quotations
NovelAI Privacy Policy
Anlatan Inc., 501 Boylston Street Floor 10, Boston, MA 02116, United States, is the controller of the personal data described in this policy
You can reach us at
Qualifications & exceptions
Controller status is stated for the personal data described in this policy only.
Not stated here
The policy is titled for NovelAI but does not itself explain how the NovelAI name or the novelai.net site relates to Anlatan Inc.
Security & Safeguards · Company practice
Stories are end-to-end encrypted and NovelAI cannot read them
Your stories, including their lorebooks, and your scripts and prompt chunks are encrypted in your browser before they are saved. The key is derived from your password and never leaves your device. NovelAI stores only the encrypted data and says it cannot read it.
Supporting quotations
your stories are end-to-end encrypted and we cannot read them
Your stories, including their lorebooks, and your scripts and prompt chunks are encrypted in your browser before they are saved, with a key derived from your password that never leaves your device
We store only the encrypted data and cannot read it.
Qualifications & exceptions
Applies to what is saved: stories, lorebooks, scripts and prompt chunks.
The part of a story sent for generation is processed in readable form, as covered separately.
Text sent for generation is processed in readable form and not kept
The part of a story you send for generation is processed in readable form to produce the output. NovelAI says it is not kept.
Supporting quotations
The part of a story you send for generation is processed in readable form to produce the output and is not kept, as described next.
other than as traffic passing through our hosting and network providers on the way to our servers
Qualifications & exceptions
Not kept, with the encrypted image-cache exception covered separately.
The policy says none of its listed providers receives prompts or generated content, other than as traffic passing through hosting and network providers on the way to NovelAI's servers.
Prompts are not stored, except an encrypted image cache for up to one hour
NovelAI says it does not store your prompts. What you send for generation is processed only to produce your output. The one exception is an encrypted cache of uploaded images, held for up to one hour.
Supporting quotations
we do not store the prompts you send for generation
We do not store your prompts. What you send for generation is processed only to produce your output and is not kept. The only exception is an encrypted cache of uploaded images, held for up to one hour.
Uploaded images are held in an encrypted cache for up to one hour.
Qualifications & exceptions
The only stated exception is the encrypted cache of uploaded images, up to one hour.
Publishing an image on Explore publishes its embedded generation settings, including the prompt, as covered separately.
Publishing an image on Explore also publishes its prompt
If you publish an image on Explore, the generation settings embedded in the image, including its prompt, are published with it. The policy says anything published on Explore goes to the public.
Supporting quotations
If you publish an image on Explore, the generation settings embedded in it, including its prompt, are published with it.
The public, for anything you publish on Explore.
Qualifications & exceptions
Applies when you choose to publish an image on Explore.
The policy describes what you publish on Explore as public by your choice.
Account, stored content and usage data are used to provide the service
NovelAI uses your account details, the content you store (end-to-end encrypted), what you submit for generation (processed, not stored), your usage history and your messages to provide the service you signed up for. The listed uses are your account, stored content, generation, NovelAI Explore, contests, support and emails about your account. The stated legal basis is performance of the contract with you.
Supporting quotations
Providing the service you signed up for: your account, the content you store, generation, NovelAI Explore, contests, support, and emails about your account.
Performance of our contract with you.
Until you delete your account.
Until erased at your request.
Qualifications & exceptions
Account, stored content and account event log are kept until you delete your account; usage records are kept until erased at your request, which can be after the account is deleted.
Charges & Financial Obligations · Company practice
Billing data is used for payments; full card numbers do not reach NovelAI
NovelAI uses your billing details, partial payment-method details and transaction records to take payments and issue invoices. Full card numbers and security codes go directly to the card gateway and never reach NovelAI. Payment providers named in the policy receive the payment data it describes.
Supporting quotations
Taking payments and issuing invoices.
Full card numbers and security codes go directly to our card gateway and never reach us.
Keeping invoices and tax-jurisdiction records after your account closes: our legal obligation under tax and accounting law, and our legitimate interest in keeping accounting records and defending payment disputes.
Chargebee (billing and invoices); our card gateway and card acquirer.
Invoices and tax-jurisdiction records, as long as tax and accounting law requires.
Qualifications & exceptions
Legal basis is performance of the contract; keeping invoices and tax-jurisdiction records after the account closes rests on a legal obligation and a legitimate interest.
Invoices and tax-jurisdiction records are kept as long as tax and accounting law requires; other payment records, including billing name and address, until erased at your request.
Device, account and payment identifiers are used to prevent fraud and abuse
NovelAI uses technical data about your device and connection, account and payment identifiers, and records of past enforcement to prevent fraud, abuse of free features and unlawful content. The stated legal basis is its legitimate interest in protecting the service and its users. Fingerprint and Google reCAPTCHA Enterprise receive the device and connection data.
Supporting quotations
Preventing fraud, abuse of free features, and unlawful content.
Technical data about your device and connection, account and payment identifiers, and records of past enforcement.
Fingerprint and Google reCAPTCHA Enterprise receive technical data about your device and connection
so we keep them after an account is deleted
Qualifications & exceptions
Fraud-prevention records are kept for as long as NovelAI operates the service, including after an account is deleted and, where its interest in preventing fraud overrides, when erasure is requested.
Technical logs and error reports are kept to keep the service secure
NovelAI keeps technical logs and error reports to keep the service secure and working, relying on its legitimate interest. Sentry receives technical error reports. Logs and reports are kept up to 90 days, or one year when kept for a support case.
Supporting quotations
Keeping the service secure and working. Technical logs and error reports.
Our legitimate interest in the security and reliability of the service.
Sentry (technical error reports)
Up to 90 days, or one year when kept for a support case.
Qualifications & exceptions
Kept up to 90 days, or one year when kept for a support case.
NovelAI uses your email address, subscription status and which features you use to send marketing emails, on the basis of your consent. Customer.io, the marketing email provider, receives these details only if you opted in. The marketing profile is kept until you withdraw consent or delete your account.
Supporting quotations
Sending marketing emails. Your email address, subscription status and which features you use. Your consent.
Customer.io (marketing emails, only if you opted in)
Until you withdraw consent or delete your account.
Qualifications & exceptions
Applies only if you opted in.
The marketing profile is kept until you withdraw consent or delete your account.
Usage and advertising measurement relies on consent or legitimate interest
NovelAI measures how the service is used and how its advertising performs using a visitor identifier and records of how you arrived at and use the service, such as pages viewed, features used and purchases. This never includes your prompts, your stories or anything you generate. The legal basis is your consent for tools you can switch on or off under Manage Cookies, and legitimate interest for NovelAI's own usage statistics.
Supporting quotations
Measuring how the service is used and how our advertising performs.
This never includes your prompts, your stories or anything you generate.
Your consent, for the tools you can switch on or off under "Manage Cookies". Our legitimate interest in understanding and improving the service, for our own usage statistics.
PostHog; Plausible Analytics; Google (Tag Manager and Google Ads); Osano
Up to 6 months. The profile held by our analytics provider, until erased at your request.
Qualifications & exceptions
Usage analytics are kept up to 6 months; the profile held by the analytics provider is kept until erased at your request.
Analytics and advertising-measurement providers receive usage data, never prompts or content; Osano receives consent choices.
Not stated here
The policy does not say which listed tools are controlled under Manage Cookies and which count as NovelAI's own usage statistics.
NovelAI also receives payment, security and Google sign-in data from others
NovelAI receives payment and authentication results, chargeback notices and risk assessments from its payment and security providers. If you sign in with Google, it receives the account data described in the Google sign-in section.
Supporting quotations
From the payment and security providers in section 5: payment and authentication results, chargeback notices, and risk assessments.
From Google, if you sign in with Google: the account data described in section 4.
Qualifications & exceptions
Google data is received only if you sign in with Google.
Account & Service Control · Restriction or exception
An email and password, and a billing address to pay, are required
To open an account you must provide an email address and a password, or a Google account plus a separate encryption password if you sign in with Google. A billing address is needed to pay. Without them NovelAI says it cannot provide the account or take the payment.
Supporting quotations
An email address and a password to open an account, or a Google account plus a separate encryption password if you sign in with Google, and a billing address to pay.
Without them we cannot provide the account or take the payment.
Data Access & Collection · Company practice
Signing in with Google gives NovelAI your Google ID, email and verification status
If you choose to sign in with Google, Google sends NovelAI your Google account identifier, your email address, whether Google has verified that address, and, for Google Workspace accounts, your organisation's domain. NovelAI says it requests no other access to your Google account and does not store anything else in the sign-in response.
Supporting quotations
Google sends us your Google account identifier, your email address, whether Google has verified that address, and, for Google Workspace accounts, your organisation's domain.
We request no other access to your Google account and do not store anything else Google includes in the sign-in response.
Qualifications & exceptions
Applies only if you choose to sign in with Google.
The organisation domain is sent for Google Workspace accounts.
The Google account identifier is used only to recognise you at sign-in
NovelAI uses the Google account identifier for one purpose only: to recognise you when you sign in again. It is shared with no one other than the hosting providers that run NovelAI's systems, and it is deleted with your account.
Supporting quotations
We use the Google account identifier for one purpose only: to recognise you when you sign in again.
The identifier itself is shared with no one other than the hosting providers that run our systems, and it is deleted with your account.
Qualifications & exceptions
Sharing is limited to the hosting providers that run NovelAI's systems.
Deleted with your account.
Not stated here
The policy lists account identifiers among fraud-prevention data kept after account deletion; it does not say whether the Google account identifier is part of that data.
The Google email becomes your account email and is handled like any account email
Your Google email address becomes the email address of your NovelAI account. NovelAI uses it for messages about your account, for billing if you pay, for marketing emails only if you opt in, and, in hashed form, to prevent abuse. It reaches the providers listed in section 5 for those purposes.
Supporting quotations
Your email address becomes the email address of your NovelAI account.
for marketing emails only if you opt in, and, in hashed form, to prevent abuse
including a hashed form of your email address
Qualifications & exceptions
Marketing emails only if you opt in.
After you delete your account, the email is kept only as described in section 6, which keeps a hashed form of the email address with fraud-prevention and payment records until you ask for erasure.
Google user data is not sold, used for ad targeting or for AI training
NovelAI says it does not sell Google user data, use it to target advertising, or use it to develop, improve or train AI models. It says its use of information from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. If it wants to use Google user data in a new way, it says it will tell you and ask for your consent first.
Supporting quotations
We do not sell Google user data, use it to target advertising, or use it to develop, improve or train AI models.
If we want to use Google user data in a new way, we will tell you and ask for your consent before doing so.
Hosting, network and backup providers run NovelAI's systems and hold its data
CoreWeave, Cloudflare and Google Cloud (backups) run NovelAI's servers, network and backups and hold the data the policy describes. Your stories reach them only in encrypted form, which the policy says neither NovelAI nor they can read, and the Google account identifier is shared only with these hosting providers.
Supporting quotations
Hosting and network: CoreWeave, Cloudflare, Google Cloud (backups). They run our servers, network and backups and hold the data described in this policy.
Your stories reach our hosting and backup providers only in the encrypted form described in section 2, which neither we nor they can read.
The identifier itself is shared with no one other than the hosting providers that run our systems
Qualifications & exceptions
Stories reach hosting and backup providers only in encrypted form.
Prompts and generated content reach hosting and network providers only as traffic passing through on the way to NovelAI's servers.
Third-party scripts and media loaded in your browser receive your IP address and browser details
Google (fonts), jsDelivr (editor assets), YouTube (embedded videos) and rss2json (blog feed) each receive only your IP address and browser details when the resource loads in your browser.
Supporting quotations
Google (fonts); jsDelivr (editor assets); YouTube (embedded videos); rss2json (blog feed). Each receives only your IP address and browser details when the resource loads.
Qualifications & exceptions
Each receives only IP address and browser details, when the resource loads.
Charges & Financial Obligations · Company practice
Chargebee and the card gateway and acquirer receive payment data
Chargebee (billing and invoices), NovelAI's card gateway and its card acquirer receive the payment data described in the data section: billing details, partial payment-method details and transaction records. Full card numbers and security codes go directly to the card gateway.
Supporting quotations
Payments: Chargebee (billing and invoices); our card gateway and card acquirer. They receive the payment data described in section 3.
Your billing details, partial payment-method details and transaction records.
Full card numbers and security codes go directly to our card gateway and never reach us.
Qualifications & exceptions
The policy says full card numbers and security codes never reach NovelAI itself.
Not stated here
The policy does not name the card gateway or card acquirer.
Mailgun and Customer.io receive your email address and the messages sent to you
Mailgun handles account emails and Customer.io handles marketing emails, only if you opted in. They receive your email address and the messages NovelAI sends you. Customer.io also receives your subscription status and which features you use, so the emails can be relevant to you. Your email address is used for account messages and, if you pay, for billing.
Supporting quotations
Mailgun (account emails); Customer.io (marketing emails, only if you opted in). They receive your email address and the messages we send you.
Customer.io also receives your subscription status and which features you use, so that we can send you emails that are relevant to you.
Your email address, subscription status and which features you use. Your consent.
we use it for messages about your account, for billing if you pay, for marketing emails only if you opt in
Qualifications & exceptions
Customer.io's role applies only if you opted in to marketing emails.
Fingerprint, reCAPTCHA Enterprise and Google Sign-In receive security and sign-in data
Fingerprint and Google reCAPTCHA Enterprise receive technical data about your device and connection for account and payment security. Google Sign-In provides the account data described in the Google sign-in section. The providers also send NovelAI back payment and authentication results, chargeback notices and risk assessments. NovelAI says it does not sell Google user data.
Supporting quotations
Fingerprint and Google reCAPTCHA Enterprise receive technical data about your device and connection; Google Sign-In, the account data described in section 4.
Technical data about your device and connection, account and payment identifiers, and records of past enforcement.
payment and authentication results, chargeback notices, and risk assessments
Google sends us your Google account identifier, your email address, whether Google has verified that address
We do not sell Google user data
Qualifications & exceptions
Google Sign-In applies only to people who choose to sign in with Google.
PostHog, Plausible, Google and Osano receive usage and consent data, never prompts or content
PostHog, Plausible Analytics, Google (Tag Manager and Google Ads) and Osano receive the usage data described in the data section, such as a visitor identifier and how you arrived at and use the service. They never receive your prompts or content. Osano also receives your consent choices.
Supporting quotations
Analytics, advertising measurement and consent management: PostHog; Plausible Analytics; Google (Tag Manager and Google Ads); Osano. They receive the usage data described in section 3, never your prompts or content; Osano receives your consent choices.
A visitor identifier and records of how you arrived at and use the service, such as pages viewed, features used and purchases.
Your consent choices and when you made them.
Qualifications & exceptions
Never prompts or content.
Consent choices go to Osano.
Not stated here
The policy does not say which provider handles which kind of usage data.
Sentry, Zendesk and Slack receive error reports, support messages and internal notices
Sentry receives technical error reports, Zendesk receives what you send to support, and Slack receives internal notices about your account.
Supporting quotations
Error monitoring, support and internal messaging: Sentry (technical error reports); Zendesk (what you send to support); Slack (internal notices about your account).
Technical logs and error reports.
Not stated here
The policy does not say what the internal Slack notices about your account contain.
Explore posts are public and kept until you delete them
What you publish on Explore goes to the public, which the policy describes as your choice. Explore posts are kept until you delete them. A published image carries its embedded generation settings, including its prompt.
Supporting quotations
The public, for anything you publish on Explore.
What you publish on Explore is public by your choice.
Until you delete them.
If you publish an image on Explore, the generation settings embedded in it, including its prompt, are published with it.
Qualifications & exceptions
Publishing is by your choice.
Backups keep deleted data for up to 90 days.
Not stated here
The policy does not say whether copies others make of a public Explore post are removed when you delete it.
None of the listed providers receives prompts or generated content
The policy says none of the listed providers receives your prompts or anything you generate, other than as traffic passing through the hosting and network providers on the way to NovelAI's servers.
Supporting quotations
None of these providers receives your prompts or anything you generate, other than as traffic passing through our hosting and network providers on the way to our servers.
We store only the encrypted data and cannot read it.
Qualifications & exceptions
Traffic passing through hosting and network providers on the way to the servers is the one stated exception.
Stories reach hosting and backup providers only encrypted.
Account, stored content and account event log are kept until you delete your account
NovelAI keeps your account, the content you store and your account event log until you delete your account. Data you delete stays in backups until they expire.
Supporting quotations
Your account, the content you store and your account event log Until you delete your account.
Data you delete remains in backups until they expire.
Invoices are kept as long as tax law requires; other payment records until you ask for erasure
Invoices and tax-jurisdiction records are kept as long as tax and accounting law requires. Other payment records, including your billing name and address, are kept until erased at your request.
Supporting quotations
Payment records Invoices and tax-jurisdiction records, as long as tax and accounting law requires. Other payment records, including your billing name and address, until erased at your request.
Fraud-prevention records are kept for as long as NovelAI operates the service
Fraud-prevention records are kept for as long as NovelAI operates the service. NovelAI says removing individual records would weaken its ability to recognise repeat fraud and abuse, so it keeps them after an account is deleted and, where its interest in preventing fraud overrides, when erasure is requested.
Supporting quotations
Fraud-prevention records For as long as we operate the service. Removing individual records would weaken our ability to recognise repeat fraud and abuse, so we keep them after an account is deleted and, where our interest in preventing fraud overrides, when erasure is requested.
Qualifications & exceptions
Kept after account deletion.
Kept despite an erasure request only where NovelAI's interest in preventing fraud overrides.
Not stated here
The policy does not say how NovelAI decides when its fraud-prevention interest overrides an erasure request beyond saying it assesses each request.
The marketing profile is kept until you withdraw consent or delete your account
NovelAI keeps the marketing profile until you withdraw your consent or delete your account.
Supporting quotations
Marketing profile Until you withdraw consent or delete your account.
Retention & Deletion · Company practice
Backups are kept 90 days and still hold data you deleted until they expire
Backups are kept for 90 days. Data you delete remains in backups until they expire.
Supporting quotations
Backups 90 days. Data you delete remains in backups until they expire.
Retention & Deletion · Company practice
After you delete your account, fraud, payment and usage data remain
After you delete your account in settings, NovelAI keeps the fraud-prevention and payment records listed in the retention table, including a hashed form of your email address. It also keeps the usage records and the analytics profile until you ask NovelAI to erase them.
Supporting quotations
After you delete your account in settings we keep the fraud-prevention and payment records above, including a hashed form of your email address, and the usage records and analytics profile until you ask us to erase them.
Qualifications & exceptions
Usage records and analytics profile stay until you ask for erasure.
The hashed email address is kept with the fraud-prevention and payment records, and fraud-prevention records may stay even after an erasure request.
Legal Rights & Agreement Rules · User right or choice
People in the EEA have access, correction, erasure, restriction, portability and objection rights
If you are in the European Economic Area, the policy gives you the right to access your personal data, to have it rectified or erased, to restrict its processing, to receive the data you provided in a portable format, and to object to processing based on legitimate interests. Where processing rests on consent, you may withdraw consent at any time without affecting processing already done. You also have the right to complain to a data protection authority.
Supporting quotations
If you are in the European Economic Area, you have the right to access your personal data, to have it rectified or erased, to restrict its processing, to receive the data you provided in a portable format, and to object to processing based on our legitimate interests.
Where processing is based on your consent, you may withdraw it at any time without affecting processing that already took place.
You also have the right to complain to a data protection authority.
Qualifications & exceptions
Stated for people in the European Economic Area.
Objection applies to processing based on legitimate interests; withdrawal applies where processing is based on consent.
Erasure and objection requests about fraud-prevention records can be refused, as covered separately.
Not stated here
The policy states these rights for the European Economic Area only and does not say what rights people elsewhere have.
Legal Rights & Agreement Rules · Restriction or exception
Erasure and objection requests about fraud-prevention records may be refused
NovelAI may refuse erasure and objection requests that concern its fraud-prevention records where its interest in preventing fraud overrides, as set out in the retention section. It says it assesses each request.
Supporting quotations
We may refuse erasure and objection requests that concern our fraud-prevention records where our interest in preventing fraud overrides, as set out in section 6; we assess each request.
where our interest in preventing fraud overrides, when erasure is requested
Qualifications & exceptions
Applies to fraud-prevention records only.
Refusal is for requests where the fraud-prevention interest overrides; each request is assessed.