SpintherSpinther

Privacy

Last updated: November 2026

What changed in November 2026: from the fourth beta, sent to testers in November 2026, Spinther can also count when it crashed or stalled, as part of usage data. A yes given before that change does not cover these counts: they are sent only once you have said yes again — see “Usage data, if you turn it on”. The reports behind those counts stay on your iPhone.

The short version

This website sets no cookies for us and has one optional form: a list you can join for the public beta’s TestFlight link and, once, the news that Spinther has launched. It counts its visits and sign-ups without recording a name, an address or an identifier. The Spinther app has no account and no sign-in, and it collects nothing about you unless you turn usage data on. Your tasks live on your iPhone and sync through your own iCloud, encrypted. We keep no copy of them. If you connect an AI assistant to Spinther, our connector reads them from your iCloud to answer it, and stores none of them. If you also let the assistant make changes, the connector leaves each change it asks for in your own iCloud, its content encrypted, for the app to make. If your Apple Account uses Advanced Data Protection, the connector cannot read your iCloud; you can instead let Spinther on your iPhone answer the assistant through the connector — while Spinther is on screen, or from a notification without opening it — which passes each answer on and keeps none of it; a change your assistant asks for while your iPhone cannot be reached waits with the connector until Spinther next connects, sealed so that only your iPhone can open it. The connector’s own pages, at mcp.spinther.app, set short-lived cookies and run one small script. This website sets no cookies of ours, and only its home page runs scripts, which “This website” below describes.

The rest of this page explains that in the detail the GDPR asks for.

Who is responsible

The data controller is Spinther, at:

Tegnérgatan 36
113 59 Stockholm
Sweden

For any privacy question or request, email hello@spinther.app.

We have not appointed a Data Protection Officer under Art. 37 GDPR: we are not a public authority, and our core activities involve neither large-scale systematic monitoring nor large-scale processing of special categories of data. We are established in Sweden, and therefore in the European Union, so no Art. 27 representative is required.

This website

spinther.app is a set of pages served by a Cloudflare Worker. It sets no cookies of ours and stores nothing of ours in your browser. On this website there is no analytics script, no session recording, no tag manager and no advertising technology of any kind, so there is no consent banner.

The site does count its visits, on the server, as each page is served. A count records which page was opened, the name of the site that linked to it if your browser passed one on (the domain only, such as reddit.com), and whether you arrived from somewhere else or moved between our pages. That is all. It records nothing about you: not your IP address, not your browser or device, and no identifier, so one page view cannot be connected to another or to a person. Automated requests and link previews are left out. A sign-up on the beta form is counted the same way, each time we send a confirmation email and when a confirmation link is opened: the count records which of the home page’s two forms was used and the domain of the page that linked to the home page (which can be this site’s own), plus the time to the second that Cloudflare adds to every count. It holds no name, no email address and no identifier, and we do not match it to an address. Once a week the totals (visits, page views, sign-ups and the referring domains behind them) are added to our records in PostHog, next to the app’s usage counts.

The home page loads exactly two scripts, and nothing else from any other domain. One is a small script of our own that submits the beta sign-up form described below without reloading the page. If your browser has an assistant built in, the same script also lets it look up our public pages, open one, or enter an email address in the form for you; it sends nothing itself, and the form is sent only when you press its button. The other is Cloudflare Turnstile, which checks that a submission comes from a person rather than a bot. Turnstile may store a short-lived token in your browser for that check. It is not an advertising or analytics product and it does not track you across sites. Every other page loads no scripts at all, and nothing is fetched from any other domain. For anything other than the beta, you reach us by writing to hello@spinther.app from your own email.

Serving the site necessarily involves your IP address and request metadata reaching Cloudflare, who host it. That is ordinary web delivery, described under processors and retention below.

The connector for AI assistants, at mcp.spinther.app, is a separate service with pages of its own, and is described under “Connecting an AI assistant” below.

The beta sign-up list

If you give us your email address on the home page, we store the address and the date you confirmed it, and nothing else. No name, no company, no country, no open or click tracking.

It works in two steps: you enter the address, we email you a link, and the address is only added to the list when you click that link. The page that click opens shows the public TestFlight link for the beta. Until you click, the address is kept with the time you sent it and the two details the sign-up count needs (which form, and the referring domain), so that the confirmation can be counted too; the click deletes those details. If you never click, the unconfirmed address and its details are deleted automatically within 48 hours.

The list has exactly two uses: that confirmation email, and one email on the day Spinther launches. It is not a newsletter, it will not be used for anything else, and it is never sold or shared. Anything beyond those two emails is something you asked for, such as an answer to a message you send us. The confirmation and the launch email are sent for us by Cloudflare, named under processors below. You can be removed at any time by writing to hello@spinther.app, and the whole list is deleted 90 days after launch.

Installing the beta itself happens through Apple’s TestFlight, under Apple’s terms: what TestFlight collects is Apple’s, not ours, and the app in the beta collects nothing unless you turn usage data on, as described below.

The app: what it stores, and where

Spinther’s App Store privacy label declares four items, all belonging to the optional usage data described below: Product Interaction (the usage counts), Device ID (the random installation identifier that comes with them), and Crash Data and Performance Data (the counts of crashes, stalls and slow launches). All four are marked as not linked to you and not used to track you, and every other category is Data Not Collected. Concretely:

