PRIVACY POLICY

1. Scope, controller, eligibility, and privacy principles

1.1. This Policy applies to the website, registered and accountless access, private text chat, pre-created AI Character pages and media, browser-local conversation history, free and fixed-term paid features, official support and reporting forms, cryptocurrency checkout and activation, security systems, Cookie Settings, Google Analytics 4, and advertising delivered through Aefia (the “Service”).

1.2. This Policy does not govern an independent advertiser, destination website, wallet, exchange, blockchain network, payment provider, authentication provider, analytics provider acting for its own purposes, or other third party that independently determines its own processing purposes and means. That party's own privacy notice and terms apply to its independent processing.

1.3. The Service is intended only for adults who are at least 18 years old, have reached the age of legal majority, satisfy any higher local age requirement for adult content, and may lawfully access the Service. We do not knowingly permit minors to use the Service. If we reasonably learn that a minor has used it, we may restrict access, preserve only server-side data reasonably necessary for child protection, security, or legal compliance, and delete or de-identify other server-side data where reasonably possible and legally permitted. Aefia cannot remotely access, erase, or recover chat history stored only in the minor's browser.

• Data controller: The individual who privately operates and controls Aefia determines the purposes and means of the processing described in this Policy, except where a third party acts as an independent or joint controller for its own service. Privacy questions and rights requests must be submitted through the Privacy Contact Form on this page.
• Public contact channels: General support and security requests are handled at /feedback. Privacy rights and complaints are handled at /privacy. Copyright, illegal-content, child-safety, non-consensual intimate-content, real-person likeness, and advertisement reports are handled at /feedback.
• Browser-only persistent chat history: Aefia never stores ordinary User messages or generated replies as persistent server-side chat history. Persistent conversation history exists only in the User's browser. After local deletion, Aefia has no server copy and cannot retrieve, reconstruct, or restore the deleted conversation.
• No Operator chat viewer: The Operator has no administrative interface, server archive, or routine tool for opening ordinary private conversations and does not manually review them. Chat text becomes visible to the Operator only when a User voluntarily copies and submits that text through an official text-based form or correspondence channel.
• Lawfulness and fairness: Personal data is processed only where a lawful basis applies and in a manner intended to be fair, proportionate, and understandable.
• Purpose limitation: Personal data is processed for specified service, contractual, security, support, payment, consent, analytics, advertising, compliance, and legal purposes and is not intentionally reused for a materially incompatible purpose without an additional lawful basis and any required notice or consent.
• Data minimization: We aim to process only personal data reasonably necessary for the stated purpose. Users are encouraged to use a pseudonym and avoid unnecessary real-world details.
• Accuracy and storage limitation: We take reasonable steps to correct or delete materially inaccurate server-side personal data and retain it only for the periods described below or another period that is reasonably necessary and lawful.
• Security and accountability: Reasonable technical and organizational measures are used to protect personal data and document material privacy choices, security events, and rights requests.
• Pseudonymous, not guaranteed anonymous: Ordinary use does not require a public real-name profile. IP addresses, device data, Account or session identifiers, temporary chat processing, support records, analytics identifiers, advertising identifiers, payment records, and blockchain transactions may nevertheless constitute personal data and may permit identification when combined with other information.

2. Personal data we process and its sources

2.1. The exact data processed depends on whether you browse the Service, use accountless access, create an Account, use private chat, view pre-created character media, use free or paid features, interact with an advertisement, change Cookie Settings, contact support, submit a report, or make a cryptocurrency payment.

2.2. Depending on the feature used, we may process the following categories:

