Legal
Privacy Notice
- Version
- 0.1.0-draft
- Effective
- [FD-32: Effective date]
- Status
- Draft
DRAFT — NOT FOR PUBLICATION. This document has not been approved by legal counsel and is not in effect. 38 highlighted items still need to be decided or reviewed.
What personal information Nexdren AI collects, why, how it is protected and shared, how long it is kept, and your rights.
1. Summary
- Nexdren AI is an adult-only AI companion service. Your conversations can be intimate and sexual in nature, and we treat them as highly sensitive.
- Nexdren AI is currently in a pre-launch preview. Section 3 explains exactly what happens to your data today. Most of this notice describes how data will be handled once accounts, AI replies and payments launch.
- We do not sell personal information and do not use your conversations for advertising.
- You can ask to access or delete your data at any time using the contacts in section 16.
2. Who is responsible for your data
The controller (or "data fiduciary" under Indian law, "business" under some U.S. state laws) is [FD-01: Legal entity name and entity type], [FD-04: Public business address].
- Privacy contact: [FD-06: Privacy contact email]
- EU / UK representative and data protection officer, if required: [FD-35: EU/UK representative and DPO]
3. What happens today (preview)
This section reflects how the website actually works at the moment.
- What
- Age confirmation
- What happens
- When you confirm you are 18+, your browser stores a cookie (
nexdren_age) and a local-storage entry (nexdren.age) for 30 days. If you choose "under 18", a session-storage flag (nexdren.age.declined) blocks the site until you close the browser. These stay on your device.
- What
- Chat messages
- What happens
- When you send a message, the message and recent messages in that chat are sent to our server only to be checked against our content rules. Our application code does not save them. No AI provider receives them, because AI replies are not connected yet.
- What
- Accounts
- What happens
- Accounts cannot be created. Login and registration forms do not send data anywhere.
- What
- Payments
- What happens
- No payments are taken.
- What
- Server logs
- What happens
- Our hosting provider ([FD-13: Hosting provider and region]) may record standard request information such as IP address, time and browser type.
- What
- Analytics and advertising
- What happens
- None in use.
- What
- Moderation events
- What happens
- Our server can send moderation alerts to Make.com, but this is not switched on. When switched on, alerts contain no message text (see section 8).
| What | What happens |
|---|---|
| Age confirmation | When you confirm you are 18+, your browser stores a cookie (nexdren_age) and a local-storage entry (nexdren.age) for 30 days. If you choose "under 18", a session-storage flag (nexdren.age.declined) blocks the site until you close the browser. These stay on your device. |
| Chat messages | When you send a message, the message and recent messages in that chat are sent to our server only to be checked against our content rules. Our application code does not save them. No AI provider receives them, because AI replies are not connected yet. |
| Accounts | Accounts cannot be created. Login and registration forms do not send data anywhere. |
| Payments | No payments are taken. |
| Server logs | Our hosting provider ([FD-13: Hosting provider and region]) may record standard request information such as IP address, time and browser type. |
| Analytics and advertising | None in use. |
| Moderation events | Our server can send moderation alerts to Make.com, but this is not switched on. When switched on, alerts contain no message text (see section 8). |
4. Information we collect after launch
- Category
- Account and login
- Examples
- Email address, password (stored only as a salted hash), login times, account settings
- Source
- You
- Category
- Age assurance
- Examples
- That you passed an age check, the method used, date, and the result. The type of data processed by any verification provider is described in section 9.
- Source
- You; age-assurance provider
- Category
- Conversations
- Examples
- Your messages, AI-generated replies, chosen companions
- Source
- You; generated by the Service
- Category
- Generated images
- Examples
- Images generated for you and the prompts used
- Source
- Generated by the Service
- Category
- Sexual and intimate interaction data
- Examples
- Content of explicit conversations; preferences and fantasies you express
- Source
- You
- Category
- Preferences and inferences
- Examples
- Content settings (such as explicit-content opt-in), favourite companions, and preferences the Service infers from your conversations to personalise replies
- Source
- You; generated by the Service
- Category
- Moderation and safety records
- Examples
- Which content rule was matched, outcome (allowed, blocked, reviewed), related account and time; for serious cases, the specific content reviewed
- Source
- Generated by the Service
- Category
- Payment information
- Examples
- Plan, amount, billing status, payment-method type and last four digits, billing country. Full card numbers are handled by the payment processor, not by us.
- Source
- You; payment processor
- Category
- Affiliate / referral information
- Examples
- Referral code used at sign-up; for affiliates, contact, payout and tax details
- Source
- You; affiliates
- Category
- Device and technical data
- Examples
- IP address, device and browser type, approximate location derived from IP, logs, security events
- Source
- Your device
- Category
- Cookies and local storage
- Examples
- See the Cookies Notice
- Source
- Your device
- Category
- Support tickets
- Examples
- Messages you send to support and our replies
- Source
- You
- Category
- Legal and compliance requests
- Examples
- Copyright notices, removal requests, law-enforcement requests and related correspondence
- Source
- You; third parties
| Category | Examples | Source |
|---|---|---|
| Account and login | Email address, password (stored only as a salted hash), login times, account settings | You |
| Age assurance | That you passed an age check, the method used, date, and the result. The type of data processed by any verification provider is described in section 9. | You; age-assurance provider |
| Conversations | Your messages, AI-generated replies, chosen companions | You; generated by the Service |
| Generated images | Images generated for you and the prompts used | Generated by the Service |
| Sexual and intimate interaction data | Content of explicit conversations; preferences and fantasies you express | You |
| Preferences and inferences | Content settings (such as explicit-content opt-in), favourite companions, and preferences the Service infers from your conversations to personalise replies | You; generated by the Service |
| Moderation and safety records | Which content rule was matched, outcome (allowed, blocked, reviewed), related account and time; for serious cases, the specific content reviewed | Generated by the Service |
| Payment information | Plan, amount, billing status, payment-method type and last four digits, billing country. Full card numbers are handled by the payment processor, not by us. | You; payment processor |
| Affiliate / referral information | Referral code used at sign-up; for affiliates, contact, payout and tax details | You; affiliates |
| Device and technical data | IP address, device and browser type, approximate location derived from IP, logs, security events | Your device |
| Cookies and local storage | See the Cookies Notice | Your device |
| Support tickets | Messages you send to support and our replies | You |
| Legal and compliance requests | Copyright notices, removal requests, law-enforcement requests and related correspondence | You; third parties |
We do not ask for, and you should not share, government ID numbers, financial account numbers or other people's personal information in conversations.
5. Why we use information
- Purpose
- Provide the Service (accounts, generating replies and images, remembering conversation context)
- Data used
- Account, conversations, images, preferences
- Purpose
- Keep the Service adults-only
- Data used
- Age assurance, technical data
- Purpose
- Moderate content and keep the Service lawful and safe
- Data used
- Conversations, images, moderation records, technical data
- Purpose
- Process payments, prevent fraud and handle billing issues
- Data used
- Payment, account, technical data
- Purpose
- Provide support and handle complaints and appeals
- Data used
- Support tickets, account, relevant conversations
- Purpose
- Run the affiliate programme
- Data used
- Referral and affiliate data
- Purpose
- Security, debugging and preventing abuse
- Data used
- Technical data, logs
- Purpose
- Comply with law and respond to legal requests
- Data used
- Any category, only as needed
- Purpose
- Send service messages (receipts, renewal reminders, policy changes)
- Data used
- Account, payment
- Purpose
- Send marketing, only if you opt in ([FD-30: Marketing communications])
- Data used
- Email address
| Purpose | Data used |
|---|---|
| Provide the Service (accounts, generating replies and images, remembering conversation context) | Account, conversations, images, preferences |
| Keep the Service adults-only | Age assurance, technical data |
| Moderate content and keep the Service lawful and safe | Conversations, images, moderation records, technical data |
| Process payments, prevent fraud and handle billing issues | Payment, account, technical data |
| Provide support and handle complaints and appeals | Support tickets, account, relevant conversations |
| Run the affiliate programme | Referral and affiliate data |
| Security, debugging and preventing abuse | Technical data, logs |
| Comply with law and respond to legal requests | Any category, only as needed |
| Send service messages (receipts, renewal reminders, policy changes) | Account, payment |
| Send marketing, only if you opt in ([FD-30: Marketing communications]) | Email address |
Model training. Whether conversations are used to train or improve AI models: [FD-29: Use of conversations for training (recommended: not used)].
6. Legal bases (EEA, UK and similar laws)
If EU or UK data protection law applies to you, we rely on:
- Processing
- Providing conversations and images
- Article 6 basis
- Performance of our contract with you (Art. 6(1)(b))
- Article 9 condition (special-category data)
- Conversations may reveal data about your sex life or sexual orientation. We will ask for your explicit consent (Art. 9(2)(a)) before processing it. You can withdraw consent at any time; the Service cannot provide companion conversations without it.
- Processing
- Age assurance
- Article 6 basis
- Legal obligation (Art. 6(1)(c)) where a law requires age checks; otherwise legitimate interests (Art. 6(1)(f)) in keeping minors off an adult service
- Article 9 condition (special-category data)
- If biometric age estimation is used: explicit consent (Art. 9(2)(a))
- Processing
- Moderation and safety
- Article 6 basis
- Legitimate interests (Art. 6(1)(f)) in a lawful, safe service; legal obligation where reporting is required
- Article 9 condition (special-category data)
- [COUNSEL: condition for processing special-category data in moderation records, e.g. Art. 9(2)(f) legal claims, Art. 9(2)(g) / UK DPA 2018 Sch. 1 para. 10 preventing unlawful acts]
- Processing
- Payments and accounting
- Article 6 basis
- Contract; legal obligation (tax and accounting)
- Article 9 condition (special-category data)
- Not applicable
- Processing
- Security and fraud prevention
- Article 6 basis
- Legitimate interests
- Article 9 condition (special-category data)
- Not applicable
- Processing
- Marketing
- Article 6 basis
- Consent
- Article 9 condition (special-category data)
- Not applicable
- Processing
- Non-essential cookies (none today)
- Article 6 basis
- Consent
- Article 9 condition (special-category data)
- Not applicable
| Processing | Article 6 basis | Article 9 condition (special-category data) |
|---|---|---|
| Providing conversations and images | Performance of our contract with you (Art. 6(1)(b)) | Conversations may reveal data about your sex life or sexual orientation. We will ask for your explicit consent (Art. 9(2)(a)) before processing it. You can withdraw consent at any time; the Service cannot provide companion conversations without it. |
| Age assurance | Legal obligation (Art. 6(1)(c)) where a law requires age checks; otherwise legitimate interests (Art. 6(1)(f)) in keeping minors off an adult service | If biometric age estimation is used: explicit consent (Art. 9(2)(a)) |
| Moderation and safety | Legitimate interests (Art. 6(1)(f)) in a lawful, safe service; legal obligation where reporting is required | [COUNSEL: condition for processing special-category data in moderation records, e.g. Art. 9(2)(f) legal claims, Art. 9(2)(g) / UK DPA 2018 Sch. 1 para. 10 preventing unlawful acts] |
| Payments and accounting | Contract; legal obligation (tax and accounting) | Not applicable |
| Security and fraud prevention | Legitimate interests | Not applicable |
| Marketing | Consent | Not applicable |
| Non-essential cookies (none today) | Consent | Not applicable |
India (DPDP Act 2023). Where Indian data protection law applies, we process personal data on the basis of your consent, given through a clear notice, or for legitimate uses permitted by the Act. [COUNSEL: confirm DPDP position, including whether the Service will be offered in India at all — see FD-33 and FD-10].
United States. Several U.S. state laws treat information about sex life as "sensitive". Where those laws apply, we process it only to provide the Service you request, or with your consent where required.
7. Who we share information with
We share personal information only as described here. We do not sell it, and we do not share it for cross-context behavioural advertising.
- Recipient
- AI text-generation provider
- Purpose
- Generate companion replies
- Data
- Your message, recent conversation context, companion profile
- Provider
- [FD-11: LLM provider]
- Recipient
- Image-generation provider
- Purpose
- Generate images
- Data
- Image prompts
- Provider
- [FD-12: Image-generation provider]
- Recipient
- Hosting provider
- Purpose
- Run the website and servers
- Data
- All data processed by the Service
- Provider
- [FD-13: Hosting provider and region]
- Recipient
- Database and authentication provider
- Purpose
- Store accounts and conversations
- Data
- Account, conversations, images, moderation records
- Provider
- [FD-14: Database / authentication provider]
- Recipient
- Payment processor
- Purpose
- Take payments, prevent fraud
- Data
- Payment and billing data
- Provider
- [FD-15: Payment processor]
- Recipient
- Age-assurance provider
- Purpose
- Check age where required
- Data
- See section 9
- Provider
- [FD-16: Age-assurance provider]
- Recipient
- Moderation providers
- Purpose
- Detect prohibited content
- Data
- Content being checked
- Provider
- [FD-17: Moderation providers]
- Recipient
- Make.com (workflow automation)
- Purpose
- Moderation alerts and review notifications
- Data
- Event ID, category, outcome, time, pseudonymous ID. No message text, email, name or IP address.
- Provider
- Make.com, only if enabled ([FD-28: Make.com scope and contract])
- Recipient
- Support and email tools
- Purpose
- Support tickets and service emails
- Data
- Contact details, ticket content
- Provider
- [FD-40: Support and email tooling]
- Recipient
- Authorities
- Purpose
- Legal reporting and lawful requests
- Data
- Only what the law requires
- Provider
- e.g. NCMEC where U.S. law requires a report; law enforcement with valid legal process
- Recipient
- Professional advisers; a buyer of the business
- Purpose
- Legal advice; corporate transactions
- Data
- As needed, under confidentiality
- Provider
- —
| Recipient | Purpose | Data | Provider |
|---|---|---|---|
| AI text-generation provider | Generate companion replies | Your message, recent conversation context, companion profile | [FD-11: LLM provider] |
| Image-generation provider | Generate images | Image prompts | [FD-12: Image-generation provider] |
| Hosting provider | Run the website and servers | All data processed by the Service | [FD-13: Hosting provider and region] |
| Database and authentication provider | Store accounts and conversations | Account, conversations, images, moderation records | [FD-14: Database / authentication provider] |
| Payment processor | Take payments, prevent fraud | Payment and billing data | [FD-15: Payment processor] |
| Age-assurance provider | Check age where required | See section 9 | [FD-16: Age-assurance provider] |
| Moderation providers | Detect prohibited content | Content being checked | [FD-17: Moderation providers] |
| Make.com (workflow automation) | Moderation alerts and review notifications | Event ID, category, outcome, time, pseudonymous ID. No message text, email, name or IP address. | Make.com, only if enabled ([FD-28: Make.com scope and contract]) |
| Support and email tools | Support tickets and service emails | Contact details, ticket content | [FD-40: Support and email tooling] |
| Authorities | Legal reporting and lawful requests | Only what the law requires | e.g. NCMEC where U.S. law requires a report; law enforcement with valid legal process |
| Professional advisers; a buyer of the business | Legal advice; corporate transactions | As needed, under confidentiality | — |
We require service providers to use data only on our instructions, keep it confidential and protect it, under written agreements.
8. AI processing and Make.com
- To generate a reply, your message and recent conversation context are sent to the AI provider. The provider's retention and training terms will be listed here once selected ([FD-11: LLM provider retention and training terms]).
- Moderation checks run on our own servers before content is sent to the AI provider and before a reply is shown to you. If a check cannot be completed, the content is blocked rather than allowed.
- Make.com is used, if enabled, only to route moderation alerts to our review team. Make.com is not our database, AI provider or payment processor, and does not receive conversation content by default.
9. Age assurance data
- Today: age confirmation is a self-declaration stored on your device.
- Where stronger checks are required: we will use an independent age-assurance provider ([FD-16: Age-assurance provider and method]). Methods may include age estimation from a selfie, a document check, or a reusable age token. We aim to receive only the result ("over 18: yes/no") and not your ID document or images. Any biometric processing will be described here, with your explicit consent requested where required, before it starts.
10. International transfers
We and our providers may process data in countries other than yours, including the United States ([FD-13: Hosting provider and region]). Where EU or UK law requires it, we use recognised safeguards such as adequacy decisions, the EU-U.S. Data Privacy Framework (where the recipient is certified) or standard contractual clauses, together with a transfer risk assessment. The founder may access systems from India; any such access is subject to the same safeguards. [COUNSEL: confirm transfer mechanism once vendors are chosen]
11. How long we keep information
- Data
- Conversations and generated images
- Retention
- [FD-24: Conversation and image retention]
- Data
- Account data after you delete your account
- Retention
- [FD-24: Post-deletion retention]
- Data
- Age-assurance result
- Retention
- [FD-24: Age-assurance record retention]
- Data
- Moderation records
- Retention
- [FD-24: Moderation record retention]
- Data
- Material we are legally required to report to child-safety authorities
- Retention
- For the period the law requires (in the U.S., 1 year where 18 U.S.C. §2258A(h) applies) [COUNSEL: C-04]
- Data
- Payment and tax records
- Retention
- As long as tax and accounting law requires
- Data
- Server logs
- Retention
- [FD-24: Log retention]
- Data
- Backups
- Retention
- [FD-24: Backup retention]
| Data | Retention |
|---|---|
| Conversations and generated images | [FD-24: Conversation and image retention] |
| Account data after you delete your account | [FD-24: Post-deletion retention] |
| Age-assurance result | [FD-24: Age-assurance record retention] |
| Moderation records | [FD-24: Moderation record retention] |
| Material we are legally required to report to child-safety authorities | For the period the law requires (in the U.S., 1 year where 18 U.S.C. §2258A(h) applies) [COUNSEL: C-04] |
| Payment and tax records | As long as tax and accounting law requires |
| Server logs | [FD-24: Log retention] |
| Backups | [FD-24: Backup retention] |
12. Deleting your data
- You will be able to delete individual conversations and your account from your settings.
- Deleted data is removed from active systems within [FD-24: Deletion timeframe] and from backups when they expire.
- We may keep limited data after deletion where the law requires it (for example tax records, or material preserved for a child-safety report) or to defend legal claims.
13. Your rights
Depending on where you live, you may have the right to:
- access a copy of your personal information;
- correct inaccurate information;
- delete your information;
- receive your information in a portable format;
- object to or restrict certain processing;
- withdraw consent at any time (this does not affect processing before withdrawal);
- opt out of the sale or sharing of personal information (we do neither) and limit the use of sensitive information;
- appeal our decision on your request, and complain to your data protection authority.
To exercise your rights, email [FD-06: Privacy contact email]. We may need to verify your identity. We will not discriminate against you for exercising your rights.
India: you may also nominate another person to exercise your rights and contact our grievance officer at [FD-06: Privacy contact / grievance officer].
14. Security
We design the Service to limit who can see your data:
- Access to conversations is limited to systems that need it to run the Service. Staff may view specific content only when handling a moderation review, a report, a support request you make, or a legal obligation, and such access is logged. [LAUNCH-GATE: role-based access controls and access logging must exist before publication]
- Production systems are to be served over encrypted connections (HTTPS), with data encrypted at rest by our storage providers. [LAUNCH-GATE: confirm both are in place before publication]
- Secrets and credentials are stored server-side and never in the website code.
No system is completely secure. We do not offer end-to-end encryption, and we do not claim that your data can never be accessed.
Data breaches. If a breach is likely to put you at risk, we will notify you and the relevant regulators as the law requires.
15. Children
Nexdren AI is only for adults. We do not knowingly collect information from anyone under 18. If we learn that a user is under 18, we close the account and delete their data, except information we must keep by law (for example for a child-safety report). If you believe a minor is using the Service, contact [FD-06: Privacy contact email]. See the Underage and Age Assurance Policy.
16. Contact and complaints
- Privacy: [FD-06: Privacy contact email]
- Post: [FD-04: Public business address]
You can also complain to your local data protection authority (for example the ICO in the UK or your EU national authority).
17. Changes
We will post any update here with a new version number and effective date, and notify account holders of material changes before they take effect.