Terms of Service

1. Who you are contracting with

atdesk is sold by:

In these terms, "we", "us" and "our" mean Exceedity Ltd. "You" means the person who subscribes.

We have no phone line. Email is how we are reached, and it is monitored.

2. These terms, and when they apply

These terms apply when you subscribe to atdesk. The contract between us starts when Stripe confirms your subscription, and it continues until you or we end it.

You must be 18 or over to subscribe.

Your privacy notice is at /privacy and forms part of this agreement.

We may sell to consumers and to people buying for their work. Where a section applies only to consumers, it says so.

3. What atdesk actually is

atdesk puts a Claude Code session that is already running on your computer, in VS Code, onto your phone. You can read it, type into it, answer approval prompts, and get a notification when something needs you.

Concretely, what you are buying is two things:

1. A licence to install and use the atdesk software on up to five of your own

computers, and to use the atdesk web app on your phones.

2. A slot on our relay — the small service at relay.atdesk.dev that carries

sealed messages between your phone and your computer so that neither has to be reachable from the internet.

atdesk drives Claude Code on your own machine. It does not run Claude anywhere else. Nothing is forked, copied or run in a cloud. If your computer is off, asleep or offline, there is nothing for your phone to talk to.

How it works, stated plainly because it affects what you are agreeing to:

• Reading works by following the transcript file that Claude Code already

writes for every session. It needs no cooperation from the running process.

• Typing works by injecting into the Claude Code panel through **VS Code's

local debugging port. That port is optional**. Setup asks you, and if you say no, everything else still works — you can read the session and get notifications, you just cannot type into it. Turning the port on also lets any other program already running on your computer drive your editor, so it is a real widening of your attack surface. That is your decision to make, and it is yours to reverse.

• Notifications are sent from your computer to your phone through Apple's,

Google's, Mozilla's or Microsoft's push service, depending on your phone. The words are encrypted; the push service sees that a message was sent, and when.

• The background services on your computer listen on loopback only

(127.0.0.1). They are not reachable from any network.

atdesk is not affiliated with, endorsed by, or connected to Anthropic, Microsoft or Apple. We name Claude Code, VS Code and iOS to describe what atdesk works with. All trade marks belong to their owners.

4. What you need before you subscribe

• Node 20 or newer, VS Code, and Claude Code opened in VS Code at least once.
• Your own Anthropic Claude subscription.

atdesk does not include, resell, proxy or give you any access to Claude. We supply no AI service of any kind. Everything Claude does for you is supplied by Anthropic to you, under your own agreement with them, and billed to you by them. If your Claude subscription ends, is suspended, hits a usage limit, or changes, atdesk keeps running and has nothing to drive. That is not our failure and it is not a "broken month" (section 11).

5. How you must use atdesk

5.1 A person, present

atdesk is built for one person, using one Claude Code session, with that person present and answering. That is not a style preference. Anthropic's Consumer Terms prohibit accessing their service "through automated or non-human means" and say not to add scheduled or unattended prompting. atdesk is compatible with that because you type every prompt and you answer every approval.

So, as a condition of this licence:

(a) You must not use atdesk to send prompts, or to give approvals, on a schedule, on a timer, in a loop, or at any time when no person is reading them.

(b) You must not run atdesk unattended or on a schedule — that is, in a way where prompts are sent or approvals given at times when nobody is reading them.

atdesk ships skills that let one Claude Code session put a message into another, and ask a previous session a question. Those are permitted and supported. A person starts them, a person reads the answer, and the point of them is to bring an earlier session's context back to a human decision. What this clause forbids is leaving the product running to prompt itself while you are asleep.

(c) You must not share your invite code, your install token, your pairing link or your device keys with anyone else, and you must not let another person use your subscription.

(d) You must comply with the terms of your own Claude subscription. Those terms are between you and Anthropic. We cannot see what you do in a session and we cannot police it — which is exactly why this is your obligation and not ours.

If we reasonably believe you are using atdesk in breach of (a) to (d), we may suspend your access under section 13. If Anthropic suspends or terminates your account, that is a matter between you and them, and it does not entitle you to a refund from us.

5.2 Things you must not do

• Resell, sublicense, rent or share atdesk, or use it to provide a service to

anyone else.

• Copy, modify or create derivative works from the software, except where the law

gives you that right regardless of what a contract says (for example, making a back-up copy, correcting errors, or decompiling for interoperability under the Copyright, Designs and Patents Act 1988).

