Privacy Policy

Applies to the website opaopa.app and the application opaopa studio (opaopa.studio). Shown here are the parts relevant to the application; Part B, on the website, is available at opaopa.app/privacy.

This is a courtesy translation. The German version ("Datenschutzerklärung") is the legally binding text. In case of any discrepancy, the German version prevails.

1. Controller

Florian Kirchner
Antonia-Kozlova-Straße 9
22763 Hamburg
Germany

Email: contact@opaopa.app
Phone: +49 156 7917 1310

No data protection officer has been appointed. The conditions of Section 38 of the German Federal Data Protection Act are not met: opaopa is operated by one individual with no employees, and no special categories of personal data within the meaning of Article 9 GDPR are processed.

2. What opaopa does

opaopa studio is a writing environment for novelists. Users write their manuscripts in the browser, maintain a collection of notes on characters, places and world-building (the "Story Bible"), and can have their texts analysed by an artificial intelligence when they explicitly ask for it.

Two things up front, because they matter for everything that follows:

Manuscripts are the heart of it. What users write belongs to them. These texts are stored so that they can keep working on them, and they are used for AI analysis. An analysis only takes place when the user triggers it themselves. So that the application can show in advance how much of the allowance an analysis would use, the text in question is first sent to the AI provider purely to be counted; nothing is analysed and no response is generated (see C6).

No training on user content. Neither we nor the AI provider use manuscripts to train or improve AI models.

3. Your rights

You have the right at any time to:

• Access the data we hold about you (Article 15 GDPR)
• Rectification of inaccurate data (Article 16 GDPR)
• Erasure of your data (Article 17 GDPR)
• Restriction of processing (Article 18 GDPR)
• Data portability — a copy of your data in a common format (Article 20 GDPR)
• Object to processing based on legitimate interests (Article 21 GDPR)
• Withdraw consent you have given, with effect for the future (Article 7 (3) GDPR)

An email to contact@opaopa.app is enough for any of these. We respond within one month.

Right to complain. You may lodge a complaint with a supervisory authority at any time. The authority responsible for us is:

Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit
Ludwig-Erhard-Str. 22, 20459 Hamburg, Germany
mailbox@datenschutz.hamburg.de

4. Deleting your account

You can request deletion of your account at any time by email. This deletes your projects, chapters, Story Bible entries, cover images and your user account, along with the other data stored for your account: the results of AI analyses, your writing profile, the usage metrics and the details stored at sign-in (see C2).

A note on backups: For resilience, encrypted backups of the database are created. Deleted data may persist in those backups for up to 30 days and is then removed permanently by automatic rotation. Selectively deleting individual records from a backup is not technically possible. During that period, backups are used solely to restore the service after a failure.

Part A — Both properties

A1. Hosting and delivery

Both properties are hosted by Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA. Server functions run in Frankfurt am Main (region fra1); static content is delivered through Vercel's global network.

When you open a page, the hosting provider processes technically necessary connection data — IP address, time of access, the address requested, the amount of data transferred, and browser and operating system identifiers. This processing is required to deliver the page, keep it stable and defend against attacks.

Legal basis: Article 6 (1)(f) GDPR (legitimate interest in secure operation).
Transfer outside the EU: A data processing agreement including the EU Standard Contractual Clauses is in place with Vercel.

A2. Fonts

The typefaces used are served from our own servers. No connection is made to Google Fonts or any other external provider when you open the pages.

A3. Contacting us by email

If you write to us, we process your email address, any name you provide and the contents of your message in order to handle your request. The mailbox is operated through Google Workspace (Google Ireland Limited, Dublin).

Legal basis: Article 6 (1)(b) GDPR where your enquiry concerns a contract, otherwise Article 6 (1)(f) GDPR.
Retention: until your request has been dealt with, and beyond that only where statutory retention periods apply.

A4. Sending email

System emails — your sign-in link, or confirmation of the waiting list — are sent through Plus Five Five, Inc. ("Resend"), 2261 Market Street #5039, San Francisco, CA 94114, USA. Delivery runs through the provider's European region. Your email address and the contents of the message are transmitted. Opens and clicks are not measured. Images in the emails, such as the logo, are loaded from our server when you open the message; this produces the connection data described in A1.

Legal basis: Article 6 (1)(b) GDPR.
Transfer outside the EU: A signed data processing agreement including the EU Standard Contractual Clauses is in place. Resend is additionally certified under the EU-US Data Privacy Framework.

A5. Backups

To protect against data loss, backups of the database are created automatically. These contain the entire dataset, including manuscripts and account data.

Every backup is encrypted before it is transferred. The key required to decrypt it is held solely by us; the storage provider cannot read the contents.

Providers involved:

• Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA — storage of the encrypted backups. The storage bucket is permanently set to the EU jurisdiction; the data does not leave the EU. A data processing agreement with Standard Contractual Clauses is in place, and Cloudflare is certified under the EU-US Data Privacy Framework.
• GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA — execution of the backup run. During this, the data sits unencrypted in the memory of the executing servers for a few seconds before it is encrypted. A data processing agreement with Standard Contractual Clauses is in place.