WhatWhere it lives
Tasks, projects, notes, ideas and reminders, and the history of changes a connected AI assistant made On your iPhone, and mirrored to your own private iCloud database. Every field holding your content is encrypted. With Standard Data Protection, Apple holds the encryption keys. Turn on Advanced Data Protection and the keys stay only on your trusted devices, so not even Apple can read them.
Dictation audio Transcribed on the device as you speak. The audio is never written to a file and never uploaded. The text it becomes is kept with your tasks and ideas, like anything you type.
Calendar events and Apple Reminders Read on your device only, with your permission, and only to display or import them. Never copied to us.
Your preferences On your iPhone, with some synced through your own iCloud so your devices agree.
Diagnostic logs Apple’s on-device logging only, with your content marked private so it is redacted. Nothing is sent anywhere.
Crash, stall and launch reports The reports iOS hands Spinther through Apple’s MetricKit, kept on your iPhone: the newest thirty daily summaries and the newest thirty other reports, marked to be left out of your device backup, and removed by Erase All Data and Settings. A report itself is never sent; if you turn usage data on, Spinther sends only counts taken from it, described below. There is no third-party crash or performance software in the app.

A little sits outside that encryption. The times a task, an idea or an assistant’s change was made are stored unencrypted, because iCloud cannot order encrypted columns, and lists sorted by when things were added, and the assistant history, sort on them. So is whether a task or idea is newly added, for its brief highlight, and the bookkeeping of a change an assistant asks for, described below under Changes your assistant asks for. Many of your preferences, and the settings of the smart lists and the Ideas list, sync through iCloud’s key-value storage rather than with your tasks, and outside this encryption. They include the titles of groups you have collapsed there — in a list grouped by project, a project’s name.

Because this data sits in your iCloud account rather than on our servers, we hold no copy of it, so we cannot recover it for you or produce it in response to a request — from you or from anyone else. The connector for AI assistants, described below, reads it only for a connection you make, and keeps none of it; the changes a connection that may make changes asks for wait in your iCloud, not with us, until the app makes them or they are deleted as described below. Deleting the app and its iCloud data removes it.

Usage data, if you turn it on

Usage data is off until you turn it on. Spinther can send basic usage counts: things like how often you capture a task or idea and which features get used, and whether Spinther crashed or stalled. No personal information, and never the content of your tasks, notes or ideas. Nothing is sent unless you say yes, and you can change your mind in Settings any time.

The counts go to PostHog, an analytics service, on its European servers in Frankfurt, Germany. They are sent to an address on our domain, hermes.spinther.app, which PostHog runs, not us, and which passes them on to those servers through Cloudflare, one of PostHog’s own suppliers. Spinther sends the counts itself rather than through PostHog’s own software kit, so a count contains what is listed here and nothing that a kit would add:

What happens to the time before you agree. A new installation of Spinther keeps a small tally on your iPhone of how its first week went: how many things you captured in your first session — the first seven minutes after you first open Spinther — and how quickly the first three came, whether any of those captures came from outside the app (Siri or a shortcut, the share sheet, a widget, a control, the app icon’s quick actions or an AI assistant you connected), whether any of them was dictated, and whether you captured something on three of your first seven days. Not tied to that first week, it also notes which way of capturing you reach for first, whenever that is, and whether Spinther has full access to your calendars at the moment you say yes. Spinther also keeps a second, smaller tally from your first capture on: how many capture sessions you have had — each time you open a capture sheet or dictate and save something, add a task or idea with the share sheet’s quick buttons, create one through Siri or a shortcut, speak into the Dictate control, or an AI assistant you connected adds tasks or ideas, when you open Spinther or from a notification without opening it, counts once — which sitting is in progress, and when you last saved something. That is how Spinther knows when to ask you the question, which it does after the fifth session. Separately, Spinther notes which app you first imported from, if any. While usage data is off, all of that stays on your iPhone. If you turn usage data on, the first-week tally goes with your yes, once, as a summary, along with how long it had been since you first opened the app, whether you had already reached the first of the two milestones below, and — where a time for it was recorded — how long that took; and the import note becomes part of the short summary described above. The session tally is never sent as such; from then on each count of a capture carries the number of the sitting it belongs to, and that numbering carries on from the sittings before you agreed rather than starting again at one. If either tally shows you had already captured something earlier that same day, one more count goes with your yes, saying that day was a day you captured on — unless that day has already been counted. Those two milestones draw on the first-week tally if you reach them after saying yes: three captures in the first session with at least one dictated or made from outside the app, and capturing on a third day in the first week. Each is sent as one count with its totals. There is no log of your individual actions waiting to be sent, and what you did before agreeing is never sent action by action. If your copy of Spinther was updated from a version that kept no first-week tally, there is none to send; the session tally starts with your first capture on the new version.

Once you have said yes, turning usage data off sends one last count, recording that it was turned off, and then nothing more. It keeps the random identifier on your iPhone, and the beta group if you joined one, so turning it back on continues as the same installation. Erase All Data and Settings removes the identifier, your choice and everything else Spinther keeps for usage data, both tallies, the import note and the beta group included, after which the installation counts as a new one. The app behaves identically whether usage data is on or off.

Your yes or no is also kept in your iPhone’s keychain, which iOS normally keeps even after an app is deleted. It holds that one answer, when it was recorded and which version of what Spinther sends it covered, and nothing else; it never reaches us, and it cannot move to a new iPhone or to your other devices. If you install Spinther again on the same iPhone, it picks up your answer: after a no, we don’t ask again; after a yes, Spinther first tells you that usage data is on and lets you turn it off there and then, and only after that starts again, under a new random identifier that is not linked to the old one. If what Spinther sends has changed since you said yes, or your yes is more than a year old, it asks you again instead, and a yes given on a version of Spinther that did not yet keep this copy is not kept at all. Erase All Data and Settings deletes the kept answer too. Deleting Spinther on its own does not: the answer is on your iPhone, not with us, so we cannot remove it. To clear it, install Spinther again and use Erase All Data and Settings, or erase your iPhone and set it up as new.

