How handl. handles your information
handl. is a personal assistant that answers questions, keeps track of your day, messages people, and — when you ask it to — picks up the phone and makes a real call on your behalf. Doing that well means holding some genuinely personal information. This page explains exactly what we hold, why we hold it, who else ever sees it, and how to get rid of it.
The short version. We collect what handl. needs to do the jobs you give it, and nothing for advertising. We do not sell your information, we do not share it with data brokers, we do not track you across other companies' apps and websites, and we do not use your data to train anyone's AI models. Everything we store is encrypted at rest. Loop messages delete themselves after twelve months — sooner if you set a shorter timer. Disconnecting an email account or a wearable deletes what we hold from it. Deleting your account in Settings removes it and everything in it, once the app has checked it is you. Section 09 names the two records we keep on purpose, and the records other companies keep under their own policies.
Who we are
handl. is a product of Relleps, Inc., a company incorporated in Delaware, USA. For UK and EU data protection law, Relleps, Inc. is the controller of the personal information described on this page — meaning we're the ones who decide what is collected and why, and the ones you can hold to account for it. Our servers are hosted in the United States. Where we transfer information out of the UK, the EEA or the UAE, we rely on the safeguards set out in section 12, with the providers described in section 05.
You can reach us any time at info@handlai.co. These terms sit alongside our Terms of Service.
What we collect, and why
Feature by feature, in plain English. Anything marked optional is only collected if you choose to use that part of the app.
Our position is minimum access, by feature, not by default. handl. does not run a standing background capture of your screen, keystrokes, microphone, or camera, and it does not read your email, messages, or location unless that specific feature is what you're using and you've turned it on. What each feature can see is scoped to what that feature actually needs to do its job — your saved addresses, for instance, are used only for travel-time and "leave now" alerts and are never handed to anyone the assistant speaks to (see below). If you disconnect a feature or an account, we stop collecting through it immediately; see "Disconnecting an account: forget, not just stop" (section 08) for what that means for data already held.
Signing in
Your email address and a password. Passwords are never stored in plain text — only a salted cryptographic hash, which can't be turned back into your password. You can also claim an @handl (your address in handl.'s messaging) and, optionally, lock the app with a passcode or Face ID. Face ID and Touch ID are handled entirely on your device by Apple; no biometric data ever reaches us. The app-lock passcode never leaves your phone — no endpoint accepts it, and it is held in the device-only keychain as a salted hash rather than as the digits you chose.
You can instead sign in with Apple or Google. We receive the account identifier, email address and name they send us, and no password.
Your profile
Your name, date of birth, country of residence, email addresses and phone numbers (you can save several of each, with one marked default), and your device's time zone so "3pm Thursday" means the right moment. Optionally, so the assistant doesn't have to ask you twice: a passport number and expiry, airline and hotel loyalty numbers, seat and meal preferences, food allergies, your home and office addresses, quiet hours, and which assistant voice you prefer.
Two of these are deliberately fenced off. Your saved addresses exist only to work out travel times and "leave now" alerts — they are never given to anyone the assistant speaks to. Your allergies are health information and are treated as such (section 04).
Verifying a phone number is optional. If you do verify one — we text you a six-digit code — that number becomes discoverable by people who already have it saved in their address book, so they can message you in handl. without sending a request first. An unverified number is never used for discovery.
Talking to the assistant
The tasks and questions you give handl., typed or spoken, and the assistant's replies. If you speak, the recording is transcribed to text and the text is what we keep. Over time handl. also notes a small number of learned facts about how you work — "always books a window seat", "'the usual' means the Thai place" — so it stops asking the same questions. These are listed in Settings and you can delete any of them; nothing is hidden from you.
Where switched on, handl. also keeps a short record of your recent conversations, at most 90 days of them, with card, document and date of birth details blanked before they are written. Each night it builds a short profile of your preferences from that record, so you do not have to repeat yourself. The profile never holds a document, card or loyalty number, a date of birth or a health detail. Telling handl. to forget something removes it from both. We also keep a rolling list of your last 120 commands, to check that requests are being routed correctly, and, when handl. is learning the steps of a booking site, a trace of the moves its browser made, for 30 days. All of it is deleted with your account.
Bookings and the calls that make them
When you ask handl. to book something, we store the details of the business (name, number, category, notes), the booking itself and its status, and a transcript of the call so you can check what was actually agreed. Any recording of the call is held by our voice-call provider, not on our servers. We also keep a simple note of whether a business answered, which is how handl. learns a better time of day to try them next time.
Text messages
When you ask handl. to text someone, we store the message, who it went to, and any reply that comes back, so the conversation makes sense when you open it.
You can also text handl. directly, at the same number it texts you from. That only works from a number you have verified on your account: a text from a number nobody has verified is never processed by an AI model — the sender receives one short pointer to the app, at most once a day, and nothing else happens. Nobody who happens to know handl.'s number can reach your assistant with it.
Messaging other handl. users
You can message anyone else on handl., handle to handle, one to one or in a group. We store what is sent: message text, voice notes, photos and videos, files, location pins, shared contacts, events and polls, reactions, timestamps and the @handls involved, plus whether you have accepted, declined or blocked a conversation. A conversation is stored once and shared by the people in it, so each of you can read it. Nobody else can, and it isn't used for anything but delivering it: your messages don't feed an AI model and don't appear in your briefing. A one-to-one conversation is never read by the assistant. You can also share a card into a chat, such as your Whoop or Oura day, your weight trend or your agenda. It contains only the lines you see on it and goes only to the people in that chat. The one exception to the AI rule is yours to trigger: if you long-press a message and tap Summarise, that one message goes to our AI model provider (a voice note is first turned into text by our speech-to-text provider), and the summary is saved on the message, so both people see the same one. Nothing else from the conversation is sent.
There is exactly one exception, and it takes two deliberate acts to reach it. handl. reads a conversation only when (a) the group has added handl. to it as a member, and (b) a member addresses handl. by name in a message. Ordinary chatter in a group handl. belongs to is not read; only the turn that names it, plus that group's own recent messages for context, is sent to a model — and never a message from any other conversation. If handl. proposes a booking in a group, it can only be executed after the person who created the group confirms it; agreement from anyone else does nothing.
You can also set a disappearing-message timer on a conversation — 24 hours, 7 days or 90 days — after which its messages and their attachments are deleted. In a group, only the creator can change the timer. Whether or not you set one, every message is deleted after twelve months (section 07).
To show you which of your contacts are already on handl., your phone computes a SHA-256 hash of each saved number and sends only those hashes. We check them against the numbers people have verified on their accounts, tell your phone which matched, and discard the hashes. The phone numbers themselves never reach us. We should be straight about the limit of that: a hashed phone number is not a secret — the range of possible numbers is small enough to work through offline — so this protects the address book you upload, particularly the numbers of people who have never signed up. It is not a claim that a registered user's number is cryptographically hidden from someone who has already obtained our storage. That case is guarded by the encryption in section 10.
People you save as contacts
The name, phone number and relationship ("wife", "mother") of anyone you save so handl. can message or call them for you, plus an optional birthday and your own notes. This is personal information about someone other than you — please only add people who'd be comfortable with it. They can ask us to remove it by writing to the address in section 16.
Records, family and documents
Records is where you keep the dates handl. watches for you. It holds the people in your household (the name, date of birth and relationship of a partner, parent or child, and any allergies you note for them, which are health information under section 04), your documents (type, number, country and expiry of a passport or licence), your vehicles (plate, make, model) and schools (name, fees, events). You can also keep files in a document vault, such as a passport scan or a photo for an application, and keep travel tickets filed under your trip. Files are encrypted, and the contents of the vault are never put in front of the AI: a file is used only at the moment a form asks for it. (A scan you upload for handl. to read is read once by our AI model provider.) These are details about other people, so please only add those you are entitled to. They can ask us to remove them by writing to the address in section 16.
Reminders, notes, lists and watches
Whatever you put in them: reminder text and due times, notes, checklist and shopping items, and — for a location reminder — the place, its coordinates and radius, and whether it should fire when you arrive or when you leave. You can also ask handl. to watch a product page for a restock or price drop, which stores the link, your target price, and what each check found.
Location
Only with your permission, and only for what the permission prompt says. While using the app: finding places near you and answering location-aware questions. In the background: triggering location reminders — the geofence is evaluated on your phone, and your continuous whereabouts are not streamed to us or stored as a location history.
Your calendar, camera, photos, microphone and contacts
All device permissions, all optional, all only used for the stated purpose: the calendar to check for clashes and add confirmed bookings; the microphone to turn speech into a task; the camera and photo library to send a photo or video in a chat and to set your profile picture; your address book so you can pick someone to save as a contact. Your profile picture is stored, encrypted, on our servers so people you message can see it. It is deleted when you remove it or delete your account.
Health and fitness
See section 04 — it's short, and it's separate on purpose.
Wake-up calls
If you switch them on, we store the time you chose and the briefing prepared for that morning's call. You set this up yourself, and it stops the moment you turn it off.
Payments and subscription
Your subscription is bought through Apple In-App Purchase and its status is managed by our subscription-management provider. We see whether you are subscribed, not how you paid. Separately, if you want handl. to hold a real-world booking that requires a card, that card is stored and charged by our payment processor. Your own card number never reaches our servers. Where handl. pays at an online checkout for you, it uses a single-use card number created for that one purchase, not your own card.
Connected email accounts (optional)
If you connect Gmail or Outlook, handl. reads recent inbox metadata — sender, subject and a short snippet, not the full message body — to build your daily digest, and can create draft emails for you. Connecting an inbox also lets handl. mail you your daily encrypted backup file. You can disconnect at any time in Settings — see section 08, which sets out exactly what that deletes.
Reading what is inside an email is a separate permission, and it is off until you turn it on. Switch on Read email contents and handl. may open the full text of a small number of confirmation-shaped emails: to find your flights, hotel stays, reservations, deliveries and renewals, to notice a subscription about to go up in price, and to look up an order you have asked it about. The text of each one goes to the model that reads it, is used once, and is not kept — what handl. stores is the detail itself, such as a flight number and a booking reference. Leave it off and the paragraph above is the whole of it: sender, subject and a preview line, and those features stay quiet rather than working from a guess. Opening a single email yourself in the app has always shown you its contents and does not need this setting. We record when you turned it on or off and the exact wording you were shown, and you can read that record in the app's Trust Center.
Keeping travel tickets from email is a third, separate permission, and it is off until you say yes. The first time handl. notices a ticket or voucher attached to a travel email it has read under the permission above, it asks you once whether to keep tickets like it; until you answer, it holds only where that attachment is (the message and the file name), never the file. Say yes and handl. keeps the PDF, photo or Apple Wallet pass attached to a flight, hotel, train, car hire, tour, cruise or transfer confirmation, encrypted, filed under your trip so it is on your phone offline — and only those: an attachment that turns out not to be a ticket is read once and not kept. Say "Not now" and handl. does not ask again. The email's own text is still never kept. You can switch it off in Trust Center and delete every ticket it kept; disconnecting the mailbox deletes them too. Tickets you add yourself, and confirmations of bookings handl. made for you, are kept without this permission and stay until you delete them or your account. We record your yes or no and the exact wording you were shown.
Google user data
When you connect your Google account, handl. asks Google for three permissions: to read your Gmail (the metadata above, and full emails only if you switch on Read email contents), to create drafts and send the emails and backups you ask for, and to read and add events in your Google Calendar (so it can check your diary and set up a Google Meet when you ask). Google shows you each one before you agree.
handl.'s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain terms: we use Google data only to provide the features you can see in handl. and that you asked for; we never use it for advertising, never sell it, and never use it to train or improve AI or machine-learning models, ours or anyone else's. It reaches only the providers that run those features for you (the AI model that reads an email for you, listed in section 05), on terms that bar them from keeping or training on it. No person at handl. reads your email or calendar unless you ask us to (for example in a support request), it is needed for security or to investigate abuse, or the law requires it.
Connected Slack and Microsoft Teams (optional)
If you connect Slack or Microsoft Teams, the messages waiting on you — direct messages, group chats, and messages that @mention you, from the last 24 hours — can appear in What needs you beside your email, under the same rules. To decide what to show, handl. reads the recent ones and sends the sender, a preview and where it was (“#eng”, “a Teams chat”) to the model that ranks them; nothing is written to disk but the message and conversation IDs, the sender, and the time. The words themselves are fetched from Slack or Microsoft again when you open a message, ask handl. to answer it, or ask about it (“what did I miss on Slack”), and are not kept. When you dismiss one, handl. remembers who it was from, never what it said. A reply or a message goes only when you tap Send on the exact words, or, if you have turned on letting handl. reply for you, under the same rules as email: never to someone new, never about money, a date or anything legal, and always written to your consent log first. For Teams, handl. reads your chats but not your team channels, and can only post into a channel when you ask.
Your bank (optional)
Only if you choose to connect a bank, handl. receives read-only transaction data from it through Plaid: which bank it is, and the payments that recur in your transactions. We use it for one thing, finding your recurring subscriptions and bills. You sign in to your bank through Plaid, not through us, so handl. never sees your bank login. Your transactions are fetched from Plaid live each time you look, and are not stored. What we do keep is the connection token that lets us ask, and it is encrypted at rest and never sent to your phone. handl. never moves money through Plaid; the connection can read, not pay. Bank data is never sent to an AI model and never reaches a phone call.
Notifications and diagnostics
To send you a push notification we store a device push token. Our server logs record errors and the fact that a request happened; they are deliberately written so that the contents of your messages, documents and profile never appear in them.
Calls handl. makes for you
This is the part of handl. that most deserves a clear explanation, so here it is in full.
Calls only happen because you asked for one. handl. does not call anybody on its own initiative. Every call is the direct result of a task you gave it, and you can watch it live and hang it up from the app.
Third parties are told, up front, every time. The first thing the assistant says is that it is handl., an AI assistant calling on your behalf, on a recorded line — before anything else is discussed. If it's transferred to a different person mid-call, it says it again to them. It never claims to be human and never pretends to be you. Calls are recorded and transcribed so that you have a record of what was agreed; if the person on the other end asks whether they're being recorded, the assistant confirms it honestly.
It shares the minimum, and no more. On a call to a business or to someone you asked it to contact, the assistant may volunteer only your name, phone number and email address — the three things a booking actually needs. Your home and office addresses, your health data and the contents of your messages are excluded outright: they are not put in front of the model that drafts the call at all, so there is nothing for it to say. The one exception is a dietary note. When you ask handl. to book a table, a saved allergy is passed on as a note for the table, such as "one guest, shellfish", without saying which guest.
Three details are shared only when your own instruction asks for them: your passport number, your date of birth and your airline and hotel loyalty numbers. "Text my wife I'll be home at six" carries none of them. "Give them my Skywards number" carries that one, and only that one. This is enforced twice over — the value is kept out of the drafting prompt unless your command mentions it, and the drafted words are then scanned once more before they are spoken, with any unasked-for value stripped out. The stored copy in your own app keeps what was drafted, so nothing is hidden from you.
Date of birth has one extra path, because businesses genuinely do ask for it to confirm a booking. If it comes up mid-call, the assistant does not answer from memory: it pauses, a notification arrives on your phone, and it says nothing until you tap to allow it. No answer within the call's short window counts as a no, and the assistant tells the business it can't provide that. For anything else a caller asks for — home address, card details, ID numbers — there is no real-time permission path, so the assistant simply declines and suggests they contact you directly.
Wake-up calls are the one deliberate carve-out, and they are a call to you, not about you. They ring the number on your own profile and read you your own day: your agenda titles and times, a weather line, and — if you have connected a wearable — your own sleep and recovery figures. That is health data spoken aloud, which is why it is only ever spoken back to the person it belongs to, on their own number, and why the briefing carries nothing else: no passport number, no date of birth, no addresses, no message content. It exists only because you switched it on and picked the time, and it stops the moment you switch it off.
Health information
handl. holds health data only if you choose to use its health features: weight entries you log, allergies you save on your profile, workout and meal plans you ask it to build, and, if you connect Whoop, Oura, Fitbit or Withings, the daily summary those devices produce: recovery or readiness score, sleep score and hours, heart-rate variability, resting heart rate, and weight where the device records it. If you turn on Apple Health, we read your weight, sleep, resting heart rate and steps from it.
Some health information reaches us only because you tell it to handl. for a task, such as asking it to request wheelchair help or a special meal from an airline. We use that only for the task you asked for. Saved allergies are passed to a restaurant only when you ask handl. to book there, as a note for the table such as "one guest, shellfish". Health details you mention in a chat are not saved as facts about you.
What we do with it: show it to you, feed it into a briefing or a plan you asked for, and nudge you when recovery or sleep looks poor. Composing a briefing or a plan means sending the relevant figures to our AI provider for that one request; they are not used to train any model. Your weight log is sent to our AI model provider only as context when you ask a question about your own history. It is not used to train any model.
handl. uses health information, from the sources you connect and the health needs you mention, only to do what you ask. It is never used for marketing, never sold and never used to train a model. You can disconnect a source or delete what it holds at any time. We are adding a step that asks for your permission before any health information is used.
We do not use health or fitness data for advertising or marketing of any kind. We do not sell it, share it with data brokers, or use it for anything other than the health features you're using in the app. Disconnecting a wearable in Settings stops the sync, revokes our access at the provider where the provider allows it, and deletes the readings we stored from it. Section 08 sets out exactly what goes and, for Fitbit weight, what stays. Deleting your account deletes all of it.
Who else touches your data
We use a small number of specialist providers to do the work. We use them under written terms that limit them to processing your information on our instructions, and each only ever receives what it needs for its own job. We describe them here by what they do.
| Provider | What it receives | Why | Where it is based |
|---|---|---|---|
| Our AI model providers | The task or question you gave the assistant, and the specific saved details that task needs; the agenda and health figures behind a briefing; in a group that added handl., the addressed message and the recent context of that group; a message you asked to have summarised; a document you asked handl. to read | Understanding what you asked for and composing the reply | United States |
| Our web search provider | The search query for a current or local question, which can contain a place or company name, and your approximate area (city or region, never your exact position). No account details | Finding web pages that answer the question | United States |
| Our speech-to-text provider | The audio of something you dictated, or of a Loop voice note you asked to have summarised | Turning speech into text | United States |
| The website you asked us to book | When a venue takes online bookings, our own automated browser fills the booking form of that venue with the details a reservation needs, your name, phone number, email and party details, exactly as a human assistant would. Only for the specific booking you asked for, only on the site of that venue or its booking platform, and their own privacy terms then apply to what you would have given them yourself | Completing the booking you requested without a phone call | Wherever that business is |
| Our browser-automation providers | The web page our automated browser is looking at while it carries out a task for you, and the task itself with your own name, email, phone number and date of birth taken out. No account details | Choosing the next step for the automated browser | Available on request |
| Our private computing workspace | The files you attach to a request that needs work done on them (comparing quotes, totalling a statement, turning receipts into a spreadsheet), and the code that does that work. Nothing else: no account details, keys or payment details, and the workspace has no internet access | A private, disposable workspace for that one task, deleted as soon as the task ends | Available on request |
| Our voice-call provider, and its voice provider | The number being called, your first name, the purpose of the call, and the briefing or message to be spoken; the words the assistant is about to say; the resulting recording and transcript | Placing and running phone calls, in the voice of the assistant. The recording is held here, not on our servers | United States |
| Our telephony and text-message provider | Your phone number and the contents of texts sent or received on your behalf; verification codes; call metadata | Carrying texts, verification codes and phone calls | United States |
| Our messaging provider for Apple Messages | Only if you message handl. through Apple Messages: your messages and replies, and an opaque Apple conversation id (no phone number) | Carrying Apple Messages | European Union |
| Our maps and places provider | The place you searched for, and start and end points for a travel-time estimate | Business details, addresses and "leave now" timings. Searches are passed straight through and never written to our storage | United States |
| Our weather provider | The coordinates of the place you asked about. No account details | Forecasts | Europe |
| Our flight data providers | For a search: the route, dates and number of travellers, never your name or contact details. For a flight you follow: the flight number and date | Finding flight times and prices, and live status and position | United States and European Union |
| Our flight booking provider | Flight bookings only: your name, date of birth, gender, email and phone and, only when a fare requires it and you have said yes, your passport number and expiry | Booking the flight you chose | United Kingdom |
| Our hotel booking provider | Hotel bookings only: your name, email and phone as the guest, and the stay you chose | Booking the hotel you chose | Available on request |
| Our hosting provider | Everything we store, encrypted at rest | Running our servers and storage | United States |
| Our payment processor | Your card details, entered directly into the secure form of the processor, and the amount of any booking hold or purchase. Its form also collects device identifiers for payment fraud prevention | Holding and charging a card when a booking or purchase requires one. Your own card number never reaches our servers | United States and Ireland |
| Our subscription-management provider | An app user id, your subscription and trial state, and device identifiers | Unlocking the paid plan you bought through the App Store | United States |
| Our push-notification relay, and Apple | Your device push token and the text of the notification itself | Delivering push notifications | United States |
| Our email delivery provider | Your email address and the email itself, such as a password-reset link or a booking receipt | Sending you the emails that handl. itself sends | United States |
| Apple or Google sign-in | Only if you choose it: your sign-in request. We receive back an account id, your email address and name | Signing you in without a handl. password | United States |
| Google (Gmail and Calendar) | Only if you connect it: an OAuth grant to your mailbox and calendar | Reading recent inbox metadata for your digest, sending drafts and backups you asked for, and reading and adding calendar events you asked for | United States |
| Microsoft (Outlook) | Only if you connect it: an OAuth grant to your mailbox | The same digest, draft and backup features as Gmail | United States |
| Whoop, Oura, Fitbit, Withings | Only if you connect one: an OAuth grant to your daily metrics | Sleep, recovery and weight figures for the health features | United States and European Union |
| Plaid | Only if you connect a bank: your bank sign-in, entered through Plaid rather than handl., and the bank data Plaid collects from it. Plaid Inc. collects that data under its own End User Privacy Policy, not only on our instructions | Connecting your bank, read-only, so handl. can find your recurring subscriptions and bills | United States |
| Link | Only if you connect your Link wallet: a request for a single-use card for a purchase you approved | Paying for that one purchase | United States |
| AwardWallet | Only if you connect it: a read-only grant to your loyalty balances and status | Showing your miles and points | Available on request |
| Philips Hue, Sonos, SmartThings | Only if you connect one: an OAuth grant to control the devices on that account | Doing what you ask with your lights, speakers or smart home | Available on request |
| Only if you connect it: a sign-in grant (your name, email and photo) and permission to post as you. We send only the exact post you approved | Posting to LinkedIn when you ask and say yes | United States | |
| Meta (Threads) | Only if you connect it: a grant to your Threads profile and permission to post as you. We send only the exact post you approved | Posting to Threads when you ask and say yes | United States |
| Slack | Only if you connect it: a grant to your workspace. We read your recent direct messages, group messages and mentions to show what needs a reply, and send only messages you approved (or, if you turned it on, replies under the rules above) | Showing what needs a reply, and reading and replying in Slack when you ask | United States |
| Microsoft (Teams) | Only if you connect it: a grant to your Teams chats and the names of your teams and channels. We read your recent chats to show what needs a reply, and send only messages you approved (or, if you turned it on, replies under the rules above) | Showing what needs a reply, and reading and replying in Teams when you ask | United States |
| Telegram | Only if you link it: your Telegram chat ID, the messages you send to the handl. bot, and its replies | Letting you use handl. from Telegram | Available on request |
A current list of the companies we use as service providers, and where each is based, is available on request from info@handlai.co. Section 12 explains the safeguards for information that leaves the UK, the EEA or the UAE.
Two things worth saying plainly about the AI providers: your data is sent to them only to process the specific request in front of them, and it is not used to train their models. We use them on API terms that exclude training, and handl. has no fine-tuning or model-training pipeline of any kind.
We should be equally plain about what we do not claim. handl. carries no advertising SDK, no attribution SDK, no general-purpose analytics SDK and no crash-reporting SDK, and it never asks for a tracking permission because it has nothing to track you with. But it would be wrong to say the app talks only to our servers: the form of our payment processor sends its own fraud-prevention telemetry, our subscription-management provider reports subscription events so we know how many people subscribed, and every push notification travels through our push relay and Apple. Those are the exceptions, and none of them is used for advertising or to track you across the apps of other companies.
We also share information with the businesses and people you ask us to contact, on the terms set out in section 03. And we may disclose information if the law requires it, such as a court order or a valid legal process, or to protect the safety of a person.
Lending handl. your sign-in for one site (optional, off by default)
The browser described above is normally a stranger to the site it visits: it fills a public booking form the way anyone could. There is one exception, and you have to switch it on yourself, one site at a time. If you are part-way through something on a site you are signed in to — a return, an order, an account change — and you leave the app before it finishes, handl. can carry on where you left off. To do that, your phone sends that one site's sign-in cookies to our server, which opens a throwaway browser that is signed in as you for the length of that task.
What that means, plainly: for that task, on that site, handl. is you. So the limits matter, and these are the ones we hold ourselves to. It applies only to sites you have added to the list yourself, and the list starts empty — no site is on it until you put it there, and you can take one off at any time. It happens only while a task on that site is already running, and our server uses that one site's cookies and no others: anything else that arrives with them is discarded unused. They are held in memory for that browser alone, are never written to our storage or our logs, and are gone when the browser closes at the end of the task. We never keep them to use again — your phone sends them afresh for each task that needs them. And handl. will not place an order or confirm a payment while signed in as you — it stops and hands the decision back to you — except up to a spending limit you have set for that specific merchant yourself.
We do not sell your personal information, we do not share it for advertising, and we do not track you across other companies' apps and websites.
A push notification cannot reach your phone directly. It passes through our push relay and then the Apple notification service, and lands on a lock screen anyone nearby can read. That is why notifications about messages do not show the message by default. They say only that someone sent you one. You can turn previews on if you prefer; they are off until you do.
Why we're allowed to (UK/EU)
If you're in the UK or the EEA, the law asks us to name a lawful basis for each thing we do. In plain terms:
- To perform our contract with you — your account, profile, tasks, bookings, calls, messages, reminders, lists and subscription. This is simply us doing the thing you signed up for.
- Your consent — health and wearable data, wake-up calls, location, calendar, camera, photos, microphone and address-book access, connected email accounts, adding handl. to a group conversation, and sharing anything beyond your name, phone and email on a call (which happens only on your own instruction, or, for a date of birth, on a permission you grant during the call itself). You gave each of these separately and can withdraw any of them at any time, in the app or in your device settings, without affecting the rest.
- Our legitimate interests — keeping the service secure and available, preventing abuse, and fixing what's broken. We've balanced this against your privacy: it means error logs and rate limits, not profiling or advertising.
- Legal obligation — where we have to keep or disclose something to comply with the law.
Health data is special category information under UK and EU law. handl. holds it only when you choose to use a health feature, and section 04 says how it is used and how to remove it. We are adding a step that asks for your permission before any health information is used.
If you are in the United Arab Emirates, the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) applies the same way: we process your information to provide the service you asked for, on your consent where the list above says consent, and to meet our legal obligations.
How long we keep it
Most of what you put into handl. is kept for as long as your account is open, so the app keeps working the way you expect without you re-entering things. Everything with a shorter clock is listed here, with the real number.
| What | How long | Then what |
|---|---|---|
| Loop messages | 12 months — or the shorter timer you chose for that conversation (24 hours, 7 days or 90 days) | The message, its row and any voice note, photo or video attached to it are deleted. An hourly sweep applies whichever window is shortest |
| A very long conversation | Its most recent 500 messages | Older ones go early, with their attachments, even if they haven't reached 12 months |
| Messages from a sender you declined | 30 days from when they were sent | Deleted. Declining never tells the other person they were declined, and this doesn't either |
| Your daily inbox digest | Transient — rebuilt each time, held in memory | Nothing to delete; it is dropped the moment you disconnect the mailbox |
| Wearable daily metrics | Until you disconnect the wearable | The stored readings are deleted at disconnect (section 08) |
| Your weight log | Until you delete an entry, or your account | It is your own record rather than a provider's, so disconnecting Fitbit does not clear it |
| Conversation record, command list (where switched on) | 90 days of recent conversation; your last 120 commands; 30 days of browser-step traces | Older entries are removed automatically |
| Encrypted backup snapshots | 14 daily snapshots, on a rolling rotation | The oldest is deleted as each new one is written, so anything you delete inside your account disappears from backups within 14 days |
| A released @handl | 90 days of quarantine after account deletion | Only then can anyone else claim it |
| Server logs | Kept only as long as our hosting provider keeps them, and not copied anywhere else | They record that a request happened and any error, and are deliberately written so the contents of your messages, documents and profile never appear in them |
Disconnecting an account: forget, not just stop
Turning off a connection that only stops the sync isn't privacy, it's housekeeping. Disconnecting in handl. means we delete what we took.
Gmail
Disconnecting deletes the stored access and refresh tokens and everything handl. derived from your mailbox — the learning signals holding real senders and subjects, your digest state, the ledgers of which messages you dismissed or replied to, and any travel tickets kept from your email. All of it goes immediately. We then revoke the grant at Google, so the token is dead even if a copy existed anywhere.
Outlook
Everything on our side goes exactly as it does for Gmail: tokens, learning signals, digest state and ledgers, immediately. The one thing we cannot do is revoke the grant for you. Microsoft's identity platform offers no safe app-scoped revocation — the call available to us would sign you out of everything, everywhere, which is not ours to do. So if you want the grant itself removed as well as our copy of it, remove handl. at account.microsoft.com. We'd rather tell you that than let you assume it happened.
Whoop and Oura
Disconnecting revokes our access at the provider and deletes the readings we stored from it — the daily recovery, readiness, sleep and heart-rate figures. Nothing is kept back.
Withings
Disconnecting deletes our stored access and the readings we took from it. Withings offers no way for an app to withdraw its own access, so remove handl. in your Withings account settings as well.
Fitbit
Disconnecting revokes our access at Fitbit and stops the sync. One thing is deliberately kept, and we want to be explicit about it: weight entries already synced stay, as your own weight log. They are readings about your body that you chose to bring into your history, not a cache of someone else's data — and losing months of your own chart because you swapped a device would be the wrong default. They remain individually deletable in the app, they are included in your data export, and they are erased with your account.
Your bank
Disconnecting a bank removes the connection at Plaid first, which ends your consent and stops Plaid reading from your bank for us, and then deletes our record of it, token included. If Plaid can’t be reached, the bank stays listed as connected so you can try again, rather than looking gone while it is still live.
LinkedIn, Threads and Slack
Nothing is ever posted or sent from these accounts without your yes on the exact words, and a record of that yes is kept in your consent log. Disconnecting deletes our stored access tokens immediately, and we revoke the grant at the provider wherever the provider lets us — Slack does, so we do. Where it doesn’t, we tell you in the app, and you can remove handl. in that service’s own settings. Disconnecting Slack also deletes the record of which Slack messages you answered or dismissed, and who they were from.
Microsoft Teams
Disconnecting deletes our stored tokens and the record of which Teams messages you answered or dismissed, immediately. As with Outlook, we cannot revoke the grant for you: Microsoft offers no app-scoped revocation. To remove it there too, remove handl. at myapps.microsoft.com (a work or school account) or account.microsoft.com (a personal one) — the app tells you this when you disconnect.
Telegram
Unlinking — in the app, or by sending /stop to the bot — removes the link between
your Telegram chat and your handl. account straight away. The bot then answers nothing from that chat until
it is linked again.
handl. never connects to your personal Facebook account. When you ask it to post there, it opens Facebook’s own share screen with your text filled in, and you post it yourself.
Deleting your account
Settings, then Delete My Account, permanently and immediately removes what we hold about you. To make sure it is you, the app first asks for Face ID or your passcode, or for you to sign in again. In full: your profile and credentials, saved contacts and businesses, bookings, call transcripts, text messages, Loop messages and their voice notes, photos and videos, health and wearable data, your weight log, reminders, notes, lists, watches, learned facts, connected-account tokens, your stored backup snapshots, and the internal indexes that pointed at you (contact discovery, matched contacts held by other people, and the call and record lookups that live outside your own folder). This cannot be undone, and you do not need to email us to do it.
Any bank you connected is also removed at Plaid, not just forgotten here. Your deletion never depends on Plaid, though: if Plaid can’t be reached at that moment, everything here is still deleted, including the connection token, and the connection may stay open at Plaid until you ask Plaid to close it.
A connected Slack workspace has its grant revoked at Slack as part of the deletion, the same as pressing Disconnect. Microsoft (Outlook and Teams), LinkedIn and Threads offer no way for an app to withdraw its own access, so for those our tokens are destroyed and the grant stays listed in that service’s own settings until you remove it there.
Your messages to other people are redacted out of their copies, so what survives is only the other person's own side of the conversation — which is their information, not yours. Messages you sent under a handle you had previously renamed away from are redacted too.
Your @handl isn't given to anyone else for at least 90 days afterwards. An @handl is the address people message you at and the name on every message they've already had from you; handing it straight to the next person to ask would quietly point all of that at a stranger.
What we can't reach
Deleting your account deletes it from our systems. It does not reach inside the companies in section 05, each of which keeps its own records under its own policy and its own retention clock. Being specific about which:
- Our telephony and text-message provider: logs of the texts and calls carried for you.
- Our voice-call provider: recordings and transcripts of calls the assistant placed.
- Plaid — the bank data it collected when you connected, kept under its own End User Privacy Policy.
- Our payment processor: payment records, which it must keep for financial and anti-fraud purposes. We do delete your customer record there, and the cards saved on it.
- Apple and our subscription-management provider: your subscription record. Deleting your account does not cancel a subscription. Cancel it in iPhone Settings, then your name, then Subscriptions.
- Our AI model and speech-to-text providers: short-term API logs of the requests we sent them.
- Our computing workspace provider: the workspace and the files in it are deleted when your task ends, and any short-term logs it holds are covered by its own policy.
- Our browser-automation providers: we ask them not to keep the pages our automated browser sends them, and any short-term logs they hold are covered by their own policies.
- Withings, Philips Hue, SmartThings and Sonos: we delete our access tokens, but none of them lets us withdraw the permission you granted. Remove handl. in the app or account settings of that company.
If you want their copies removed, you're entitled to ask us and we'll pass the request on; we'll also tell you honestly where a provider's legal retention obligation means the answer is no.
Two more limits worth stating. Data you delete from inside your account can survive in our rolling encrypted backups until those snapshots rotate out, which takes at most 14 days; deleting your account deletes your snapshots outright. And if you had daily backups delivered to your own connected inbox, any copy already sitting in that inbox before deletion isn't something we can retroactively unsend — those are yours to delete.
Two records are kept after deletion on purpose. If you reported a message, or someone reported one of yours, the report is kept so that abuse cannot be erased by deleting an account. And if a business or a person asked handl. never to call or text them again, their number stays on our do-not-contact list. That list is about them, not you.
Security
Everything we store about you is encrypted at rest with AES-256-GCM, and travels between your phone and our servers over HTTPS. Encryption at rest is not a setting we can forget to switch on: in production the server refuses to start if no encryption key is configured, rather than quietly falling back to plaintext storage. Backup snapshots are encrypted with the same key, and an unencrypted snapshot is never mailed anywhere. Passwords are stored only as salted hashes. You stay signed in on a device for up to a year. If you do not open handl. for 30 days, you are signed out and need to sign in again. Access to production data is limited to the people who need it to run the service. Your passport number is masked in the app itself, and the app can be locked behind a passcode or Face ID that never leaves your phone.
One thing we don't claim: Loop is not end-to-end encrypted, and an honest assistant can't pretend otherwise. To act on a request, something has to read it; a group that adds handl. as a member has added a participant that must be able to hear. Your one-to-one messages are never read by an AI model unless you ask for one to be summarised, and are never used for anything but delivering them. They are still readable by our infrastructure, in the same sense that messages on any hosted messenger are, so hold us to the encryption, deletion and access limits above rather than to a promise we cannot keep.
No system is perfectly secure, and we won't pretend otherwise — but if a breach ever affected your data, we'll tell you and the relevant regulator as the law requires.
Your rights and choices
Wherever you live, you can do all of this yourself in the app:
- See, edit or delete anything on your profile, and any saved contact, business, reminder, note, list item, weight entry or learned fact
- Disconnect Gmail, Outlook, Slack, Microsoft Teams, Whoop, Oura, Fitbit or Withings at any time in Settings
- Turn off wake-up calls, App Lock, or any individual device permission, in the app or in iOS Settings
- Export a copy of your data — Settings → Export My Data — as a JSON file covering your profile, contacts, businesses, bookings, message calls, reminders, notes, lists, watches, calendar invites, health plans, weight log, learned facts, wake-up settings and your full Loop message history. Media is referenced by id and kind rather than embedded, so the export stays a file you can actually open
- Delete your account and everything in it — Settings → Delete My Account
- Log out, ending the session on that device
If you're in the UK or the EEA you also have the rights to access, correct, erase, restrict and object to our processing of your information, to receive it in a portable form, and to withdraw consent at any time. Most of these are the buttons above; for anything else — including asking us to remove information you added about someone else — write to info@handlai.co. We'll respond within one month. You're also entitled to complain to your data protection authority (in the UK, the Information Commissioner's Office at ico.org.uk).
If you're in California or another US state with a privacy law, you have comparable rights: to know what personal information we collect and why, to a copy of it in a portable form, to correct it, to delete it, to limit the use of sensitive personal information, and not to be discriminated against for exercising any of them. Under the CCPA/CPRA we have not sold or shared personal information for cross-context behavioural advertising in the preceding twelve months, and we never have, so there is no "Do Not Sell or Share My Personal Information" opt-out to offer you — there is nothing to opt out of. You can exercise the access, portability and deletion rights yourself with the buttons above, or by writing to us; we don't require an account or a fee to answer, and an authorised agent may make a request on your behalf.
If you are in the United Arab Emirates, the UAE Personal Data Protection Law gives you the right to be told what we hold about you and why, to receive a copy of it in a structured, machine-readable form, to have it corrected, to have it erased, to restrict or stop our processing of it, to object to decisions about you made solely by automated processing, and to withdraw consent at any time. Most of these are the buttons above. For anything else, write to info@handlai.co and we will respond within one month. If you are not satisfied with our answer, you can complain to the UAE Data Office.
International transfers
handl. runs on servers in the United States. If you use handl. from the United Kingdom, the European Economic Area, the UAE or anywhere else outside the US, your information is transferred to and processed in the US, and by some of the providers in section 05 in other countries besides. The table in section 05 says where each kind of provider is based.
Where a provider is outside the UK, the transfer relies on safeguards recognised under UK law where the data-processing terms of that provider include them, such as adequacy regulations or the International Data Transfer Addendum to standard contractual clauses. The United Kingdom and the European Union treat each other as adequate. Alongside those safeguards we apply the practical measures in section 10: encryption in transit and at rest, minimised sharing, and written terms that limit each provider to processing only on our instructions.
Where we transfer personal information out of the UAE, each provider that receives it is bound by written terms to protect it, and some transfers are simply necessary to do what you asked, such as sending your name to the airline you are booking. The countries involved, chiefly the United States, may not have data protection laws equivalent to those of the UAE, which is why we rely on those terms and on the measures in section 10.
You can ask us for a copy of the transfer safeguards that apply to you by writing to info@handlai.co.
Change of control
If Relleps, Inc. is ever acquired, merged, reorganised, or sells the business or assets behind handl., your information may transfer to the acquiring party as part of that transaction. We're saying so plainly rather than burying it, because it is the point at which most privacy promises quietly stop applying.
The commitments on this page travel with the data. Any successor takes it subject to this policy as it stood when they received it, and cannot apply materially different terms to information collected beforehand without telling you in the app first and, where the law requires consent, obtaining it. If you'd rather not be part of that, you can export your data and delete your account before the change takes effect — which is why we commit to notifying you in advance rather than afterwards.
We do not sell personal information, and a change of control is not a workaround for that: your data is not a product that can be sold on its own, only an asset of the business that remains bound by these commitments.
Children's privacy
handl. is not intended for anyone under 16, and we do not knowingly let anyone under 16 hold an account. If you believe a child has created one, write to us and we will delete it. Parents can add details of their own children (name, date of birth, allergies, school) to Records as dependants, so handl. can make bookings for the family. Those details belong to the account of the parent. They do not give the child an account.
Changes to this policy
We'll update the date at the top of this page whenever this policy changes, so it's easy to see whether anything's new. If a change materially affects how we use your information, we'll tell you in the app before it takes effect.