editing.help · Subtextual

Privacy Policy

Last updated October 24, 2026

Who this covers

This policy covers the editing.help website (the studio, its courses, samples and Notes) Subtextual, the writing app at editing.help/app/, and Subtextual for Mac, the same app for the Mac from the Mac App Store or as a download from editing.help. All are made by editing.help, a business of Dev Edit Portland, Inc., 3055 NW Yeon Ave #747, Portland, OR 97210. Questions about this policy go to info@editing.help.

Subtextual Capture, the companion Mac app, has its own privacy policy.

The editing.help website

Using the site

The site doesn’t include analytics or advertising scripts, and its pages and fonts don’t rely on a third-party tracking service. Like any website, its host keeps ordinary request logs; see “Who processes data” below.

Asking about Subtextual. If you type a question into “Ask anything about Subtextual.” on this site and send it, your browser sends it to Subtextual’s server at ask.editing.help. The server sends it, with the site’s own pages, to an AI model (Anthropic’s Claude, through OpenRouter) on services that keep no copy of it and don’t use it for training. Your browser never contacts them directly. Subtextual doesn’t keep your question or the answer: each request leaves only a short record of its outcome, size, cost and time, with no words and no IP address, kept for 3 days. Your IP address is used only to limit how many questions one visitor can ask. It’s held in the server’s memory for at most a day, never written down, and isn’t sent to OpenRouter or Anthropic. Neon, which runs the server, keeps its own network logs under its own privacy policy. Don’t type anything private there. Nothing is sent until you send a question.

Writing to editing.help

Contact and interest links open your own email app, and nothing is sent until you choose to send it. Your message is then handled by your email provider and the receiving email service. Describe your need broadly, and leave out confidential client or learner material until handling arrangements are agreed. An inquiry is never permission to subscribe you to marketing email.

Course samples

Samples can be read and printed without an account. They don’t connect to AI, and they don’t save or submit your work. Nothing you write on a printed copy is sent anywhere.

Payments

Purchases and enrollment for courses aren’t open. The one thing you can pay for is the Subtextual AI subscription, described below. It’s sold through Link, and its payment happens on Link’s checkout page, run by Stripe, not on this site, so no card information is collected by editing.help.

Ground First letters

The Ground First newsletter is on Substack. If you subscribe, you enter your email on Substack, not here, and Substack’s own terms and privacy policy apply.

Links to other sites

Links to Substack, LinkedIn, randalll.com and other portfolio or method sites lead to separate websites with their own practices. Choose what you share there.

Subtextual: without an account

Everything you write stays in your browser’s storage on the device you’re using: your documents with their subtext and notes, your Pretext (including captures and their images), your groups and pins, your display settings, your AI settings, and the Capture pairing code. So do the restore points Subtextual keeps before a restore, and anything it sets aside because it couldn’t be read. None of it is sent to Subtextual. Undo history is kept in memory only, and is never saved.

Covers and other pictures you add, by uploading, pasting, dropping or dragging them in from a web page, are stored inside the document. When you drag a picture from a web page onto a document’s card, Subtextual fetches that one image from the site it’s on, once, at that moment, without cookies or a referrer, and keeps a small copy inside the document. Apart from the services named in this policy, that’s the only time the app contacts another website.

Clearing your browser’s data, using private browsing, or losing your device can remove it. You can export any document at any time, as Markdown, Word, PDF, a full project file, or a context bundle for an AI, and import Markdown, plain-text and Word files, or a Subtextual project file. Both happen in your browser: nothing is sent anywhere, and images linked from an imported file aren’t fetched. An imported document is a new document like any other, never replacing what’s already there, and it stays in your browser unless you turn on sync for it.

Subtextual: if you sign in

Signing in is optional. You can sign in with a six-digit code sent to your email, or with your Google account. Sign-in is handled by Neon Auth, a service of Neon, which stores sign-in details on Subtextual’s behalf.

What sign-in records

When you sign in with an email code, Neon Auth receives your email address, the name you type, and the time of each code. A code expires after a few minutes. Sign-in codes are sent by email through Google Workspace, which sees the address and the message and keeps its own delivery logs.

When you sign in with Google, Neon Auth receives your name, email address, Google account ID and profile picture link from Google, plus sign-in tokens from Google.

To keep you signed in, Neon Auth records your session, including your IP address and browser type. A session lasts up to 7 days.

Subtextual uses your name and email only to identify your account and show who’s signed in. It doesn’t load your profile picture or use the Google tokens, IP address or browser type.