• Account, session, and authentication data: Internal Account, browser, device, or session identifier; Account creation time; sign-in and authentication events; email address or external authentication identifier where the selected sign-in or recovery method uses one; language; age confirmation; interface preferences; Account status; access level; Paid Access start and expiration; and recovery or security records.
• Temporarily processed private-chat data: The current User message, the limited locally stored conversation context selected by the browser for the request, the selected AI Character, applicable Character and system instructions, safety information, and the generated reply are processed temporarily by Service and AI-provider systems to provide the requested response. Aefia does not write these messages or replies to a persistent server-side chat database, archive, application log, analytics system, persistent cache, or server backup, and the Operator does not manually review ordinary private-chat requests.
• Browser-local conversation history: Private User messages, generated replies, selected AI Character, conversation titles, timestamps, and local conversation settings stored by the website in the User's browser. Aefia cannot access that local history while it remains at rest in the browser. Only the limited context selected by the browser for a new generation request is transmitted transiently for that request. Aefia cannot remotely delete the local history and cannot retrieve, reconstruct, or restore it after local deletion.
• Character and feature interaction data: Pre-created AI Characters, pages, images, videos, plans, settings, features, or other Service items viewed, selected, requested, saved, hidden, unlocked, or used, together with timestamps and technical delivery records.
• Device, network, and request data: IP address; country or coarse location inferred from IP; browser type and version; operating system; device type; language; time zone; referrer; requested URL; user-agent information; session or storage identifiers; request and response metadata; network information; timestamps; and security signals.
• Usage, performance, and diagnostics data: Pages visited; buttons and features used; session duration; generation attempts; response latency; model or provider routing; errors; failed requests; rate-limit events; crash or diagnostic information; and aggregated or event-level operational measurements. Aefia does not place ordinary private-message bodies, generated replies, conversation titles, wallet addresses, transaction hashes, or other sensitive content in persistent diagnostic logs or analytics events.
• Moderation, security, fraud, and abuse data: Automated safety results and rule-category signals that do not contain a persistent copy of the message body; bot, scraping, credential-abuse, payment-fraud, and invalid-advertising-activity signals; blocked-request metadata; suspicious activity; Account restrictions; reports; appeals; and limited textual evidence voluntarily supplied by a User through an official form. Aefia does not maintain a persistent archive of ordinary chat prompts or replies for moderation or human review.
• Support, privacy, and legal-request data: The text entered into support, privacy, copyright, illegal-content, child-safety, payment, and appeal forms; request category; relevant Account, session, URL, advertisement, or transaction identifiers; safe reply contact voluntarily provided; verification information reasonably necessary to protect the requester or Account; and records of acknowledgment, investigation, response, and resolution. Official Aefia forms accept text, URLs, references, and identifiers only; file and media uploads are not supported.
• Cryptocurrency payment and access data: Invoice or payment identifier; payment status; amount; cryptocurrency asset; blockchain network; timestamp; transaction hash; destination address; limited sending-wallet information visible to the processor or public blockchain; confirmation status; fixed access period; activation record; refund address where provided; reconciliation information; and fraud or risk signals. We do not request seed phrases, private keys, full wallet or exchange passwords, one-time authentication codes, or bank-card details for the current cryptocurrency-only payment flow.
• Cookie, local-storage, consent, and privacy-choice data: First-party cookie or local-storage identifiers; browser-local chat history; age-gate status; consent status; consent timestamp; region; category, purpose, or vendor choices; consent-management string where used; policy or interface version; withdrawal records; advertising opt-outs; and recognized browser privacy signals where legally required and technically supported.
• Google Analytics data: After the required analytics choice, Google Analytics 4 with Measurement ID G-EEJTYM7NBC may process the _ga and _ga_EEJTYM7NBC identifiers, page location, page title, referrer, timestamps, browser and device information, approximate geographic information, session state, configured events, and aggregated engagement. Private chat text and generated replies are not intentionally sent to Google Analytics.
• Advertising and ad-measurement data: Where advertising is active and permitted by the User's choice, TrafficStars and related advertising infrastructure may process IP address, browser and device characteristics, cookie or advertising identifiers, country or coarse location, page URL, referrer, consent signal, ad-zone information, advertisement category, impressions, viewability, clicks, conversions, frequency information, auction data, and fraud or security signals.
• Communications: Transactional notices, service announcements, support correspondence, and any optional marketing preference or consent. Optional direct marketing is not sent without a lawful basis and any consent required by applicable law.

2.3. Personal data may be provided directly by you; generated automatically by your browser, device, Account, session, or wallet; transmitted temporarily during an AI request; inferred from limited technical data such as IP-derived country; received from AI, hosting, security, analytics, advertising, authentication, communications, or payment providers; obtained from public blockchain records associated with a payment; or created through fraud-prevention, support, and compliance processes.

