The reason to trust handl. is how it is built.
handl. rings businesses on your behalf, books things in your name, and holds enough about you to be useful at it. That is a great deal to hand over, and the word of somebody is a poor reason to hand it over.
So this page does not ask for it. It takes six things handl. claims about your data and, for each one, gives the mechanism that makes it true and what it costs you in convenience. The second half is the part worth reading. Everything here describes the build that ships today.
Deleting your account actually deletes it
Deleting your account wipes your data, tombstones your handle so it cannot be reused before release, and redacts your messages out of any shared thread — deleting the content and clearing what you left on the copy of the conversation that someone else holds — rather than leaving it orphaned.
Settings, then Delete My Account. There is no email to support and no cooling-off queue. The app asks once whether you are sure and checks that it is you, with Face ID or your passcode, and then it runs.
It clears the obvious things — your profile, your saved contacts and businesses, your bookings, call transcripts, your messages, notes, lists and reminders, your health and wearable entries, your connected-account tokens and your backup snapshots — and then the less obvious ones: the internal indexes that pointed at you from outside your own folder.
Your @handl is held back for at least ninety days rather than passed to the next person who asks for it. A handle is the address people message you at and the name on every message they have already had from you; handing it straight on would quietly point all of that at a stranger.
Your messages inside threads that belong to other people are redacted rather than orphaned. The content goes, the reactions you left on their messages are cleared, and their own side of the conversation is left exactly as it was, because it is theirs and not yours to delete.
The order of those two steps is deliberate and the code says so where it does it: the handle is tombstoned before it is released, so there is no window in which it is available and your history still points at it.
What it costs you. All of it, immediately. There is no grace period to change your mind and no copy kept aside that support could restore for you later.
And one limit stated plainly rather than left for you to discover: deletion reaches our systems. The carrier that put the calls and texts through, the voice-call provider that holds recordings of calls, the payment processor, and the model providers that handled the requests each keep their own records under their own retention clocks. Ask us and we will pass the request on — and tell you where the legal retention duty of a provider means the answer is no.
The other five work the same way: a thing handl. does, the mechanism that makes it so, and what it takes from you in return.
Name, phone and email. Anything else, it asks you mid-call or declines.
handl. volunteers only your name, phone number and email. Anything else it is asked for on a call — a date of birth, a passport or loyalty number — it will not answer from memory. For a date of birth it checks with you live, mid-call, and waits for your answer; for everything else it declines and suggests they contact you directly.
Two different things can put a detail in front of a stranger: something you typed before the call, and something they ask for during it. They are handled separately, because they fail in different ways.
Before the call. A phone call is the one place your data leaves in a form nobody can pull back, so the check runs before the number is dialled rather than on the words after they are drafted. handl. reads your request for the shape of an identifier — a reference or membership number, a date of birth, card or bank details, a national identifier, an identity document, a postal address, or the contact details of somebody else. When it finds one it does not strip it out and dial anyway. It stops, tells you which kind of detail it found, and offers you another way to get the thing done.
During the call. Asked for something on the line, the assistant does not answer from memory. A date of birth is the one detail businesses ask for often enough to deserve a path of its own: handl. pauses, a notification arrives on your phone, and it says nothing until you tap to allow it. No answer inside the short window of the call counts as a no, and it tells them it cannot provide that. For a home address, card details or an ID number there is no such path at all, so it declines and suggests they contact you directly.
The check before the call recognises shapes, and the code is explicit about where a shape is ambiguous: an unlabelled short code, a number written out in words, or an identifier in another language can read as ordinary booking text. That is why the rule is about refusing to dial rather than about what a sentence can hold — and it is why the live check sits behind it rather than instead of it.
What it costs you. A cancellation that genuinely needs your membership number is a call handl. will not place — you get the wording to send yourself and the number to ring, and the ten minutes it would have saved you, it does not save you. And when someone on the line asks for your date of birth, the call stops and waits on you. If your phone is face-down, the window closes and handl. tells them it cannot provide it.
handl. never stores the passwords you use on other sites or your own card number, and never types either.
When a task reaches a sign-in page, handl. hands it to you. It does not fill the form and it does not read what you put in it: a field it recognises as secret — a password, a card number, a security code, bank details — it refuses to type into at all.
Checkout works the same way on purpose. The moment that needs a card is handed back for you to tap and pay.
Nothing is stored because nothing arrives. The value does not reach a server that could keep it.
The password for handl. itself is the one credential we do hold, and we hold it as a salted hash that cannot be turned back into your password.
What it costs you. Anything behind a sign-in needs you, in the moment. handl. carries a task up to that wall and no further, and a purchase finishes under your thumb or not at all.
Every purchase, card hold and checkout is gated before it happens.
Before handl. spends money on your behalf — a purchase, a card hold, or a checkout — the action goes through a risk gate first, and a checkout that needs it hands control back to you to tap and pay.
Spending is the category where a mistake cannot be undone by apologising, so it is the one handl. gates hardest.
Before money moves, the action is classified and checked against the spending limits set on your account — rather than going ahead on the strength of having understood you correctly.
Where a checkout cannot be finished safely on your behalf, handl. stops and hands it back, and what it hands back is the last tap, not the whole errand.
What it costs you. handl. will not quietly take the last seat while you are asleep. When a price is moving, the gate is the reason you might miss it. That is the trade, and it is the right way round.
When handl. stops to ask you, the log keeps the words you were shown
handl. keeps an append-only consent log: entries are added, and nothing edits or removes one afterwards. Where it stopped to ask you before acting, the entry records the exact plain-words disclosure you were shown, what you decided, who decided it, and why it stopped — and you can read the whole log yourself in the app.
Where handl. stopped to ask you before acting, the entry keeps the exact plain-words disclosure you were shown — not a code, not a pointer to a version of a policy, the sentence itself. A consent record that cannot tell you what you were told is not much of a record.
Beside it: what you decided, including the times you said no; who decided, which is you or someone you nominated to approve on your behalf; and why handl. stopped there rather than carrying on.
You read the whole thing from the Trust Centre in the app, whenever you want to.
What it costs you. It is a log, so it accumulates and it cannot be tidied. There is no removing a line you would rather were not in it. Deleting your account takes the log with everything else, and that is the only way it goes.
handl. has no model-training pipeline of any kind.
There is no training pipeline in the codebase to switch off, no dataset being assembled from your sessions, and no telemetry sink quietly collecting them.
A model call goes out to do the thing you asked for and the answer comes back. That is the whole of the arrangement.
The providers running those models keep short-term logs of the requests we send them, under their own contracts. That half is contractual rather than something our code enforces, and the privacy policy names them rather than implying they are not there.
What it costs you. handl. does not get better at your particular life by studying it in the background. What it knows about you is what you told it and what it saved because you asked it to.
Where to check any of this
Two documents bind us where this page only describes. They are longer, duller, and they say these things in the language that counts. Where one of them and this page differ, the document governs.
Every claim on this page was checked twice on — once against the code that enforces it, and once against the policy that binds us. Three claims that had been written down for this page failed one of those two checks. They were dropped or narrowed to what could be shown, rather than reworded.