1. Scope and data operator
This policy describes processing by the Readeep operating entity/individual listed below within Studio and related publication flows. Studio and Reader may share account identity and sign-in sessions. Google, AI providers and services outside Readeep have their own policies.
2. Data processed
Account data includes Google identifiers, email, display name, avatar, roles, preferences and terms acceptance records. Google handles authentication; Readeep does not request your Google password.
Writing data includes workspaces, members, drafts/versions, characters, worldbuilding, imported references, AI requests, outputs, summaries and semantic search data. Publication data includes author/organization profiles, covers, sources, rights and AI declarations, submissions, feedback and schedules.
Operational data may include sessions, IP and device/browser details in technical logs, processing activity, providers/models, tokens, credits, plans and transactions when enabled. Configured API keys are processed to connect providers. Support and complaint records may contain information you send.
3. Purposes and legal bases
Readeep processes data for authentication, collaboration permissions, project storage/processing, AI tasks, service usage management, moderation/publication, support and complaints, system protection and legal duties.
Each activity must have an appropriate legal basis. Where consent is required, Readeep must provide information and obtain valid consent for that purpose. Accepting terms or reading this policy does not replace separately required consent. New purposes cannot simply be inferred from uploading content.
4. Who can access content
Workspace drafts and references are accessible according to member permissions. Authorized personnel may access them as necessary for operations, support, security or legal duties. Moderators may process submissions and rights evidence.
After approval and scheduled release, work details, pen name/public profile, cover and released chapters become reader-accessible. Search engines or others may retain publicly released data. Removal from Readeep cannot guarantee immediate deletion of independent external copies.
5. Technical providers, AI and transfers
Relevant data may go to authentication, storage, backup, infrastructure or AI providers to deliver features. Writing, reference analysis, summaries, semantic search or content assessments may require prompts, excerpts or relevant content. Providers/models depend on platform/workspace configuration. Avoid unnecessary secrets or personal data in prompts.
Providers may process data abroad. Use must satisfy applicable protection and transfer requirements. Readeep must identify recipients, scope and necessary conditions before processing. Do not assume every provider has the same retention period or no-training commitment. Permission to operate Studio does not itself grant rights to train general-purpose models on private drafts.
Necessary data may also be provided to competent authorities or parties to a case on an appropriate legal basis. Submitting for publication does not itself make rights documents or private contact details public.
7. Retention and security
Retention depends on service purposes, account/content status and legal requirements. Submissions, transactions or dispute records may be needed as evidence or to resolve obligations. Data must be appropriately deleted or anonymized when no basis for retention remains. Backups may require a separate processing cycle and cannot justify continued public display of removed content.
Readeep applies appropriate access controls, credential protection and backup management. No system guarantees absolute security. Protect devices, accounts and API keys, review workspace membership and report suspected incidents through the contact channel.
8. Your rights and requests
Subject to applicable legal conditions, you may be informed, access, correct, request provision/deletion/restriction of data, object, withdraw consent, complain or seek compensation. Email the listed contact. Readeep may verify identity proportionately and responds within applicable statutory deadlines.
Legal exceptions, evidence retention or others’ rights may limit requests; Readeep must explain why it cannot comply. Withdrawal does not invalidate earlier lawful processing and may prevent dependent features from operating. Specify whether you seek story removal, account deletion or both, as their scope differs.
9. Children’s data and policy changes
Do not provide children’s or others’ personal data without a lawful basis and necessary consent/representation. Contact Readeep if data has been supplied inappropriately.
Readeep publishes updated versions and notifies material changes. New processing purposes requiring consent must receive it before processing. This policy does not remove Readeep’s data protection duties.
10. Operator and contact
Send support requests, copyright notices or personal data requests to the contact below. Identify the request and relevant account or URL. Supply only necessary evidence and redact unrelated sensitive information.
- Operating entity/individual
- Not yet provided
- Contact address
- Not yet provided
- Contact email
- Not yet provided