Like any request over the internet, each count reaches PostHog from your connection’s IP address, which also passes Cloudflare on the way, as Cloudflare carries the count for PostHog. Spinther tells PostHog, with every single count, not to work out a location from that address, and the project is set so the address itself is not stored. The counts held from Spinther carry no country and no other location.

When the app connects to the internet

Spinther itself reaches the network on five occasions. iCloud sync runs by itself while you are signed in to iCloud, two are things you start, one happens only for an AI assistant you connected to answer from your iPhone, and sending usage counts happens only if you have agreed to it. Of these, only the assistant connection passes your content through us, as described under “Connecting an AI assistant”:

Separately, the first time you dictate, iOS may download its own speech model. That is Apple’s asset pipeline, requested by the operating system rather than by Spinther, and nothing about it reaches us.

Connecting an AI assistant

Spinther has a connector that lets an AI assistant you use, such as Claude or ChatGPT, read your Spinther workspaces, tasks, projects and ideas so it can answer questions about them, and, if you allow it, ask Spinther to change them. When you add it, you choose what the assistant may do: read only; read and write; or read, write and tidy up, which also lets it move tasks and ideas to Trash, move finished tasks to the Archive, and bring them back. It is a service of ours, at mcp.spinther.app, run on Cloudflare. Nothing happens unless you add it to your assistant. The app itself is not involved, except in the one case described under “Answering from your iPhone” below, and the usage-data switch governs none of it.

How it works. When you add the connector, you choose on its connect page what the assistant may do (read only is preselected), then sign in to iCloud on Apple’s own page with the Apple Account your iPhone uses. Apple then gives the connector a sign-in token that lets it read and write Spinther’s data in your iCloud. Each time your assistant asks, the connector reads what it needs from your iCloud and sends the answer to the assistant. On a connection that may make changes it also writes the changes the assistant asks for, as described under “Changes your assistant asks for” below. This works only with Standard Data Protection, where Apple holds the keys to your iCloud data. With Advanced Data Protection on, Apple’s sign-in ends in an error and the connector cannot read or write anything; for such an account the connect page offers Use My iPhone Instead, described under “Answering from your iPhone” below.

What the connector keeps, for each connection you make:

Separately, an assistant app may register itself with the connector: its name and where to send you back after signing in. That registration describes the app, not you.

What it does not keep: your tasks. What a read brings in — only the fields the connector answers from, and on a connection that may make changes, the changes waiting in your iCloud — is held in the server’s memory while the connection is in use, and is never written to the connector’s storage. The connector’s own request logs are switched off, and what it logs, when something fails or when it deletes waiting changes, holds nothing about you. Cloudflare’s request and security logs are covered under retention below.

What your assistant receives. Its answers contain your workspaces, tasks, projects and ideas, as the assistant asks for them. Once they reach the assistant, they are handled by the company that runs it, under your agreement with that company, not by us on your behalf.

Changes your assistant asks for. On a connection that may make changes, the connector does not change your tasks itself. It writes each change the assistant asks for as a record in your own private iCloud database, in a part kept for these changes, and Spinther makes the change the next time you open it, as you would make it yourself, and lists it in a history in Spinther’s settings. The record holds what the assistant asked for — a title, notes, a date — encrypted, as your tasks are. Not encrypted, because they are not your content: the kind of change, whether Spinther has made it yet, which assistant asked, the connection’s random identifier, when it was asked for, taken up or refused, and a random identifier Spinther makes up each time it starts. If Spinther cannot make a change, it adds why to the record: a code, not encrypted, and a message, encrypted. The connector passes that on to your assistant on a later request, and deletes the record as it does.

The records are deleted when they have done their job. A change Spinther has made is kept for an hour afterwards, so that until your iCloud catches up the connector still counts it as on its way, and is then deleted by Spinther the next time you open it, unless the connector has deleted it first. A change Spinther could not make is deleted once your assistant has been told, or the first time you open Spinther 30 days or more after it failed. Until you next open Spinther, a change waits in your iCloud. What happens to waiting changes when you narrow what a connection may do or disconnect is described below.