2.4. Users cannot upload files or media, publish, distribute, or create public character profiles, galleries, images, videos, or other public media through the current Service. Official support, privacy, payment, and reporting forms accept text, URLs, references, and identifiers only. Text entered into private chat is not made public. Private support, privacy, payment, and reporting submissions are not public posts.

3. Purposes and legal bases

3.1. The legal basis depends on the data, purpose, User location, Operator location, and applicable law. Different legal bases may apply to different parts of the same interaction.

• Providing the requested Service — contract: Account, session, temporary chat, browser-local preference, feature, transaction, and technical data may be processed where necessary to create and maintain access, route a prompt, temporarily process the limited browser-supplied context, generate and deliver an AI reply, display pre-created character media, authenticate a User, activate fixed-term Paid Access, and otherwise perform the Terms of Service or take requested steps before a purchase.
• Browser-local conversation continuity — requested functionality and, where required, consent: Conversation history is saved by default in first-party browser storage to keep the requested chat available on the same browser profile. The Cookie Policy explains the applicable device-storage basis and any separate regional consent requirement. Aefia does not receive a persistent server-side copy merely because the browser stores the history.
• Cryptocurrency payments — contract, legal obligation, and legitimate interests: Payment and blockchain data may be processed to create an invoice, detect and confirm a transaction, associate it with the correct Account or session, activate access, reconcile payments, investigate errors, process an approved refund, prevent fraud, satisfy accounting or legal obligations, and establish or defend claims.
• Security and abuse prevention — legitimate interests and legal obligation: Limited Account, session, device, network, request-metadata, automated rule-category, and fraud data may be processed to protect Users and infrastructure, enforce access controls, prevent underage access, detect attacks and scraping, investigate fraud, protect advertising integrity, and comply with binding legal duties. Ordinary message bodies and generated replies are not retained as a moderation archive and are not made available through an Operator chat-viewing interface.
• Support and legal requests — contract, consent, legal obligation, and legitimate interests: Contact and request data may be processed to respond to a User, verify authority, resolve technical or payment problems, handle privacy rights, review copyright and illegal-content notices, document decisions, protect affected persons, and comply with procedural duties.
• Strictly necessary device storage — applicable exemption: Cookies or similar storage may be used where genuinely necessary for security, sessions, authentication, consent storage, age-gate continuity, checkout continuity, or a feature expressly requested by the User, as described in the Cookie Policy.
• Google Analytics — consent: Where applicable law requires consent, Google Analytics 4 with Measurement ID G-EEJTYM7NBC is activated only after the User grants the analytics choice. It is used to measure traffic, sessions, pages, technical performance, errors, and aggregated engagement. Aefia uses a basic consent implementation in the affected jurisdictions, so Google Analytics does not load before consent.
• Optional advertising and personalized or targeted advertising — consent: Where applicable law requires consent to store or access information on a device or to process data for personalized advertising, targeted advertising, audience creation, retargeting, or similar purposes, the relevant processing begins only after the required affirmative choice.
• Contextual or limited advertising — consent or another lawful basis: Where permitted, contextual, limited, or non-personalized advertising may use limited page, device, security, and consent information under the legal basis available for the specific processing. Device storage remains subject to applicable cookie rules.
• Sensitive or special-category chat data — explicit consent or another narrow legal condition: Where temporary private-chat processing reveals or clearly implies sex life, sexual orientation, health, religion, ethnicity, political views, or another legally protected category, processing relies on explicit consent where that condition is required and available. Limited processing may also occur where another narrow legal condition applies, such as protection of vital interests or establishment, exercise, or defense of legal claims.
• Service reliability and improvement — legitimate interests or consent: Minimized technical, usage, and aggregated data may be processed to measure reliability, investigate errors, improve safety, manage capacity, and evaluate features where the Operator's interests are not overridden by Users' rights. Aefia does not use a persistent server-side archive of private conversations for product improvement because no such archive exists.
• Legal compliance and protection — legal obligation, legitimate interests, and vital interests: Server-side data may be processed or preserved where reasonably necessary to comply with applicable law, court orders, accounting duties, valid authority requests, child-protection obligations, or to protect a person from a serious and imminent threat. Aefia cannot preserve or recover browser-local chat history that it does not possess.

