Draft: not yet in force. The service is not open to the public yet.
Privacy notice: Watchkeeper phone access and shared library
Draft for the owner's approval. Text in square brackets and bold is a placeholder: it is filled or removed before this page goes live.
[DATE: Last updated … (set on approval)]
In short
- Watchkeeper runs on your Mac. Your projects stay there unless you switch on phone access or the shared library.
- On its first run, the panel makes you a free phone login at watchkeeper.nexodyne.org. That call sends a password made on your Mac and a scrambled form of a key for your Mac. It sends nothing about your projects.
- Only while you have phone access switched on does your Mac send what the panel shows to our server, so your phone can show it. Switching phone access off deletes the server's copy at once.
- Our server can read what your Mac sends while phone access is on. It is not end-to-end encrypted (section 6).
- We hold no email address, no real name and no payment details. We never sell your data, we run no ads and no third-party analytics, and we use nothing you send to train AI models.
- The shared library is off until you switch it on. Then each problem you solve and save is scrubbed on your Mac, waits 24 hours where only you see it, then other members who share can search it without seeing who shared it. It is pseudonymized, not anonymous, and the scrub cannot catch everything (section 7).
- Delete your login at any time: in the panel, on your phone, or by email to info@nexodyne.org.
1. Who we are
1.1 Nexodyne Limited, a company registered in England and Wales (company number 16539459), whose registered office is at 71–75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom ("Nexodyne", "we", "us"), runs watchkeeper.nexodyne.org. We are the controller of the personal data this notice describes. That means we decide how and why it is used. We are responsible for it under the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018 and, for people in the European Union, the EU GDPR.
1.2 For anything about your data, email info@nexodyne.org.
2. What this notice covers
2.1 This notice covers the phone login, phone access and the shared library for Watchkeeper. That means the calls the plugin makes to watchkeeper.nexodyne.org, and the pages you use there on your phone.
2.2 It does not cover what Watchkeeper keeps on your own Mac. That stays in local files we cannot see, including your own library of solved problems (7.1). Your login is kept on your Mac in ~/.wk/hosted.json: your username, your password, your Mac's key and a few dates. Only your user account can read that file.
2.3 nexodyne.org has its own privacy notice. The jobs Watchkeeper starts run with your own Claude Code login and plan, under Anthropic's terms and privacy policy, not ours.
3. What leaves your Mac, and when
3.1 On the first run. When you first open the panel, the plugin makes your phone login. It sends a password made on your Mac and a scrambled form (a SHA-256 hash) of a key for your Mac. It also sends the Watchkeeper version and an invite code, if you have one. It sends no host name, user name, folder, project, operating system or hardware detail. Our server also sees the internet (IP) address the call came from, as every web server does. To stop this call, switch off the setting watchkeeper.phoneLogin before you open the panel.
3.2 Once a week. When you open the panel, at most once in 7 days, the plugin tells our server the login is still in use. It sends your Mac's key and nothing else.
3.3 While phone access is on. You switch phone access on in the panel. Then your Mac sends what the panel shows (section 4, "The panel's state"). It sends it when it changes, and at least every 60 seconds. It also sends the output of jobs, so you can see them on your phone. Before anything is sent, your Mac shows your home folder as "~". It also scans every text for passwords and keys (such as API keys) and for email addresses, and leaves them out. The scan catches common patterns; it cannot catch everything, so keep passwords and keys out of what the panel shows.
3.4 From your phone. You sign in with your username and password, then with a passkey. Your phone sends us the passkey's public key and signatures. Your face, fingerprint or passcode is checked on your phone and never reaches us. The private key never leaves your phone.
3.5 While phone access is off, your Mac sends no project data, apart from shared library items if you switched sharing on (3.6). It still answers the weekly check (3.2), and it sends one call to delete the server's copy if that is still waiting.
3.6 While sharing is on. If you switch on the shared library, your Mac sends each solved problem you save from then on, after scrubbing it, and the words of your searches of the shared library. Section 7 says what an item holds and how it is scrubbed.
4. What we keep, why, and for how long
"Nexodyne" in the last column means our owner. When the owner asks for help with the server, it also means an AI assistant working for the owner (section 8). Cloudflare also sees every request while it is delivered (section 8).
| Data | Why we use it | Lawful basis | How long we keep it | Who can read it |
|---|---|---|---|---|
| Your password | To check your login | Legitimate interests (giving you a ready phone login); contract once you use phone access | We never store it. The server uses it only for the moment it takes to scramble or check it | You; Cloudflare while it is delivered |
| Your password in scrambled form (an scrypt hash) | To check your login | As above | While your login exists; in backups up to 30 days after | Nexodyne |
| Your Mac's key in scrambled form (a SHA-256 hash) | To know your Mac when it calls | As above | While your login exists; in backups up to 30 days after | Nexodyne |
| Account number and username | To find your login | As above | While your login exists; in backups up to 30 days after | Nexodyne; you |
| A note that a login was removed: a scrambled form (SHA-256) of its account number, why it was removed (deleted or unused) and when | So the Mac that made the login learns why it stopped working | Legitimate interests (keeping the service working) | 365 days; in backups up to 30 days after | Nexodyne |
| When the login was made and last used, whether phone access is on and when it changed, whether it came from an invite, the Watchkeeper version | To apply the limits, to remove unused logins (section 10) and to help you if something goes wrong | Legitimate interests (running a fair, free service) | While your login exists; in backups up to 30 days after | Nexodyne |
| Invite code (scrambled), its note, when it was used and by which login | To let testers in before sign-up opens | Legitimate interests (testing the service) | 30 days | Nexodyne |
| Sign-in sessions: a scrambled session token, its stage and times, and the sign-in challenge | To keep your phone signed in | Contract | Until the session ends (12 hours at most), then removed within an hour; in backups up to 30 days after | Nexodyne |
| IP address and its counts, to limit sign-ups and sign-ins | To stop abuse | Legitimate interests (security) | Held in memory only, 24 hours at most; gone when the server restarts | Nexodyne |
| IP address (or the network part of an IPv6 address) and counts of commands and phone keys set up | To limit what the phone page accepts | Legitimate interests (security) | For the current day only; deleted when phone access goes off | Nexodyne |
| Web server log: IP address, time, the page or call asked for, its result and size, the browser's name | Security and finding faults | Legitimate interests (security) | 15 days at most (the log starts afresh each day and keeps the last 14 days' files) | Nexodyne |
| Phone keys: the key's id, its public key, its label (such as "iPhone"), when it was set up and the IP address it came from | So your Mac can trust your phone, and our server can check your sign-ins | Contract | Keys waiting for you to trust them: until you trust or reject them, or 7 days. Trusted keys: while phone access is on | Nexodyne; you |
| Sign-in counters: one number per phone key, which goes up at each passkey sign-in | To spot a copied phone key | Legitimate interests (security) | While phone access is on | Nexodyne |
| The panel's state (only while phone access is on): project names and folders (your home folder shown as "~"), branches, the subjects of recent commits, how many files changed, Claude session titles and models, open questions and suggestions with their texts, job summaries, Gemini tasks, usage pace and spend figures, free memory | To show the panel on your phone | Contract | Replaced each time your Mac sends it (at least every 60 seconds); deleted when phone access goes off, or the login is deleted or removed | Nexodyne; you, on your signed-in phone |
| Commands from your phone: what you pressed, with its text (answers, notes, job prompts of up to 8,000 characters) and your phone's signature | To carry your presses to your Mac and the results back | Contract | Until your Mac answers, then 7 days; deleted when phone access goes off | Nexodyne; you |
| Job output: what the assistant wrote, the tools it used with a file path or the start of a command, their results, cost and turns | To show your jobs on your phone | Contract | The newest 50 jobs, 1 MB each; deleted when phone access goes off | Nexodyne; you |
| Fault log: command numbers and kinds, when they were delivered and answered, short texts of up to 200 characters | To find faults | Legitimate interests (keeping the service working) | 30 days, 5 MB at most; deleted when phone access goes off | Nexodyne |
| Shared library items (only with sharing on): the item (7.3), whether it is on hold or live, when it goes live, and a private link to your login | To share solved problems with members who share, and to let you remove yours | Consent (7.11) | On hold: 24 hours, or deleted when you switch sharing off. Live: until you remove it, delete your login, or the login is removed after 90 days unused. The library is not in our backups, so a removed item leaves no copy behind | Nexodyne; you; once live, every member who shares, never with the link to you |
| Backups of the login database (the rows above marked "in backups"; never the panel's state, commands, job output or phone keys) | To recover from a fault | Legitimate interests (keeping the service working) | 14 days on our server; 30 days on our owner's computer and, encrypted, on GitHub | Nexodyne; GitHub holds only the encrypted file |
4.1 Job output can quote parts of your files or the results of commands, just as the panel does on your Mac. Your files themselves are never uploaded.
4.2 Please do not let the panel carry other people's personal data that you have no right to share. Keep sensitive information out of it too, for example about health, beliefs or private life.
4.3 No automated decisions with legal or similarly significant effects are made about you. Limits and the abuse checks above are not decisions about you.
5. What we never get
- Your Claude account, its login or its plan. Jobs run on your Mac with your own Claude Code login.
- Your email address, your real name or any payment detail. We do not ask for them.
- Your password in a form we keep, your Mac's key, or the private key of any passkey.
- Your face, fingerprint or phone passcode.
- Anything about your projects before you switch phone access on, and anything new after you switch it off. The one exception is a solved problem you share to the library, and only while sharing is on (section 7).
6. What our server can see: the honest limit
6.1 While phone access is on, our server stores the panel's state, your commands and your job output. It stores them in a form it can read. It is not end-to-end encrypted. We read it only to run the service and to fix faults.
6.2 Your Mac acts only on presses signed by a phone key you trusted on your Mac after checking its code. A password alone shows no project data. It can only add a phone key that waits for you to press Trust on your Mac.
6.3 But anyone who took full control of our server could read what Macs send while phone access is on. They could also send your phone a changed page that asks you to approve a command of their own. What protects you then is your Mac. It acts only on commands signed by a phone key you trusted. It checks each one against its own allowed actions and limits, which our server cannot change. And until you switch on edit and full jobs in the panel, a phone can start only plan jobs, which read and suggest. Your phone's confirm screen helps too: before a job starts, it shows the project, the mode and the start of the prompt, then asks for Face ID or your passcode. But a changed page could show you something false. If your phone ever asks you to approve something you did not ask for, do not approve it. Switch phone access off in the panel instead.
7. The shared library (only if you switch it on)
[New for the shared library: for the owner's approval]
7.1 Your own library stays on your Mac. When Claude solves a problem in your project and its tests pass, it can save the fix to your own library: a title, the problem, the steps that led to the fix, a short note, the code and the test command. These are files in ~/.wk/library/ on your Mac. Saving them, and searching your own library, uses no network and sends nothing to us. What Claude reads from your library goes into your Claude session, like anything else it reads, under Anthropic's terms (section 2.3). The same holds when you ask Watchkeeper to write rules from your library: Claude Code does that on your Mac with your own plan.
7.2 Sharing is off until you choose. The first time you open the panel, it asks once: "Share solved problems" or "Not now". Nothing is ticked for you. If you choose to share, you also confirm, once, that the code you share is yours to share, under the MIT-0 licence (our terms, section 8). You can change your answer at any time with the sharing switch in the panel's Library section (or the setting watchkeeper.librarySharing). Sharing goes on only after you confirm it yourself, in the panel or in your own terminal; Watchkeeper is built to refuse it when Claude asks. Sharing uses your free phone login (3.1); it does not need phone access. Before you switch sharing on, the panel shows you exactly what would be sent, using an item from your own library if you have one.
7.3 What sharing sends. With sharing on, each problem you save from then on goes to our server as one item of at most 8 KB. An item holds: a title, the problem, the steps (what you asked and what the model decided), the note on the fix, the code (at most 80 lines) and its language, the test command and how many tests passed, up to 8 tags, the Watchkeeper version, the time it was made, the licence (MIT-0) and your confirmation that it is yours to share. No account, user name, folder, project name or host name is ever a field of its own. Problems saved before you switched sharing on stay on your Mac. Your Mac sends each item with your login's key, so our server knows which login sent it (7.6).
7.4 The scrub on your Mac, and its limit. Before an item leaves your Mac, Watchkeeper replaces your home folder with "~". It replaces every other folder path with a placeholder, apart from common system folders such as /usr and /tmp. It also replaces email addresses, IP addresses, web addresses and private host names (such as those ending in .internal or .local) with placeholders. It also replaces your name, your git name and email, your project names, the hosts of your git remotes, your package names and authors, and every word in your own list, ~/.wk/library-words.txt; add the names of your company and clients there. Web addresses on public code and documentation sites, such as github.com and pypi.org, keep their site name; a part of such an address that names the owner or repository of one of your git remotes is replaced. Other parts are kept, so check that they do not name a private project. An item that seems to hold a password, key or token is not sent at all, and our server checks again and refuses such items. The scrub catches common patterns and the words it knows. It cannot catch everything: another person's name, a customer's detail or an unusual secret can slip through. Read each item after it is sent (7.5) and remove anything that should not be there.
7.5 A 24-hour hold that only you see. Each new item waits on our server for 24 hours before it joins the shared library. During that time no other member can see or search it. Your panel (and your library page on our site, with your phone login) shows the exact text that was sent, with a Remove button; one press deletes the item at once. After 24 hours the item goes live. Like everything on our server, items are stored in a form our server can read (section 6).
7.6 What other members see, and the link we keep. Members who share can search live items. They see the item (7.3), with the time it was made shown only as the day, never which login shared it. Our server keeps a private link from each item to your login, and no search answer includes it. We keep this link so that you can remove your items and so that deleting your login removes them. Because of this link, shared items are pseudonymized, not anonymous: we can tell which login shared an item. The text of an item could also point to you, for example through a detail the scrub missed. Members can read live items from anywhere in the world. [For a lawyer: whether showing live items to members worldwide needs a transfer safeguard under Chapter V of the UK and EU GDPR, given that the items are pseudonymized and scrubbed.]
7.7 How long items stay. A live item stays until you remove it, delete your phone login, or the login is removed after 90 days unused (section 10). You can keep up to 500 items and share up to 20 new ones a day. A refused item is not kept, and its text is not logged. Switching sharing off stops new items at once and deletes any still in their 24-hour hold. We keep a small record linked to your login: when you switched sharing on, and whether you removed an item on hold. We use it only for the search rule in 7.9, and delete it with your login. Items already live stay, because you gave them under the licence; remove them one by one in the panel (or on your phone), or delete your login to remove them all.
7.8 Copies others already have. Removing an item takes it out of the shared library at once. It cannot recall copies. A member who found the item before you removed it may have used it in their own code, and the licence lets them keep it. Their Claude, or other AI tool, will have read it under that tool's own terms. [For a lawyer: what Article 17(2) of the UK and EU GDPR asks of us for items that members have already copied, and whether this paragraph is enough.]
7.9 Searching the shared library. Search is open to logins with sharing on and at least one item accepted. An item on hold counts until you first remove an item on hold, or switch sharing off while one is on hold; after that, search needs a live item. Your Mac sends the words you search for, and our server answers with up to 10 live items. The words travel inside the call, not in its address, so the web server log does not hold them, and we keep no record of the words you search for. You can search up to 60 times an hour. Results reach Claude marked as untrusted reference written by another member and not checked by us, and Claude is told never to follow instructions inside them. Check any code before you use it.
7.10 Search, never training. We use shared items only to answer members' searches and to show you your own items. We never use them to train an AI model, and our server runs no AI model. The licence lets anyone who receives an item use it as they wish, and other members' AI tools read the items they find under those tools' own terms; we cannot control either.
7.11 Lawful basis: your consent. For the shared library we rely on your consent (Article 6(1)(a) of the UK and EU GDPR), which you give by choosing "Share solved problems" and confirming that the code is yours to share. You can withdraw it at any time, as easily as you gave it: switch sharing off. That stops new items at once and deletes items still on hold. Withdrawing does not make what we did before unlawful. Items already live stay until you remove them or delete your login (7.7). The counts we keep to apply the limits rely on legitimate interests (running a fair, free service). [For a lawyer: (a) whether keeping live items after sharing is switched off, until the user removes them, fits Articles 7(3) and 17(1)(b), or whether switching off should offer to remove them all; (b) whether consent is freely given under Article 7(4) when searching the shared library depends on sharing, given that the plugin and the own library stay free for everyone.]
7.12 Please share only what you may. Share only code that is yours to share, never an employer's or a client's secret, and keep other people's personal data out of what you save. Keep sensitive information out too, for example about health, beliefs or private life. Our terms (section 8) set the rules for shared items.
8. Who handles your data
8.1 We use a small number of service providers. Contabo and Cloudflare act only on our instructions and must keep your data secure.
| Provider | What it does | Where |
|---|---|---|
| Contabo GmbH (Germany) | The server that runs watchkeeper.nexodyne.org and stores the data in section 4 | [COUNTRY: to be confirmed] |
| Cloudflare | Delivers the pages and calls and protects the site from attacks. Every connection is decrypted at Cloudflare and encrypted again on its way to our server, so Cloudflare sees what passes while it is delivered | Worldwide, including the United States |
| GitHub (Microsoft) | Stores encrypted copies of our login database backups; only we hold the key | The United States |
| Providers of AI models (such as Anthropic) | When our owner asks an AI assistant for help with the server, it may see data stored there while it does that task | Several countries, including the United States |
8.2 Providers of AI models handle what they see under their own terms and privacy policies. We never use your data to train AI models. [to confirm: model training is switched off on the AI account our owner uses for server work]
8.3 We may also share data if the law requires it, or to protect the rights or safety of our users or us. We may share it with our professional advisers. If our business is sold, we may share it with the buyer, who must then protect it as this notice says.
8.4 We never sell your personal data. We share nothing with advertisers, and we run no advertising scripts and no third-party analytics.
9. International transfers
9.1 Our company is in the United Kingdom and our server is in [COUNTRY: to be confirmed]. [If the country is in the European Economic Area: data moves between the two under the UK's adequacy regulations for the European Economic Area. It also moves under the European Commission's adequacy decision for the United Kingdom.]
9.2 Cloudflare may process data in the United States and other countries. For those transfers it relies on the EU–US Data Privacy Framework and its UK extension (the UK–US data bridge). If that ever lapses, it relies on the EU standard contractual clauses with the UK Addendum. GitHub and the providers of AI models may also access data from the United States or other countries. They do so under the safeguards their own terms set out [to confirm]. Email us for details.
10. Deleting your data
10.1 Switch phone access off in the panel (or from your phone). Your Mac stops sending at once. When the call arrives, our server deletes its copy: the panel's state, commands, job output, phone keys, limit counts and fault log. If the call cannot reach our server, the panel says so, and your Mac sends it again until it does. Your login stays, so you can switch phone access on again.
10.2 Delete your phone login in the panel (Delete phone login, then confirm), or on your phone (Delete this account, with your passkey). Our server deletes your login, your sessions and everything in 10.1 at once. Your login's row in our backups is gone within 30 days. We keep one short note for 365 days: a scrambled form of the login's number, why it was removed and when, so the Mac that made the login learns why it stopped working. The note holds nothing else. Deleting your login also deletes all your shared library items, on hold or live (section 7). The panel then offers to make a new login; it never makes one without your press.
10.3 Unused logins are removed. A login unused for 90 days is deleted with everything in 10.2, including your shared library items. Opening the panel counts as use. After such a removal, the next time you open the panel it makes a new login by itself, with phone access off (unless the setting watchkeeper.phoneLogin is off). We hold no email address, so the warning is in the panel: from day 60 it shows the date the login will be removed.
10.4 By email. Write to info@nexodyne.org with your username. We may first ask you to show that the login is yours. Deleting it yourself in the panel is always faster.
10.5 Shared library items. Remove one item in the panel or on your phone; it is deleted at once. Switch sharing off to stop new items and delete those on hold. Removal cannot recall copies that members already took (7.8).
11. Your rights
11.1 You have the right to:
- ask for a copy of your data (most of it you can already see on your phone);
- ask us to correct data that is wrong;
- ask us to delete your data (section 10);
- withdraw your consent to the shared library at any time, by switching sharing off (7.11);
- ask us to limit how we use your data;
- object to our use of your data where we rely on legitimate interests;
- receive the data you gave us in a common format, or ask us to send it to someone else.
11.2 To use any of these rights, email info@nexodyne.org. We reply within one month. It is free.
11.3 If you are unhappy with how we handle your data, please tell us first. We confirm we have your complaint within 30 days and look into it without delay. You can also complain to the Information Commissioner's Office (ICO): ico.org.uk/make-a-complaint or 0303 123 1113. If you live in the European Union, you can complain to your local data protection authority.
12. Cookies and browser storage
12.1 watchkeeper.nexodyne.org sets one cookie, __Host-wk, when you sign in. It is strictly necessary: without it the site cannot know you are signed in. It is sent only over HTTPS, only to watchkeeper.nexodyne.org, and cannot be read by the page's scripts. After your password it lasts 15 minutes; after your passkey, 12 hours at most, and it ends after 2 hours without use. Signing out ends it.
12.2 Your passkey is kept by your phone (and its password manager, if you use one), not by us.
12.3 The phone page keeps nothing in your browser's own storage (such as local storage).
13. Age
13.1 Watchkeeper phone access is for people aged 18 or over. We do not knowingly collect personal data from anyone under 18. If you think a child has made a login, email us and we will delete it.
14. Security
14.1 We protect your data with encrypted connections (HTTPS) and keep passwords and tokens only in scrambled form. Passkeys need your face, fingerprint or passcode. Each login has its own closed folder. Your Mac acts only on presses signed by a phone key you trusted.
14.2 Keep your password and your phone safe. Anyone who sees your password can sign in. They see no project data, and they can only add a phone key that waits for you to press Trust on your Mac. Never press Trust for a key you did not set up yourself. If you think someone has your password, press New password in the panel. It ends every phone session and clears any phone key waiting for your trust.
14.3 No system is perfectly secure, and section 6 says what our server can see. If a breach puts your data at risk, we will say so on this page and tell the ICO where the law requires it.
15. Changes to this notice
15.1 We may update this notice. The date at the top shows when it last changed. We hold no email address for you, so we will describe any significant change on this page at least 14 days before it applies.
16. Contact
Nexodyne Limited 71–75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom Company number 16539459 Email: info@nexodyne.org