Privacy Policy

1. Who we are and when this policy applies

Eria Studios, Inc. (“Eria,” “we,” “us,” or “our”) operates Enspeller. This policy applies to enspeller.com, studio.enspeller.com, and related Enspeller services. For personal accounts and our websites, Eria generally determines why and how personal information is processed and acts as controller. When an organization customer controls an account or project, the organization may be the controller and Eria processes its Customer Personal Data under our Data Processing Addendum. Ask your organization about its own privacy practices.

The Eria Studios corporate website has a separate policy at eriastudios.com/privacy.html.

2. Information we collect

• Account and organization data: name, email, account identifier, authentication and security events, profile preferences, organization membership, role, invitations, and permissions.
• Manuscript and project data: novels, chapters, notes, lore, timelines, references, comments, exports, collaboration history, and project settings you or a collaborator provide.
• AI feature data: the relevant project excerpt, instruction, prompt or chat message, requested analysis, provider response, embeddings, feature state, and bounded usage/cost metadata.
• Voice data: audio you submit for transcription and text or generated audio for speech, only if voice is enabled and you request it.
• Usage, device, and log data: IP address, browser/device type, approximate location derived from IP, timestamps, feature and screen interactions, sync state, error reports, security events, and diagnostic data designed to exclude manuscript bodies.
• Billing and transaction data: plan, billing contact, country, tax information, subscription and payment status, invoice and transaction identifiers, and limited payment-method details such as brand and last four digits. Stripe receives full payment credentials directly; we do not store full card numbers or security codes.
• Communications: support, privacy, legal, billing, abuse, security, and feedback messages and attachments you choose to provide.
• Cookie and local-device data: sign-in/session data, security and preference storage, consent choices, and offline-first browser databases containing local project replicas and queued sync work.

3. Sources

We collect information directly from you; from collaborators and organization administrators; automatically when your device interacts with the service; from Stripe for billing status; from WorkOS and connected identity providers for authentication; and from service providers that return delivery, security, or requested feature results. We do not buy data brokers’ profiles about Enspeller users.

4. Why we process information and our legal bases

Where we rely on legitimate interests, we consider necessity, proportionality, and your rights. Where consent is the basis, you may withdraw it at any time for future processing.

5. Manuscripts, AI, and automated processing

Your content remains yours. Enspeller is analytical: it critiques, cross-references, and asks questions. It does not silently replace manuscript prose. Any proposed change must remain attributable and subject to user acceptance or rejection.

AI work runs after sync or on an explicit request, not on the keystroke path. We send only the portion reasonably needed for the feature to an approved provider. Production AI accounts must prohibit training on requests and meet the zero-retention controls stated in our Subprocessor Register. We store Enspeller’s resulting analysis and provenance when needed to show the feature, but providers may not retain a copy for their own model training.

Enspeller does not use solely automated processing to make legal or similarly significant decisions about you. Analytical findings may be wrong; authors and organization users decide whether and how to act on them.

6. When we disclose information

• Processors and service providers: the infrastructure, identity, encryption/email, AI, and voice vendors listed in our Subprocessor Register, limited to the stated purpose and subject to written protections.
• Payment processing: Stripe for checkout, subscriptions, invoices, fraud prevention, and payment-related obligations. Stripe may act as our processor for some activity and independently for obligations imposed on payment providers.
• Your organization and collaborators: account administrators and authorized project members receive data and controls consistent with their role. Organization owners may manage membership, access, retention, export, and deletion.
• Legal and safety: recipients where disclosure is required by valid law or reasonably necessary to protect rights, safety, security, or prevent fraud. We review government requests and disclose only what is legally required.
• Business transactions: advisers and a buyer, successor, or financing party under confidentiality in a merger, acquisition, reorganization, financing, or asset transaction, with continued protection consistent with law.

We do not sell personal information and do not share it for cross-context behavioral advertising. We do not provide manuscript content to data brokers or advertisers.

7. International processing

Enspeller’s primary production hosting region is the United States. Other providers may process data in the United States or the other locations stated in the Subprocessor Register. For transfers that require safeguards, we use applicable adequacy decisions, the European Commission’s Standard Contractual Clauses, the UK International Data Transfer Addendum, or another lawful mechanism. We assess transfer risks and apply supplementary technical and contractual measures where needed. Organization customers receive the contractual terms in our DPA.

8. Retention and deletion

We keep information only as long as reasonably necessary for its purpose. The criteria include whether your account, project, or subscription remains active; whether data is needed to provide a requested feature; security and dispute needs; user/organization deletion choices; and tax, accounting, contract, or other legal duties.

• Projects and manuscripts: until an authorized user deletes them or the account is closed, subject to encrypted backup rotation and legal holds.
• AI provider copies: production routes must operate with zero data retention; Enspeller retains its own requested result and provenance only as needed for the product and user controls.
• Account and identity data: for the account term and account-closure process, with minimal records retained where required for security or legal claims.
• Billing, contract, and acceptance records: for the period required by tax, accounting, fraud-prevention, limitation, and contract law.
• Logs and support records: for a bounded period based on security, reliability, and resolution needs; longer only for an active incident, dispute, or legal hold.

Deletion removes live copies and then residual encrypted backups through scheduled rotation. Offline copies on a device remain under the device/account holder’s control until cleared or the application completes its local closure workflow.

9. Security

We use administrative, technical, and organizational safeguards designed for manuscript data, including TLS in transit, encryption at rest, project-scoped application-layer encryption, managed key operations, role and tenant isolation, scoped collaboration tokens, least privilege, content-minimized logs, encrypted backups, and incident response procedures. No system is completely secure. Report a suspected security issue to compliance@eriastudios.com.

10. Your rights and choices

Depending on your location and the circumstances, you may have rights to be informed; access and receive a copy; correct; delete; restrict or object; port data; withdraw consent; opt out of certain targeted advertising, sale, or profiling; appeal a refusal; and complain to a regulator. These rights may have legal exceptions. You may also change profile data, export supported project data, manage collaborators, cancel billing, and close a personal account through Enspeller where available.

To submit a request, use account privacy controls or email compliance@eriastudios.com from the address associated with your account and state the right you wish to exercise. We will verify your identity proportionately and respond within the period required by law. Do not email passwords, government IDs, or manuscript content unless we provide a secure method. Authorized agents may act where law allows, subject to proof of authority and direct verification when permitted.

If an organization controls your account, submit the request to that organization first; we will assist it as processor. We will not discriminate against you for exercising a privacy right.

11. Regional information

• EEA, UK, and Switzerland: you may complain to the supervisory authority where you live, work, or believe an infringement occurred. You may ask us for information about the applicable transfer safeguard.
• California: see our California Privacy Notice for notice-at-collection disclosures, categories, retention, and request instructions.
• Other U.S. states: where applicable, you may appeal a denied request by replying to our decision with “Privacy appeal.” We do not sell data or use it for targeted advertising.

12. Children

Enspeller is intended only for adults who are at least 18 years old. We do not knowingly permit anyone under 18 to create or use an account. If you believe a person under 18 provided personal information to Enspeller, contact us so we can investigate, disable the account, and delete the information as required by law.

13. Cookies and local storage

Read our Cookie Notice. The marketing site does not use optional analytics or advertising cookies as of this version. The studio uses necessary storage for accounts, security, settings, and offline editing. Optional analytics may run only after an affirmative choice where consent is required.

14. Changes

We may update this policy as Enspeller, our providers, or law changes. We will post the new version and effective date and provide prominent in-product or email notice before a material change takes effect. We will obtain consent where law requires it. An earlier version continues to govern processing that cannot lawfully be changed without consent.

15. Contact