Privacy Policy

Who we are

Jarvey ("Jarvey", "we", "us") is the AI agent that joins your meeting, answers out loud when you call its name, and writes the recap afterwards. It runs at jarvey.io and is operated by Comind AI, company registration number 1223189, registered at Office 105, Al Ghanin 3 Building, Al Muraqabat, Dubai, UAE.

We are the data controller for your account and for how we run the service. We are a data processor for the meeting content you and your colleagues create inside it.

If your company is the controller of what is said in your meetings, our Data Processing Agreement is the Article 28 contract for it, and it is already in force. There is nothing to sign.

Your use of Jarvey is also governed by our Terms of Service.

This policy covers Jarvey. It does not cover the services you reach through Jarvey: Google Meet, Zoom, Microsoft Teams, your board, your own AI provider. Those are governed by their own terms, and we name each of them below rather than leave them implied.

What happens during a call

This is the part worth reading in full, because it is the part that is unusual.

1. You paste a Google Meet, Zoom or Microsoft Teams link. Jarvey joins that call as a visible participant with a name, and the call announces it to the room the same way it announces a person.
2. While the call runs, the audio of the people speaking is streamed to us in real time. It is never written to a file or a bucket on our side.
3. That audio is processed by OpenAI's realtime and transcription models, which is what lets Jarvey hear its name, understand the question, and answer in a voice. Soniox transcribes the same audio a second time so we can compare the two. TypeSafe reads lines of the transcript to tell whether one was said to Jarvey.
4. What was said is written to our database as text, one row per utterance, with the speaker's display name from the call.
5. When the call ends, OpenAI reads that transcript and writes the recap, and models reached through OpenRouter write the short list of decisions, owners and open questions that becomes your workspace memory.
6. If you connected a board, Jarvey may write a card or a page to it, using the access you granted.

We do not keep the audio. We do keep the transcript, because the recap, the memory and the search across past calls are made of it. Deleting the workspace deletes both, as described below.

What we store

• Account: your email address, the display name you choose, when you signed in, and, if you sign in with Google, nothing beyond the email, name and picture on your Google profile.
• Workspace: its name, its settings, its timezone, and the written memory Jarvey keeps for it.
• Calls: the title, the times, the Google Meet, Zoom or Microsoft Teams link you pasted, who took a seat and when, and the recap.
• Calendar: if you connect Google Calendar, a copy of the events from the past week and the next four weeks in the calendars you choose: the title, the times, whether it repeats, the call link, and the names and email addresses of the guests. We replace the copy every few minutes and delete it when you disconnect.
• Transcripts: the text of what was said in a call, with speaker names.
• Memory: the short factual lines Jarvey keeps between calls (a decision, an owner, an open question).
• Connections: the access tokens for the board or workspace you connected, and the name and URL of that board.
• Billing: your Stripe customer and subscription identifiers. Card numbers never reach us; Stripe holds them.
• Operational records: model usage and cost per call, timing metrics, sign-in codes, and invitation tokens.

We do not ask for, and have no field for, a home address, a date of birth, a government identifier, or a payment card.

What we do not do

We do not train any model on your calls. We do not sell your data. No part of Jarvey is funded by making your meetings legible to anybody but you.

Nothing from inside a call ever reaches an advertising network: not the audio, not the transcript, not the memory, not a task Jarvey wrote. While ad measurement is on, Google and Meta learn that a visit to one of our public pages led to a signup, to a finished setup, and to a paid subscription; Meta is also handed a one-way hash of the email address on the account, never the address itself, so that it can tell those apart in its own records. That is the whole of it. Where you are visiting from decides whether it is on until you turn it off or off until you allow it, and "Cookies and analytics" below says which and how to change it.

Where it runs

On Railway, in the United States. If you are outside the US, your data is transferred there. For transfers out of the EEA or the UK we rely on the Standard Contractual Clauses.