Legal basis: Article 6 (1)(f) GDPR (legitimate interest in availability and recoverability), in conjunction with Article 32 (1)(c) GDPR.
Retention: hourly snapshots for 48 hours, daily snapshots for 30 days, then automatic deletion.

A6. Social media profiles

We maintain profiles on Bluesky, X and Instagram. If you visit those profiles, the privacy terms of the respective provider apply; we have no influence over their processing. No social media buttons or embedded content that would send data to those providers on page load are used on our own pages — only ordinary links.

Part C — Application opaopa studio

C1. Database and user account

The application uses Supabase, Inc., 970 Toa Payoh North, Singapore, for its database, authentication and file storage. The database is located in Frankfurt am Main.

Legal basis: Article 6 (1)(b) GDPR.
Transfer outside the EU: data processing agreement with Standard Contractual Clauses.

C2. Registration and sign-in

You can sign in either

• with a sign-in link sent by email: you enter your email address and receive a single-use link, or
• with your Google account: Google then transmits an identifier for your account, your email address, your name and the address of your profile picture. Name and profile picture address are stored in the account data by our authentication provider (Supabase, see C1); the application does not read or use them. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

We do not offer sign-in with a password.

Processed: email address; with Google sign-in, additionally the account identifier, name and profile picture address; times of registration and sign-ins; the chosen interface language and your animation setting; the time and version of your confirmation of the legal texts (see C9). The authentication provider also records the IP address and browser identifier for each sign-in.

Beta invitation list. Access to the closed beta is by invitation. For this we keep a list with the email address of the person invited, the time of the invitation and, where applicable, an internal note. The entry exists even if you never sign in. We delete it on request at any time, and at the latest after the beta ends. The legal basis for this is Article 6 (1)(f) GDPR (legitimate interest in managing access).

Legal basis: Article 6 (1)(b) GDPR.
Retention: until your account is deleted.

C3. Cookies and browser storage

The application sets only technically necessary cookies:

In addition, your browser's session storage records which chapter you last had open. It also holds random identifiers per browser tab that prevent the same chapter or Story Bible entry from being edited in two tabs at once. These entries are removed when you close the browser tab.

No cookies are set for advertising or analytics purposes. Under Section 25 (2) TDDDG, no consent is required for technically necessary storage, which is why there is no consent banner.

C4. Your content

The content you create in the application is stored: projects, chapters, Story Bible entries, planning data, and project settings such as genre and language. Added to this are the results of the AI analyses you trigger — assessments, annotations, summaries and suggestions for Story Bible entries together with the passages they quote — and the state of a chapter's text that an analysis refers to. For Story Bible entries, we record which changes were adopted from an extraction. While you write, we automatically save earlier states of your chapters at intervals. They serve as a safety net against accidental loss of text. You currently cannot view or restore these states yourself in the app. They are deleted as soon as the chapter is permanently deleted.

Within the application, this content is visible only to you. There is no function to share or publish content, and no way for other users to see it. We ourselves access your content only as far as is necessary to operate the service, fix faults or handle your requests.

Please note: if your texts contain information about real people, you are responsible for that processing.

Legal basis: Article 6 (1)(b) GDPR.
Retention: until you delete the content or have your account deleted. Deleted chapters and Story Bible entries go to a trash area and can be restored from there; the trash is not emptied automatically. You can delete chapters permanently there. Story Bible entries in the trash and deleted planning elements remain stored until you delete the project; on request we delete them earlier, an email is enough.

C5. Cover images

You can upload a cover image for each project or choose one through the integrated Unsplash search. Uploaded images are stored in Supabase file storage. This storage is not public. The application creates a link for your signed-in account that expires after a short time. An image can only be retrieved through such a link; while it is valid, anyone who has the link can open the image.

When you use the image search, the search term — a term you enter or, when you open the cover image dialog of an existing project, the project title prefilled there — is transmitted through our server to Unsplash Inc., 225 Duncan Mill Road, Toronto, Ontario, Canada. No account data is transmitted. Your browser loads the preview images of the search, and a selected Unsplash cover image, directly from Unsplash's servers; Unsplash thereby learns your IP address and browser identifier. When you select an image, we report that selection to Unsplash without any details about you. An adequacy decision of the European Commission is in place for Canada.

Legal basis: Article 6 (1)(b) GDPR.

C6. AI analysis of your texts

This is the central function of the application and the most significant processing — please read this section carefully.

When it happens. An analysis only takes place when you trigger it yourself through a control such as "Assess chapter" or "Start extraction". An analysis may consist of several consecutive requests. Two things run without a click of their own:

• Counting in advance. So that we can show you before an analysis how much of your allowance it would use, the application sends the content that would be analysed to a counting function operated by Anthropic. This happens as soon as the application displays such a figure — for example when you open the chapter menu, an analysis dialog or the overview of a Story Bible entry — and immediately before every analysis. The content is only counted: no analysis takes place and no response is generated. No counting takes place while you are writing.
• Writing profile. After a chapter assessment, your writing profile is updated if something significant has changed, otherwise after every third assessed chapter (see C7).