Answering from your iPhone. If your Apple Account uses Advanced Data Protection, choose Use My iPhone Instead on the connect page. There is then no iCloud sign-in and the connector reads nothing from your iCloud. The first time your assistant asks Spinther something, the connector shows it a link for you to open on your iPhone (your assistant may open it for you); the link opens Spinther with a card that names the assistant, as the connector verified it, and what you allowed it to do, and asks you to connect. From then on, while Spinther is on screen and for about half a minute after you leave it — or for five minutes, shown as a Live Activity, when you choose that in the card — the app keeps a connection open to the connector, and each question your assistant asks is passed down it to your iPhone, which answers from the tasks it holds and sends the answer back; the connector passes the answer to your assistant and keeps none of it. A question and its answer are held in the server’s memory only for as long as that one request lasts, and are never written to its storage — apart from a change held for your iPhone, described below. When your assistant asks later, and Spinther may show you notifications, the connector sends your iPhone a quiet notification saying your assistant is asking. Before the notification is shown, Spinther answers from your iPhone in the background, without opening and whether or not the iPhone is locked, within what you allowed the assistant to do: it answers the questions, and on a connection that may make changes it makes the changes the assistant asks for — reminders included — as you would make them yourself; the notification then says what was answered and made. When a change your assistant asked for, or one held for your iPhone, was sent to Spinther answering that way, the connector, once that answering ends, sends your iPhone one more notification, which shows nothing and carries only the connection’s random identifier: iOS uses it to wake Spinther, still without opening, to do what answering that way could not — set, move or cancel the alarms of escalated reminders, bring its notifications, badge, widget, control and Spotlight entries up to date, and give your iCloud time to carry the change to your other devices — instead of leaving that until you next open it; Spinther sends the connector nothing in return. iOS delivers it in its own time, or not at all — never to a Spinther you closed from the app switcher, nor with its Background App Refresh turned off — and Spinther then catches up when you next open it. It does not answer that way after you choose Stop Answering in Spinther, until your iPhone has been unlocked once after a restart, or after thirty runs of answers within 24 hours with no tap, Answer, link or opening of Spinther of yours between them — a run being what it answers within ten minutes of starting (Spinther reports an opening at most once a minute, so opening it again within that minute can leave one run counted); the notification then waits for you: choosing Answer on it lets Spinther answer without opening, and tapping it opens Spinther, which answers. If neither happens in time, or Spinther may not show notifications, the connector shows you the link again, and opening it starts Spinther answering again, with no card the second time. Each time Spinther comes to the screen it tells the connector so, at most once a minute, sending only the code your iPhone uses to connect; the connector then starts that count of runs again and says whether changes are waiting for your iPhone, and keeps nothing of the visit. A change your assistant asks for on such a connection is made on your iPhone at once, as you would make it yourself, and listed in the same history; nothing waits in your iCloud. If your iPhone cannot be reached when your assistant asks for a change — it is off or offline, or no notification brought Spinther in time — the connector holds the change instead of asking you to open the link first, and tells your assistant it is waiting, with the link to make it at once. (Not when your iPhone has not been unlocked since it restarted: your assistant is then told to ask again.) The connector sees the change only in its memory, as it sees every question, while it seals it for your iPhone: encrypted to a key Spinther made on your iPhone, whose private half stays in its keychain, so what the connector keeps cannot be read with anything we hold. The connector sends it to Spinther the next time your iPhone connects — when you open the link, choose Answer, or open Spinther, or when your assistant next reaches it within the limits above — and Spinther makes it as it makes any other. After Stop Answering, opening Spinther alone does not send it; opening the link or choosing Answer does. A change Spinther could not make is reported to your assistant on a later answer. Open a link only when you have just connected Spinther from your assistant yourself: whoever opens it in Spinther answers that assistant with their own tasks, which is why the card names the assistant and warns when it could not verify the app’s name. A connection whose link is not opened within fifteen minutes of connecting expires.

For such a connection the connector keeps, instead of a sign-in token: a scrambled (SHA-256) form of the one-time code the first link carries, kept marked as used once your iPhone has connected so that a second opening of the link within its fifteen minutes is told it was used, and after that a scrambled form of the code your iPhone uses to connect from then on; what you allowed the assistant to do; which assistant, with the name and, where it registered one, the web address its app registered under, so the card can name it; your time zone and first day of the week; when the connection was made, when it was last used and when a link was last shown; when your assistant was first asked to open the link for you without having done so, and whether it was seen not to, at most until your iPhone next connects; a timer that ends the connection after 30 days unused; while Spinther may show you notifications, the address Apple gives Spinther on your iPhone for sending it notifications, and whether it is a development build’s or one from TestFlight or the App Store, which your iPhone sends when it connects and removes when it connects with notifications turned off or set to deliver quietly, used only to tell you your assistant is asking and, once the address is shown to be your iPhone’s, to wake Spinther without showing anything after it was sent a change in the background; whether your iPhone has answered a notification sent to that address, which shows the address is your iPhone’s, until the address changes or is removed; the times notifications went to an address not yet shown to be yours, those of the last 24 hours counted, so that no more than three a day go to an address that might be someone else’s, older times dropped when the next such notification is sent and the rest kept until the connection ends; how many notifications were sent since your iPhone last connected, until it next does; when the last one was sent, with a scrambled (SHA-256) form of its one-time code, until your iPhone shows it received that notification or another is sent; when each run of answers your iPhone gave in the background began, those of the last 24 hours counted and older ones dropped the next time it answers in the background, all of them forgotten when you tap a notification, choose Answer, open the link or open Spinther; while a question is waiting on a notification, the same scrambled form of its one-time code, with when it was sent and the address it went to, which your iPhone sends back when it connects in answer, to show the notification reached it, or to say it has not been unlocked since it restarted, dropped once your iPhone connects or the wait ends; the public half of the key that seals changes for your iPhone, which can seal but not open them, sent by your iPhone when it connects; while your iPhone cannot be reached, each change your assistant asks for, sealed as described above, with which kind of change it is, when it was asked for and how many times your iPhone was sent it and could not get at it or did not answer, and, for one Spinther could not make, that kind, that time and the reason’s code, never Spinther’s own words about it; and a random identifier for the connection, which takes the place of the scrambled Apple Account identifier, since no Apple Account is involved. The one-time code itself is kept only inside your assistant’s grant, encrypted under the access your assistant holds, as the sign-in token’s key is. The code your iPhone uses is kept on the iPhone, in its keychain, where it never syncs or moves to another device, and is removed when you disconnect in Spinther or erase all data there. Erasing all data also asks the connector, if it can be reached then, to end each such connection, which deletes what it keeps for it.

Counting use. So that we can tell whether the connector works and is used, it keeps counts with Cloudflare: one for each new connection, and whether it reads from your iCloud or answers through your iPhone; when your assistant uses one of its tools, which tool and whether it worked or the reason it did not, your iPhone not being connected among the reasons; each change your assistant asks for, with its kind, such as adding a task; each change Spinther could not make that your assistant is told about, with the reason’s code; when the connector finds that Apple has ended a connection’s sign-in; each time connecting the same assistant again replaces a connection; and, for a connection answered from your iPhone, each time it shows the link, and whether it was the first, a later one, or one your assistant opened for you, and each notification it sends, with whether your iPhone answered in time — in the background, or after your tap — said it had not been unlocked since it restarted, or why the notification could not be sent, each notification it sends to wake Spinther after a change, or why it could not be sent, and each change it holds for your iPhone, with the tool that asked for it. Every count records which assistant it was for, what you allowed it to do and when, besides those details, and nothing else: nothing about you or your device, no identifier for you or the connection, and nothing you or your assistant wrote. What you ask your assistant is not recorded. Changing what an assistant may do later is not counted.

