Privacy Policy

1. Overview

Entangled Text (“we”, “us”) is an AI-assisted fiction writing studio at entangledtext.com. This policy explains what we collect, why we collect it, how long we keep it, and the choices you have. It applies to the website, dashboard (Story Studio), public guides and tools, and related services.

We do not sell your personal data. We do not use your manuscripts to train third-party foundation models.

2. Information we collect

Account data: Username, email, hashed password, optional display name, preferences, and security settings (for example two-factor authentication status).

AI keys you connect: On Free, AI runs on an API key you connect from a provider such as DeepSeek, OpenAI, Anthropic, Google Gemini, xAI or OpenRouter; Pro and Ultra subscribers may add one too. We store the key encrypted (AES-GCM), use it only for requests you start, show only its last characters, and delete it when you remove it or close your account. Pro and Ultra AI otherwise uses platform-managed credentials. See Security.

Project content: Titles, outlines, chapters, revision history, export artifacts, and related studio metadata required to operate the product.

Billing data: If you subscribe to Pro or Ultra or buy a word top-up, our payment processors — Stripe and PayPal — handle your card or PayPal details directly. We store subscription status, a processor customer reference, and ledger entries needed for support and tax records — never full card numbers.

Usage & security logs: Approximate request metadata (timestamps, endpoint class, IP, user agent), rate-limit events, and admin audit events. These exist for reliability, abuse prevention, and security investigation — not for advertising profiles.

Communications: Messages you send via contact forms, support chat, or email, plus newsletter subscription status if you opt in. When you ask Kestrel for help and she passes your question to our support desk, that question and the reply are handled as a support message and appear in our support inbox; the rest of your conversation with her does not.

Public tools in the browser: Many /tools analyzers run locally in your browser. Manuscript text for those local tools is not uploaded to our servers for analysis. Signed-in features (cloud save, optional AI panel art, etc.) may store what you explicitly save.

3. How we use information

• Provide Story Studio features (generate, edit, export, beta-reader shares)
• Authenticate you, protect accounts, and enforce rate limits
• Process subscriptions and send transactional email (receipts, security notices)
• Improve reliability and fix bugs (aggregated or support-scoped diagnostics)
• Comply with law and respond to lawful requests

We may send product updates or newsletter content only where you have consented or where transactional mail is required to provide the service.

4. AI providers and subprocessors

When you generate on your own key, prompts and the necessary book text are sent to the provider you chose, under your account with them and their terms and privacy policy.

When you generate with included Pro / Ultra AI, prompts and necessary context are sent to the routed model provider under their terms and privacy policy. Built-in AI uses platform credentials we control. Providers may process content in their regions according to their documentation.

We also use infrastructure and service vendors typical of a SaaS product (hosting, CDN, email delivery, payments). They process data only to provide their service to us.

5. Cookies and similar technology

We use essential cookies/session storage for login, CSRF protection, and preferences. Analytics or advertising scripts, when enabled on public pages, follow their own policies; dashboard pages are not intended for advertising crawl/monetization in the same way as public marketing content.

6. Retention

Account and project data are retained while your account is active. Security logs are retained for a limited operational window. After account deletion requests are processed, we remove or anonymize personal data except where we must retain records for legal, billing dispute, or security reasons. When you delete your account, we keep a private, access-restricted copy of it for up to 14 days so we can understand what went wrong, and then erase it.

So we can find and fix what goes wrong for authors, we keep a private record of the AI requests made from your account (what was asked and what came back) and of how you use your dashboard (the pages you open, the buttons you press, and any error you were shown — never what you type) for up to 60 days. It is access-restricted, never shared or used to train AI models, and it is removed when you delete your account, apart from the 14-day copy described above.

7. Your rights and choices

Depending on where you live, you may have rights to access, correct, delete, export, or restrict processing of personal data, and to object to certain processing. You can update account fields in the dashboard, unsubscribe from marketing email via the link in those messages, and delete your account and all its data yourself from Dashboard → Account → Delete account. If you would rather we did it, ask via Contact.

If you publish a public story, that content is intentionally visible on the web until you unpublish it. Unpublished or deleted public pages may still appear in search caches briefly until crawlers refresh.

8. Children

Entangled Text is not directed at children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal data from children.

9. International transfers

We may process data in the United States and other countries where our vendors operate. Where required, we rely on appropriate transfer mechanisms and vendor terms.

10. Changes

We may update this policy. The “Last updated” date at the top will change when we do. Material changes may also be announced in the product or by email when appropriate.

11. Contact

Privacy questions: use the Contact form. Related: Security, Terms of Service, About.