Privacy Policy for Inkwell

Rundquist Tech LLC ("we", "us", or "our") respects your privacy and is committed to protecting it through this Privacy Policy. This policy describes the types of information we collect, how we use it, and your rights.

This policy applies to your use of the Inkwell apps — the Inkwell macOS application and the Inkwell Reader for iPhone and iPad — along with their connected features and services (collectively, "Inkwell").

Inkwell does not track you across other companies' apps or websites. We do not sell your data, and we do not use your scripts to train any AI model.

1. Information We Collect

a) Required Telemetry

We collect a minimal set of technical signals essential for operating and improving Inkwell. This includes:

• App launches, quits, and unexpected terminations
• App version and version-install events
• Crash reports, hang reports, and error logs
• Platform and device model (e.g., "iPhone 17 Pro", "macOS 14")
• Performance diagnostics
• Writing-session counts and durations (how long a session lasted and why it ended). Never the words you write

These signals are collected automatically and cannot be disabled, as they are necessary for app stability, debugging, version-adoption tracking, and understanding overall product engagement. They never include the content of your scripts.

If you are signed in, your writing sessions are also saved to your account so we can show your writing time and streaks back to you. That record contains more than the anonymous signal above — see Section 1c.

b) Optional Usage Analytics

Inkwell collects anonymized usage data to help us understand how the apps are used. This includes:

• Feature usage (e.g., which tools are accessed most frequently)
• File-format breakdown (e.g., proportion of .ink vs .fountain vs .pdf vs .fdx opened)
• UI interaction patterns (e.g., which themes and reading sizes are selected)
• Quill AI prompt types (kinds of queries, never the prompt text itself)

These analytics are tracked using PostHog and are tied to a non-personally identifiable, randomly generated install ID. They never include the content of your scripts.

Default behavior: Inkwell Reader for iPhone and iPad has anonymous analytics enabled by default on first launch; the Inkwell macOS app has them disabled by default. In both apps you may enable or disable usage analytics at any time in the app's Settings → Privacy panel. Disabling analytics fires a one-time opt-out event so we have an audit trail of your choice.

Analytics never include your script content. Disabling analytics does not affect the required-telemetry signals listed above, which we need to keep the app stable.

c) Writing Activity on Your Account

When you are signed in, Inkwell records each writing session to your account. This is what powers the writing time, daily streak, and per-script breakdown shown on your Inkwell profile. Unlike the analytics in Section 1b, this is a first-party record tied to your account rather than an anonymous ID, and it is not affected by the analytics toggle — turning analytics off does not stop it, because it is a feature you are using rather than measurement we are doing.

Each session record contains:

• When the session started and ended, and how much of it was active vs. idle
• Your document's word count at the start and end of the session, and the difference between them
• The title of the script you were working on, so your profile can show what you have been writing
• An identifier for the document, so we can tell one script apart from another and group your sessions by project. The app determines this from the file's location on your device, but that location is scrambled before it is stored — what we keep is a fixed-length code that cannot be turned back into a path, folder name, or the account name on your computer. We cannot read it, and neither could anyone who obtained the database.
• Your platform and app version

We never record the words you write. Session records are kept for as long as your account exists and are deleted when you delete your account (Section 6).

If you are signed out, none of this leaves your device — writing time is tracked locally only.

2. Content and Data Handling

a) Script Content

Inkwell is local-first, and that has not changed. Your scripts live on your device as ordinary files. Nothing is uploaded to our servers unless you explicitly turn sync on, and you turn it on per document.

There are two exceptions to "we don't store your scripts," and we want to be specific about both rather than leave them under a blanket claim. The first is encrypted sync, described just below. The second is the small conversation memo we keep when you chat with Quill — see Section 2c.

If you turn sync on for a document, we store a copy of that document on our servers. It is encrypted on your device before it is sent, and it stays encrypted in transit and at rest on our servers. The key that unlocks it is derived on your own devices and never leaves them — we do not have it, cannot ask for it, and cannot read your script. But the encrypted bytes are on our servers, and we would rather say that plainly than keep describing this as though nothing is stored.

This is not the same as your files being encrypted on your Mac or iPhone. A synced document that has been downloaded to a device is an ordinary, unencrypted file there, protected by your operating system and whatever disk encryption you use (e.g. FileVault), the same as every other file you own. What our encryption protects is the copy we hold.

What we can see about a synced document. The contents, title, folders, and tags are encrypted and opaque to us. Some things are deliberately not encrypted, because a device that has not been unlocked yet still has to be able to show you an honest picture of your library:

• How many documents you have synced
• The size in bytes of each document, and of each saved version
• When each was created, changed, and last synced
• How many versions of it we hold
• The names you give the devices you enroll (e.g. "James's MacBook Pro"), and which device saved which version

So we can tell that an account has 14 documents totalling 6 MB and that one of them changed on Tuesday from a laptop. We cannot tell what any of them say, or even what they are called.