So that we hear first when the connector fails, it also keeps records of its own health with Cloudflare, apart from the counts: for each request it answers, which kind of page or endpoint it was, the response’s status code, how long it took and when; and for each failure of one of its parts — its own storage, Apple’s notification service, Apple’s iCloud sign-in, or fetching an assistant’s details at the start of a connection — the error’s code and when. They record nothing else: not the address of the page, nothing about you or your device, no identifier for you or the connection, and not which assistant it was.

Its pages. The connector’s own pages set short-lived cookies to complete a sign-in, for at most ten minutes, and the connect page runs one small script that reads your time zone and first day of the week from your browser and sends them with your choice. Both are needed for the connection you asked for, so there is no consent banner there either.

Limiting requests. To protect the connector from abuse, Cloudflare counts, for one minute at a time, how often each internet address starts a connection answered from an iPhone, and how often it makes each of a few requests to the connector that anyone can make: an assistant app registering itself, the connect page, Disconnect, the connections page and its forms, and Apple’s return from its sign-in page. Requests past a limit are turned away until the minute is up. Each count is kept under a scrambled (SHA-256) form of your IP address, or for an IPv6 address of its first half, never the address itself, and the connector stores neither. Cloudflare keeps each count at the data centre that handles your request, which may be outside the European Union. A scrambled IP address can still be matched to the address by trying every possible one, so it is treated as personal data; Cloudflare holds it for us as our processor, and the legal basis is the one for serving and securing the connector, under Legal bases.

The connections page. At mcp.spinther.app/connections you sign in to iCloud the same way and see the connections your assistants can still use — which assistant, when it was last used and what it may do — and can change what each may do. A connection an assistant has itself given up is not listed; Disconnect still reaches what it kept. A connection answered from your iPhone is not listed there either, since no Apple Account signed in for it: it belongs to the iPhone, and is changed or ended in Spinther’s settings, under Connected Assistants. To keep you signed in there for ten minutes, the page sets a cookie holding a random token and keeps a matching entry, naming the scrambled identifier for your Apple Account, which is deleted after those ten minutes. The sign-in token Apple returns for that visit is used once, to learn which Apple Account signed in, and is not kept; so is the one from the sign-in that narrowing a connection asks for, which is also used to delete changes as described next.

Narrowing what a connection may do there also deletes changes it asked for before then that Spinther has not yet made. Setting it to read only deletes all of those, and those it could not make that your assistant has not been told about; setting it from read, write and tidy up to read and write deletes those that move something to Trash or the Archive or back, or turn an idea into a task or a project. To do that, narrowing asks you to sign in to iCloud again, and the connector deletes those changes from your iCloud at once, with that sign-in, used for this visit only and not kept, or with the connection’s own sign-in if your assistant used it recently; if some had not been started yet, the page says how many. If what the connection may do was changed elsewhere while you were signing in, nothing is changed and the page says so. If iCloud cannot be reached at that moment, the page says so, and the connector deletes them the next time your assistant uses the connection; if you open Spinther before then, Spinther makes them. Allowing a connection to do more needs no second sign-in.

Disconnecting. Go to mcp.spinther.app/disconnect and sign in with the same Apple Account: every connection between Spinther and an AI assistant ends, and the sign-in tokens kept for them are deleted. The connector then uses that sign-in, for this visit only and without keeping it, to delete from your iCloud every change your assistants asked for that is still there, so Spinther does not start making any of them. If some had not been started yet, the page says how many. If iCloud cannot be reached at that moment, the page says so, and the next time you open Spinther it makes the changes still waiting; disconnect again before then to delete them. When you connect the same assistant again, the sign-in you complete deletes the changes the connection it replaces left waiting, whenever iCloud can be reached; no page reports it. When a connection goes 30 days unused, the connector deletes the changes it asked for only if it still has that connection’s iCloud sign-in open from your assistant’s recent use; otherwise, and whenever Apple ends the sign-in, Spinther makes them the next time you open it. To narrow what an assistant may do without disconnecting it, use the connections page instead. Remove Spinther from your assistant’s connectors too, so it stops offering to use it. If you can no longer sign in there, for instance because you have since turned on Advanced Data Protection, removing Spinther from your assistant is enough: once the assistant stops using the connection, what the connector keeps is deleted within 30 days. A connection answered from your iPhone is not ended there: in Spinther, under Settings and Connected Assistants, its Disconnect ends it at once, deleting what the connector keeps for it and your assistant’s access with it, and removes the code from your iPhone; remove Spinther from your assistant too. Without that, it is deleted 30 days after the assistant last used it.

Permissions the app may ask for

Each is optional and revocable at any time in iOS Settings: microphone (dictation), notifications (reminders, and telling you when an assistant you connected through your iPhone is asking), calendar (read-only, to show your events), reminders (to import them) and alarms (for escalated reminders).

Spinther asks when you first use the feature that needs it. The one exception is reinstalling the app onto a device that already holds your iCloud data, where notifications and calendar are requested up front so your existing reminders keep working.

Spinther never requests location. There is no location code anywhere in the app.

Legal bases

We process personal data only where Art. 6(1) GDPR gives us a lawful basis. There is very little to process:

PurposeDataBasis
Answering your email, including privacy requests and beta enquiries; replies to the question in the beta confirmation email are also read to shape Spinther and counted, by hand, each week Your email address and whatever you write to us Legal obligation — Art. 6(1)(c) for rights requests under Art. 12–22; legitimate interests — Art. 6(1)(f) for ordinary correspondence, including a reply you choose to send to the question in the beta confirmation email: our interest is learning what the beta is for, and you can object at any time
Sending you the beta’s TestFlight link and, once, the news that Spinther has launched Your email address and the date you confirmed it Consent — Art. 6(1)(a), given by clicking the link in the confirmation email, withdrawable at any time under Art. 7(3)
Keeping the sign-up form free of bots Connection metadata assessed by Cloudflare Turnstile Legitimate interests — Art. 6(1)(f) in protecting the form from automated abuse
Basic usage counts from the app Everything listed under “Usage data, if you turn it on”: usage counts, the counts of crashes, stalls and slow launches, your major iOS version, kind of iPhone, build of Spinther and how it was installed, the beta group if you opened an invite, the short set-up summary (imports and number of projects), the first-week tally sent with your yes, the sitting number on each capture count, and a scrambled random installation identifier; never your content Consent — Art. 6(1)(a), off unless you turn it on, withdrawable in Settings at any time
Connecting an AI assistant, if you add the connector Everything listed under “What the connector keeps”: the encrypted iCloud sign-in token, your time zone and first day of the week, what you allowed the assistant to do, which assistant, the connection’s random identifier and the scrambled identifier for your Apple Account; the ten-minute session described under “The connections page”; your workspaces, tasks, projects and ideas while they are read to answer the assistant, never stored by the connector; on a connection that may make changes, the changes the assistant asks for, written to your own iCloud for Spinther to make; and, for a connection answered from your iPhone, what “Answering from your iPhone” lists in place of the sign-in token, including the notification address and the notification that wakes Spinther after a change, and your answers while they pass through to the assistant, never stored, and the changes held for your iPhone while it cannot be reached, sealed so that only your iPhone can open them Contract — Art. 6(1)(b), necessary to provide the connection you asked for; Disconnect ends it
Serving and securing this website and the connector IP address, request metadata, technical logs Legitimate interests — Art. 6(1)(f) in operating and protecting the site; strictly necessary to deliver the page you asked for
Counting visits and beta sign-ups on this website Read from the request as the page is served, then discarded: the referring site (except that, for a sign-up, its domain is kept as described next), whether your browser says it is opening a page, and your browser’s name, used only to leave out automated requests. Kept: the page, the referring domain and whether it was a new visit, and for a sign-up which form was used and the referring domain, with no name, address or identifier. A sign-up’s two details wait beside the unconfirmed address, for at most 48 hours, until it is confirmed Legitimate interests — Art. 6(1)(f) in knowing whether anyone reads the site, how they found it and whether it leads them to the beta
Counting use of the connector, if you add it The counts described under “Counting use”: which assistant, what you allowed it to do, when, and which tool, kind of change or reason’s code, with nothing that identifies you; and the health records described there: each request’s kind, result and time, and each failure’s code, with when Legitimate interests — Art. 6(1)(f) in knowing whether the connector works and is used

Legitimate interests assessment. For delivering and securing the site and the connector, our interest is in keeping them available and protected from abuse. No less intrusive means achieves this, the data involved is limited to connection metadata, it is never used for advertising or profiling, it is kept briefly, and it does not override your rights. For counting visits and sign-ups, our interest is in knowing whether the site is read at all and whether it leads anyone to the beta; the count is taken from the requests we already have to answer, nothing is read from your device, and what is kept holds no name, address or identifier. A count carries the time to the second, so with very few sign-ups it could in principle be matched to an address by time; we do not do that, and a count is deleted after three months. A sign-up’s two details sit beside the unconfirmed address for at most 48 hours, only so that the confirmation can be counted. For counting use of the connector, our interest is in knowing whether it works and is used; the counts are taken from requests the connector already handles, your assistant’s and your own sign-ins, hold no identifier and none of your content, and cannot be traced back to you. You may object at any time under Art. 21 by writing to us.

Nothing here relies on consent except the two things that ask for it in so many words: the beta sign-up list, and usage data in the app. Both are opt-in, both can be withdrawn at any time, and withdrawing costs you nothing.

Processors

We use three processors. Cloudflare and PostHog each act under a data processing agreement and only on our documented instructions. Apple holds our email under its standard iCloud terms, and we have no separate data processing agreement with Apple.

ProcessorPurposeTransfer safeguard
Cloudflare, Inc. Hosting, CDN and TLS for this website, Turnstile bot protection on the beta sign-up form, storing the confirmed sign-up list and sending its two emails, storing the site’s visit and sign-up counts; running the connector for AI assistants, and storing what it keeps and its counts of use. Cloudflare uses its own suppliers, listed at cloudflare.com/gdpr/subprocessors Global edge including the US; what the connector keeps for each connection is stored in the EU, apart from the short-lived copies described under International transfers. EU–US Data Privacy Framework; EU Standard Contractual Clauses, with the UK Addendum and the Swiss amendments, where the Framework does not apply. These are in Cloudflare’s data processing addendum, which forms part of our agreement with Cloudflare
PostHog, Inc. Receiving and storing the app’s usage counts, only from people who have turned usage data on, and this website’s weekly visit and sign-up totals. PostHog uses its own suppliers to run the service, listed at posthog.com/subprocessors; the storage itself is in Germany The counts are held on PostHog’s European servers in Frankfurt, Germany. PostHog is established in the United States, so where it needs access from outside Europe we rely on the EU Standard Contractual Clauses in its data processing agreement, which we signed on 21 September 2026
Apple Receiving and storing our email correspondence with you at spinther.app, in an iCloud Mail mailbox Apple says it generally stores personal data with Apple Inc. in the United States, and relies on the EU Standard Contractual Clauses for transfers out of the European Economic Area, the United Kingdom and Switzerland. These are Apple’s own arrangements, described in its privacy policy, not an agreement we have signed