What is transmitted, depending on the function you choose:

• the full text of the chapter in question
• Story Bible entries with names, alternative names, titles and full contents
• details already extracted from your chapters and suggestions for Story Bible entries
• previous AI annotations with the quoted passage, their classification and their handling status (open, resolved, skipped)
• metrics, scores and observations from up to eight of your most recently assessed chapters, and the averages and trends derived from them
• your writing profile and the level calculated from it (see C7)
• project settings such as genre, language, the level of editorial intensity you have chosen and the settings of an extraction
• internal technical identifiers of individual annotations, suggestions and Story Bible entries (random strings unrelated to you as a person)

What is not transmitted: your email address, your user identifier, your name, project identifiers and project titles. Beyond the content listed above, the request contains no details about you. Whatever you write in your texts yourself — names, for instance — is transmitted as content.

Recipient. Our contracting party is Anthropic Ireland, Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, Ireland. Processing takes place on servers operated by Anthropic PBC in the United States.

No use for training. Under Anthropic's commercial terms, content submitted through the programming interface is not used to train AI models.

Deletion by the provider. Anthropic deletes inputs and outputs within 30 days under its own retention policy. Where a request is flagged for a possible breach of the usage policies, retention may extend to up to two years.

What we store ourselves. We do not record your texts or the AI's responses in logs. Stored in the database are the results of an analysis (see C4), the state of the chapter's text it refers to, and usage metrics (see C8). The results include some details that are not shown to you but are needed for later analyses, such as partial scores and the writing profile. Technical logs contain error details and internal identifiers, including your user identifier.

Legal basis: Article 6 (1)(b) GDPR — the analysis is the contractually owed core of the service and is requested by you.
Transfer outside the EU: data processing agreement including Standard Contractual Clauses as part of the commercial terms.

C7. Writing profile

From your previous chapter assessments, the application derives a profile of your recurring strengths and areas for development. This profile exists solely to tailor future feedback to the way you write, and is maintained across your projects.

The profile is meant to contain summarising observations, not excerpts from your manuscripts; the AI is instructed accordingly. It cannot be technically ruled out that an observation picks up a short phrase from a chapter. The profile is currently not displayed in the application; it feeds solely into future analyses, and we will tell you its contents on request. It is not made available to anyone else and is not used to evaluate you outside the application. No automated decision producing legal effects or similarly significant effects within the meaning of Article 22 GDPR takes place.

Legal basis: Article 6 (1)(b) GDPR.
Retention: until your account is deleted.

C8. Usage metrics

For each AI analysis, the time, the type of action, the model used, the volume of text units processed and the resulting cost are stored, linked to your account and to the project and chapter concerned. This supports the display of your remaining allowance, billing, and the detection of abuse. Neither your texts nor the AI's responses are stored in the process.

Legal basis: Article 6 (1)(b) GDPR; as regards abuse detection, Article 6 (1)(f) GDPR.

C9. Confirmation of the legal texts

When you sign in, you confirm that you have taken note of this privacy policy. The time and version of that confirmation are stored in your user account so that we can demonstrate that we informed you. If the texts change significantly, you will be asked to confirm again the next time you open the application. There are no terms of use during the closed beta; once they exist, you will be asked to accept them in the same way.

Legal basis: Article 6 (1)(f) GDPR. Our legitimate interest is being able to demonstrate that we have met our information duties (Article 5 (2) GDPR).

C10. Exporting your data

You can export your manuscripts in DOCX, PDF, Markdown and ZIP formats. The files are generated on our own servers; no further providers are involved.

C11. Product feedback

The application links to a feedback form operated by Notion Labs, Inc., 2300 Harrison St, San Francisco, CA 94110, USA. The form opens in a new window; your entries are processed there, not in our database. Use is voluntary.

Legal basis: Article 6 (1)(a) GDPR (consent through voluntary use).

C12. Payment processing (applies once paid plans launch)

Paid subscriptions are handled through Paddle. Paddle acts as the seller: your contracting party for the purchase is

• Paddle.com Market Ltd., Judd House, 18–29 Mora Street, London EC1V 8BT, United Kingdom — for buyers outside the USA, or
• Paddle.com Inc. — for buyers in the USA.

Paddle collects your name, email address, billing address and payment details directly in its own checkout, issues the invoice and remits VAT. So that the purchase can be matched to your account, we pass your internal user identifier to Paddle. The checkout loads a script from Paddle that may set its own cookies. Payment details never reach us. Our database stores only the subscription tier, its status, the billing period, the payment method and Paddle's identifiers.

Invoices and subscription notices are sent by Paddle on behalf of opaopa. Your bank or payment statement will show a reference to Paddle.

An adequacy decision of the European Commission is in place for the United Kingdom.
Legal basis: Article 6 (1)(b) GDPR; for invoice data additionally Article 6 (1)(c) GDPR.

Changes to this privacy policy

We update this policy when the processing changes — for instance through new features or providers. The current version is available on opaopa.app and within the application. For significant changes, signed-in users are asked to confirm again the next time they open the application.

Last updated: 8 October 2026