Syncing documents

Signing in doesn’t upload anything by itself. You choose which documents to sync, one at a time, with Sync this document in a document’s settings. Turning sync on for a document brings the documents nested inside it along. A synced document is stored as one record: its title, the page text with its formatting, the subtext beneath it (including any AI-written bullets, marked with the model and Reader that wrote them), its Context notes, its links to other documents, its brief and Reader for the AI, whether it’s archived, the images placed in it (including its cover), and its dates, including when each paragraph and thought was written and last edited. Linking to another document doesn’t sync that document; only documents you turn sync on for are uploaded. A document opened out of another remembers where it sits, and that travels with it. The database also stores your account ID and a revision number. It’s kept in a database run by Neon in the United States (AWS US East, Ohio), so it’s available wherever you sign in.

Documents you don’t sync stay only in your browser, and so do your Pretext, your groups, pins and recent list, your settings, your AI keys, “About you” and any custom readers you write, and the Capture pairing code. A synced document arrives on another device ungrouped and unpinned. Subtextual also keeps a small record in your browser of which documents are synced, their revisions and your account ID. The built-in Guide is saved in your browser like a document but is never synced.

Your browser talks to Neon’s sign-in and database services directly; there’s no other Subtextual server in between. Access rules in the database let each account read and change only its own documents.

A synced document, including its images, can be up to about 10 MB. Larger documents stay on your device.

Two devices, one document

If a synced document was changed on two devices, the version in your account wins, and the other device’s edits are saved there as a separate document named “… — another version”. That copy stays only on that device unless you choose to sync it.

Stopping sync and signing out

Stopping sync for a document removes it from your account. Your other devices keep their local copy, stop syncing it, and show a notice.

Signing out stops syncing on that device and clears your personal things from the browser. Synced documents are removed from it by default; they stay in your account and come back when you sign in. You can choose to keep them on the device instead. Documents that aren’t synced are never deleted without asking: you choose to sync them first, download a backup, or keep them. Signing out also clears your AI settings (your keys, models, “About you”, custom readers, and the Subtextual AI key on that device), your Pretext (including captures from Subtextual Capture and their images) and the Capture pairing code. Your display settings, such as the theme, typeface and text size, stay. Changes to documents you keep upload the next time you sign in to the same account there; if a different account signs in, they stay on the device and are never uploaded to it.

Private sync (end-to-end encryption)

Private sync is optional and off by default. When it’s on, your synced documents are encrypted on your device, with a passphrase only you know, before they’re uploaded. Subtextual’s server stores them but can’t read them: the title, the page, the subtext and the notes are all encrypted. The copies on your own devices stay readable there. A device that remembers the key keeps it in that browser’s storage; lock or sign out to forget it.

Its limits, plainly:

• Usual sync isn’t end-to-end encrypted. Without Private sync, synced documents travel over an encrypted connection and are kept under the database’s access rules, but the server can read them.
• You trust the web app’s code. The encrypting is done by the Subtextual app that editing.help serves to your browser. Private sync protects what the server stores; it can’t protect you from the code that does the encrypting.
• Some facts stay visible to the server: each document’s ID, its size, when it was created and last saved, how many documents there are, how often each is edited, whether it’s been deleted, and who shares with whom.
• Sharing: sharing is off while Private sync is on. Pages you were already sharing when you turned it on, and the notes on them, can stay shared as plain copies, which the server can read; Subtextual marks them as plain copies. To keep one private, stop sharing it.
• Older copies: Older unencrypted copies can remain in recovery history for up to 6 hours, and in a saved restore point for up to 30 days. A copy of the database made before you turned it on keeps them while that copy exists.
• The AI works as before: when you ask, the text in that question’s scope goes to the AI provider, readable, as it does without Private sync. Questions you ask the AI (Ask, the Ghost Editor and the Librarian) send the passages they need straight from your browser to the AI service: your own provider with your own key, or Subtextual’s OpenRouter account with Subtextual AI. That holds even for Private sync documents. They never pass through Subtextual’s servers. With Subtextual AI, it goes through Subtextual’s OpenRouter account to providers that keep no data; Subtextual’s servers don’t see the text.
• Pictures in your Pretext don’t sync while Private sync is on.
• No recovery without your passphrase or recovery key. If you lose both, your synced documents can’t be opened, by Subtextual or by support. The copies on your devices stay readable there.
• The clipboard: if you copy your passphrase or recovery key, it stays in your clipboard, like anything you copy, until something replaces it.
• Turning it off sends every synced document back up unencrypted, from the device where you confirm, and deletes the key. The server can read them again.