Apple’s other roles

Apart from holding our email, three things happen through Apple, and none is a processor relationship, so none belongs in the table above:

We will update this section before engaging any new processor.

International transfers

Cloudflare is established in the United States and runs this site and the connector for AI assistants on a global edge network. What the connector keeps for each connection you make is stored in the European Union, and what it reads or writes while answering your assistant, what it passes on from your iPhone for a connection answered there, and the changes your assistants asked for that it reads from your iCloud to delete them when you disconnect or connect the same assistant again, is held in memory there too. Your requests and its answers, including the answers your iPhone sends and the iCloud sign-in token each time you sign in for the connector, are still handled by the Cloudflare data centre nearest to you. When that data centre reads one of the connector’s records about your connection, such as your assistant’s grant, it may keep a short-lived copy there, and Cloudflare logs the connection’s random identifier outside the European Union for billing and debugging. So your connection metadata, your requests and the answers as they pass through, the short-lived copies, the scrambled addresses the request limits count under and that identifier may be handled and stored outside the European Economic Area, the United Kingdom and Switzerland. The connector’s counts of use and health records hold nothing about you, and Cloudflare offers us no way to choose where they are kept. For those transfers we rely on the EU–US Data Privacy Framework where the recipient is certified, and otherwise on the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Module 2), with the UK International Data Transfer Addendum for UK transfers and the Swiss addendum under the revised FADP. You can request a copy of the relevant safeguards by emailing us.

If you join the beta sign-up list, your email address is stored by Cloudflare in the EU, in a store we have restricted to Cloudflare’s EU jurisdiction. The two emails are sent through Cloudflare’s email service, which we cannot restrict to the EU, so for those two sends the address may be handled outside the European Economic Area, the United Kingdom and Switzerland, under the safeguards described above.

The app’s usage counts are held on PostHog’s European servers in Frankfurt. PostHog itself is established in the United States, so for any access from outside Europe we rely on the EU Standard Contractual Clauses in its data processing agreement, with the UK Addendum and the Swiss addendum where those apply. PostHog also uses its own suppliers to run the service, which it lists at posthog.com/subprocessors. One of them, Cloudflare, carries each count from hermes.spinther.app, the address on our domain that PostHog runs, to PostHog’s servers. PostHog does not promise that a count enters Cloudflare’s network inside Europe, so on that hop it may pass through a data centre outside the European Economic Area.

Our email correspondence with you at spinther.app is kept in an iCloud Mail mailbox. Apple says it generally stores personal data with Apple Inc. in the United States, and that it relies on the EU Standard Contractual Clauses for transfers of personal data out of the European Economic Area, the United Kingdom and Switzerland. Those are Apple’s own arrangements, and we have no separate agreement with Apple about them. Apple describes them in its privacy policy at apple.com/legal/privacy. The same holds for the notifications the connector asks Apple’s push notification service to deliver, for a connection answered from your iPhone: the one saying your assistant is asking, and the one that wakes Spinther after a change.

How long we keep things

DataKept for
Email correspondence, including privacy requests and replies to the question in the beta confirmation email Up to 24 months after the exchange ends, then deleted, unless it is needed for a legal claim. The weekly count of replies is a number, not the replies, and holds no address
An unconfirmed email address from the beta sign-up form Up to 48 hours, then deleted automatically, together with its two sign-up count details (the form and the referring domain). If you never click the link, we never keep it
A confirmed address on the beta sign-up list Until 90 days after launch, then the whole list is deleted — or immediately, whenever you ask
Cloudflare request and security logs Retained briefly by Cloudflare under their own rotation, and never copied into any store of ours
The connector’s request limits, under a scrambled IP address Counted over a one-minute window; never copied into any store of ours
Visit and sign-up counts for this website Three months, then deleted by Cloudflare. The weekly totals made from them are kept in PostHog alongside the app’s usage counts. Neither holds a name, an address or an identifier
Usage counts, if you turned usage data on Kept by PostHog, which guarantees to hold them for a year on the plan we are on and names no date for deleting them after that. We would rather tell you that than promise a shorter period we cannot enforce — the period is set by the plan and cannot be shortened by us. The counts carry nothing that names or contacts you, and turning usage data off stops new ones at any time
What the connector keeps, if you connect an AI assistant The encrypted iCloud sign-in token: until you disconnect, Apple ends the sign-in, you connect the same assistant again, or the connection goes 30 days unused, whichever comes first. What you allowed the assistant to do: as long as the token. The time you set a connection to read only, or from read, write and tidy up to read and write: until the changes that this deletes are deleted, which is at once unless iCloud cannot be reached then, or the connection ends. The sign-in token from the sign-in that narrowing asks for: not kept beyond that visit. Your time zone and first day of the week, which assistant, the connection’s identifier and the scrambled identifier for your Apple Account: until you disconnect, and at most 30 days after your assistant last renewed its access. Your assistant’s access tokens: an hour each. A session on the connections page: ten minutes. An assistant app’s registration, where it makes one: up to 90 days after it was last used. Your tasks are never stored. The changes your assistant asks for are kept in your own iCloud, not by us, for as long as “Changes your assistant asks for” above describes. For a connection answered from your iPhone: what the connector keeps for it, until you disconnect in Spinther or the connection goes 30 days unused; the notification address, until then too, or until your iPhone connects with notifications turned off, you erase all data in Spinther, or Apple says it no longer works; whether that address has been shown to be your iPhone’s, until the address changes or is removed; the times of notifications sent to an address not yet shown to be yours, counted for 24 hours, dropped once older than that when the next such notification is sent, and otherwise kept until the connection ends; the times of the runs your iPhone answered in the background, counted for 24 hours and kept no longer than the list under “Answering from your iPhone” says; the count of notifications since your iPhone last connected, and the last one’s time and scrambled code, likewise; the scrambled one-time code, until the connection ends, marked as used once your iPhone connects; a question and its answer, only while that one request lasts, apart from a change held for your iPhone: that change, until Spinther answers it, your iPhone has three times been sent it and could not get at it or did not answer, when it becomes one Spinther could not make, you set the connection in Spinther to read only (or, for a change that moves something to Trash or the Archive, from read, write and tidy up to read and write), or the connection ends; and for one Spinther could not make, its kind, time and reason, until your assistant is told, you set the connection to read only, or the connection ends. The counts of use and the health records: three months, then deleted by Cloudflare
Your usage-data answer, kept on your iPhone Until you remove it with Erase All Data and Settings, or erase your iPhone and set it up as new. It never reaches us, so we cannot delete it for you
Your tasks and everything you write in the app For as long as you keep them. They are in your iCloud, not ours, so only you can delete them — the app’s Erase All Data and Settings does exactly that

