A journal entry. A medical symptom you looked up and pasted into your notes. The draft of a difficult conversation you’re preparing for. Therapy session reflections.
Note-taking apps hold some of the most intimate content people generate — more private, in many ways, than their photos. And most people have never thought carefully about what their notes app can see, or what happens to that content when terms of service change, companies are acquired, or employees access data for “quality control.”
The Notes App Privacy Problem Most People Skip
Privacy conversations around cloud software mostly center on photos, messages, and location data. Notes get overlooked, probably because they feel less concrete than images. But the privacy architecture of your notes app has real stakes.
Notes contain context that nothing else can match. A photo shows you at a location. Your notes show you what you were thinking, planning, and worried about. For any analysis of a person based on written content, a notes archive is the richest possible source.
Most note content is unstructured text — the most useful format for AI training. Photos need to be analyzed and labeled. Text can be ingested directly. Notes written inside a cloud service are exactly the kind of content that trains language models, assuming the provider’s terms allow for it.
Notes are rarely audited for what’s in them. People occasionally review their photo libraries and message history. Notes are usually just a place to dump thoughts without review, which means years of private content accumulate in cloud services that most people have never thought carefully about.
What Different Notes Apps Actually Do With Your Data
Apple Notes
Apple Notes content syncs through iCloud. By default, iCloud Notes is not end-to-end encrypted. Apple introduced Advanced Data Protection to change this — when enabled, Notes are end-to-end encrypted and Apple cannot access them.
Without Advanced Data Protection, Apple can technically access iCloud Notes content in response to valid legal process. Apple’s privacy policy commits to not using Notes content for advertising targeting, but the company does process iCloud content to provide and improve services.
If you use Apple Notes and haven’t turned on Advanced Data Protection, your notes are encrypted at rest but readable by Apple under appropriate circumstances.
Google Keep and Docs
Google’s notes products run on Google’s infrastructure under Google’s terms. Google’s privacy policy allows using your content to improve products and services, which has historically included using document content for AI development with some opt-outs available.
Google doesn’t use the specific content of private documents for advertising targeting in the narrow sense. But the broader signals derived from what you write — topics, entities, patterns — feed into Google’s understanding of you across its products.
This is different from “Google is reading your diary” as a literal statement. The practical reality is that writing private notes in Google Keep means those notes live in an advertising-funded ecosystem where derived signals from your content have commercial value.
Notion
Notion stores your data on its servers and holds the encryption keys. Notion’s privacy policy permits the company to use content to improve products, which in current industry practice typically includes some form of AI training on user data.
Notion does not offer end-to-end encryption. Content is processed server-side. The company holds SOC 2 Type 2 and ISO 27001 certifications, which means internal access controls are audited — that’s real. But it’s different from the cryptographic guarantee that Notion employees cannot access your notes.
Evernote
Evernote had a visible privacy controversy when a policy change briefly allowed employees to read user notes for “quality control.” The policy was revised after backlash, but the episode illustrated a core difference: “we don’t read your notes” is a policy statement, and “we can’t read your notes” is a technical guarantee. Evernote has never offered the latter.
Evernote encrypts content at rest and in transit, but holds the keys. The company has changed ownership multiple times — the data governance questions that follow acquisitions apply directly here.
The Two Fundamental Architectures
There are two ways notes apps can be built, and understanding the difference is more useful than comparing privacy policies:
Server-holds-keys. Notes are encrypted in transit and at rest, but the provider can decrypt them. Google Keep, Notion, Apple Notes without Advanced Data Protection, and Evernote all fall here. The protection against outside attackers is real. The protection against the provider itself is contractual and legal, not technical.
Client-side / local-first. Notes live as files on your device. The provider never has keys to decrypt them. Obsidian is the most prominent example — your vault is a folder of Markdown files on your device. Obsidian Sync uses end-to-end encryption so that content is encrypted before leaving your device. Other tools in this category include Logseq and Joplin.
The local-first model provides guarantees that the policy model cannot. No change of company ownership affects your notes. No terms of service update changes what a provider can access. The files are yours in a literal, not metaphorical, sense.
The File Format Question
Data ownership isn’t only about encryption. It’s also about whether you can extract your data — and in what form.
A notes app that stores your content in a proprietary binary format and only exports as PDF is not an app where you own your data in any meaningful sense. You get a printout, not your files.
Formats that mean real ownership:
- Plain Markdown (.md files): Readable by any text editor, renderable by many apps, no lock-in. Used by Obsidian, Bear (with export), iA Writer, and others.
- Plain text (.txt): Universally accessible and readable in 30 years without special software.
- Open JSON export: Structured but machine-readable and convertible with standard tools.
Formats that don’t:
- Proprietary database formats: Apps that store notes in a format that requires the app to read. If the app shuts down, you need a converter tool that may not exist.
- PDF-only export: Your data, rendered into a format that’s hard to edit, search programmatically, or migrate cleanly.
- Fragmented HTML export: Technically exportable, but arriving as a folder of thousands of HTML files that requires custom tooling to reassemble.
Before committing your primary knowledge archive to any notes app, export a test batch. Open the files in a plain text editor. If you can read them, you actually own them.
Practical Steps If You Want Better Notes Privacy
Audit what you have
Start with an honest inventory. What’s in your current notes app, and how sensitive is it? A notes app full of shopping lists and meeting agendas has a different risk profile than one that contains health records, financial planning, or personal reflections.
The goal isn’t to achieve perfect privacy for every sticky note. It’s to make sure your most sensitive content is handled thoughtfully.
Export first, migrate second
Most cloud notes apps offer an export function. Run it before making any changes — you want a local copy of everything regardless of what you decide to do with it. Common export formats:
- Apple Notes: Export via File > Export All Notes as PDF, or use a third-party tool for plain text export
- Notion: Settings > Export all workspace content (Markdown + CSV)
- Evernote: File > Export Notes > ENEX format, then convert with tools like Yarle
- Google Keep: Google Takeout exports Keep as JSON
Consider separating storage from editing
If you prefer a cloud-based notes editor for its features but want better control over storage, one practical approach is to write in a local-first editor (Obsidian, Bear, iA Writer) and sync the underlying files through a storage provider with clearer data commitments rather than the notes app’s built-in cloud.
This separates the editing experience from the data infrastructure. You get the editor you want; you choose where the files live.
daftei handles files in any format — including Markdown vaults and plain text — with AES-256 encryption at rest and TLS 1.3 in transit, and explicitly never trains third-party AI models on your content. It’s not a notes editor, but as a sync and storage layer for files you manage locally, it fits this approach.
Move the most sensitive content first
If a complete migration feels daunting, prioritize. Move the content you’d be most uncomfortable with a stranger reading: health notes, financial planning, relationship reflections, anything you wrote assuming no one else would ever see it.
Less sensitive content — project notes, task lists, reference material — can follow at whatever pace suits you.
The Vendor Risk No One Mentions
There’s one more factor worth naming explicitly: the risk of the vendor’s circumstances changing.
A notes app you’ve used for years, with good privacy commitments today, might be acquired by a company with a different business model. The acquiring company gets access to your data under the terms of that acquisition, which may be very different from the terms under which you created your notes.
This isn’t hypothetical. It’s happened repeatedly across productivity software. The legal mechanism is usually a clause in the privacy policy saying something like “in the event of a merger or acquisition, your data may be transferred.”
The only durable protection against this risk is a format and architecture where the vendor’s ownership structure doesn’t affect your data. Markdown files on your device, backed up to a storage service with explicit commitments around acquisition handling, is more robust than notes locked in a vendor’s proprietary format with a “we hope the acquirer respects your privacy” clause.
Choosing where your most private thoughts live is worth more than a few minutes of attention.