If you share a document

You can invite someone to read a document and write beneath it: an editor, a teacher, a writing partner. Only you write the page.

• What goes up: a copy of what you chose to share, kept up to date as you change it: the whole page, or only the paragraphs you pick. With chosen paragraphs, their place on the page goes too (“¶ 3”), and how many paragraphs the page has, so the other person’s numbers match yours. Your own thoughts beneath the page and the AI’s bullets stay on your device, unless you tick Include my subtext for that invitation; then your thoughts beneath the shared paragraphs go too, and the AI’s bullets, marked as the AI’s (never which model or service wrote them). Your Context notes, the document’s brief and Reader, its cover and its links never go. The address you typed for the invitation (if any) and a scrambled form of the invitation link go up too. The link itself is never stored.
• Sync is separate: sharing doesn’t sync the document. You can share a document that otherwise stays only on your device.
• Who can read it: each person you invite, until you stop sharing with them. Each invitation has its own role (Editor: reads and writes beneath; Read only: reads) and its own choice of paragraphs. If you typed their address, only that address can accept. The link works once.
• They see each other’s notes: off unless you turn it on for a document. Off, each person sees the page, their own notes and your replies to them. On, the people on that page also see each other’s sent notes, including those sent before it was turned on, on the paragraphs each of them can read, marked with each person’s name. Drafts never show, and your replies stay with the person you replied to. Turning it off takes effect the next time they look.
• Where: in the same Neon database as synced documents (United States, AWS US East, Ohio), under the same rule that each row is readable only by the people it belongs to.
• When you stop sharing: the copy is deleted at once, and the person can’t open the page again. Their notes stay beneath your page, marked as theirs, until you remove them.
• If you delete the document for good: sharing it stops too.
• The invitation: you can copy the link and send it yourself. If you typed their address and choose Send invitation, Subtextual emails it to that address and no other, from invites@editing.help (shown as “Subtextual”), through Google Workspace. Replies go to info@editing.help, never to you directly. The email holds your name, the document’s title, what they can read and the link. Your name and the title appear only in the message, never as the sender or the subject. At most three emails go out for each invitation, and at most two a day to any one address.
• When notes arrive: when someone sends you notes, Subtextual can email you a short message: who sent notes, how many, on how many paragraphs, and the document’s title. Never their words. At most one every ten minutes for each person on each page. Turn it off for a document in its menu (Email me when notes arrive).

If someone shares a page with you

To write beneath someone’s page, you sign in, so your notes have an author that can be trusted.

• Your account: your email, your name, and how you signed in (see “What sign-in records”).
• Your notes: each note is yours. A note stays private to you, as a draft, until you press Send; then the writer sees it beneath its paragraph. Drafts are saved in your account so they’re not lost, and only you can read them. If you hang a note from words on the page, those words are kept with your note.
• The writer’s replies: you see them beneath your notes while the page is shared with you.
• Other people on the same page: by default they don’t see your notes, and you don’t see theirs. If the writer turns on They see each other’s notes, the people on that page see each other’s sent notes (never drafts) on the paragraphs they can read, marked with each person’s name, until the writer turns it off or stops sharing with them. The page tells you when it’s on, and so does the invitation if it was on when you were invited.
• Read only: if you’re invited to read, you read the page (and the writer’s subtext, if they shared it) and, when the writer turns it on, the notes others send. You write nothing beneath it.
• Emails: if the writer chose to email the invitation, it came from Subtextual through Google Workspace. When you send notes, the writer may get one short email saying that you did and how many. It never holds your words.
• The writer’s AI: when the writer asks the AI about their page, your notes can go with the question, marked with your name, to the AI provider the writer chose (see “The AI is optional”). The writer can turn this off for each document. The invitation says so before you accept.
• When sharing ends: you keep your own notes and the words you hung them from. You never keep the page, and never the writer’s replies. You can remove your notes, or export them, at any time. Removing a note also removes it from the writer’s page.
• Leaving: you can stop reading a page at any time (Leave). Your notes stay yours.

Field Guides

Field Guides is a public shelf of guides from editing.help, inside Subtextual.