Your rights

Under the GDPR and UK GDPR you may request access to your personal data (Art. 15), correction of it (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and portability (Art. 20), and you may object to processing based on legitimate interests (Art. 21).

Where we rely on consent — the beta sign-up list and usage data in the app — you may withdraw it at any time under Art. 7(3): write to us, or reply to any email from us, for the list, and use the switch in Settings for usage data. Withdrawing is as easy as giving it and costs you nothing. Deleting the app does not withdraw a yes by itself; the switch in Settings, or Erase All Data and Settings, does.

In practice the personal data we hold is the correspondence you have sent us, your email address if you joined the beta sign-up list, and, if you have connected an AI assistant, what the connector keeps. Email hello@spinther.app and we will respond within one month, as Art. 12(3) requires.

Usage counts are the exception, and the reason is structural. They arrive under a scrambled random identifier and with nothing else that points to a person, and Spinther tells PostHog not to build any profile behind that identifier — so there is no record there to look anything up by. We cannot tell which counts came from your installation, and cannot look them up, correct them or delete them for one person (Art. 11). What you control is on your iPhone: the switch in Settings stops the counts, and Erase All Data and Settings discards the identifier.

What the connector keeps is filed under the scrambled identifier for your Apple Account, which we cannot work out from your name or email address. So we cannot find it from an email to give you a copy of it or correct it (Art. 11(2)). You can see part of it yourself: after the same sign-in, the connections page at mcp.spinther.app/connections lists each connection your assistant can still use, with its assistant, its last use and what you allowed it to do, and lets you change that. The way to erase all of it is Disconnect, which deletes it at once: sign in at mcp.spinther.app/disconnect with the same Apple Account. If you cannot sign in there, removing Spinther from your assistant has it deleted within 30 days of the assistant’s last use of the connection. What it keeps for a connection answered from your iPhone is filed under that connection’s random identifier, not an Apple Account, and we cannot find it from an email either; you can see it and erase it at once in Spinther, under Settings and Connected Assistants, with Disconnect, and removing Spinther from your assistant has it deleted within 30 days likewise. The connector’s counts of use and health records are the exception: they are filed under nothing that points to you or a connection, so, like the app’s usage counts, they cannot be found for one person, and they are deleted after three months.

Children

Spinther is intended for adults. We do not knowingly process personal data from children under 16. If you believe a child has sent us personal data, write to us and we will delete it.

Automated decision-making

There is none. We carry out no automated decision-making, and no profiling, producing legal or similarly significant effects (Art. 22). Usage counts are read in aggregate, to see how the app is used; nothing in the app or for you changes because of them. The app contains no AI or machine-learning model that evaluates you in any way. An AI assistant you connect to Spinther is run by the company that provides it, not by us.

Security

Everything is served over HTTPS. Your content in the app is encrypted in iCloud, apart from the little named under The app: what it stores, and where. The app talks to no server of ours — except the connector, in the one case where you let it answer an assistant from your iPhone, after your tap and over an encrypted connection — and has no account database and no third-party SDK, which removes most of the surface a notice like this usually has to account for. The one server of ours that touches app data is the connector for AI assistants, and only for people who connect one: it stores each sign-in token encrypted, so that our storage alone cannot open it, and never stores your tasks, nor the answers your iPhone sends through it; a change it holds for your iPhone it stores only sealed to your iPhone’s key, so that our storage alone cannot open it either; on a connection that signs in to iCloud, the changes your assistant asks for it writes only to your own iCloud, their content encrypted there. Apart from what the connector keeps, the one store of app data outside your iPhone and your iCloud is the usage counts held by PostHog, and only for people who turned usage data on. Access to the little we do hold is limited and multi-factor protected.

No system is perfectly secure. If you believe you have found a security issue, please email hello@spinther.app.

In the unlikely event of a personal data breach likely to risk your rights and freedoms, we will notify the supervisory authority without undue delay and within 72 hours where feasible (Art. 33), and notify you directly where the risk to you is high (Art. 34).

Changes

We may update this notice as the product changes. The date at the top always shows when the current version took effect. If a change materially affects how we handle your data, we will say so prominently here before it takes effect.

Complaints

If you think our processing infringes the GDPR you may lodge a complaint with a supervisory authority (Art. 77) — in the EU or EEA state where you live, where you work, or where the issue arose. Our lead supervisory authority is the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY); in the UK it is the Information Commissioner’s Office. We would genuinely rather hear from you first, if you are willing.