Content in our database is stored on encrypted disks and reached only over TLS. To be exact about the limit of that: Jarvey is a hosted service that runs the AI for you, so it is not end-to-end encrypted. The running application must be able to read a transcript in order to write a recap from it. We do not claim otherwise.

Our application logs are written with a redaction rule that replaces anything named like speech (a transcript, an utterance, a prompt, audio) before it is written, so meeting content does not reach our log search. The same rule replaces tokens and keys.

Who else processes your data

Each of these sees one specific thing. Nobody on this list sees everything.

We may add or change a provider. When we do, this table changes with it.

Google user data

When you sign in with Google we request openid email profile. When you ask Jarvey to create a meeting link for you, we request meetings.space.created, which lets us create a Meet space and read the link for it. We store the resulting token so you do not have to grant it again, and you can disconnect it at any time.

When you connect Google Calendar we request calendar.calendarlist.readonly and calendar.events.readonly. The first lets us show the list of your calendars so you choose which ones Jarvey reads. The second lets us read the events in those calendars, so we can show your week and send Jarvey to the calls you add it to. Both are read-only: Jarvey never creates, changes or deletes an event. Your colleagues in a workspace see the title and time of a call only after someone adds Jarvey to it. Disconnecting deletes the token and the copy of your events.

Jarvey's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to train models, and we do not transfer it except as needed to provide the feature you asked for, with your consent, or where the law requires it.

Recording, and the consent that is yours to get

Jarvey processes what people say in a meeting. In many places (parts of the United States, most of Europe) that requires the consent of the people in the room, and the obligation to get it is yours, not ours.

Jarvey is built so that this is possible rather than hidden: it joins as a named participant, the meeting host must admit it, and everyone can see it in the participant list for the whole call. Do not bring Jarvey into a call where the people in it have not been told.

Cookies and analytics

We use four strictly necessary cookies. One keeps you signed in for your session. Two support Google sign-in by storing the sign-in state and the page to return you to. One stores the workspace you are connecting to the Claude assistant. The sign-in and connection cookies expire after ten minutes and are deleted when you return. All four are set by our server and cannot be read by scripts. We do not use them for analytics or advertising.

Anonymous visit counts increment one aggregate counter on our server when a public site or app document loads. This happens whether you allow, reject or ignore optional analytics. The request carries no cookie, analytics identifier, referrer, page address, query or body. The aggregate record stores only a five-minute time bucket and a number, not an IP address or user agent. Reloading counts again, so this measures visits rather than unique people.

Cookieless site measurement uses PostHog to count how our public pages are used: page views, how long a page stays open, how far down it you read, which sections you reached, which questions you opened, and clicks on links and on the buttons that open Jarvey, including a button's location, the site a link leads to, and campaign and referral information. It also times the page itself: how quickly it appeared, how much its layout moved while loading, and how long it took to respond to a press. It starts when a public page opens, whether you allow, reject or ignore optional analytics. It does not store analytics identifiers in cookies, local storage or session storage, link site events to your account, or record your screen. PostHog uses the request's IP address, browser user agent, hostname and a daily salt to calculate a temporary identifier on its servers. Visitor counts are approximate, and a returning visitor may count again on another day. URL query strings and fragments are removed from captured URL properties; campaign parameters may be recorded separately. Global Privacy Control and Do Not Track disable this PostHog collection.

In the United States site measurement is not cookieless. There we do not ask first (see Advertising measurement below), so the same measurement runs with PostHog's own identifier kept in this browser, in a first-party cookie and in local storage, and records a masked replay of the landing page. That identifier is the one optional product analytics uses, so a visit to our public pages is linked to the sign-in and the setup that follow it in this browser, and to your account once you sign in. Turning product analytics off under Your Privacy Choices stops it, removes that identifier, and returns this browser to cookieless site measurement. Global Privacy Control and Do Not Track disable it as they disable the rest.

