Privacy Policy

ehllo is a product of EHLLO LTD (“EHLLO LTD”, “we”, “us”), a company registered in England and Wales, Company No. 17434728. EHLLO LTD is the controller of the personal data described here.

ehllo is a relationship workspace: you capture the people you meet, record what mattered, and get help turning that into a follow-up. This policy explains what data we collect, why, and how you stay in control of it — including data we access through an optional Google account connection (Microsoft support is coming soon).

Data you give us directly

• Account information — your name, email address, and profile details when you sign up or sign in. If you sign in with Apple, Apple gives us your name, the first time only, and either your email address or a private relay address that forwards to it, if you chose to hide yours. We never see your Apple ID password. If you sign in with Google (including Google's one-tap prompt on our website), Google gives us your name, email address and profile picture. We never see your Google password.
• Contacts and encounters — people you capture, meeting notes, voice recordings you choose to transcribe, and shared meeting summaries.
• Saved memories — notes you choose to keep about the people you meet, so ehllo can remind you of them and help you follow up.
• Follow-ups — AI-drafted next actions generated from your notes, which you review and approve before anything is sent.
• Events — events you add manually or paste a link for, and your going/not-going status for them.
• Your public card — the profile information you choose to share when someone scans your QR code or visits your public link.
• Your phone's contacts (optional) — if you allow it, the app reads the names, email addresses and phone numbers in your address book on your phone, so you can pick someone when adding them to a meeting. Your address book is not uploaded; only the person you pick is saved to ehllo.

Data from Google (optional)

Connecting a Google account is entirely optional and is separate from signing in to ehllo. Microsoft (Outlook and OneDrive) support is coming soon; the equivalent Microsoft permissions are noted below and will apply only once it launches. If you choose to connect an account from Settings, we request only the following, and only for the purposes below:

• Read your calendar (Google Calendar calendar.readonly / Microsoft Calendars.ReadWrite) — we look up which calendars you have and read the title, time, location and attendees of events on them. That is what lets ehllo suggest events worth tracking and, once you confirm a conversation happened during one, link the two together. Reading the list of calendars is what makes meetings on a work or team calendar visible at all; without it only your primary calendar can be seen.
• Create and update events ehllo makes (Google Calendar calendar.events / Microsoft Calendars.ReadWrite) — when you approve a follow-up that needs a meeting, ehllo puts that meeting on your primary calendar, and updates or removes it if you change or cancel the follow-up here. It only ever changes events it created itself; everything already in your calendar is left exactly as it is.
• App-created files (Google Drive drive.file / Microsoft OneDrive app folder) — scoped only to files ehllo itself creates; we cannot see or access any other file in your Drive or OneDrive.

You can disconnect a connected account at any time from Settings → Connected accounts. Disconnecting immediately deletes the access and refresh tokens ehllo stored and revokes ehllo's access with Google, so ehllo also disappears from your account's list of connected apps. You can double-check that list any time in your Google security settings.

Granola. If you connect Granola from Settings → Connected accounts, ehllo signs in to your Granola account with your permission and reads the meetings it holds from the last 30 days, then new ones every few hours: each call's title, date, attendees, Granola's summary and the notes you wrote. ehllo keeps a copy of each as a meeting for you to review, matched to your people by email, and nothing is shared with anyone unless you share that meeting yourself. Disconnecting deletes the access ehllo stored and stops new calls arriving; meetings already brought in stay until you delete them.

Your iPhone's calendar. On iPhone you can instead connect Apple from Settings → Connected accounts. ehllo then asks iOS for access to the calendar on your phone and, only after you allow it, reads the title, time, location and organiser of the events in the next 14 days, and the names and email addresses of the people invited to them, and sends them to ehllo, so they can be suggested and linked to your conversations just like Google and Microsoft events. ehllo does not read your reminders and does not change your calendar. Disconnecting stops ehllo reading it; events already added stay until you remove them, and you can withdraw access at any time in your iPhone's Settings.

People who are not ehllo users

ehllo holds some information about people who have not signed up themselves, because an ehllo user met them. If that is you, this is what we hold, where it came from and what you can do.

• You shared your details on someone's ehllo card. What you typed into the form (your name, email and anything else you chose to add) goes to the person whose card it was. We also set up an ehllo account for that email address, with a card made from what you typed, so that the person you met has you in their People. That card is not shown publicly: only the person you shared it with can see it, until you sign in to ehllo yourself, which makes the account and card yours. If the email belongs to an ehllo account someone has signed in to, nothing is added to it until that account says yes.
• Someone added you to a meeting they recorded or noted. We keep your name and email on their meeting. Adding you sets up no account and sends you nothing: you hear from ehllo only if they share the meeting with you, in one email with a link to it. If you later join ehllo at that address, the meetings shared with you there appear in your account and you are connected to the person who shared them. Every such email has a link to stop them.
• You were on a calendar invitation, or in a Granola call, with an ehllo user who connected their calendar or Granola. We keep your name and email address as part of that event or call, in their account only.
• Someone noted who introduced them to someone else, or wrote a note that mentions you. That stays in their account, private to them.

We do this on the basis of the legitimate interest of the ehllo user in keeping a record of the people they meet, and ours in providing that service. It is kept for as long as the user who holds it keeps it, or until their account is deleted. You can ask us what we hold about you, have it corrected or deleted, or object, by writing to product@ehllo.io. An account set up for your email that you never signed in to can be deleted on request.

How we use your data

• To operate the core product: capturing contacts, recording context, and drafting follow-ups.
• To generate AI summaries, extracted follow-ups and draft messages, and to transcribe recordings you make. See AI processing below for what is sent, to whom, and what we never do with it.
• To detect and suggest calendar events worth tracking, and to put a meeting on your calendar when you approve a follow-up that needs one, if you've connected a calendar.
• To send transactional email (for example, magic-link sign-in) via our email provider. If you choose to stop the emails ehllo sends when someone adds you to a meeting, shares one with you or invites you to an event, we keep a scrambled form of the address so we can honour that, never the address itself, and you can turn them back on from the same link.
• To keep the product secure and prevent abuse.

We do not sell your data, and we do not use your private notes or contacts to serve ads.

AI processing

ehllo uses AI to turn what you capture into something useful: a summary of a conversation, the follow-ups it contains, and a draft message. Three kinds of processor are involved, and which one handles your data depends on how ehllo is configured at the time:

• Text (summaries, extracted follow-ups, drafts, and answers from the assistant) — Anthropic (Claude), Google (Gemini) or OpenAI.
• Transcription (audio you record in ehllo) — Groq, Google (Gemini) or OpenAI (Whisper). The audio itself is sent, not just a transcript of it. While you record, and when you speak a question to Ask, your phone's own speech recognition (Apple on iPhone, Google on Android) may also turn what is said into text as you go, and may send the audio to Apple or Google to do so.
• Voice (the ehllo voice that reads the assistant's answers aloud, and live conversations with ehllo) — Google (Gemini). When an answer is read aloud, only the words of ehllo's answer are sent, a sentence or two at a time. In a live conversation, your voice is streamed through ehllo's own server on Google Cloud in the United States to Google, so ehllo can understand and answer you, and the questions you ask are looked up in your own ehllo records as described above. ehllo does not store the audio, either way; what was said in a live conversation is added to your chat as text.

What is sent. For a summary, extraction or draft, we send the note or recording that request is about. The assistant is broader: to answer a question about your relationships it is first sent a short index of your workspace — the names of people you have met, the titles and dates of events, whether you were going, a truncated snippet of each summary or note, and the titles of your follow-ups — and then the fuller records for only the items your question concerns. It is never sent your full notes or transcripts to build that index.

Calendar data is included in this, and you can switch it off. If you have connected a Google or Microsoft calendar, the titles and dates of events synced from it can appear in what is sent, because an event title is often the only record of where you met someone. You can stop that without disconnecting anything: in the ehllo app, open Settings → Connected accounts and turn off Use calendar context in AI. With it off, event names and dates are removed from everything sent to an AI provider — enforced on our servers, not just in the app — while your notes, summaries, names and follow-ups are unaffected. It is on by default, because it is what ehllo has always done. Disconnecting the calendar entirely also works, and the rest of ehllo continues either way.

You review everything; AI decides nothing. AI proposes and you dispose. It does not send a message, complete or activate a follow-up, or change a person's details on its own. Nothing drafted for you leaves ehllo until you have read it and chosen to send it.

What we never do. We do not train models on your data. We do not use data obtained from Google APIs — including data obtained through Google Workspace APIs such as Google Calendar — to develop, improve, or train non-personalized AI and/or ML models, and our agreements with the providers above restrict them to processing your data solely to return the result you asked for, not to train their own models. We do not use Google user data for advertising, and we do not sell it or transfer it to data brokers or information resellers. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Subscriptions and payments

ehllo Plus is sold and billed by Google Play or the Apple App Store. We never see, receive or store your card number, your billing address or anything else you give the store to pay with. The store tells us only that a purchase exists and what state it is in.

What we keep about a subscription:

• Which store, and an identifier from it for the purchase, so we can ask that store whether the subscription is still live and can recognise the same purchase again.
• What was bought and its state: the plan, whether it renews, and the dates it runs between.
• An identifier we generate for your ehllo account, which we hand to the store at purchase so a notification from it can be matched back to you. It is specific to ehllo and is not your email address.
• Messages from the store about renewals, cancellations, refunds and payment problems, kept so that the same message arriving twice cannot be applied twice.

We also keep a record of AI usage so we can charge credits correctly and see what the product costs to run: which feature was used, when, how long a recording was, how many tokens a model used, and whether it succeeded. That record holds no part of what you said, wrote or were told.

This information is kept while your account exists and for as long as we are required to keep records of a transaction. Deleting your account removes it along with everything else, which does not itself cancel a subscription: that is cancelled in the store that sold it.

Reports and blocks

If you report someone, we store who made it, who it is about, the reason you chose and anything you wrote, and email it to our team so we can act on it within 24 hours. The person you report is never told who reported them.

If you block someone, we store only that you blocked them, so we can hide them from you. They are not told. A block ends when you unblock them, or when either account is permanently deleted. If an account is deleted, the reports it made or received are kept without the account linked to them, so a pattern of abuse can still be seen.

Data sharing

We share data only with the service providers needed to run ehllo, under agreements that restrict them to providing that service, and with other ehllo users only to the extent you choose to share it — for example, publishing your card or sending someone a shared meeting summary. We do not share your connected Google or Microsoft data with any third party outside of what's described here.

• Supabase — our database, sign-in and file storage.
• Vercel — hosts the website and the servers the app talks to; it runs in the United States.
• AI providers — named under AI processing above, and Google Cloud, which carries live voice conversations in the United States.
• Apple and Google speech recognition — on your phone, as described under AI processing.
• Resend — sends ehllo's emails (sign-in links, meeting and event emails).
• Expo, Apple and Google push notifications — deliver notifications to your phone. A notification can contain a name and a short line, for example who connected with you or the title of a follow-up that is due.
• Apple Wallet and Google Wallet — if you add your card to a wallet, the pass holds your name, role, company and card link, and Google Wallet receives them to create it.
• Google Play and the Apple App Store — for subscriptions, as described above.

We also use an error-reporting service (Sentry), in the app and on the website. It receives technical details when something fails — the device model, OS version and, if you are signed in, your account ID — and timing measurements for a sample of requests (one in ten), and in the app it counts sessions, so we can find and fix problems. It does not record your screen. No content you record or write is sent to it.

Who can see what

The short version of everything above, by kind of data. “ehllo's systems” means our servers doing the work you asked for: storing, matching, reminding, transcribing and summarising. “AI providers” means the processors named under AI processing, and only for the request they are handling.

ehllo's servers can read your data in order to do the work above. What keeps it private is who is allowed to ask for it: your sign-in, the per-account isolation and the agreements described in this policy, together with encryption in transit and at rest. It is not protected by encryption keys that never leave your device, and we do not describe it that way anywhere.

How we protect your data

We use technical and organizational security measures to protect your data, including the calendar, profile and file data accessed through a connected Google or Microsoft account:

• Encryption in transit. All traffic between your device, ehllo, and the Google and Microsoft APIs is encrypted with TLS (HTTPS). ehllo is not served over unencrypted connections.
• Encryption at rest. Your data is stored in a managed PostgreSQL database (Supabase) with AES-256 disk encryption.
• Extra protection for connected-account credentials. The OAuth access and refresh tokens that let ehllo call Google and Microsoft on your behalf are additionally encrypted at rest in an isolated secrets store and are never exposed through our public API. They can only be decrypted by a server process acting for the account that owns them.
• Per-account isolation. Contact, encounter, calendar and follow-up records are protected by database row-level security, so one account cannot read another account's data.
• Restricted internal access. Access to production systems and data is limited to the ehllo personnel who need it to operate the service, over authenticated connections.
• Least-privilege scopes. ehllo requests only the Google and Microsoft permissions described above; calendar writes and Drive/OneDrive access are limited to events and files ehllo itself creates.

If we become aware of a security incident affecting your data, we will notify affected users and the relevant authorities as required by applicable law.

Retention and deletion

We keep your data for as long as your account is active. You can delete individual contacts and encounters at any time from Settings, and you can delete your entire account from Settings at any time. To request a copy of your data, contact us at the address below.

• Disconnecting a connected account immediately deletes the stored access and refresh tokens and revokes ehllo's access with Google, so ehllo no longer appears among the apps with access to your account.
• Recordings and shared meetings — a recording kept in ehllo's cloud expires after 3 days, and a daily job deletes expired files from our storage. A recording you keep only on your device is uploaded briefly to be transcribed and that copy is deleted once the transcript is made. The guest link to a meeting you share lasts 30 days from when you last saved it while shared, and you can stop sharing at any time. Recordings you send to your own Google Drive or OneDrive are yours, kept by that service, and are not deleted by ehllo.
• Things you delete — a note, memory or person you delete is hidden from you and from everything ehllo does straight away, and kept in our database, marked deleted, until your account is deleted, so it can be restored if deleted by mistake.
• Deleting your ehllo account hides it straight away: your cards stop opening and the people you have met see that you have left. Everything is kept for 30 days so that signing in again can bring it back, and then permanently deleted from our live systems: your cards, contacts, encounters, notes, saved memories, recordings, follow-ups, uploaded images and connected-account tokens, along with ehllo's Google access, the Sign in with Apple authorisation, which we revoke with Apple as soon as you ask, and your sign-in. We email you when you delete your account and the day before it is erased. People you have connected with keep their own record of having met you. Residual copies in encrypted backups age out within 30 days of that deletion on our standard backup rotation, after which the data cannot be recovered. You can also read how to delete your account without the app.

Where your data is processed

ehllo is operated from the UK, and some of the service providers that help us run it — hosting, database, AI processing and transactional email — process data on servers outside the UK and European Economic Area, mainly in the United States (our hosting, and live voice conversations, which are always processed there). Where data is transferred internationally, we rely on appropriate safeguards, such as the UK International Data Transfer Agreement, the EU Standard Contractual Clauses, or transfers to a country the UK recognises as providing adequate protection.

Your rights

EHLLO LTD processes your data on these bases:

• Our contract with you — your account, cards, people, meetings, notes, follow-ups, events, reminders, the AI features you use, and subscriptions.
• Your consent — connecting Google, Microsoft, Granola or your phone's calendar or contacts, turning on calendar context in AI, recording, and notifications. You can withdraw it at any time from Settings or your phone's settings, and the rest of ehllo keeps working.
• Legitimate interests — keeping ehllo secure and working (error reports, abuse reports and blocks), and holding the details of people our users meet, as described above.
• Legal obligation — keeping records of transactions for as long as the law requires.

ehllo does not make decisions about you by automated means that have legal or similarly significant effects. Its AI drafts and suggests; you decide.

Under UK data protection law you have the right to access, correct, delete, restrict or object to our processing of your personal data, and to receive a copy of it in a portable format. You can delete your data yourself from Settings at any time, or exercise any of these rights by contacting us at the address below.

If you believe we have not handled your data properly, you can complain to the UK Information Commissioner's Office (ICO) at ico.org.uk. We would appreciate the chance to put it right first.

Cookies and storage

ehllo's website uses only the cookies it needs to keep you signed in and secure, and stores a few preferences in your browser. We do not use advertising or analytics cookies. On the home page and the sign-in page we load Google's sign-in script so you can sign in with Google; Google may set its own cookies when it loads, under Google's privacy policy.

Children

ehllo is not intended for anyone under 18, and we do not knowingly collect data from children. If you believe a child has created an account, tell us at product@ehllo.io and we will delete the account and its data.

Contact us

The data controller is EHLLO LTD, a company registered in England and Wales, Company No. 17434728, whose registered office is 76 Gideon Road, London, SW11 5UT. Questions about this policy or your data can be sent to product@ehllo.io.