Privacy Policy
Last updated: November 13, 2026
This policy explains, in plain language, what personal data we process on journzy.com and in the writing app (write.journzy.com), why, and what rights you have over it. The site uses no cookies and no persistent identifiers. We count anonymous page views and clicks and measure page performance; a random session id lives only in your browser tab.
1. Who is responsible for your data
The controller of your personal data is Obsurvive, Inc., a company based in the United States: 300 Delaware Ave, Ste 210 #355, Wilmington, DE 19801, USA. For any privacy matter, write to privacy@journzy.com.
2. Our representative in the European Union
Because we are based outside the European Union, we have designated a representative in the EU under Article 27 of the GDPR:
Luis Morales — EU representative of Obsurvive, Inc.Madrid, Spain
eu-representative@obsurvive.com
You and any EU data protection authority can contact our representative, instead of or in addition to us, about anything related to how we process your personal data.
3. Your manuscript is yours
On our landing page we promise that your writing is not used to train models without your explicit consent. This is the formal version of that promise:
Manuscripts and story-bible content—characters, places, relationships—belong to the author. We will never use them to train AI models without your explicit opt-in consent, given separately and revocable at any time. Without that consent, your text is processed only to provide the service: checking your story's continuity, returning the flags and, if you connect an external AI app, sending it what it asks for from the projects you open for it.
This commitment governs all of Journzy and the AI providers that Journzy uses. It does not govern an external AI app that you connect yourself, such as ChatGPT or Claude: that app handles your text under the terms of the company that provides it. We explain this in “Connected AI apps”.
4. Your account data
When you create an account in the app (write.journzy.com), we process your name, your email address, the books and content you write, and your settings.
Purpose: to provide the service, to maintain your account and to communicate with you about it. We do not share your email with anyone for marketing, and we will never send you anything unrelated to Journzy.
5. Emails
In the emails we send you about the service and your account, such as billing notices and product news, we record whether they are delivered, whether you open them and which links you click. To do this, the email carries an invisible image, and its links pass through our tracking domain before they take you to where they point. Sign-in codes, sign-in links and invitation links are not tracked. We use this to learn whether our emails arrive and are read, and which links are useful; the data is processed on Journzy-managed infrastructure in the European Union. If you block images in your email app, we do not record that you opened it. If you object to this tracking, write to privacy@journzy.com. Amazon Web Services (Amazon SES) and Resend send the emails for us as our processors.
6. Payments and billing
Link, a Stripe company (Stripe Managed Payments), takes the payment for the Author plan as merchant of record. Stripe and Link receive your name, your email address, your billing address and your payment method to take payment and issue receipts. Journzy never sees your full card number.
Each of them handles that data under its own privacy policy: Stripe and Link.
7. AI processing
When you use an AI feature, the content you send to it goes through Journzy's AI gateway to the model providers that serve it. Today models are served through OpenRouter with Zero Data Retention enforced for the whole account.
Your text is not used to train models without your explicit, revocable consent.
This section is only about the AI that Journzy uses. Zero Data Retention and our promise about training do not apply to external AI apps that you connect yourself; for those, read “Connected AI apps”.
8. Connected AI apps (such as ChatGPT or Claude)
You can connect your own AI app, such as ChatGPT or Claude, to your Journzy books. To connect it, you sign in to Journzy and, on the permission screen, choose the projects the app can read. At first no project is ticked, and the app cannot read any other project.
Access is read-only: the app cannot change, add or delete anything in Journzy. From the projects you open for it, the app can ask for:
- the list of your books and their outlines;
- the text of your scenes and the results of searching your manuscript;
- your story-bible information (characters, places, threads and world entries), except fields you keep hidden from AI;
- the results of Journzy's writing checks and Journzy's findings about your text;
- your own comments.
Comments from other people, such as the private comments of your alpha or beta readers, are never sent to the app.
To change an app's projects, go to Account › Connected apps, choose the app and use “Change projects”. If you untick every project, the app can no longer read your books. To end the connection, use “Disconnect” next to the app: the connection ends at once, any access the app already had stops within a few minutes, and its project choice is deleted. A connection also ends on its own after 30 days without use or 90 days after you approved it.
9. What the connected AI app receives
When you ask a connected app something, Journzy sends the content the app asks for to that app's provider, for example OpenAI for ChatGPT or Anthropic for Claude. That provider does not process the data on our behalf and is not a Journzy subprocessor: it handles the data under its own terms, its privacy policy and your settings in that app, and it may process it outside the European Economic Area.
What this policy says about Journzy's AI providers, Zero Data Retention and model training does not apply to that provider. Before you connect an app, read its terms and check your settings in it, for example whether you let it use your conversations to improve its models.
Disconnecting the app stops it from reading your projects again, but it does not delete copies its provider already received. To delete them, use that app's options or contact its provider.
10. Connected app logs
So that you can see what each app read, and to protect the service, Journzy keeps two logs:
- The read log: for each app call that returns content, your user, account and project IDs, the connected app's client ID, the tool name, the date and time, and the IDs of the items returned (books, scenes, story-bible entries, comments or findings).
- The security audit log: for each call, your user, project and connected-app IDs, a connection session ID, the tool name, the date and time, the outcome (and an error code if the call fails), how long it took, the response size, the scopes granted and a SHA-256 hash of the call's arguments.
Neither log stores your manuscript text, what you searched for, or the call's arguments in readable form.
Security audit records contain identifiers, not names or manuscript content. They are not anonymous, because the identifiers can be linked to your account. We use them only for security: to detect and investigate abuse or unauthorized access.
You can see the read log in Account › Connected apps, with “See what it read”, and in the copy of your data that you download from your account. How long we keep each log is in “How long we keep your data”.
11. Legal bases
We process your data on these bases under Article 6 GDPR: the contract, to provide the service and handle payments (Art. 6(1)(b)), and legitimate interest, for the security of the service and fraud prevention, and to measure the delivery, opens and clicks of our emails (Art. 6(1)(f)). When you connect an AI app, sending it what it asks for and keeping the read log are part of the service you ask us for (Art. 6(1)(b)); the security audit log is based on our legitimate interest in protecting the service (Art. 6(1)(f)).
12. How long we keep your data
Account data is kept until you delete the account. Billing records are kept as long as tax law requires; Stripe and Link keep them, as the merchant of record for the payment.
If you joined the launch list, we delete those emails within 90 days.
Anonymous site statistics are kept for at most 25 months.
Records of email delivery, opens and clicks are kept while your account exists. If you delete it, we remove your address from them.
Both connected app logs follow a 400-day retention policy and are then deleted automatically. The security audit log is managed in whole months and keeps at most 13 months.
If you delete a project, its read log is deleted. If you delete your account, your whole read log is deleted. Security audit records are not deleted when you delete a project or your account: they are kept until their retention period ends. If you want us to delete any of these records earlier, write to hola@journzy.com.
What a connected AI app already received is kept by its provider under its own terms; deleting your account or disconnecting the app does not delete it.
13. International transfers
The controller is in the United States, so your data may be processed outside the European Economic Area. Where the law requires it, our processors rely on standard contractual clauses. If you connect an external AI app, what we send at your request goes to its provider, which may be outside the European Economic Area.
14. Analytics
With our own tool, hosted in the European Union, we measure anonymously how the site is used: which pages are visited, how long you spend on them while the tab is in view, how far down each page you scroll, which links to other sites you click, which files you download, page performance and which buttons are used (for example, which format you download the character sheet in, never what you write in it). We also note your browser's language and the page's, and your screen size in four rough bands, never the exact size. For an external link we only keep the domain when it is a known site, such as a search engine, a social network or our app; any other counts as “other”.
If you arrive from a campaign, a search engine, an AI assistant or a social network, we remember in that tab where you came from, the first page you saw and its language, and add them to the links that lead to the app. If you create an account, the app only adds one to that day's anonymous count of sign-ups by first page, source and language. That count is never stored with your account and cannot be used to recognise you.
We use no cookies and no persistent identifiers: a random session id lives only in your browser tab and disappears when you close it. We do not share this data with third parties.
15. Cookies and local storage
The site sets no cookies. To count visits it uses your browser's session storage (sessionStorage) with a random id and, in the same tab, the first page you saw and where you came from; all of it is deleted when you close the tab. Only the character sheet uses this browser's local storage (localStorage), to keep what you type in it; that text never reaches us, and the sheet's Delete button removes it.
The app (write.journzy.com) uses one strictly necessary session cookie to keep you signed in. Your browser's storage keeps only what the app needs to work, such as your preferences and work not yet saved. Its analytics stores nothing in your browser: it uses no cookies and no persistent identifiers, and each time you open or reload the app you are a new anonymous visit. Some actions in your account, such as creating a book, exporting it or changing your plan, are recorded on our servers with your account id, to provide the service and improve it.
During checkout, Stripe's payment and fraud-prevention scripts can set cookies to complete the purchase and protect your payment.
Light or dark theme follows your system preference and stores nothing in your browser.
The site also uses session storage to remember that you closed the language suggestion; it is deleted when you close the tab.
16. Where everything is hosted
This site is served from servers in the European Union (Hetzner, in Germany and Finland), behind Cloudflare's network, which acts as a CDN and security layer and processes IP addresses transiently for that purpose.
Real-world maps: when you open a real-world map in the app, your browser asks our own servers for the base map (write.journzy.com, the same servers as the app, behind Cloudflare). No other third party receives your IP address or the map area you look at. The map data comes from OpenStreetMap, in the build that OpenFreeMap publishes; we host it ourselves.
Video tutorials: those on this site and in the app are hosted on YouTube. A page shows only a picture of the film from our servers until you press play; until then, your browser asks YouTube for nothing. When you press play, it loads the film from YouTube's player without tracking cookies at youtube-nocookie.com; YouTube, a Google service, receives your IP address and which film you play and handles them under Google's privacy policy. We send YouTube nothing about you or your account; Google is not on the Subprocessors list because it does not process data on our behalf.
The full list of the companies that process personal data on our behalf, with what each one does and where, is on Subprocessors. The providers of AI apps that you connect yourself are not on that list, because they do not process data on our behalf.
17. Your rights
The GDPR gives you the rights of access, rectification, erasure, portability, restriction and objection. To exercise any of them, write to privacy@journzy.com; we respond within the legal one-month deadline.
18. Your right to complain
If you think we have not handled your personal data correctly, you can complain to a data protection authority, in particular in the EU country where you live, where you work, or where the problem happened. You can find the list of EU authorities at https://www.edpb.europa.eu/about-edpb/about-edpb/members_en. We would like to help first, so please write to us at privacy@journzy.com.
19. Changes to this policy
If this policy changes, we will publish the new version here with its date. If a change affects how we handle your email, we will tell you by email first.