Your privacy

Who this covers

These Terms explain how Erotic Reads collects, uses, stores, and shares information when you visit or use the Service. Erotic Reads is for adults 18 and over; we do not knowingly collect personal information from anyone under 18.

Information you give us

Depending on what you do, we may collect:

• your email address, verification status, display name, password hash, avatar, and account settings;
• short-lived hashed tokens used for email verification and password recovery;
• two-factor authentication and encrypted-messaging setup data;
• submission titles, author, reader or uploader credits, work type, source and rights information, summaries, excerpts, notes, audio files, and cover images;
• private-message text and image attachments as encrypted application records, plus sender, recipient, timestamps, read status, and other delivery metadata needed to route them;
• when you connect Patreon, Patreon user and membership identifiers, campaign and tier information, entitlement and charge status, trial or membership history, synchronization times, and encrypted OAuth access and refresh tokens;
• information you send when you contact us, report content, or make a copyright request.

Please do not include unnecessary sensitive personal information in a submission, reader note, message, or support request.

Information collected automatically

The Service and its hosting infrastructure may receive ordinary technical information such as IP address, browser and device type, timestamps, referring page, request information, and security or error logs. We use this information to deliver pages, prevent abuse, troubleshoot failures, and protect the Service.

The age gate stores a confirmation in your browser’s local storage. The submission form may also save an unfinished text draft in local storage on your device; selected audio and image files are not saved in that draft. Authentication uses a session cookie. Private-message keys are managed by the Service rather than stored in your browser, so password resets and new-device sign-ins work normally. The installable app caches only a small offline shell and icons; accounts, APIs, and recordings remain network-only.

How we use information

We use information to:

• create and secure accounts, verify email addresses, recover passwords, authenticate members, and provide account features;
• receive, review, publish, unpublish, and manage readings and related rights information;
• encrypt, store, and route private messages and show delivery or unread status;
• link a Patreon identity, verify membership status, prevent repeated trial offers based on observed history, and apply or remove membership benefits;
• send editorial notifications to eligible admins and moderators unless they disable them;
• send account, review-decision, and optional new-message notification emails;
• respond to support, privacy, safety, and copyright requests;
• maintain security, enforce our Terms, prevent fraud and abuse, and comply with law; and
• improve reliability and understand technical failures, without selling your personal information.

When information is shared

We share information with people and providers who help operate the Service, such as hosting, storage, database, security, email delivery, and infrastructure providers. Account and notification emails are delivered through Resend. They may process information only as needed to provide those services or comply with law.

Moderators and administrators can access account and submission information needed for editorial review, safety, support, and Service administration. Approved metadata, cover images, and recordings are public through the library. For a pre-existing recording, the account screen name is presented publicly as the uploader rather than as the performer. If you message another member, the Service delivers the message and any attached image through the authenticated application.

If you connect Patreon, information is exchanged with Patreon through its authorization, membership API, and webhook services so that we can confirm your benefits. Erotic Reads does not receive or store your full payment-card details. Patreon processes membership billing under its own privacy policy.

Editorial cover searches may send book-title or author queries and a courtesy contact identifier to Open Library. We may also disclose information to comply with a valid legal process, respond to an emergency, protect rights and safety, investigate abuse, or support a business transfer. We do not sell personal information.

Free accounts may be shown advertising supplied by ExoClick. Loading or interacting with an ad may allow ExoClick and participating advertisers to receive technical identifiers and information such as IP address, browser or device details, page context, ad impressions, and clicks, and they may use cookies or similar technology subject to their own policies and applicable consent requirements. Paid members, moderators, and administrators do not load the ad-provider script while their ad-free benefit is active.

Some providers may process information in other countries, where it may be subject to different privacy laws and lawful access by courts, law enforcement, or national-security authorities. Their own terms and privacy policies govern their independent processing.

Encrypted messages

Message text and attached images are encrypted in transit and at rest using the Service's application-managed encryption key. The application decrypts message content only for an authenticated participant viewing a conversation, which allows password resets and new-device access to work normally. Authorized service operations could technically access this content when needed for security, support, or legal compliance. We do not sell message content or use it for targeted advertising.

No security system is perfect. Your device, browser extensions, a recipient, recovery material, or a compromised account may expose content. Encrypted messages may also be retained as needed to deliver them, show conversation history, prevent abuse, or comply with law.

Retention and deletion

We keep information for as long as needed to provide the Service, maintain security, resolve disputes, meet legal and accounting obligations, and enforce our agreements. Session cookies expire after seven days unless replaced by a new session. Verification and password-reset records expire automatically and are removed when used or replaced.

Patreon connection records are kept while the account remains linked. Disconnecting removes the current local connection and benefits but does not cancel Patreon billing. Limited trial and prior-membership history may be retained across disconnecting and reconnecting to prevent an ineligible repeat trial. Closing the Erotic Reads account removes that stored Patreon history from the active database, subject to backups, security records, disputes, and legal obligations.

You can update profile information and close your account from the account settings. Closing an account removes the account, credentials, sessions, avatar, and unapproved submissions. An approved reading may remain in the public library with the reader or uploader credited as “Former member,” because it has become part of the moderated collection. Backups, legal records, and security logs may persist for a limited period before normal deletion.

Your choices

You may access and update account details through your account page, remove your avatar, disable optional editorial or message notifications, disconnect Patreon locally, and request account closure. Patreon billing must be cancelled through Patreon. You may also contact us to ask about access, correction, deletion, or a copy of personal information, subject to identity verification and any information we must retain by law.

Depending on where you live, you may have additional privacy rights. We will handle valid requests under the law that applies to you. We may need to keep information that is necessary for safety, legal claims, copyright disputes, or other legitimate obligations.

Security and changes

We use measures appropriate to the Service, including password hashing, secure session cookies in production, origin checks on account-changing requests, access controls, and encrypted messaging design. No transmission or storage method can be guaranteed perfectly secure, so please use a unique password and protect your devices and recovery codes.

We may update this Policy when the Service or applicable requirements change. The current version will always be posted here with its effective date.

Privacy questions and requests can be sent to [email protected].

Last updated September 18, 2026