Removing a synced document. There are two separate actions. Remove from sync stops syncing the document and keeps everything, and is reversible. Delete from cloud destroys our copy immediately— there is no grace period, no retention window, and no way to undo it. Every encrypted version of it is erased from our servers on the spot; what remains is a receipt noting that a document of that size was deleted and when, so we can answer "what happened to my script?" later. Deleting your account destroys your synced copies the same way (Section 6).

In every one of those cases, the file on your own device is left exactly where it is. Inkwell never moves, renames, or deletes a document file on your disk.

Separately, when you use Quill:

• Portions of your script may be transmitted to third-party language-model providers (e.g., OpenAI, Google Gemini) so the model can respond to your questions about the script.
• Those providers may temporarily retain the content as required for processing, subject to their own privacy policies.
• We do not use your content to train or fine-tune any model.
• Quill on iPhone and iPad is read-only — it discusses the script but cannot edit it. The agentic editor lives on macOS.

Quill is opt-in: it activates only when you sign in and chat. Sync is opt-in too, and also requires an account. If you never sign in, no script content leaves your device.

b) AI Responses

We may store the results of your AI interactions (e.g., suggestions, completions) for the purpose of:

• Debugging
• Crash reproduction
• Product improvement

c) Quill Conversation Memos

Quill conversations themselves stay on your device — we do not keep a copy of every message. But so that a long conversation does not lose its thread, we store a small summary for each Quill thread on our servers, updated as you chat. It is written by a language model from your recent turns and can include:

• Characters that have come up, and short notes about them
• Story beats and decisions you and Quill have settled on
• Open questions the conversation has not resolved
• Preferences you have expressed about how you want to work

This is derived from your creative work, and it is stored against your account and the thread it belongs to. We are calling that out directly because an earlier version of this policy said stored AI results were "not linked to your script content or identity," and for these memos that was not accurate.

Memos are used only to give Quill continuity within your own conversation. They are not used to train models, are not shared between accounts, and are deleted when you delete your account (Section 6). If you never use Quill, no memo is ever created.

3. On-Device Data (Inkwell Reader for iPhone & iPad)

The iOS Reader stores the following entirely on your device. None of it is uploaded to our servers:

• Recents list— file names and last-opened timestamps for documents you've opened, plus a security-scoped bookmark so the file can be re-opened.
• Scroll position — the last-viewed paragraph in each document, so you return to where you left off.
• Sides selection— which character(s) you've chosen for the sides view, per document.
• Reading preferences — your theme and reading-size choices.

Files opened from Files.app, iCloud Drive, or AirDrop are accessed in place via Apple's security-scoped bookmark system. We never copy a script's contents into our servers.

4. Use of Third-Party Services

Inkwell uses the following service providers:

• Google Firebase – for authentication, account management, and messaging
• Sign in with Apple and Sign in with Google – optional authentication providers. We receive only your email and a user identifier; we never see your provider password.
• PostHog – for anonymous product analytics. Subject to your in-app Privacy toggle (see Section 1b above).
• OpenAI, Google Gemini, Anthropic, and other LLM providers – for Quill AI-driven features. Engaged only when you actively use Quill chat.
• Stripe – for subscription billing if you choose to subscribe. Payment-card details are handled by Stripe and never touch our servers.

These providers may collect or process information subject to their own privacy policies. We do not control their practices.

5. Data Security

We use reasonable administrative, technical, and physical safeguards to protect your information. However, no system can be 100% secure, and we cannot guarantee the absolute security of your data.

6. Your Rights & Choices

You have the following rights, depending on your jurisdiction:

• To know what information we collect
• To request deletion of your anonymized telemetry ID
• To disable optional analytics in the app's Settings → Privacy panel
• To decline AI features and use Inkwell entirely offline
• To delete your account. Deletion is initiated from within the apps (Settings → Manage Account → Delete Account) and completes on the web for verification.

What account deletion removes. Your sign-in, subscription records, credit history, writing-session history (including script titles and document identifiers, per Section 1c), and Quill conversation memos (Section 2c) are all deleted. Every screenplay you had synced is destroyed as well — the encrypted copies, all of their versions, and the wrapped keys and device records that go with them, including documents you had already removed from sync. The files on your own devices are untouched; they are yours and we never had a way to reach them. If that purge cannot be completed we stop and delete nothing, and tell you so, rather than leave your encrypted work behind an account that no longer exists. Three things are deliberately kept: records of payment events, which we retain as financial history in a form no longer pointing at you, administrative audit entries recording that the deletion happened, and the deletion receipts described in Section 2a, which are how we can later prove your screenplays were in fact destroyed. Any active subscription is cancelled as part of the process.

If you have questions or requests, contact us at privacy@rundquist.tech.

7. Updates to This Policy

We may update this Privacy Policy from time to time. When we do, we'll revise the "Last updated" date and may notify you in-app or via our website at https://inkwell.app/privacy.

8. Contact Us

If you have questions about this policy or our data practices, contact:

Rundquist Tech LLC
4546 El Camino Real B10 #781
Los Altos, CA 94022

Email: privacy@rundquist.tech

© 2026 Rundquist Tech LLC. All rights reserved.