Optional product analytics counts app page views and browser interactions for us. Outside the United States it runs only if you allow it; in the United States it runs until you turn it off. In the app, the SDK loads in opted-out mode so it can apply a choice made later on the page; until you allow analytics it sends no analytics events or session recordings. Outside the United States, ignoring the privacy choices leaves optional product analytics off. If you allow it, PostHog keeps its own identifier in this browser, in a first-party cookie and in local storage, so that one visit is not counted as several. We record ordinary navigation inside the app to find broken or confusing flows. Inputs and app text are masked, network contents are not recorded, and calls, invitation pages and the transcript studio are never recorded. Global Privacy Control and Do Not Track are an answer in themselves: where either is set we do not ask and do not collect optional product analytics.

Setup progress is measured separately from optional product analytics. The setup draft stored in your browser includes a random attempt identifier, renewed after seven days. We send the attempt identifier, flow version and screen reached to PostHog so a reload or sign-in redirect does not split the same setup into separate attempts. With them we send which advertisement or link the setup was opened from: the source and campaign labels on that link, and whether you came through our home page. We do not send the advertising network's click identifier or the rest of the address. These progress events do not include your questionnaire answers or screen recordings, and the measurement SDK does not persist its own browser identifier. After you sign in, our server links successful saves and completed setup to your account and workspace. This is attempt-level measurement, not anonymous cookieless site counting. Global Privacy Control and Do Not Track suppress these attempt events. Renewal limits reuse of the identifier; it does not delete previously collected events.

You can change your answer for this browser below. We keep that choice in local storage so you do not have to repeat it, and never send the choice to PostHog. Turning optional product analytics off stops that collection and recording in the app, and clears the identifiers PostHog kept in this browser when the app applies the change. Basic cookieless site measurement, setup progress and aggregate visit counts do not depend on this choice; in the United States, turning it off is what makes site measurement cookieless.

The browser choice does not disable server-side records and product events about completed actions such as account creation, calls and billing. These are separate from optional browser tracking.

Advertising measurement tells Google and Meta which of their advertisements led to a visit or a signup. Two tags do it, the Google Ads tag and the Meta pixel, and both are measurement rather than audience building. Google's runs in Basic Consent Mode with personalized advertising signals off and ad-data redaction on. Meta's is loaded with its automatic collection switched off and Limited Data Use on, so it is not given the presses, form fields or page contents it would otherwise gather and match you by. Neither tag runs on a call page, an invitation or inside the product: they run on our public pages, the sign-in and the start of setup, and nowhere else.

Whether it starts is decided by where you are visiting from, and our server decides it. Before it answers, our server looks up the country of the network address your request arrives with, against a database file it holds itself; nobody outside it is asked, and we keep no record of the lookup. The page is the same for everybody, and only a small, uncacheable answer about which arrangement applies differs.

• In the United States ad measurement and product analytics are on when a public page opens, and you can turn it off at any time under Your Privacy Choices. You get notice and a way out rather than a question first, which is the arrangement the state privacy laws that reach us provide for.
• Everywhere else, including the EEA, the United Kingdom and Switzerland, nothing about advertising runs until you allow it. Our privacy dialog asks you to allow all, reject all, or choose optional product analytics and ad measurement separately, and the page waits for your answer: before it no advertising request is made and no advertising cookie is written. Rejecting costs you nothing, and the page then works exactly as it would have.
• If our server cannot tell where you are, you get the stricter arrangement.
• Global Privacy Control and Do Not Track are an answer in themselves: where either is set, ad measurement is off and nothing on the site can turn it on.