• Reading the shelf: it needs no account and uses no cookies. Your browser fetches the list and the guides from Subtextual’s library service at Neon. Subtextual keeps no record of who reads them. To answer a request, Neon’s servers see your IP address; Subtextual uses it only for a moment, in memory, to slow floods of requests, and never stores it. Neon’s own request logs, kept for 3 days, record only that a request happened and when.
• Adding a guide: makes your own copy, kept in your browser like any of your documents. A newer edition never replaces it; you choose whether to add it beside the one you have.
• Publishing (only for the publisher’s account): only what the publisher chooses becomes public, as a snapshot of that document at that moment, with or without its subtext. AI bullets and shared editors’ notes are never included. Later edits stay private until a new edition is published. Unpublishing takes a guide off the shelf; copies readers already added stay theirs.

The AI is optional

With each question, the AI also receives the instructions that shape its answer: your “About you”, the document’s brief, and its Reader, including the instructions of any custom reader you’ve written.

Notes from people you invited: when you ask the AI about a page you’ve shared, the notes people sent you on it go with the question, labelled with each person’s first name (“[Editor: Dana]”), so the AI can tell their words from yours. Turn this off for a document in its menu (“Include their notes when you ask the AI”).

There are two ways to use the AI, and you can use neither. With your own key, or with a Subtextual AI subscription.

With your own key

If you choose to use the AI with your own key, you connect a key from Anthropic, OpenAI or OpenRouter in Settings. The key is stored only in your browser. It isn’t synced, and it never appears in exports or project files.

When you ask the AI something, your browser sends the text in that question’s scope (the whole document by default, or just its paragraph, or linked documents too, if you choose) straight to the provider you connected, under that provider’s own terms and privacy policy. Nothing passes through editing.help, and Subtextual doesn’t see or store these requests. Choosing OpenRouter in Settings also fetches its public list of models; that request carries no writing.

With Subtextual AI (subscription)

Subtextual AI is an optional subscription that includes AI answers without a key of your own. You need to be signed in to subscribe, and the subscription belongs to that account. If you subscribe:

• Payment: Subtextual AI is sold through Link. Stripe, through its Link service, is the seller and takes your payment on its own checkout page, by card, Apple Pay, Google Pay, Link, or another method shown there. For that purchase, Stripe is responsible for your payment information under Link’s privacy policy (link.com/privacy). It stores your card details, email address, name and billing address, and uses your address to work out and pay sales tax or VAT. It may offer to save your details in a Link account. If you use Apple Pay or Google Pay, that wallet passes your payment details to Stripe under Apple’s or Google’s own terms. Subtextual gives Stripe your account email and an internal account ID, so the purchase can be matched to your account. Subtextual never sees your card number.
• What Subtextual stores: with your account, your Stripe customer and subscription IDs, whether the subscription is active, when the current period ends, whether it’s set to end, whether it was sold through Link, which plan you have (the $5 plan or Patron) and your Patron level, and the packs of added replies you’ve bought (amounts and dates). No card details. It’s kept in the same Neon database in the United States (AWS US East, Ohio), in a part the browser can’t reach. It’s kept while your account exists, so you can subscribe again, and deleted with your account. Subtextual also keeps a short record of Stripe’s billing notifications (an ID, the type and the time, with no card or personal details) for 90 days, to avoid processing one twice, then deletes it.
• Your AI key: Subtextual creates a personal OpenRouter key for your account, under Subtextual’s OpenRouter account. It’s stored encrypted on Subtextual’s server and given only to your own signed-in browser, which keeps it in its AI settings. It’s never synced, exported or put in a document.
• Your questions: your browser sends them straight to OpenRouter with that key. No Subtextual server sees them. OpenRouter routes them to the Anthropic Claude model you choose (Claude Haiku 5.5 by default, or Claude Sonnet 5.5), only through providers that keep no copy of your prompts and don’t train on them (currently Google Vertex and Amazon Bedrock). OpenRouter keeps usage information, such as token counts and cost, but not your text.
• The monthly allowance: OpenRouter applies it to your key, using that usage information. Subtextual doesn’t store your questions or the answers anywhere except in your document.
• Email: Link sends your receipts, invoices and any refund notices, and may remind you before a renewal. Subtextual uses your account email only for billing notices, such as a price change, never for marketing.
• Your purchase data: you can ask Link to delete the data from your Subtextual AI purchase. Link then cancels the subscription and Subtextual AI stops, and Subtextual removes its own subscription record when you delete your account.
• The Patrons page: if you’re a Patron and choose to be listed, the name you type is shown publicly on editing.help/patrons/, once editing.help approves it. It’s kept with your account in the same database, and removed when you turn the listing off, stop being a Patron, or delete your account. Viewing the page sends nothing about you to Subtextual beyond an ordinary page request.