• Attack, overload, probe or attempt to gain unauthorised access to the relay, to

another customer's install, or to anyone else's computer or phone. Install identifiers are addresses, not secrets; connecting to one that is not yours is not a clever trick, it is a breach of these terms and may be a criminal offence under the Computer Misuse Act 1990.

• Work around the five-computer limit, or use invite codes that were not issued

to you.

• Use atdesk for anything unlawful.

6. Your computers, and your phones

Your subscription covers up to five computers.

Each computer needs its own install slot. You get one by using a single-use invite code that we issue. Codes expire if unused — 14 days by default.

Two honest details:

• The limit is administered by us, not enforced by a counter. We issue up to

five codes per subscription. There is no mechanism on your computer or on the relay that watches how many machines you own.

• Phones are not limited. You can pair as many as you like. There is one

technical ceiling: at most eight devices can be connected to one computer at the same time. A ninth is refused until one of the others disconnects.

If you exceed five computers, we will email you and give you 14 days to bring it back within the limit. If it is not resolved, we may suspend the extra slots, and we will tell you which ones. We will not cut you off without telling you first.

Replacing a computer. Ask us for a code for the new one and tell us the old one is finished with. We will revoke the old slot. Revocation is permanent — see section 13.2.

7. Price, VAT and billing

£8 per month, including VAT. Prices are in pounds sterling.

There is no annual plan. One price, one billing period. Decided 2026-08-17, and deliberately: an annual plan means someone who cancels in month two forfeits ten months, which sits badly beside "no minimum term".

The number shown is the number charged, in every country. Stripe Tax calculates the VAT or sales tax due where you are and takes it out of that figure, rather than adding it on top.

Charged every month on the anniversary of your first charge.

Your subscription renews automatically until you cancel it. Each renewal is charged to the card you have on file, at the price then in force.

Payment is handled entirely by Stripe. Checkout and the billing portal are Stripe's, not ours. We never see your full card details. Stripe holds your billing identity, your email address and your payment method; we can see which subscriptions are active and the email address attached to them.

We do not run an account system and there is no password on atdesk's side. Your billing email address is how we identify you, and a link we email you is how you reach your billing page. That link reaches billing only. It cannot read a session, type into one, or add a computer.

If the price changes, we will give you at least 30 days' notice by email. A new price never applies to a period you have already paid for. If you do not want it, cancel before it takes effect.

8. The free trial, and when the first charge lands

14 days free. A card is required. Then it charges.

• You enter card details at checkout. Nothing is taken on day 1.
• On day 15, unless you have cancelled, we charge the first £8.
• You can cancel at any point during the trial, in one click, in the Stripe

billing portal. If you cancel during the trial, you are charged nothing at all.

• One trial per customer. We may refuse a trial to someone who has already had

one.

We will email you at least 3 days before the trial ends, telling you the date and the amount, and how to cancel.

9. Your legal right to change your mind (consumers)

This section is in addition to the free trial, not instead of it. It is a right you have by law.

You have 14 days to cancel this contract without giving a reason. The 14 days run from the day the contract is made — that is, the day you subscribe — not from the day you are first charged.

Because the trial is also 14 days, these two periods normally end on the same day. In practice that means: cancel within your first 14 days and you pay nothing, whichever route you use.

To cancel, tell us clearly that you want to. The easiest way is to cancel in the Stripe billing portal, or email inbox@exceedity.com. You may use the model cancellation form if you prefer; a copy is at the end of this document.

Starting the service straight away. atdesk is no use to you in 14 days' time, so at checkout we ask you to confirm two things:

• that you want us to start supplying the service immediately, during the

cancellation period; and

• that you understand you will lose the right to cancel the download and use of

the software once supply has begun.

If you cancel within the 14 days having asked us to start immediately, you pay only for what you used up to the point you told us — and during a free trial that amount is nothing.

10. Cancelling, and a charge you did not mean to make

Cancel any time in the Stripe billing portal. There is no notice period and nothing to ask us for.

When you cancel:

• You keep access until the end of the period you have paid for.
• You are not charged again.
• We do not refund the remainder of the current period, unless a section of these

terms says we do (sections 11, 13 and 15 all do, in specific circumstances).

And one promise beyond the law: if you are charged and you tell us within 14 days of that charge that you did not mean to continue, we will refund it in full and close the subscription. No reason needed, no questions asked. This applies to the first charge after a trial and to any renewal.