3.2. We do not intentionally use private chat text for analytics or advertising and do not include private messages, generated replies, conversation summaries, intimate preferences, or sensitive classifications in analytics events, advertising requests, page URLs, referrers, audience segments, or conversion events.

3.3. We do not sell private chat text, generated replies, passwords, payment credentials, or wallet secrets. Disclosure of online identifiers or advertising data may nevertheless be legally classified as a sale, sharing, targeted advertising, or cross-context behavioral advertising in some jurisdictions even where no money is paid. Applicable opt-outs are described below.

4. AI processing and sensitive adult-chat data

4.1. To generate a reply, the User's browser sends the current message, the limited locally stored conversation context selected for that request, the selected AI Character instructions, settings, safety information, and limited technical metadata through Aefia to one or more AI or model-infrastructure providers. The amount of context depends on the active feature, model, technical limits, safety requirements, and conversation settings.

4.2. Aefia processes the message and returned reply only transiently in memory or request transport for generation and delivery. Aefia does not write ordinary User messages or generated replies to a persistent server-side chat database, application or reverse-proxy log, analytics platform, persistent cache, or server backup, and the Operator has no administrative chat viewer for ordinary conversations. An AI or model-infrastructure provider may process or temporarily retain API content under the applicable provider agreement for delivery, security, abuse prevention, reliability, or legal compliance.

4.3. Where applicable law requires explicit consent for processing sensitive or special-category data voluntarily entered into adult chat, that consent must be obtained through a separate affirmative choice. It is distinct from age confirmation, acceptance of the Terms, cookie consent, analytics consent, advertising consent, or payment.

4.4. You may withdraw sensitive-chat consent prospectively through available Account controls or the Privacy Contact Form. Withdrawal does not affect processing that was lawful before withdrawal. It may disable the affected chat feature. Locally stored history remains on your device until you delete it through the chat menu or browser settings. Aefia cannot remotely erase or restore browser-local history because Aefia has no persistent copy.

4.5. Aefia has no persistent conversation archive or administrative chat viewer for routine or investigative manual review. The Operator can read private-chat text only when the User voluntarily copies and submits that text through an official support, privacy, payment, reporting, or appeal form or correspondence channel. A legal request cannot give Aefia access to a browser-local or server-side chat archive that Aefia does not possess.

• No analytics or advertising use: Private messages, generated replies, conversation summaries, intimate preferences, and sensitive-chat classifications are not intentionally sent to Google Analytics 4 or TrafficStars for measurement, advertisement selection, or audience creation.
• No persistent Aefia chat archive: Aefia never stores ordinary User messages or generated replies as persistent server-side chat history and provides no administrative chat viewer for opening ordinary conversations.
• No manual review of ordinary chats: The Operator does not manually review ordinary private chats. The Operator can read chat text only when a User voluntarily copies and submits it through an official text-based channel.
• No recovery after local deletion: After a User deletes a conversation or all Aefia site data from the browser, Aefia cannot recover it because Aefia has no server-side copy.
• No real-person exploitation: Users must not use the Service to identify, profile, expose, threaten, blackmail, discriminate against, or exploit an identifiable real person.
• No guaranteed transmission secrecy: Chats are not public and persistent history stays in the browser, but current messages must travel through online infrastructure to generate replies. No network, browser, or provider can be guaranteed completely secure.
• No Aefia model training from stored chats: Aefia does not use a persistent server-side archive of identifiable private chat content to train a public or general-purpose model because Aefia does not maintain such an archive.
• Minimized improvement use: Aggregated technical measurements, de-identified operational information, and user-supplied reports may be used to investigate failures, evaluate safety, prevent abuse, and improve reliability where lawful and subject to appropriate safeguards.

5. Recipients, advertising, and international transfers

5.1. Personal data is disclosed only where reasonably necessary for the purposes described in this Policy. Depending on the feature, recipients may include:

