Privacy Policy
Effective date: November 11, 2026
Outerline is a local-first markdown editor. Your documents are files in a library you choose on your Mac or iPhone, locally or through a storage provider. We do not see, store, or access them unless you explicitly choose to send data to us, such as by publishing a document through an Outerline account. This policy covers the Mac and iPhone apps, Outerline accounts and publishing, and the outerline.so website.
Your Documents
Outerline reads and writes .md files in your chosen library on Mac or iPhone. You can use a local folder, Outerline’s iCloud Library, or a folder available through a storage provider. If you choose iCloud Drive, Apple syncs the files under your Apple Account, subject to Apple’s privacy policy. Other providers handle synchronization under their own policies. Other than documents you explicitly publish through an Outerline account, Outerline does not transmit your documents to our servers.
Importing a web page makes a request directly from your device to the source website. Extraction happens on-device; the address and page body are not sent to an Outerline or Defuddle extraction server. Imported notes can retain remote image URLs. Opening a rendered preview with remote images can make requests to their hosts, which handle those requests under their own policies.
Outerline Accounts & Publishing
You can use Outerline locally without an account. An Outerline account is only required if you choose to publish a document to Outerline's sharing service.
When you create an Outerline account, we collect your name, email address, email verification status, account status, and the date you accepted the Terms and Privacy Policy. We use this information to create and manage your account, verify your email address, send sign-in codes and links, and control access to publishing.
Publishing new documents, updating shared pages, and republishing require active Publish access, normally through the Outerline Publish subscription. Apple processes the purchase, and we never receive your payment details. To know whether your subscription is active, we store subscription records from Apple such as the product identifier, transaction and original transaction identifiers, subscription status, environment, expiration and renewal dates, auto-renew state, and any cancellation or revocation date. We use these records only to grant, maintain, and revoke access to publishing.
When you publish a document, Outerline sends the document title, optional description, Markdown content, document identifier, and publishing settings to Outerline's sharing server. It also sends the position and colour of each highlight in the document, the labels and targets of the document’s links (including identifiers of linked Outerline documents), and, for imported web pages, source details such as the original title, author, site, and address. Comments and notes attached to highlights are not sent. The server stores the Markdown, rendered HTML (which displays your highlights), public link slug, publish status, timestamps, and revision history so the share link can work and stay updated when you save changes.
Published documents are public to anyone with the link. Outerline asks search engines not to index published pages, but that is not access control. Anyone with the link may view the page, copy the Markdown, or import a snapshot into Outerline while the document is published.
If you stop sharing a document, the public link will no longer show the document. Stopping sharing is not the same as deleting all hosted content; Outerline keeps the share record and revision history so you can republish the document later.
Outerline uses email delivery providers, such as SendGrid, to send account verification and sign-in codes and links. We also keep limited security records, such as hashed account and publisher tokens, device name, platform, last-used timestamps, and rate-limit records for sign-in attempts.
If you choose Sign in with Apple, we store Apple’s account identifier, the name and email Apple provides when available, and encrypted refresh credentials used to maintain and revoke that authorization. Apple may provide a private relay email address. We use these records to sign you in and manage your account connection.
Account Deletion and Retention
To delete your account, open Settings > Account > Manage Account in either app, then choose Delete account in the browser and confirm with your account email. You can also contact [email protected] for assistance.
Account deletion removes hosted shares and their revision history from the live service and revokes account access. It removes the profile’s name and replaces its email with a deletion address. It does not change your local documents or cancel an Apple subscription. Limited account, authentication, security, and subscription records can remain after deletion. Encrypted database backups can contain older records until their scheduled retention expires; deletion does not immediately erase those backup copies.
Diagnostics & Performance
The Mac app uses Apple’s MetricKit framework to receive crash, hang, and performance diagnostics locally. Outerline stores these payloads in its local Application Support area, inside its app container in the App Store version. They are not uploaded automatically.
Choose Help > Diagnostic Snapshot on Mac to generate a local file and reveal it in Finder. Generating the file does not send it to us. The snapshot can include:
- App version, build number, macOS version, and hardware model
- Crash and hang stack traces, CPU, memory, and disk metrics
- Document count, uptime, available storage, and thermal state
- Display configuration, appearance, and accessibility preferences
- Locale, preferred languages, and metadata-write diagnostic summaries
Review the generated file before attaching it to a bug report or sending it to support. We receive the diagnostic files you explicitly share with us. The iPhone app does not provide this Mac diagnostic-snapshot command.
App Updates
Outerline updates are delivered through Apple's TestFlight and App Store update systems. Outerline does not run a separate in-app update checker.
MCP Integration
Outerline includes a built-in MCP (Model Context Protocol) server that lets you connect your library to AI tools such as Claude Desktop or Claude Code. The MCP server runs entirely on your Mac. Outerline does not send any data to Anthropic or any other AI service.
When you connect an AI tool, that tool may read documents from your library as part of a conversation. The privacy of that data is governed by the policy of the AI service you choose to connect — for example, Anthropic's privacy policy for Claude. Documents are only accessible to an AI tool when you have it actively connected.
What We Don't Collect
The Outerline native apps do not:
- Automatically upload analytics, tracking data, usage data, or diagnostics
- Use advertising or tracking SDKs
- Require an account or sign-in for local editing
- Sell your data or use it for advertising
- Access your documents without your explicit action
Website Requests
The support website loads fonts from Google Fonts and uses Cloudflare Web Analytics. Your browser makes requests to these services when loading the site; those requests are separate from the native apps’ local diagnostics. See Google’s privacy policy and Cloudflare’s privacy policy for how they handle requests.
Contact
Questions about this policy? Email [email protected].
We may update this policy from time to time. Changes will be posted at this URL with a revised effective date.