What Subtextual never does

• Sell your writing, or share it with anyone you haven’t invited.
• Use your writing to train AI, or allow it to be used that way.
• Read your writing. Database administration is limited to Subtextual’s maker and is used only to keep the service running, never to read writing. Neon, which runs the database, processes it under its own terms.
• Show ads, or use advertising trackers.

Cookies, storage and analytics

• The editing.help website and Subtextual use no analytics and no advertising cookies.
• If you sign in, Neon Auth keeps you signed in with a secure cookie on its own domain. While you’re being sent to Google and back, Subtextual notes in your browser’s session storage that a sign-in is in progress.
• Your documents and settings use your browser’s local storage, as described above.

Deleting your data

When you delete a synced document or your account, or stop a share, the writing is removed from Subtextual’s database right away. Copies can remain in the database provider’s recovery history for up to 6 hours, and in a saved restore point for up to 30 days, after which they expire. Those copies are used only to recover the service after a failure.

• On your device: delete documents in Subtextual, or clear this site’s data in your browser settings.
• A synced document: stop syncing it, or delete it, in Subtextual. Its contents are erased from the database immediately; the remaining copies expire as above. When you delete a synced document, it moves to Archive on your other devices, and a small record with no writing in it (the document’s ID and dates) is kept for 30 days so they learn it was deleted, then erased.
• A Subtextual AI subscription: cancelling stops future charges at the end of the current period. Deleting your account cancels the subscription at once, deletes your AI key, Subtextual’s subscription record, your record of added replies and any Patrons page listing, then deletes your account as below. Stripe and Link keep their own payment records, as the law requires for tax and accounting. If you delete your account after a refundable charge, Subtextual keeps a one-way, keyed fingerprint of your email and card, plus the refund amount and date, for 12 months only to prevent repeated refunds; it can’t be turned back into your email or card number.
• A share: Stop sharing deletes the shared copy at once; the remaining copies expire as above. A stopped share leaves a small record (its title, who it was shared with, and the dates) with your account, without the writing. It’s erased when you delete your account. Deleting a document for good also stops its shares; stopping sync for it doesn’t.
• Notes you wrote on someone’s page: delete them yourself at any time, while sharing or after. Deleting your account deletes every note you wrote, including from writers’ pages. Those writers see that your notes were removed when your account was deleted.
• The emails’ log: Subtextual keeps a line for each email it sends (which invitation, which kind, when; no address and no words), only to hold the limits above. It’s deleted with the invitation.
• If you’re a writer and delete your account: every share and copy of your pages is deleted. The people you shared with keep their own notes, with the words they quoted, never your page.
• Your account: in Settings → Account, Delete account removes your account and every synced document at once, after asking first; the remaining copies expire as above. You then choose what stays in that browser. Synced documents are removed from it by default, or you can keep copies. Documents that were only on the device are listed, and you choose to remove them (the default) or keep them, with an offer to download a backup of everything first. Anything you keep becomes an ordinary local document that never uploads unless you turn sync on again. Your AI settings, Pretext (including captures) and the Capture pairing code are cleared; your display settings and the Guide stay. You can also email info@editing.help.

Subtextual Capture

Subtextual Capture, the companion Mac app, doesn’t send anything to Subtextual in its current version; it has its own privacy policy.

Subtextual for Mac

Subtextual for Mac is the writing app for your Mac, from the Mac App Store. Your writing stays on your Mac: there’s no account, no sign-in, no sync and no subscription, and none of your writing is sent to Subtextual or editing.help. The app goes online only for the things listed below: the AI, if you set it up, Field Guides, if you open it, and pictures you drag in from the web.