• AI and model-infrastructure providers: Providers that receive the current prompt, limited browser-supplied conversation context, AI Character instructions, settings, and technical metadata to generate replies, route requests, host models, perform automated safety checks, detect abuse, and support reliability. Aefia does not supply a persistent server-side chat archive because no such archive exists. Provider-side access, temporary retention, and processing are governed by the applicable provider agreement and provider practices.
• Hosting, database, CDN, and backup providers: Providers that host the website, APIs, Account and payment databases, static assets, encrypted connections, non-chat server logs, consent records, support records, and backups required to operate and protect the Service. Aefia's databases and server backups do not contain persistent ordinary chat history.
• Authentication, communications, and support providers: Providers used for sign-in, Account recovery, transactional notices, form delivery, support, and case management where those features are enabled.
• Security, anti-abuse, and fraud providers: Providers used, where enabled, for DDoS protection, bot detection, rate limiting, malware protection, vulnerability monitoring, incident response, fraud screening, transaction-risk assessment, and enforcement of Service rules. Aefia does not provide these services with a persistent archive of ordinary private chats.
• Analytics provider — Google Analytics 4: After the required analytics choice, Google LLC may process pseudonymous identifiers and website-usage data for Measurement ID G-EEJTYM7NBC. Aefia configures user-level GA4 event-data retention to 14 months. Private chat messages and generated replies are not intentionally sent to Google Analytics.
• Advertising partner — TrafficStars: Where advertising is enabled and the applicable privacy choice permits it, TrafficStars may deliver, secure, limit, and measure advertisements and process the advertising and device data needed for those functions, subject to applicable terms, privacy information, choices, and law.
• Cryptocurrency payment infrastructure: Wallet, node, explorer, payment, blockchain-monitoring, transaction-risk, and related providers used to create invoices, detect confirmations, identify payment errors, assess risk, activate Paid Access, and process approved refunds.
• Professional advisers: Lawyers, accountants, auditors, insurers, and other advisers where disclosure is reasonably necessary for compliance, accounting, risk management, or legal claims and subject to appropriate duties.
• Business transfers: Actual or prospective parties to a lawful reorganization, financing, merger, acquisition, asset transfer, or sale, subject to necessity, confidentiality, applicable notice, and data-protection requirements.
• Authorities, courts, rights holders, and affected persons: Courts, regulators, law-enforcement bodies, emergency or child-protection authorities, rights holders, service providers, or affected persons where disclosure is legally required or reasonably necessary to respond to a valid request, protect a person from serious harm, investigate fraud or unlawful activity, handle a copyright or illegal-content report, or establish, exercise, or defend legal rights.
• Independent third-party destinations: Advertisers, websites, wallets, exchanges, and other services reached through links may collect information directly from you under their own terms and notices. Their independent processing is not controlled by this Policy.

5.2. Depending on where the Operator, User, and providers are located, personal data may be processed outside the country in which the User lives. Where applicable law restricts international transfers, the transfer should rely on an adequacy decision, standard contractual clauses, the UK International Data Transfer Agreement or Addendum, another recognized safeguard, or a lawful derogation, together with supplementary measures where appropriate.

5.3. Information about the categories of transfer safeguard used for a relevant provider may be requested through the Privacy Contact Form, subject to confidentiality, security, and legal limitations.

5.4. Public blockchain records are distributed across independent network participants and may be permanently visible. The Operator cannot alter or erase a confirmed public blockchain transaction. Browser-local chat history is different: it is controlled by the User's browser and, once locally deleted, cannot be recovered by Aefia.

6. Cookies, local storage, analytics, advertising choices, and browser signals

6.1. The Service uses cookies, browser local storage, session storage, consent-management tools, and similar technologies for security, sessions, age-gate continuity, local conversation continuity, checkout, privacy choices, Google Analytics 4, and advertising. The current technologies, exact storage keys, providers, purposes, categories, and durations are described in the Cookie, Local Storage, Analytics and Advertising Technology Policy at /cookies and Cookie Settings.

6.2. Conversation history is saved by default in first-party browser local storage as part of the standard same-browser conversation-continuity feature and can be deleted through the chat menu. Aefia does not receive or maintain a persistent server-side copy, and the Operator has no chat viewer for opening that local history. Where applicable law requires a separate prior choice for persistent device storage, that choice must be obtained in the affected jurisdiction.

6.3. Google Analytics 4 with Measurement ID G-EEJTYM7NBC and non-essential TrafficStars advertising storage are activated only after legally valid consent where required. For affected jurisdictions, Aefia uses a basic Google consent implementation: Google Analytics does not load or send analytics requests before analytics consent.

