Roam

Privacy policy

Where Roam runs

Roam runs on your Mac. When she joins a call, she joins from your computer as her own participant. The record she keeps of your calls and her memory stay on your Mac; we never keep them.

What we keep

Your account: your email address and the name you give. Your team: its name and its members, and the Discord servers it added Roam to.

The keys that sign your Roam app in, stored only as a hash, until you sign Roam out.

How much of Roam's voice you used each day (counts and cost, never what was said), to keep each account within its daily limit.

If you join the waitlist: your email address.

What passes through our server and is not kept

Roam's voice: the audio she speaks and hears goes from your Mac through our server to OpenAI's voice model and back. We pass it on as it is and store none of it.

In Discord, Discord's rules need a bot, which runs on our server: the voice channel's audio goes through it to your Mac and back, and none of it is stored.

Google Calendar and Google Meet

Connecting a Google account is optional. You start it in Roam's Connectors, and Google's own page then asks you to allow each permission. This section says exactly what Roam does with each one.

What Roam reads. Your Google account's email address, to show which account is connected. The list of your calendars, with their names and colours, so her calendar view matches Google Calendar and you can choose which calendars she shows. The events on those calendars that her calendar view shows (a day ago to two weeks ahead) or that you ask her about (title, time, place, notes, guests, reminders and meeting link), so she can show your week, tell you what's next, and find the link of the meeting you ask her to join. When you make a booking link, the busy times on the calendars you chose for it.

What Roam changes, and only when you ask. She makes, moves and deletes events when you ask her to, by voice or in the app, and adds a Google Meet link to an event when you ask for one. When a guest books a time on your booking link, she puts that meeting on the calendar you chose for the link, with the guest invited. She makes a new Google Meet room when you ask her to start a call, and can manage only the rooms she made. She never changes your calendars' sharing or settings.

Where it is kept. Google's sign-in tokens are kept in your Mac's Keychain. Your events are read straight from Google on your Mac, held in Roam's memory while she runs, and read again from Google when needed; they do not go through our server and we do not keep a copy of them. Her record on your Mac of what you asked and what she answered can include what she said about an event, and stays on your Mac. For a booking link, your Mac sends our server only your busy times (start and end, never a title or a guest), so the booking page can offer free times, and takes back the bookings guests make; these are kept while the link exists, and deleting the link deletes them.

Who else sees it. When you ask Roam about your calendar, the events she reads to answer go to OpenAI's models through our server, as part of that answer, and are not kept by us (see "Who processes it" below). If you ask her to hand work that involves an event to one of your own agents, such as Claude, she passes it the details you asked about. A guest on your booking link sees only which times are free. Google data is shared with no one else. It is never sold, never used for advertising, never used to decide credit or lending, and never used to train or improve AI models, ours or anyone's. No person at Roam reads your Google data, unless you ask us to for support, or it is needed for security or required by law.

Roam'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. The use of information received from Google Workspace APIs will adhere to the Google Workspace user data and developer policy, including the Limited Use requirements.

Removing it. Remove the account in Roam's Connectors: she deletes its sign-in token from your Keychain (unless you also connected that account's Gmail) and stops reading it. To withdraw Roam's access at Google as well, remove Roam at myaccount.google.com/permissions. Delete a booking link to delete the busy times and bookings our server keeps for it, or email support@agentinthecall.com and we delete them within 30 days. Step by step: Using Roam with Google Calendar and Meet.

Who processes it

OpenAI (through its API) hears what Roam is asked and makes her voice and answers; what she is asked and what she reads to answer (an event, for instance) passes through our server to OpenAI and back, and we keep none of it. OpenAI does not train on API data by default, and may keep it for up to 30 days to monitor abuse.

Anthropic: work you ask Roam for goes to the agents on your own computer, such as Claude, which send it to Anthropic under your own Claude account and its terms.

Google Meet, Zoom and Discord carry the calls Roam joins, under their own terms. Sign-in emails are sent through Resend.

In the meeting

Roam appears in the meeting as her own participant, named Roam, and the host admits her as anyone else. Once in, she plays one short sound and posts in the call's chat that she is an AI assistant, what wakes her and how to send her away. Anyone can ask her to leave, and the host can remove her.

Removing Zoom

We hold no Zoom account, token or data of yours: Roam joins Zoom from your Mac with a join our server signs for that one meeting. To remove our app, in Zoom go to marketplace.zoom.us, Manage, Added Apps, and click Remove.

Your rights

You can ask for a copy of your data, for it to be corrected, or for it to be deleted, by email to support@agentinthecall.com. We answer within 30 days. What is on your Mac, you can delete there.

Children

Roam is not for anyone under 16, and we do not knowingly collect their data.

Contact

Roam is made by Lorecraft LLC, d/b/a Roam. Email support@agentinthecall.com.