11. A month that was broken

Our sales page says: "we do not charge you for a month that was broken." That is a promise, so here is exactly what it means.

11.1 Why this clause exists

atdesk reads and types into Claude Code by working with parts of another company's product that are not a published interface. A Claude Code release can change those parts and break atdesk overnight, for everyone, through no fault of yours and before we can catch up. We publish the Claude Code version we are tested against at /status. This clause is what happens when that risk lands on you.

11.2 The three core functions

1. Reading — seeing your live Claude Code session on your phone.
2. Typing — sending a prompt or answering an approval from your phone. Only

applies if you enabled VS Code's local debugging port; it is optional.

3. Notifications — your phone being told when something needs you.

11.3 What counts as broken

A billing month is broken if, on a computer covered by your subscription, and not because of something in section 11.4, any one of the three core functions did not work for:

• more than 72 hours in a row, or
• more than 7 days in total in that month.

Each function is judged separately. If any one of them fails that test, the whole month is broken.

It counts even when the cause is not our code. A Claude Code release that breaks reading or typing is a broken month. A relay outage is a broken month. We do not distinguish between our fault and our dependency's fault, because you cannot use what you paid for either way.

11.4 What does not count

• Your computer was off, asleep, offline, or VS Code was closed.
• You had not paired a phone, or you deleted the app from your phone.
• Typing, when you chose not to enable the local debugging port, or turned it

off.

• Your Claude subscription had ended, was suspended, or had hit a usage limit.
• Notifications stopping because your phone deleted the app's storage after 7

days without you opening it. We tell you about this before you start — it is why the app must be added to your home screen — so we cannot fix it and it is not a refundable failure.

• Time after we published a working fix and told you it was available. The clock

stops for you 7 days after we email you about the fix. If the fix does not actually work, the clock keeps running.

• A failure caused by you breaching section 5.

11.5 Who decides, and how

We decide in the first instance, applying section 11.3 and nothing else.

• We will not ask you to prove a negative. If you tell us reading was down

for a week, and neither our own records nor our status page contradict it, we accept it.

• We apply it without being asked where we already know. If an upstream

release or an outage broke a core function for everyone, we credit every subscription that was live in that month, whether or not anyone claims.

• If you disagree with our decision, section 17 (complaints) applies.
• This clause does not replace your legal rights. If the service is not

supplied with reasonable care and skill, you have rights under the Consumer Rights Act 2015 — including repeat performance and a price reduction — and nothing here limits or replaces them. This clause is in addition to them.

11.6 What you get

A refund of the price of the broken month:

£8 for each broken month — the whole of what you paid for it.

Paid back through Stripe to the card you paid with. If you would rather have the time added to the end of your subscription instead of money back, say so and we will do that.

11.7 How to claim, and by when

Email inbox@exceedity.com. Tell us:

• which month;
• which of the three functions was broken;
• roughly when it started and when it came back.

If you have output from vsr status or vsr setup --check, include it. It helps. It is not required and we will not refuse a claim for want of it.

Claim within 90 days of the end of the month you are claiming for.

We will reply within 5 working days and, where we agree the claim, pay within 14 days of agreeing it.

12. Availability — what is actually true

We do not offer an uptime guarantee, and there is no service level agreement. We are not going to invent one. Here is what is true today instead:

• The relay runs on a single server. When we deploy a new version, it restarts.
• A restart drops the connection your phone is holding open. It reconnects

automatically, and you may see a few seconds of nothing.

• Your computer's connection to the relay can also drop and reconnect — a laptop

lid, a train tunnel, a Wi-Fi change.

• If your computer is not connected when your phone sends something, the

relay holds a small number of messages for a short while and answers your phone with "accepted". On the phone that looks like success, and it is not — the message is waiting, not delivered. If your computer never comes back, it is never delivered.

• Updating atdesk on your computer restarts both background services, so the

phone loses that computer for roughly ten seconds.

• We may take the service down for maintenance. Where we can plan it, we will

try to tell you first.

If any of this adds up to a month you could not use, section 11 is the remedy.

Nothing in this section removes your right, as a consumer, to have the service supplied with reasonable care and skill.

13. Suspension and revocation — two different things

These are deliberately separate, and we never confuse them.

13.1 Suspension for non-payment — reversible