6.4. The consent interface should identify applicable advertising purposes and choices, preserve evidence of the choice, and make rejection and later withdrawal as easy as acceptance.

6.5. Where personalized-advertising consent is unavailable, the Service may use contextual, limited, non-personalized, cookieless, or no advertising, depending on applicable law and partner capabilities.

• Cookie and vendor choices: Use Cookie Settings to accept, reject, or customize Analytics and Advertising choices and, where supported, review individual advertising vendors and purposes.
• Local chat deletion: Use the chat menu to delete one conversation or all locally stored history. Aefia cannot perform this deletion remotely and cannot recover locally deleted history.
• Withdraw consent: You may withdraw consent for optional analytics, advertising, or sensitive-chat processing at any time. Withdrawal applies prospectively and does not affect processing that was lawful before withdrawal.
• Opt out of sale, sharing, or targeted advertising: Where applicable law classifies advertising disclosures as sale, sharing, targeted advertising, or cross-context behavioral advertising, use Cookie Settings or the Privacy Contact Form to submit the applicable opt-out.
• Limit sensitive personal data: Where applicable law provides such a right, you may request that qualifying server-side sensitive personal data be limited to uses necessary to provide requested features, protect security, or perform another legally permitted purpose. Browser-local chat history remains under the User's direct control.
• Recognized browser signals: Where legally required and technically supported, a recognized opt-out preference signal such as Global Privacy Control is treated as an opt-out for the relevant browser or device. A non-standardized Do Not Track signal may not communicate a legally enforceable choice.
• No unlawful discrimination: The Operator will not unlawfully discriminate against a User for exercising an applicable privacy right. Some optional or personalized features may operate differently where the data or consent needed for that feature is unavailable.

6.6. Rejecting analytics or advertising technologies does not prevent access to core Service content. Browser controls may delete local history, sign the User out, reset preferences, remove consent records, interrupt checkout, or require a new privacy choice.

7. Security, retention, deletion, and incidents

7.1. We use reasonable technical and organizational measures designed to protect personal data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access. Measures may include HTTPS/TLS, access controls, secret management, password hashing where passwords are used, logging without private-chat bodies, monitoring, rate limits, provider controls, minimization, backup controls, and incident response. Aefia does not provide the Operator with an administrative chat viewer or maintain a server archive of ordinary conversations. No website, transmission method, browser, AI provider, blockchain, or storage environment can be guaranteed completely secure.

