Privacy policy
What knots keeps about you, where it lives, and who can see it. Last updated 23 November 2026.
Signing in
You sign in with Google through Cloudflare Access. Access uses your basic Google profile, including your name and email address, to sign you in. knots checks the signed token Access gives it and stores your email address as your account identifier. knots does not ask Google for your contacts, files, mail or calendar.
Signing in takes one of the service's limited Cloudflare seats, even if you never edit anything. A seat is freed after about a month without signing in. To watch capacity, Alex can see which accounts hold seats; his private reports carry totals only.
What knots keeps
- Your knots: their items, notes and attachments.
- A history of the edits it receives, which is how your screens stay in sync. It includes earlier text, when each edit was made and received, a temporary session ID for edits from a browser (or the label "api" for edits from tools), and some edits that were refused.
- API keys, if you make one. knots shows the full key once and stores its hash, ID, short prefix, your label, your email address, and when it was created, roughly last used and revoked. The record stays after you revoke the key.
- A monthly activity record. To count active accounts, knots records a hash of your email address for each calendar month (UTC) in which it accepts an edit from you or your tools. The hash is the same every month, so it can be matched to a known email address. These records do not expire on their own. Alex's monthly report shows only the total number of active accounts.
knots carries no ads and uses no advertising or third-party trackers.
In your browser
Each view remembers, in that browser, your email address, your list of knots, the knots you have opened, edits not yet sent, and your display preferences. Cloudflare Access sets a sign-in cookie. The list view also saves the app's own files so it opens offline. Someone using the same browser profile offline may see the last account's saved knots even after its sign-in has expired, so on a shared device, clear the site data for knots.2ho.me and dolist.2ho.me when you finish. Let pending edits sync, and save any old do list data or files you want to keep, before you clear it: clearing can erase the only copy.
If a browser holds data from the old do list, the list view offers to bring it in. Choosing "Bring it in" copies the old items, notes and readable files within the size limit into whichever account is signed in. After checking the server copy, the app clears the old entries that did not change meanwhile. Files over the size limit stay on the device, where you can save them.
Who handles it
Google and Cloudflare Access handle sign-in. Cloudflare hosts your knots, their history and your uploaded files, and may keep service request logs. If you email support, Cloudflare forwards your address and message to Alex's Google mailbox so he can answer. Google and Cloudflare handle this data under their own privacy policies.
Who can see it
You. Other people who sign in cannot see your knots. If you create an API key, anyone holding it can read your email address, knots, edit history and files, and change your knots, until you revoke it. If you share an exported Knotend link, anyone with it can read the items and graph it contains; JSON exports also include notes. Alex, who runs knots, can technically read stored data, and looks at it only to fix a problem you have reported or to keep the service working. He does not sell your data or use it for advertising.
Removing things
Removing an item or attachment in knots hides it from your knot. Its record and edit history remain, and an uploaded file can still be fetched through your account by its file ID. Cloudflare can recover earlier versions of the knot database for up to 30 days; that recovery covers the database, not files.
To have your account removed, email [email protected] from the address you sign in with. Alex will delete your knots and their history, your account's list of knots and its text previews, all files uploaded under your account, your API key records and your monthly activity records, and confirm when it is done. Database recovery copies may remain for up to 30 days after that. Copies in your own browsers go when you clear the site data, and anything you downloaded or exported is yours to delete.
Changes and contact
If this policy changes, the new version will be posted here with a new date. Questions: [email protected].