Privacy Policy
NovelQuill · Effective 18 October 2026 · replaces the policy of 30 August 2026
The short version
- No account, no sign-in. We never ask for your name, email address or phone number. Your library lives on your device.
- Writing with AI sends your story to our server and to AI providers. To draft a chapter, the app sends the text the model needs — your premise, characters, notes and the relevant chapters — to our service, which passes it to the AI provider that does the writing (currently Anthropic or DeepSeek for text, Google for cover art). We keep a finished draft on our server for up to 30 days so your device can collect it, then it is deleted.
- Nothing you write is used to train an AI model by us. We also choose API access that the providers do not use for training; their current terms are linked below.
- No advertising, no tracking across apps. There is no advertising identifier and no ad SDK. The app does collect anonymous usage statistics (which screens are used, how often features are tapped) through Firebase Analytics. Those statistics never contain your writing.
- You can be reached only if you ask to be. Push notifications are off until you allow them; the only ones we send say that a draft you asked for is ready.
1. Who this policy is from
NovelQuill is an app for iPhone, iPad and Mac published by its independent developer ("we", "us"). This policy explains what the app does with information, in plain terms. It describes the app as it actually behaves, not as a category of app in general.
Questions about anything here: appsupport.get@gmail.com.
2. What stays on your device
The following is stored only on your device, in the app's own storage. It is never uploaded as a library and we hold no copy of it:
- Your stories — every chapter, scene and passage you keep, including imported manuscripts.
- The Codex and your notes — the characters, places, objects and events the app records for each story, and your Characters & plot notes.
- Your character library — characters saved for reuse across stories.
- Your author profile — the name, bio, website and photo you may enter for the About-the-Author page of an export. It is used only inside files you export yourself.
- Front covers you have accepted, and app settings such as typography, appearance and notification choices.
Deleting a story deletes it from your device. Deleting the app deletes all of it. The app does not use iCloud sync; your stories are included in a device backup if you make one, and those backups are governed by Apple's terms.
3. What is sent when you write with AI
Drafting prose is not something the app can do by itself. When you ask it to write — planning or drafting a chapter, writing a whole book or a short story, "Continue writing", Rewrite, Expand, Add a scene, suggesting ideas, naming the chapters of an imported manuscript, or creating a front cover — the app sends the material the model needs:
- The story's brief: title, premise, genres, point of view, tense, tone, language, creativity level, and the characters you described.
- Your Characters & plot notes for that story.
- The text the model needs for context: the relevant chapter(s), short summaries of earlier chapters, and — for Rewrite, Expand and Add a scene — the passage and the text around it. For chapter naming, only the opening of each chapter is sent.
- Your instruction, if you typed one, and the art direction for a cover.
That request travels over an encrypted (HTTPS) connection to our service, which builds the prompt and passes it to an AI provider. The response is streamed or delivered back to your device and saved there.
The AI providers
We route each task to a provider through our own server; the app never talks to a provider directly. The providers we currently use, and what they receive:
| Provider | Receives | Used for |
|---|---|---|
| Anthropic (Claude models) | The prompt described above | Drafting and rewriting prose |
| DeepSeek | The prompt described above | Drafting prose, planning chapters, suggestions, structured tasks |
| Google (Gemini image models) | Your story's brief and art direction — never the chapters | Front cover artwork |
Each provider processes the request under its own terms. We use their developer/API services, whose current terms state that API inputs are not used to train their models (Anthropic, DeepSeek, Google). We may change or add a provider to keep the writing good and the service available; if we do, we will update this table. The app does not show which provider wrote a given passage.
4. What our service keeps, and for how long
Since the October 2026 update, long drafts (a chapter, a whole book, a short story, a cover) are written on our server while you do other things, and the app collects the result. That requires our service to hold some data for a while. Here is all of it:
| What | Why | How long |
|---|---|---|
| An installation record: a random identifier and secret the app creates on first use, and — if you allow notifications — a push token | So only your device can collect the drafts it asked for, and so we can tell it when one is ready | Kept while the installation exists. Turning notifications off deletes the push token. Deleting the app orphans the record; write to us to have it removed. |
| A project brief for each story written with AI: title, premise, characters, notes, style settings, and the titles and short summaries of its chapters (not the chapter text) | So the next chapter can be written consistently with the previous ones | Kept while the project exists. Deleting the story on your device does not yet delete the project on the server; write to us and we will delete it. |
| A finished draft (the generated chapter or story text) and its job status | So your device can download it, including after a relaunch or a lost connection | Deleted 30 days after the job finishes |
| A generated cover image | So your device can download it | Deleted 7 days after the job finishes |
| Streamed passages (Continue writing, Rewrite, Expand, Add a scene) | Answered live | Held in memory only while the response streams; never written to storage |
| Your device's IP address | Rate limiting, so one device cannot exhaust the service for everyone; ordinary hosting access logs | Rate-limit counters live in memory and are discarded on restart. Our hosting provider keeps standard access logs for its usual period. |
| Operational logs: one line per AI call with token counts, timing and the task's route | Cost and fault monitoring | Kept with ordinary server logs. These lines never contain your prose; a test in our codebase enforces it. |
| A passage you report: your reason, your note and the first 500 characters of the passage | So a person can review AI output you flagged | Kept in our server logs while it is reviewed |
Our server is hosted by Render; its job store runs on Upstash (Redis). Both see the data above as infrastructure providers and process it under their own terms.
5. Anonymous usage statistics
The app uses Firebase Analytics (Google) to count how the app is used: which screens are opened, which features are tapped, whether a draft finished or failed, and coarse properties such as whether a subscription is active, how many stories have been started (as a bucket, e.g. "1", "2–5"), the story language and the chosen typeface. This helps us see which features matter and where the app fails.
- Events are built from a fixed list of names and values in our code. There is no path by which a premise, a title, a passage, an instruction or a character name can be included — the event system has no free-text field, deliberately.
- No advertising identifier (IDFA) is collected and the app never asks for App Tracking Transparency permission, because it does not track you across other apps or websites. Firebase's advertising features are disabled in the app's configuration.
- Firebase assigns a random app-instance identifier that is not linked to your identity.
- Analytics is on by default. There is currently no switch inside the app to turn it off; if you want your usage excluded, write to us and we will tell you how, or delete the app.
The app contains no advertising SDK and no crash-reporting SDK beyond what Apple provides with your consent in iOS Settings.
6. Notifications
On first launch the app asks whether you would like notifications. Nothing is registered until you say yes and allow them in the system prompt. If you do:
- Your device receives a push token from Apple, which the app hands to Firebase Cloud Messaging and to our server (see section 4). Our server uses it for one thing: a message saying a draft you asked for is ready. We may also use Firebase to send occasional feature news to everyone with notifications on.
- The "your story is waiting" reminder after a week away is a local notification scheduled on your device. It names your story on your screen only; nothing about it leaves the device.
Turning notifications off in Settings deletes the push token from Firebase and from our server, and cancels the reminder.
7. Purchases
NovelQuill Pro is sold through Apple's in-app purchase. Apple handles payment; we never see your payment details. The app uses RevenueCat to check whether a subscription is active and to restore it on another device. RevenueCat receives a randomly generated, pseudonymous user ID and your purchase status. We have deliberately not enabled RevenueCat's device-identifier and attribution collection.
8. Files and photos
- Importing a manuscript uses the system file picker or paste. The text stays on your device until you ask the AI to work on it (section 3).
- Exporting writes an EPUB, PDF, Word or text file on your device and hands it to the share sheet or Files. Nothing is uploaded.
- Saving a share card to your photo library asks for add-only permission; the app cannot read your library.
- An author photo is copied into the app's own storage and embedded only in exports you make.
9. Listening
Listen uses the speech voices built into your device. Text is spoken on the device and is not sent anywhere for that purpose. On iPhone, playback shows a Live Activity on the Lock Screen and in the Dynamic Island; that stays on the device.
10. Your choices and rights
- Write without AI. Reading, editing by hand, importing, the Codex and export work with no connection and send nothing.
- Export everything as EPUB, PDF, Word or plain text, straight from the app.
- Delete anything. Delete a story in the app, or delete the app. To have a server-side project brief or installation record deleted, write to us with the story's title; we will confirm when it is gone.
- Notifications can be turned off in Settings at any time.
- Reporting happens only when you tap Report.
Depending on where you live — including under the laws of the European Union, the United Kingdom, California and other US states — you may have the right to know what personal information we hold, to request a copy, to request its deletion or correction, to object to or restrict processing, and not to be discriminated against for exercising those rights. Given the design above we hold very little about you; a request is usually answered by telling you so and deleting any server-side record that can be traced to your installation. Write to appsupport.get@gmail.com. We do not sell personal information and do not share it for cross-context behavioural advertising, so there is no sale or sharing to opt out of. EU and UK residents may also complain to their local data protection authority.
Our legal basis (where one is required): processing your story text to write with AI is necessary to provide the service you asked for; analytics and notifications rest on our legitimate interest in understanding and improving the app, and on your consent where the law requires it; purchase status is necessary to perform the subscription contract.
11. Security
Traffic between the app and our service is encrypted in transit with HTTPS. Each installation holds a secret that only it knows, so another device cannot collect your drafts. Drafts on the server are deleted on the schedule in section 4. No system is perfectly secure, and we cannot guarantee absolute security.
12. International transfers
Our service, its data store and the AI providers process requests on servers in the United States and possibly elsewhere. By using NovelQuill to write with AI, you understand that the text you send is processed in this way. Where the law requires safeguards for such transfers, we rely on the providers' standard contractual terms.
13. Changes to this policy
When this policy changes we update the date at the top, and where the change is significant we say so in the app or on this page. Continuing to use NovelQuill after a change means you accept the updated policy.
14. Contact
NovelQuill
appsupport.get@gmail.com