• Access limitation: Access to server-side personal data is limited to authorized persons and providers with a reasonable operational, support, security, compliance, or legal need. No person has access to an Aefia server-side archive of ordinary private chats because no such archive exists. Access to other server-side data may be restricted, logged, reviewed, and removed when no longer necessary.
• Account and session data: Retained while the Account, session, or related access remains active and thereafter only as reasonably necessary for deletion processing, security, fraud prevention, disputes, legal claims, and compliance. Following a verified deletion request, qualifying active-system Account data is generally scheduled for deletion or de-identification within 30 days unless a lawful exception applies.
• Persistent private-chat history: Stored only in the User's browser, not on Aefia's server. Aefia never maintains a persistent server-side database, archive, log, analytics record, cache, or backup of ordinary User messages or generated replies, and the Operator has no administrative chat viewer.
• Deletion and recovery of local chat history: Deleting a conversation, deleting all history through the chat menu, clearing Aefia site data, removing the browser profile or PWA, or clearing browser storage permanently removes the only persistent copy available through Aefia. Aefia cannot remotely erase, retrieve, reconstruct, or restore that deleted history because Aefia has no copy.
• Temporary AI processing: The current message and limited browser-supplied context are processed transiently by Service and AI-provider systems to generate and return a reply. They are not written by Aefia to a persistent chat database, application or reverse-proxy log, analytics platform, persistent cache, or server backup and are not manually reviewed by the Operator.
• Accountless access: Server-side data connected only to a browser, device, session, or pseudonymous identifier is retained for the period needed to provide the feature, apply limits, maintain security, and resolve payment or support issues. If the identifier is deleted or unavailable, we may be unable to locate or verify associated server-side data.
• Security and technical logs: Typically retained for up to 12 months. Logs may contain timestamps, IP addresses, request routes, response status, rate-limit events, provider status, error codes, and security signals, but Aefia does not store ordinary private-message bodies or generated replies in persistent logs. Relevant metadata may be kept longer where reasonably necessary to investigate an incident, prevent repeat abuse, comply with law, or establish, exercise, or defend legal claims.
• Support and privacy requests: Typically retained for up to 3 years after closure so the Operator can document the request and response, manage appeals, prevent abuse, and demonstrate compliance, unless a shorter or longer period is appropriate or required.
• Copyright, illegal-content, and safety reports: Typically retained for up to 5 years after closure so the Operator can document the report, evidence, response, counter-notice, appeal, and repeat-violation history, unless a shorter or longer period is appropriate or required.
• Cryptocurrency payment and accounting records: Invoice, activation, transaction, refund, reconciliation, fraud-prevention, tax, and accounting records may be retained for up to 7 years or another period required by applicable law. Public blockchain records are maintained independently and cannot be deleted by the Operator.
• Consent and privacy-choice records: Records reasonably necessary to demonstrate consent, rejection, withdrawal, policy version, region, category or vendor choice, and advertising opt-outs may be retained during the relevant processing and for a reasonable limitation period afterward, typically up to 5 years unless applicable law requires a different period. These records do not contain private chat text.
• Reports, restrictions, and legal holds: Textual evidence voluntarily supplied in a report and server-side records connected to fraud, security, invalid advertising activity, copyright, illegal content, child safety, serious harm, or a legal dispute may be retained for as long as reasonably necessary to investigate, prevent recurrence, handle an appeal, comply with a preservation duty, or establish, exercise, or defend legal claims. A legal hold cannot preserve or create browser-local or server-side chat history that Aefia never possessed.
• Server backups: Restricted server backups may contain Account, payment, support, consent, and technical data until ordinary backup rotation. They do not contain persistent ordinary chat history. If a backup is restored after an incident, previously valid deletion requests should be reapplied where reasonably possible.
• De-identification and aggregation: Server-side data may be irreversibly de-identified or aggregated where reasonably appropriate and lawful. We do not intentionally re-identify de-identified data except to test de-identification, investigate security, or comply with law.
• Data incidents: If a personal-data breach creates a notification obligation, the Operator will notify the competent authority and affected individuals as required by applicable law, taking account of the nature, scope, context, and likely risk of the incident.

8. Privacy rights and request procedure

8.1. Depending on your location, the nature of the processing, and applicable law, you may have rights to receive information; access server-side personal data held by Aefia; obtain a copy; correct inaccurate data; delete data; restrict or object to processing; withdraw consent; receive portable data; opt out of direct marketing; opt out of sale, sharing, targeted advertising, or qualifying profiling; limit certain uses of sensitive personal data; obtain information about international-transfer safeguards; request human review of a qualifying automated decision; appeal a privacy decision; and complain to a supervisory authority.

8.2. These rights are not absolute. A request may be limited where lawful, including where identity or control cannot be reliably verified, retention is required by law, deletion would adversely affect another person, data is needed for security or legal claims, the request is manifestly unfounded or excessive, or another statutory exception applies. Aefia cannot provide, search, export, remotely delete, or restore browser-local chat history or a server-side chat archive that is not in Aefia's possession.

8.3. The Operator may request information reasonably necessary to verify that the requester controls the relevant Account, safe reply contact, transaction, browser, device, or session. Verification will be proportionate to the sensitivity and risk. The Operator will not request a seed phrase, private key, full password, one-time code, or unnecessary government identity document.

How to exercise a privacy right

• Submit a request through the Privacy Contact Form on this page. Clearly identify the requested action and provide only the minimum information necessary to locate the relevant server-side data and respond safely.
• For access, correction, deletion, portability, restriction, or objection, provide the internal Account ID or the same safe reply contact associated with the Account where available.
• For accountless access, provide an available session, browser, payment, consent, or technical reference. The Operator may be unable to locate data where the relevant pseudonymous identifier no longer exists.
• To delete locally stored chat history, use the chat menu to delete one conversation or all history, or clear Aefia site data in browser settings. Aefia cannot perform this action remotely and cannot restore the data afterward.
• To withdraw sensitive-chat consent, select the relevant request type. Withdrawal affects future temporary processing and may disable the affected chat feature. It does not remotely delete browser-local history.
• To change Google Analytics or advertising choices, use Cookie Settings. Where applicable, an opt-out may also be submitted through the form or a recognized browser preference signal.
• For deletion, specify whether the request concerns the Account, support records, consent records, payment-related profile data, analytics or advertising data, or another category held by Aefia. Do not request remote deletion of browser-local history through this form.
• An authorized agent may submit a request where applicable law permits. Evidence of authorization and direct verification with the User may be required.
• If a request is denied and applicable law provides an appeal right, submit an appeal through the same form with the previous reference and any material new explanation or evidence.
• You may complain to the data-protection or privacy authority in the country or state where you live, work, or believe a violation occurred. Contacting the Operator first is not required where applicable law gives a direct complaint right.