While ad measurement is on, each tag keeps first-party advertising identifiers in this browser — Google's begin with _gcl_, Meta's are _fbp and _fbc — and we keep one cookie of our own, jarvey_attribution, for at most 90 days: the advertisement's click identifier and the campaign labels from the web address you arrived on, so that a signup can be credited to the advertisement that led to it after a sign-in has taken you away from that address. Nothing else from that address is copied, and it is never anything you typed. That cookie is read only by our own server, which hands the click identifier to the network it came from together with the fact of the signup. What the networks then learn is that a browser opened one of our public pages, that it created an account, that it finished setting up, and that it paid for a subscription, with the amount paid; with it go the identifiers above, the address of the page, your browser's user agent and its network address. For the payment, which Stripe confirms to our server without your browser, we keep Meta's two identifiers and that address and user agent with the checkout you opened, for two days at most, and remove them as soon as the payment has been reported. Nothing from inside the product is ever part of it. Turning ad measurement off stops both tags, tells them about the refusal, and removes those identifiers and our cookie from this browser. You can change either choice under Your Privacy Choices at any time, including the advertising one.

We rely on your consent for optional product analytics and session replay, balanced by data minimisation, short replay retention and the controls above. You may take that consent back at any time by turning optional product analytics off or writing to us; doing so does not undo what was collected while it was allowed.

Advertising choices in the United States

This section is the one that applies if you are visiting from the United States.

What goes to an advertising partner. While ad measurement is on, Google Ads and Meta each learn that a browser opened a page on jarvey.io, created an account, finished setting up, or paid for a subscription and how much, along with the click identifier their own advertisement added to the address you arrived with, the address of the page, your browser's user agent and its network address. Meta additionally receives a one-way (SHA-256) hash of the email address on the account and of the account's id, never the address itself, so that it can recognise the account in its own records and credit the advertisement; Google Ads receives no such hash. Each keeps a first-party cookie in this browser so that a signup can be attributed to the click that preceded it. Nothing from inside the product is sent to either of them: not your meetings, your transcripts, your recaps, your memory, your calendar, or anything about your account beyond that hash. We do not sell personal information, and we do not share it for cross-context behavioural advertising.

How to opt out. Use Your Privacy Choices. One press, applied to this browser and kept in local storage so you do not have to repeat it: it stops both tags and deletes what they wrote here. A browser that sends Global Privacy Control or Do Not Track is already opted out and we never ask it again. You can also write to privacy@jarvey.io if you would rather we did it, or to exercise a right to know, delete or correct, as described under "Your rights".

We do not charge you for it. Turning ad measurement off changes nothing else. Jarvey works the same, costs the same and keeps every feature.

How long we keep it

We keep your account, calls, transcripts and memory for as long as your workspace exists, because a recap you cannot look up later is not worth writing.

The owner of a workspace can delete it from Settings. Deleting a workspace deletes its calls, its transcripts, its memory, its connections and its invitations from our active systems, in one step and without a further request. Backups roll off on their own schedule, and billing records are kept for as long as tax law requires.

You can delete your whole account from Settings too. That deletes every workspace you own, along with everything in them, and then your account itself. A workspace you were only invited to belongs to whoever owns it and stays. For an export, write to privacy@jarvey.io.

Your rights

Depending on where you live you may ask us to give you a copy of your data, correct it, delete it, restrict how we use it, or object to a use. You may also withdraw a consent you gave, without that affecting what was done before you withdrew it.

Deleting is a button rather than a request: Settings deletes your account and everything in the workspaces you own. For anything else, write to privacy@jarvey.io and we will answer within 30 days. If you are in the EEA or the UK you may also complain to your local data protection authority.

We do not sell personal information. While ad measurement is on, we tell Google and Meta that a visit led to a signup so they can report which advertisement worked; some laws describe that as sharing for cross-context behavioural advertising. Nothing from inside a call is ever part of it, and you can turn it off at any time under Your Privacy Choices. If you are in the United States, "Advertising choices in the United States" above is written for you.

Children

Jarvey is for work. You must be at least 16 years old to use it. We do not knowingly collect data from anyone younger, and we delete it if we learn we have.

Changes

We will change this page when the product changes. If a change matters to you (a new provider that sees your calls, a new use of your data), we will say so by email or in the app rather than only editing this page. The date at the top is the date of the last change.

Contact

Privacy questions and requests: privacy@jarvey.io. Anything else: support@jarvey.io. Security reports: security@jarvey.io. Please do not open a public issue for one.