Privacy Policy

3 pages daily ("we," "our," "us") is a private daily journaling application. This policy explains what we collect, what we do with it, and the things we will never do with your writing.

3 pages daily comes in two forms and they handle data very differently, so the part of this policy that applies to you depends on which one you use.

The app collects nothing at all. If you only use the app, section 3 is the entire policy as far as you are concerned — everything after it describes a web account you do not have.

The web version needs an account so your journal can open on any machine you sign in from, which means we hold your content on our infrastructure. Sections 6 through 11 cover that.

If you use both, they stay separate: an entry written in the app is not uploaded to the web version unless you deliberately move it there.

Our iPhone, iPad and Mac app stores everything on your device and sends nothing anywhere. There is no account to create, no sign-in, and no server holding a copy of your journal — which means there is nothing for us, or anyone else, to read, lose or hand over.

Concretely, the app collects none of the following: contact information, names or email addresses, identifiers or device IDs, usage or analytics data, diagnostics or crash reports, location, advertising data, purchase history, and none of your journal content — no entries, drawings, recordings or attachments. It contains no analytics SDK, no advertising SDK and no third-party trackers.

Your writing lives in the app's local storage on that device, under your own control. Deleting the app removes that data with it, so export anything you want to keep first. Because nothing is transmitted, there is also nothing for you to request, correct or have erased by us — the rights described in section 12 concern web accounts, and an app-only user has no account for them to apply to.

Dictation inside the app uses the speech recognition built into your device. Whether that runs on-device or through Apple's servers is governed by Apple and by your own iOS settings; either way the text stays in the app and is never sent to us.

These apply to every version of 3 pages daily, without exception:

• No advertising. We do not run ads of any kind, we do not embed advertising SDKs, and we do not share data with advertising networks or data brokers.
• No AI or model training. We do not use your writing, drawings, recordings or images to train, fine-tune or evaluate any AI or machine-learning model — ours or anyone else's — and we do not supply your content to third parties for that purpose.
• No selling your data. We do not sell, rent or trade your personal information or your journal content.
• No reading your journal. Your content is not accessible to our staff in normal operations, and we do not review it for product or marketing purposes.

You own everything you write, draw, record and upload. Copyright and every other right in your content remain entirely yours — using 3 pages daily transfers nothing to us.

For the web version only, you give us a narrow permission to store, transmit and display your content back to you, strictly so that the service can function. That permission exists solely to operate the service for you, covers nothing else, and ends when you delete the content or your account.

Account information: your email address, and your name if you provide one through Google or Apple sign-in. We do not ask for a phone number or date of birth.

Journal content: your entries, voice recordings, images, drawings and attachments. We store these to provide the service, and for no other reason.

Usage data: anonymised product analytics such as which features are used and how long a session lasts, via PostHog. We explicitly do not capture journal text, search terms, image contents or audio in analytics events, and you can opt out in Settings.

Payment information: handled by Stripe. We never see or store your card number — only a Stripe customer ID and your subscription status.

Error logs: via Sentry. Error reports do not include journal content.

• To provide the service and keep your journal available across your devices
• To process payments and manage subscriptions
• To run features you start yourself, such as extracting text from an image
• To send account-related email — not marketing, unless you ask for it

That list is exhaustive. Any use beyond it would require your consent, and the exclusions in section 4 hold regardless.

Voice transcription runs on your own device. Transcription uses the speech recognition built into your browser, so the audio is processed locally as you speak and is never sent to us for conversion. Browser support for this varies; recording and playback work everywhere, automatic transcripts do not.

Text extraction from images (OCR) runs on our own infrastructure using open-source software, and the image is not sent to any third-party vision or AI service. The extracted text is stored in your private account under the same protections as the rest of your content. You choose which languages it looks for in Settings; where it finds no readable text, nothing is stored at all.

Your data is stored on Supabase-hosted infrastructure with row-level security policies, so each account can reach only its own data. Everything is encrypted in transit with TLS and encrypted at rest.

We deliberately use accurate language here: your journal is private, encrypted in transit and at rest, and protected by strict access controls. It is not "zero-knowledge" or end-to-end encrypted, because features such as server-side search and text extraction require the service to process your content. If end-to-end encryption matters more to you than those features, our downloadable apps keep everything on your device instead.

The web version relies on these providers, and no others:

• Supabase — database, file storage and authentication
• Stripe — payment processing
• Vercel — application hosting and CDN
• PostHog — anonymous product analytics, no content captured
• Sentry — error monitoring, no content captured

None of these providers is permitted to use your content for their own purposes, including model training. Our downloadable apps use none of them.

The web version uses session cookies to keep you signed in. We use no tracking cookies and no advertising cookies. If you sign in with Google or Apple, those providers may set their own cookies under their own policies. The apps use no cookies at all.

Wherever you are located, you can:

• Access — export everything you have written
• Delete — permanently delete your account and all associated data
• Correct — update your account information
• Take it elsewhere — export in open formats, as Markdown or PDF
• Object — turn off product analytics at any time in Settings

To exercise any of these, or to request account deletion, write to hi@3pagesdaily.com. We respond within 30 days. For the apps, deleting the app from your device removes the data with it, so there is nothing for us to delete on your behalf.

3 pages daily is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child under 13 has created an account, contact us and we will delete it promptly.

We keep your data for as long as your account is active. Deleting an entry removes it straight away and permanently — there is no trash, no grace period and no way to restore it afterwards, so export anything you might want back before you delete it. If you delete your account, we permanently delete all associated data within 30 days. Data held only on your device in one of our apps is under your control and is never retained by us.

We will tell you about material changes by email and an in-app notice at least 14 days before they take effect.

Privacy questions or requests: hi@3pagesdaily.com