Automated processing and human review

AI generation, temporary safety classification, fraud detection, rate limiting, analytics, advertising selection, and security controls involve automated processing and may create technical classifications or risk scores. The Service does not intend to make solely automated decisions that produce legal or similarly significant effects on Users. Where applicable law grants a right to human review or challenge for a qualifying decision, use the Privacy Contact Form.

The Operator aims to respond to a verified privacy request within 30 days. A different statutory period may apply, including one month under GDPR-style laws or up to 45 days under certain U.S. state laws, with an extension where legally permitted for complex or numerous requests. Notice of an extension will be provided where required. Requests are ordinarily handled without charge except where applicable law permits a reasonable fee or refusal for a manifestly unfounded, excessive, or repetitive request.

The Operator will not unlawfully discriminate against a User for exercising an applicable privacy right. Some optional or personalized features may operate differently where the data or consent needed for that feature is unavailable.

9. Changes, complaints, related documents, and contact

9.1. This Policy may be updated when the Service, providers, data practices, AI features, browser-storage architecture, analytics integration, advertising integration, payment flow, security measures, retention periods, or legal requirements change. The Last updated date identifies the current published version.

• Material changes: If a change materially affects how personal data is used or materially reduces a privacy protection, additional notice may be provided through the Service, an Account notice, email, or another available contact method. Where a new consent is legally required, the new processing will not begin until that consent is obtained.
• No consent by silence: Continued use may acknowledge an updated notice where applicable law permits, but silence, continued browsing, passing an age gate, accepting the Terms, or making a payment does not by itself create valid consent for processing that requires a separate affirmative choice.
• Privacy questions and rights requests: Use the Privacy Contact Form on this page for privacy questions, complaints, access, correction, deletion of server-side data, portability, restriction, objection, consent withdrawal, analytics or advertising opt-outs, sensitive-data limitation requests, automated-decision review, transfer-safeguard requests, and appeals.
• Local chat-history control: Use the chat menu or browser site-data controls to delete locally stored conversation history. Aefia cannot access or delete it remotely and cannot retrieve, reconstruct, or restore it after deletion.
• Other support: Use /feedback for general technical, Account, security, activation, and payment support. Use /feedback for copyright, illegal-content, child-safety, non-consensual intimate-content, real-person likeness, or advertisement reports.
• Related documents: This Policy should be read together with the Terms of Service at /terms, Cookie, Local Storage, Analytics and Advertising Technology Policy at /cookies, Acceptable Use, Age and Content Safety Policy at /acceptable-use, Cryptocurrency Payments, Activation and Refunds Policy at /payments-refunds, Copyright, DMCA, DSA and Illegal Content Policy at /copyright, AI Content and 2257 Compliance Statement at /2257, Cookie Settings, and any just-in-time notice displayed when data is collected.
• Independent providers: An advertiser, wallet, exchange, payment tool, destination website, analytics provider, or other independent provider may publish its own privacy notice. Review that notice before supplying personal data directly to the provider.

Privacy Contact Form

Use this text-only form for privacy questions and rights requests concerning data held or controlled by Aefia. Browser-local chat history is not held by Aefia: delete it through the chat menu or browser site-data controls. Aefia cannot remotely access, delete, retrieve, reconstruct, or restore it. File and media uploads are not supported. Provide only the minimum information necessary. Never submit passwords, one-time codes, private keys, seed phrases, wallet passwords, full payment credentials, exchange credentials, unlawful intimate imagery, suspected child sexual abuse material, private chat content, or unnecessary identity documents.