If a payment fails, Stripe will retry it over a period. If it still does not succeed, we may suspend your install slots: the relay stops carrying your traffic and your phone can no longer reach your computer.

Suspension does not destroy anything:

• Your install slot is not deleted.
• Your computer keeps its identity key, its settings and its certificates.
• Your paired phones stay paired.
• Nothing is removed from your computer, and no session data is touched — we

never had any (section 16).

Pay, and it comes back. No reinstalling, no re-pairing, no new invite code.

We will email you before we suspend, and when we suspend.

13.2 Revocation for security — permanent

Revocation is for security: a stolen laptop, a compromised key, or serious abuse. It is a deliberate one-way action and it cannot be undone. Our relay records a revocation in a way that is designed never to be reversed, precisely so that a revocation cannot be silently undone by anything else in the system.

After a revocation, that computer needs a new invite code and a fresh install, and its phones must be paired again.

We will never use revocation for a billing problem. If you ask us to revoke a computer, we will confirm with you first that you understand it is permanent.

You can also revoke a single phone yourself at any time, at your computer, with vsr revoke --fp <fingerprint>. That is yours to do and does not involve us.

13.3 Suspension or termination for breach

If you seriously breach section 5, or we are required to act by law, we may suspend or terminate your access immediately. We will tell you why, unless the law prevents us. Where we terminate for a serious breach, we do not refund the current period.

14. Leaving — and exactly what that does and does not do

We would rather tell you the awkward truth here than have you find it out later.

14.1 What happens to your subscription

Cancel in the Stripe portal. You keep access until the end of the period you have paid for. After that, we suspend your install slots and the relay stops carrying your traffic.

14.2 What stays on your computer, and what you must do

Cancelling does not remove atdesk from your computer. As of today, there is no single command that removes everything. This is what is true:

• **vsr uninstall behaves differently on each system, and we will not average

the two into one sentence. On macOS it unloads the job and removes it, so the background service does stop — it just does not say so. On Windows it removes the logon task but does not stop the process that is already running**; that continues until you reboot or run vsr stop, and it prints that on screen.

• The transport daemon is separate. vsr vsrd uninstall removes its login

item. vsr uninstall does not touch it.

• Your files stay. The install directory, the settings folder

(~/.config/vscode-remote on macOS and Linux) containing your configuration, your computer's identity key, its loopback certificates and the list of paired phones, plus the log files and the VS Code extension link, all remain until you delete them yourself.

• The VS Code debugging port stays on if you enabled it. It is a setting in

VS Code's own argv.json (remote-debugging-port), and removing atdesk does not turn it off. If you want it off, turn it off — this is the item with the most security value of anything in this list.

• Your phone. Delete the atdesk app from your home screen. Its device key

lives in that app's storage and goes with it.

We will publish a single command that does all of this. Until we have, the list above is what leaving actually takes, and we will help by email if you want it walked through.

14.3 What we keep

After you leave, our relay keeps a record of your install: its identifier, a one-way hash of its token, the owner label, when it was created and first used, when it was last seen connected, a receipt that an invite code was used, and an audit log of those events. These are kept indefinitely unless you ask us to delete them. They contain no session content and no usable credential.

Ask us at inbox@exceedity.com and we will delete what we can. Some things we must keep: Stripe holds payment records, and we are required to keep records of sales for as long as tax law requires. The privacy notice at /privacy sets out your rights over all of this in full.

15. Changes to the service, and to these terms

To the service. We will keep improving atdesk, and that means it will change. If we permanently remove one of the three core functions in section 11.2, you may cancel and we will refund the unused part of what you have paid.

To these terms. If we change them in a way that affects you, we will give at least 30 days' notice by email. If you do not accept the change, cancel before it takes effect and we will refund the unused part of what you have paid. Small corrections that do not affect your rights — a typo, a clearer sentence — we may simply make.

Discontinuing atdesk. If we stop offering the product, we will give at least 30 days' notice and refund the unused part of what you have paid.

16. What we can and cannot see

The short version: we cannot read your sessions.

Everything that travels between your phone and your computer is encrypted end to end, with keys the two of them agreed with each other when you paired them. Our relay forwards sealed messages it cannot open. It holds no key that would let it read them, and it is built so that it never learns how.

What our relay can see, and we would rather say it than let you assume otherwise: that an install connected, when, how big each sealed message was, and when it went past. It records the identifier of your install, a one-way hash of its token, and roughly when it was last seen connected. It does not record your prompts, your code, your file names, or Claude's replies, because it cannot read them.