• Your documents: each document is a file in a folder you choose. If that folder is in iCloud Drive, or macOS keeps your Documents folder in iCloud, Apple stores and syncs those files under its own terms; the app itself sends them nowhere.
• What the app keeps for itself: your workspace (groups, order and display settings), your Pretext and its pictures, the Guide, a list of your documents, restore points (the last 10 copies, made only before you restore a backup), the folder you chose and which windows were open, and your AI settings and key. All of it stays on your Mac, in the app’s own folder, ~/Library/Containers/help.editing.subtextual.mac/.
• Spotlight: so you can find documents with Spotlight, your Mac indexes each document’s title, its page and your own thoughts beneath it, never the AI’s text. The index stays on your Mac.
• The AI is optional, and uses your own key: you add a key from Anthropic, OpenAI or OpenRouter in AI Settings. The key is kept in the app’s own storage, never in a document, an export, a backup or your writing folder. Before the first request, the app shows which provider will receive your words and asks you to agree. When you ask, the text in that question’s scope goes straight from your Mac to that provider, under its own terms and privacy policy. Listing models in AI Settings also asks the provider for its list; OpenRouter’s list is public and is fetched without your key. Nothing passes through editing.help.
• Field Guides: opening Field Guides or Search Everything downloads the list of public guides from editing.help, and a guide saved to your library checks there for a newer edition. Reading them needs no account. Subtextual doesn’t record who reads what; your IP address is used only briefly, in memory, to limit request rates. Subtextual’s hosting provider (Neon) processes requests under its own privacy policy.
• Pictures from the web: when you drag a picture from a web page into a document, the app fetches that one image from the site it’s on, once, without cookies or a referrer, and keeps it inside the document.
• Nothing else: no analytics, advertising, tracking or crash-reporting service, no update checks (updates come through the App Store) and no downloaded fonts. Links open in your browser. The app’s App Store privacy label is “Data Not Collected”. If you’ve chosen to share crash data with app developers in your Mac’s settings, Apple may pass crash reports on, under Apple’s terms.
• Deleting your data: delete documents in the app or in Finder. Moving the app to the Trash may leave its own folder behind; deleting ~/Library/Containers/help.editing.subtextual.mac/ removes your settings, Pretext, restore points and AI key. Your documents stay in your folder until you delete them.

Subtextual for Mac, downloaded from editing.help

The version you download from editing.help/download/ is the same app, with the differences below. Everything above applies to it too, except where this says otherwise.

• Sign-in, sync, sharing and Field Guides: you can sign in, and then sync your documents, share pages and notes, use Subtextual AI and publish to Field Guides. What that sends, where it’s kept and how to delete it are as described for Subtextual above, with three differences: you sign in with Google in macOS’s own sign-in window, on editing.help; the app keeps your sign-in in your Mac’s Keychain, not in browser storage; and it gets its short-lived access tokens straight from Neon, Subtextual’s sign-in provider, not through editing.help.
• Claude on this Mac, if you turn it on: for a document where it’s on, asking a thought writes that question (the thought, the thoughts above it, its paragraph and, if the document reads the whole document, its paragraphs) to a hidden folder inside your writing folder. Claude Code on your Mac reads it there and writes its answer back, and both files are then removed. Subtextual sends nothing over the network for this. What Claude Code does with the question is under your own Claude account’s terms. If your writing folder is in iCloud Drive, those files sync with it for the moment they exist, like your documents.
• Update checks: about once a day, the app asks editing.help for its list of versions. That request carries your IP address and the names and versions of the app and its updater (Sparkle), never any of your writing, and no profile of your Mac. An update downloads from editing.help only when you choose to install it, and each one is checked against Subtextual’s signing key before it’s installed.
• Nothing else: no analytics, advertising, tracking or crash-reporting service. The app goes online only for sign-in and its tokens, sync and sharing, Subtextual AI and invitation email, Field Guides, the AI provider you choose with your own key (after it asks you, as above), and the update check, each only when used.
• Deleting your data: this version isn’t sandboxed, so it keeps its data in these places instead of the container above: your documents, in the writing folder you chose; ~/Library/Application Support/Subtextual Direct/ (your workspace and order, Pretext, captures and restore points); ~/Library/WebKit/help.editing.subtextual.mac.direct/ (page storage, including version history); ~/Library/Caches/help.editing.subtextual.mac.direct/ (caches and downloaded updates); ~/Library/Preferences/help.editing.subtextual.mac.direct.plist (settings); and a Keychain item, help.editing.subtextual.mac.direct.session, for your sign-in, which signing out removes. Deleting the account itself is as described for Subtextual above.

Children

The editing.help website and Subtextual aren’t directed at children under 13, and don’t knowingly collect information from them. You must be 13 or older to create an account, or older where local law requires. Sharing is for adults working together, such as an editor, a teacher or a writing partner. It isn’t meant for sharing with or from children under 13, or for school use that needs a data-protection agreement.

Who processes data

Changes

If this policy changes, the new version will be posted here with a new date. Any change to what leaves your device will be described before it takes effect.