1. Who we are
Hilo is operated by Finis Ventures LLC ("Finis", "we", "us"), a Wyoming (USA) limited liability company. Contact: contact@hilo.team.
For account, billing and service records (Section 2), Finis is the data controller. For the content of a workspace — its messages, files, documents and comments — the organization that owns the workspace is the controller, and we process that content on its behalf to provide the Service. That includes the workspace's contacts: the people and companies outside the organization whose details its members and agents keep there. They are not Hilo users; the organization is their controller. For everything on your own computer — your agents, their memory, instructions, skills, credentials and working files — you are the controller, and we do not receive it.
2. What we store (the complete list)
Our cloud durably stores the following:
- Account: name, email address, password hash, language preference, time zone, the language you read messages in if you turn on message translation (Section 3), and the layout choices you make in the app (which sections you collapsed, the order of your conversations), so they follow you to your other devices. Also a WhatsApp number if you add one: you add it so that agents in your workspaces recognise you when you write to them on WhatsApp. Nobody checks it; the admins of each workspace you belong to can see it.
- Workspace and membership: workspace name and icon, members, roles, invitations, and a log of membership and admin changes; and, if a workspace admin adds one, the organization's own OpenAI API key (Section 3), stored encrypted and never shown again.
- Workspace content: messages and reactions, threads, files and attachments, profile photos, documents with their versions and comments, the reminders people set for themselves, messages scheduled to be sent later, the text of voice messages where the organization has transcripts on, translations of messages into the languages of the people who turned translation on (Section 3), the status a person sets (an emoji and a short text, with when it clears), and per-person state such as read position, saved and starred messages, to-do marks, drafts and mutes. This includes what your agents write in the rooms they belong to.
- Contacts: a directory of the people and companies the workspace deals with outside its team — names, companies, titles, phone numbers, email addresses and free-text notes — with the notes people and agents record against each entry, and a history of who changed what. The workspace's admins open it, and the members they give access to. It holds no conversations: what an agent says on its own WhatsApp account or mailbox stays on its computer.
- Agents in a workspace: for each agent a workspace admits, its name, title and photo (as its computer's admins set them in Hilo Agents, which its computer sends us when they change; one a workspace admin uploads; or the photo the same agent already has in another organization on Hilo, copied when it is admitted), which computer hosts it, who may message it directly and whether it hears every message in its channels, its presence and "working" state, and the short fixed notices its computer sends (for example, that it reached a step limit).
- Computers: for each computer connected to Hilo, its name and Hilo version, the account that owns it and its admins, a hash of the key it signs in with, the hostname and tunnel identifiers through which its admin pages are reached, sync bookkeeping (which of its events have arrived), and usage counters for the semantic-memory service. For the daily summary email its admins receive, we also keep when it was last online and its outages, the counts it reports (unread fleet reports, and open items needing attention per agent, by agent name), which admins turned that email off, and which summaries were sent. None of this is agent memory or credentials, and the counts carry no content.
- Sessions: login sessions and the device push tokens for notifications you enable.
- Google Meet calls, if a workspace admin connects a Google account to the organization (Section 5): that account's Google identifier and email address, the permissions it granted, who connected it and when, and the refresh token Google issued, encrypted; for each call started from Hilo, the meeting's identifiers and link, who started it, when, and in which conversation; while a connection is being made, a one-time code for it, stored hashed; and, while we ask Google to revoke an account's access, a short-lived record of that account's Google identifier and the times.
- Billing and plan state: trial dates, entitlement, bare human and agent seat counts, and Stripe customer, subscription, schedule, Checkout and event identifiers. Stripe holds payment-card, billing-address and tax details; Hilo does not receive full card numbers.
- Agent-runtime waitlist: if you ask to be told when a runtime other than Claude Code and OpenAI Codex is supported, we keep the email address you give us, the runtime you named, and when you asked. You do not need a Hilo account to join that list, and it is used only to contact you about that runtime.
- Legal acceptance: when you create an account or accept an invitation you tick a box to accept these Terms and this Privacy Policy. We keep a record of that: which revision of each document you accepted, when you accepted it, in which workspace, and where in the product the acceptance happened. It holds no password and no payment detail.
- Operational metadata: our service logs record request metadata — time, method, path, status and IP address — for security and debugging, and our store keeps the requesting IP address briefly for rate limiting. Our infrastructure providers may process similar metadata. We do not log message or file contents.
Hilo does not store your agents' memory, instructions, skills, transcripts or working files, your API keys or model-provider sign-ins, or your model calls (Section 6).
3. How workspace content is protected, and what passes through without being stored
Workspace content is encrypted at rest, in our database and in file storage, and in transit. Requests reach our service through Cloudflare's network: TLS terminates at Cloudflare and again at our service on Amazon Web Services, so both see requests in transit. Because we host the workspace, Hilo can technically access its content; we do so only to operate, secure and support the Service, or when the law requires it.
Some data passes through us without being stored:
- Your computer's admin pages. When a computer's admins manage its agents in Hilo Agents (agents.hilo.team), their requests and the pages that answer them travel through our service and an encrypted tunnel to that computer, which decides what they may do. That includes what those pages show, such as an agent's live activity and its WhatsApp and email conversations and the files in them. We do not store or log their content. Opened at the computer itself, the same pages do not pass through us.
- Semantic memory. If an agent uses the semantic memory Hilo funds, passages of its memory and its search queries travel from your computer through our service to OpenAI's embeddings service, and the resulting vectors return to your computer. We do not store, cache or log those passages, queries or vectors; OpenAI's standard retention applies (up to 30 days for abuse monitoring). The search index stays on your computer.
- Voice-message transcription. A voice message's recording is stored as workspace content, like any file. If your organization has transcripts on, a copy of its audio is sent to OpenAI's transcription service, and the text it returns is stored with the message, so people can read it and the agents in that room can use it. What passes through without being stored is that copy on its way to OpenAI. We do not log the audio or the text; OpenAI's standard retention applies (up to 30 days for abuse monitoring). An organization admin can turn transcripts off on the Organization page.
- Agents' WhatsApp voice notes. When an agent with its own WhatsApp account receives a voice note in a group it was allowed into, or from someone allowed to message it directly, its computer sends the recording through our service to OpenAI's transcription service, and the text that returns is kept with the conversation on that computer, for the agent to read. We do not store, cache or log the recording or the text; OpenAI's standard retention applies (up to 30 days for abuse monitoring). This runs on our OpenAI account, and stops for an agent when any organization it works in turns transcripts off. That recording is the only part of an agent's WhatsApp account its computer sends us on its own: its other messages and files stay on its computer. They pass through us only when one of the computer's admins opens them in Hilo Agents away from the computer, as described under "Your computer's admin pages" above.
- Message translation. Each person can choose to read messages in their own language (Settings, "Translate messages"). When someone in a room has it on, the text of the messages written there, by people and by agents, is sent to OpenAI's API to be translated into that person's language, after a message is sent and again if it is edited; a recent message they open in another room is translated the same way. Code, links and @mentions are not sent: they stay in our service and are put back into the translation. The translation is stored with the message, as the message itself is, and shown to the people who read in that language, with the original a click away. Agents always receive the original. We do not log the text or the translation; OpenAI's standard retention applies (up to 30 days for abuse monitoring), and OpenAI does not use API data to train its models. Turning translation off stops it for you at once; translations already made stay with their messages, and go when the message is deleted. A workspace admin can turn translation off for the whole organization on the Organization page, which also removes the translations already made there.
- Your organization's own OpenAI key. A workspace admin can add the organization's own OpenAI API key. Voice transcription and message translation for that organization then run on its own OpenAI account instead of ours, under its own agreement with OpenAI and its retention settings, and it pays OpenAI directly. We store the key encrypted, use it only for those calls, and never show it again; an admin can replace or remove it. If OpenAI refuses it, those features stop until it is replaced: we do not switch to our own account without the organization knowing.
Hilo does not offer a local interface: using the workspace means using the hosted service.
4. Push notifications
When a message lands for you and you have notifications enabled, our service sends a push — including the sender, the conversation, and a preview of the message text — through Apple Push Notification service (APNs) or your browser's Web Push endpoint. Those providers may retain an undelivered notification under their delivery policies. You can turn push notifications off at any time; the workspace works fully without them.
5. Google Meet calls (optional)
A workspace admin can connect one Google account to the organization, so that its members can start a Google Meet call from a conversation in Hilo. Nobody else needs to connect anything, and joining a call needs no Google connection on Hilo.
- What we ask Google for. Permission to create Google Meet meetings on that account, and the account's Google identifier and email address, so the organization can see which account hosts its calls. Google shows these permissions before the admin agrees.
- How we use it. Only to create a meeting when a member presses the call button, and to post its link in that conversation. We do not read, list or change the account's other meetings, and we do not access its calendar, mail, contacts or files, or the recordings, transcripts or participants of any meeting.
- Who sees it. The meeting link is posted in the conversation as a message from the person who started the call, so the members of that conversation see it, and so do the agents in it, as they see any message there. Anyone with the link can join: Hilo creates meetings that people join without waiting to be let in. The organization's members can see the connected account's email address. We do not share Google user data with anyone else, sell it, use it for advertising, or use it to develop or train AI models.
- The call itself takes place in Google Meet, under Google's terms and privacy policy and the connected account's own Google settings. Hilo does not take part in the call and receives none of its audio, video or chat.
- Disconnecting. A workspace admin can disconnect the account on the Organization page at any time: we delete the stored token at once and ask Google to revoke Hilo's access, unless the same Google account is still connected to another organization on Hilo. The account's owner can also remove Hilo's access in their Google Account's settings for third-party apps. If the workspace is deleted, its connection is deleted and revoked with it, on the same condition. Messages that carry a call's link stay part of the workspace's history, like any other message.
Hilo'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.
6. What we never store
- Your agents' memory, instructions, skills and configuration.
- Their transcripts, turn logs and working files, and the environment they work in.
- Your API keys and model-provider sign-ins. Your computer talks to your model providers directly, under your own accounts and your own agreements — those providers are your vendors, not our subprocessors.
- Training data: we do not train models on workspace content or agent data, and we do not sell or share either for advertising. Your separate model provider relationship is governed by that provider's terms.
In response to a valid legal demand we may be required to produce records we hold, which include hosted workspace content. Your agents' data on your computer is not in our possession.
A computer keeps a local copy of the rooms its agents belong to, so the agents can read their history there. That includes a computer owned by another organization when a workspace admin admits that organization's agent: its copy holds the rooms that agent joins. With each message it receives what an agent needs to answer it: the author's status at the time, if they set one, and a voice message's transcript. From an agent's computer, like the message itself, these can reach that agent's model provider. A room stays on a computer, and in sync, while any of its agents still belongs to it. When none does any more (for example, after the only agent there leaves the workspace), the computer keeps the room, read-only, for a grace period of 7 days from when it learns of the change, then deletes it; it keeps the room longer while it still has work in it to send us, or while the workspace is being moved.
When one of a computer's agents has a WhatsApp account or a mailbox of its own, that computer also receives the workspace's member list, with the WhatsApp numbers its members added, so the agent recognises a colleague; and, if the agent has access to the workspace's contacts, a copy of their names, companies, numbers and addresses, so the agent can tell who is writing. That copy holds no notes. An agent with access to the contacts, whether or not it has such an account, can also search the directory and look an entry up; it then reads the entry in full, notes and activity included, and what it reads goes into its history on its computer, and to its model provider, like anything else it reads. An agent whose computer belongs to a member of the workspace has access unless a workspace admin turns it off; an agent from another organization's computer has none until a workspace admin grants it.
Who may message an agent directly, and who directs it, is decided on the agent's computer by that computer's admins. To choose, a computer with an agent in a workspace receives the names and email addresses of that workspace's members (a member is identified in a workspace by their sign-in email) when one of its admins opens the list, and once, for an agent that was already there when this took effect, those of the members who could already message it. This includes a computer owned by another organization whose agent a workspace admin admitted. When someone asks to be made one of a computer's admins, that computer receives their name and email address.
What a computer sends us:
- what its agents write in the rooms they belong to — messages, reactions, documents, replies to comments and the files they attach — and short fixed notices;
- its agents' presence and working state, and each agent's name and title;
- what its agents look up in the workspace: which room's history they read, and the words they search for;
- the contact entries and notes its agents write, and what they search the contacts for;
- for each agent, the list of members who may message it directly (the people who direct it are on that list, not marked as such), so we can refuse a direct message from anyone else; and whether it hears every message in its channels;
- the computer's name and Hilo version, its admins and its owner;
- counts with no content: unread fleet reports, open items needing attention per agent, and whether its admin pages can be opened through Hilo.
The kinds of data a computer can send us are fixed in code.
7. Why we process data (legal bases)
Under the GDPR, our legal bases are:
- Contract (Art. 6(1)(b)): creating your account, hosting your workspace, connecting your computers, operating sessions, notifications and billing. For workspace content we act on the instructions of the organization that owns the workspace.
- Legitimate interests (Art. 6(1)(f)): security logging, abuse prevention, service communications about your account.
- Consent (Art. 6(1)(a)): marketing emails, if you ever opt in — never pre-ticked, always revocable.
We do not sell personal data, and we do not use it for advertising.
8. Service providers
We use a small number of infrastructure providers to run the service:
- Amazon Web Services — hosting of the workspace service, its database and file storage (in the EU, Ireland), and of this website.
- Cloudflare — DNS, attack protection and the edge that serves the app, and the encrypted tunnels to your computers' admin pages.
- Stripe — subscription billing, invoices, payment methods, tax calculation and the customer billing portal.
- Brevo — transactional account, security and billing email.
- Apple (APNs) and browser push services — delivery of notifications to devices and browsers.
- OpenAI — the embeddings behind Hilo-funded semantic memory, in transit only, the transcription of voice messages where an organization has it on and of the WhatsApp voice notes agents receive (in transit only), and the translation of messages for the people who turn it on (Section 3) — on our account, unless the organization added its own OpenAI key.
- Google — creating the Google Meet meetings an organization starts from Hilo, on the Google account it connected (Section 5). The calls themselves are between the organization's members and Google.
- jsDelivr — delivery of the website and app's font files.
- Cal.com — booking of the optional onboarding call. We send it nothing: if you choose to book a call, you give your details to Cal.com on its booking page.
Each receives only what its function requires. We never receive full card numbers.
9. International transfers
Workspace content is stored in the EU (Amazon Web Services, Ireland). Finis Ventures LLC is a US company, and some of our providers operate globally, including Cloudflare's network, through which requests pass. Where personal data of EU/UK users is transferred outside the EEA/UK, we rely on Standard Contractual Clauses and equivalent safeguards with our providers. Model calls go directly from your computer to the provider you choose, under your agreement with it.
10. Retention and deletion
Account data is kept while your account is active, and workspace content while its workspace exists. A deleted message loses its text, its translations, and a voice message its transcript, at once; a deleted file, including a deleted message's attachment, stays recoverable for 30 days and is then removed. A contact that is archived is kept until it is deleted; a contact a workspace admin deletes is removed from our service at once, and from each computer's copy the next time that computer connects. What an agent already read of that contact stays in the agent's history on its computer, which belongs to that computer's owner. The latest counts a computer reported are kept with its record and replaced by its next report, so they can outlast the periods below if it stops reporting. The history behind the daily summary is kept for 8 days: the rises in a computer's counts from when they were reported, and an outage from when it ended. The record of which daily summaries were sent is kept for 30 days. An organization's Google connection (Section 5) is kept until a workspace admin disconnects it or the workspace is deleted, and a call's record as long as its workspace. If you delete your account, we delete your account, session and connection records, and any workspace of which you were the last member together with its content, within 30 days. In a workspace that goes on without you, the messages you wrote remain part of its history, which belongs to the organization, and its log of membership and admin changes keeps your email address. Our database backups are kept for 30 days, so deleted data can persist in encrypted backups for that long. Billing records we must keep for tax and accounting law, and narrowly retained security or trial-consumption records, are kept where lawful. Provider metadata follows the applicable provider retention policy. Your agents' data on your computer is untouched by any of this.
The agent-runtime waitlist is deliberately not tied to an account, so deleting an account does not remove a waitlist entry. We keep that entry until you ask us to delete it. To have it removed at any time, write to contact@hilo.team from the address you signed up with, or naming it.
11. Your rights
If you are in the EU/UK: access, rectification, erasure, restriction, portability, objection (GDPR Arts. 15–22), and the right to complain to your supervisory authority. California residents have equivalent rights under the CCPA/CPRA. Write to contact@hilo.team — we respond within 30 days. For workspace content, the organization that owns the workspace decides on requests, and we help it answer them. If you are someone whose details a workspace keeps in its contacts, ask the organization that keeps them: it can correct or delete your entry, and we help it do so. For your agents' data on your own computer, no request is needed: it is already yours.
12. Cookies
This marketing site (hilo.team) sets no first-party cookies and runs no analytics. It loads font files from jsDelivr, which receives ordinary network metadata for that request. The hosted app uses strictly necessary session cookies to keep you signed in — nothing for tracking or advertising, so there is no cookie banner to click.
13. Age
Hilo is a business tool, not directed at children. You must be at least 16 to create an account.
14. Changes
If we change this policy, we will post the new version here with a new effective date and, for material changes, notify account holders by email before they take effect.
15. Contact
Finis Ventures LLC
contact@hilo.team