Other things that are true and worth knowing:

• Notifications: the words are encrypted, but Apple, Google, Mozilla or

Microsoft (whichever your phone uses) can see that a notification was sent to your phone, and when.

• Updates are downloaded from a server we run. That request tells us your IP

address and which version you asked for.

• Access logs. The web server in front of the relay keeps standard access

logs, which include IP addresses. Retention: 14 days.

• atdesk sends us no usage telemetry. The only places your computer connects

off-machine are the relay, your phone's push service, and our download server when you update.

• Stripe holds your billing identity, email address and payment method. We

never see full card details.

• Transactional email — invite codes, billing links, the notices this document

promises — is sent by our own server, not a third party. Nobody else receives your address in order to deliver it.

Full detail, lawful bases, retention periods and your rights are in the privacy notice at /privacy.

17. If something goes wrong — complaints

Email inbox@exceedity.com. We will acknowledge within 5 working days and do our best to resolve it.

If we cannot resolve it between us: we do not use an alternative dispute resolution provider, and we are not obliged to. You can still take a dispute to court, and nothing in these terms affects your statutory rights.

18. Our responsibility to you

What we do not limit, and cannot. Nothing in these terms limits or excludes our liability for:

• death or personal injury caused by our negligence;
• fraud or fraudulent misrepresentation;
• your rights under the Consumer Rights Act 2015, including the right to services

supplied with reasonable care and skill, and our liability for damage caused to your device or your other digital content by digital content we supply;

• anything else that cannot lawfully be limited.

What we are responsible for. If we fail to comply with these terms, we are responsible for loss or damage you suffer that is a foreseeable result of that failure.

What we are not responsible for.

• What Claude Code does on your computer. atdesk is a remote control. It

carries the prompts you typed and the approvals you gave. What Claude Code then does — files it changes, commands it runs, code it writes — is between you, Claude Code and your own choices about which permission mode to run in. Keep backups. Use version control.

• Loss caused by something outside our reasonable control, including changes made

by Anthropic, Microsoft or Apple to their own products.

• Loss caused by your breach of section 5, or by your own configuration.

Business use is allowed. atdesk is licensed to one named person, and that person may use it for their work — a freelance developer buying atdesk for their own business is exactly who this is for, and an earlier draft accidentally put them in breach on day one. What is not allowed is sharing one subscription between people (section 5.1(c)).

If you use atdesk for business purposes, we are not liable to you for loss of profit, loss of business, business interruption, loss of contracts, loss of goodwill or loss of anticipated savings.

What we never limit. Nothing in these terms limits or excludes our liability for death or personal injury caused by our negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot lawfully be limited. If you are a consumer, your statutory rights are unaffected by anything in this section.

Cap. Subject to everything above, our total liability to you for all claims arising in any 12-month period is limited to the greater of £100 and the amount you paid us in the 12 months before the claim arose.

19. Other terms

• Assignment. You may not transfer your subscription to anyone else. We may

transfer this agreement to another company, and if we do we will tell you and it will not affect your rights.

• Third parties. Nobody other than you and us has any right to enforce these

terms.

• Severability. If a court finds part of these terms unlawful, the rest

continues to apply.

• Delay is not waiver. If we do not insist on something straight away, we can

still insist on it later.

• Events outside our control. We are not liable for failing to perform where

the cause is outside our reasonable control, but if it goes on for more than 30 days either of us may end the agreement and we will refund the unused part of what you have paid.

• The whole agreement. These terms and the privacy notice are the whole

agreement between us about atdesk. This does not affect any liability we have for something we told you that was untrue.

20. Governing law

These terms are governed by the law of England and Wales, and the courts of England and Wales have jurisdiction.

If you are a consumer living in Scotland or Northern Ireland, you may also bring proceedings in your own courts.

Model cancellation form

(Complete and return this form only if you wish to withdraw from the contract.)

To: Exceedity Ltd, Willoughby House, 2 Broad Street, Stamford, United Kingdom, PE9 1PB — inbox@exceedity.com

I hereby give notice that I withdraw from my contract for the supply of the following service: atdesk subscription.

• Ordered on: ______________________
• Name of consumer: ______________________
• Address of consumer: ______________________
• Signature of consumer (only if this form is notified on paper): ______________
• Date: ______________________