Privacy Policy
Hybraen is an AI that takes part in a team’s meeting: it listens, follows the shared canvas, keeps notes and remembers decisions. That only works with people’s words, drawings and names, so this page says plainly what we collect, who helps us process it, how long we keep it and what you can ask us to do. It covers hybraen.com, the Hybraen app (the shared canvas and the AI in the room) and “Try Hybraen Now”.
The short version
- Hybraen only listens to people who have agreed on the agreement screen, and you can withdraw at any time.
- Speech is turned into text and the audio is not kept. We do not make voiceprints or speaker profiles.
- Hybraen does not receive camera video. Only the other people in the room see it.
- We do not sell personal information and we do not use it for advertising.
- We do not use your meetings to train AI models. There is an optional box about this on the agreement screen; see “Improving Hybraen” below.
- Hybraen’s AI features, speech-to-text included, use Google’s Gemini models through Google’s paid Gemini API. See “AI features: what is sent to whom” below.
- A team’s sessions are kept for the team, and we delete them when the team asks.
What we collect on hybraen.com
When you request early access or an access code we collect your name, work email and your company or role, and, if you tell us, what you would use Hybraen for. We use it to contact you and to understand who wants to use Hybraen. It is kept in a Google Sheet and, where set up, in our database.
The website does not use advertising or tracking cookies. Like any website, our hosting provider sees technical data such as your IP address and browser when a page is requested. If you use “Sign in with Google”, Google’s own script runs on the page and Google may set its own cookies.
Try Hybraen Now (access code and Google sign-in)
To try Hybraen you enter an access code and sign in with Google. From your Google account we receive only your email address, your name and your Google account ID. We do not receive your Google password, contacts, files or any other Google data. We store those three items, which access code was used and when, so we know who has tried Hybraen. To slow down people who guess codes we also keep a scrambled (hashed) form of the network address a code was tried from, not the address itself.
In the Hybraen app (a session)
When your team uses Hybraen in a room, these are processed and kept for that team:
- What you say: turned into text, with the name you entered next to each line. The audio is processed to produce the text and is not stored as a recording.
- What you write and draw on the canvas, including handwriting that Hybraen reads, and pictures of the board. When someone shares a screen in the room, Hybraen also reads pictures of that screen while capture is on; the pictures are not kept, only a few sentences about what they show.
- What Hybraen makes: notes, decisions with the reasons and alternatives behind them, action items, meeting minutes, and the questions you ask Hybraen and its answers, including web research it does for you.
- Usage counts are kept for about 13 months; the daily identifiers used to count active people are removed after 90 days.
- Agreement records: your name, when you agreed or withdrew, which wording you agreed to and your choice on the optional box. When you join a meeting signed in, the record also holds your account’s email address, so the meeting can show that you attended.
- Follow-up mail. After a meeting, the host and the people who joined it can see the e-mail addresses of everyone who joined, including guests, so they can send a follow-up from their own mail app. Hybraen sends nothing.
- In your browser: a random ID and your name, kept in the browser’s local storage so we recognise the same browser. No advertising cookies.
What we do not do: we do not make voiceprints or speaker profiles, and Hybraen does not receive camera video; if people turn cameras on, the video is carried between the people in the room and not to Hybraen. Please do not say or write highly sensitive information in a session (for example health details, payment card numbers or passwords) unless your team has agreed to.
Permission, and withdrawing it
Everyone who joins a room is shown an agreement screen before the board, microphone or camera start, and Hybraen does not listen to people who have not agreed. You can withdraw at any time from the menu in the app (“Withdraw consent”), or from Settings, Account, Consent (“Withdraw my meeting consent”) while signed in: Hybraen stops hearing you and you leave the meeting. We keep the record that you agreed and withdrew. If the people in your meeting are in a place where recording needs everyone’s consent, the agreement screen is how we ask, and hosts should tell their guests before they join.
AI features: what is sent to whom
Hybraen’s AI features run on other companies’ AI models. They use Google’s Gemini models through Google’s paid Gemini API, speech-to-text included. A feature sends only what it needs, at the moment you (or your meeting) use it, over an encrypted connection. This is what each feature sends:
- The assistant in a meeting. The audio of people who agreed on the agreement screen goes to Gemini to be turned into text, with the names of the people in the room so they are spelled right; the audio is not stored as a recording. The text of the conversation, with each speaker’s name, goes to Gemini to take notes and to write the minutes and the recap at the end. Pictures of the board go to Gemini so Hybraen can read the whiteboard, and, while capture is on, so do pictures of a screen shared in the room (sent when the screen has changed, not stored). When someone asks Hybraen a question, the question, the current notes and the last few sentences go to Gemini to produce Hybraen’s spoken reply, and, for web research, the question goes to Gemini with Google Search. Gemini does not receive the audio of people who have not agreed, or camera video.
- Outcome drafts after a meeting. These are built from the meeting’s notes and minutes without a new AI request.
- Pre-meeting briefs. For each invited person, separately: the meeting’s title, time, length and the names of invited people with an account (guests are only counted), the notes of the series’ earlier meetings if that person is a participant of the series, the confirmed decisions and published outcomes that person can read, and, only if that person turned on Google Workspace, short excerpts of their own Google files attached to the meeting. One person’s files never go into another person’s brief.
- Create artifacts. What you type in the chat, and the material it reads for you: meeting recaps and notes, outcomes and decisions, briefs and feed posts you can read, the text of Google files you picked, and the text of files you upload there. Only after you agree to its notice.
- Help me write (in the feed composer). Your draft, and, if you ask for a summary, the one meeting outcome or decision you pick. Nothing is posted or kept until you publish.
- Catch me up and Ask Hybraen (in the feed). Catch me up sends the published posts you can read from the time window you choose. Ask Hybraen sends your question, the post and its comments, its decision history, and a few related posts you can read. Only when you ask.
- Hybraen in Chats. When someone sends a message to Hybraen in a chat: that message, the recent messages of the chat, and the notes and recaps that everyone in the chat may see.
- Chat Recap. When you ask for a recap of a chat, the messages of that chat that you can read in the time window you pick, with each sender’s name and time, are sent to Gemini to make a summary that only you see. It runs only when you ask, and only in chats where Hybraen is on. It reads only messages from after Hybraen was invited to the chat, unless the member who invited Hybraen chose to share the earlier messages too. The summary is stored encrypted for you alone, at most 20 per chat, and is deleted after up to 7 days or as soon as you press Dismiss; you can make up to 5 a day.
- Calendar AI and suggested meeting times. Calendar AI is described in its own section below. “Suggest a time” sends only anonymous busy times (“P1”, “P2”) and your time zone, never names or event titles.
- Artifacts search runs on our own servers and sends nothing to an AI provider.
- Meeting suggestions (off unless you turn them on). For each situation: a short excerpt (up to 280 characters) of an open question, decision, action item or post you can read, the meeting title or topic, how old it is, and the people involved as labels with first names only. Never calendars, e-mail addresses or transcripts. Suggested times are worked out on our servers, and nothing is sent to anyone until you press Send.
- Auto PRs (a developer option, off unless you turn it on). The text of one action item assigned to you goes to Gemini to decide whether it is code work. If you also turn on finding requirements in your meetings, the recorded decisions, action items, open questions and notes of a meeting you attended (not the transcript) go to Gemini to list code requirements. What is then sent to GitHub is described under Jira and GitHub.
Turning AI features off for a company. Workplace owners and admins can turn AI features off for their Workplace, which stops sending that Workplace’s data (its meetings, feed posts, chats and briefs) to the AI providers.
How the providers may use it. We use the paid versions of these services. Under Google’s Gemini API terms for paid services, Google does not use what we send or the answers to improve its products or train its models. Google may keep what we send for a limited period to detect and prevent abuse and to meet legal obligations, as their terms describe; we do not control that period. We do not ask Google to keep it for us.
Where. Hybraen stores your data in the United States (Google Cloud). The Gemini API is a global Google service and we do not choose the region where Google processes a request, so it may be processed outside the United States and outside your country. See “Where data is processed” below.
Turning AI features off. Help me write, Catch me up, Ask Hybraen, Chat Recap, Create artifacts and Calendar AI run only when you ask. You can disconnect Google Workspace on your account’s MCP page, or turn off “Use my Google files”, and then no Google file of yours is read or sent; disconnecting also withdraws your agreement to the Create artifacts notice. You can withdraw your consent to Calendar AI from Calendar AI itself, and your agreement to be heard in a meeting with “Withdraw consent” in the app or “Withdraw my meeting consent” in Settings, Account. A meeting cannot run without the AI that listens and takes notes, so if you do not want your words sent to these providers, please do not join with your microphone on.
Calendar AI
The Calendar AI is a small chat on your Calendar page that finds, books, moves and cancels your own meetings. To understand a request it sends text to Google’s Gemini AI model (see the table below and Google’s policy for how they handle it).
What is sent:
- What you type: up to 600 characters per message, plus the last few turns of the conversation. If you type an e-mail address in a message, it is part of that message.
- When it looks something up in your calendar: for each meeting, the title (first 100 characters), start time, length and whether it repeats, and for the people invited only how many there are, never their addresses. For past meetings also the name of the recurring series, whether you attended, and whether notes, a transcript, a recap or a board exist (only that they exist).
What is not sent: the notes, transcripts or recaps themselves, and anybody else’s calendar. We do not log what you type or your meeting titles.
The Calendar AI can only propose to book, move or cancel a meeting. Nothing changes until you confirm, and the people invited then get the usual e-mail. Meeting titles are encrypted in our database, but they have to be readable at the moment they are sent to the model so it can answer you. You can withdraw your consent at any time from the Calendar AI itself.
Chat invitations and join links
When a member invites someone to a chat by e-mail, we send the invitation on that member’s behalf, using the address they entered. A chat can also have a join link: anyone who opens the link and signs in can join the chat and read its earlier messages, until a member turns the link off. Share a join link only with people you want in the chat.
Meeting recap e-mail
When a meeting ends, Hybraen e-mails a short recap to each person with a Hybraen account who took part in the meeting or was invited to it and may read its recap. This e-mail is on by default. It lists the meeting’s decisions, action items and open questions, with a link to the full recap in Hybraen; it never contains the transcript. Guests without an account do not get it. To stop only this e-mail, turn off “Meeting recap e-mails” in Settings, Alerts on the website or in Account, Notifications in the iPhone and Android apps; each recap e-mail links there. The unsubscribe link at the bottom of any Hybraen e-mail also stops it, but turns off the other notification e-mails too. The e-mail is sent through Resend.
Hybraen on iPhone and Android
In the iPhone and Android apps you can sign in with Google, as on the website (we receive the same email address, name and Google account ID), or, on iPhone, with Apple (we receive your email address, which may be an Apple relay address if you choose to hide yours, and your name the first time). If you allow notifications, we store a device token for your phone, encrypted, so we can send it push notifications; we delete it when you sign out on that phone, change your password or delete your account. Push notifications are delivered through Apple Push Notification service (iPhone) and Firebase Cloud Messaging from Google (Android). A notification holds only a short line, such as the sender’s name and “New message”; it never contains the text of a chat message.
You can delete your account in either app under Account, Delete account. How to delete your account also explains what to do if you cannot sign in.
Jira and GitHub
If you connect Jira (Atlassian) or GitHub, Hybraen acts with your own account on that service and can do only what your account may do there.
- What we store: your access tokens, encrypted; for Jira, your Atlassian account ID and display name and the Jira sites you can reach; for GitHub, your GitHub user ID and username and the installations of our GitHub apps; and links between meeting items and the issues and pull requests made from them.
- What is sent: when you send an item (or Auto PRs does it for you, if you turned it on), the item’s text, the meeting’s title and date and a link to the meeting go to Jira or GitHub, with the assignee, labels or other fields you choose. Never the transcript or the recap. Everyone who can see that Jira project or GitHub repository can read it, and anyone can if the repository is public. Items can contain what other people said in the meeting, so choose carefully where you send them. Text written by Hybraen’s AI is marked as such.
- Coding agent: if your Workplace turned it on, Hybraen can ask a repository’s own Claude Code GitHub Action to work on an issue. That action runs under the repository owner’s own AI account and terms, not under Hybraen’s. Hybraen does not read your repository’s code or send it to an AI provider. Hybraen never merges on its own; if you turn on “Allow merging from Hybraen”, it merges a pull request only after you confirm.
- Jira status: if your Workplace turned on following pull requests, Hybraen moves the linked Jira issue when its pull request opens or is merged, using the account of the person who linked it.
- Atlassian’s privacy reporting: as Atlassian requires, about once a week we send Atlassian the Atlassian account IDs we hold. If Atlassian tells us an account was closed, we delete that connection.
- How long: tokens and profile details until you disconnect, delete your account, or the service stops accepting the token. To remove Hybraen’s access on Atlassian’s or GitHub’s side too, remove it in your account settings there.
Following colleagues
You can follow people in your Workplace. Following is one-way: the person is not asked and not told, and only you can see whom you follow. It changes one thing: their posts that you can already read come first in your Home feed. It does not let you see anything you could not see before. People outside your Workplaces cannot follow you. When you or they leave the Workplace, the follow is removed.
Your birthday
If you add your birthday (month and day), it is used only to post a birthday greeting to your Workplace on the day, and only if you turn on “Announce my birthday”. We store it encrypted, never show it on your profile, and delete it when you remove it.
Friends (retired)
Hybraen no longer has friends. Friendships between people in the same Workplace became follows in both directions; all other friendships were ended. A direct message between two former friends who share nothing else on Hybraen became read-only: its history stays, but no new messages can be sent. Posts that were shared with friends are now visible only to their author. Nobody was told. We keep the old friendship records for a short time after this change and then delete them.
Online status
Your status is online, away or busy. Away means the app has not been open for about five minutes, or you set it yourself. Busy means you set it yourself, or you are in a Hybraen meeting, or a meeting scheduled in Hybraen is in progress (including a Hybraen meeting that was added to your Google Calendar); “Use my calendar to set Busy automatically” turns the last part off. Events that exist only in Google Calendar never set Busy. Your status is for you: since friends were retired, nobody else sees away or busy. People who share a workspace with you can see that you are online in that workspace (the app was open in the last minute or so); they never see your events, titles or times. We do not keep a log of when you were online: we store only the latest moment you were seen.
Reports and muting
When you report a post, comment, chat message or profile, we store the report: what was reported, who wrote it, the reason, your optional note, the time and who sent it. The owners and administrators of the Workplace the content belongs to see the report, including who sent it and the reported content, so they can review it; the author is not told who reported it. A report about content that belongs to no Workplace is sent to the Hybraen team by e-mail (without the content or your note) and reviewed by us. When you mute a person, only you are affected; they are not told. We also record when you accepted our Terms of Use and which version.
Paid plans and payments
Paid Workplace plans are billed through Stripe. When an owner or administrator starts checkout, we send Stripe their e-mail address and the Workplace’s ID. Stripe collects the payment details, billing name and address on its own pages; Hybraen never receives or stores card details. We store the Stripe customer and subscription IDs, the plan, the number of seats, the billing interval, trial, renewal and cancellation dates, and the time of a failed payment. Stripe processes payment data under its own privacy policy.
On the Free plan, meetings older than 30 days are hidden in the app but not deleted; they come back if the Workplace moves to a paid plan.
Product usage statistics
To learn which parts of Hybraen are used and which are not, our servers count how often each feature is used (for example “a comment was posted” or “a meeting was started”), per company Workplace and per hour. These counts never include what you wrote, said or shared, the names of meetings, posts or files, or who did it. To count how many people were active on a day, we use an identifier that changes every day, so the counts cannot follow one person from day to day. Only a few people at Hybraen Inc. can see these statistics, as totals per Workplace; they cannot see what an individual person did.
How we use it
- To run Hybraen: take notes, answer questions, draw and write on the canvas, and bring earlier decisions back in a later meeting of the same room.
- To keep the service secure and to prevent abuse, including limiting wrong access-code tries.
- To understand which features are used, from the usage counts above, so we can improve Hybraen.
- To contact you about early access or your trial, and to answer your questions.
- To meet legal obligations.
Who processes it for us
We build on other companies’ services. They process data only to provide those services to us, under their own terms, which also say how long they keep it and whether they use it. What each AI feature sends is listed under AI features above.
| Service | What it does for us | Policy |
|---|---|---|
| Google (Gemini API) | Runs Hybraen’s AI features: speech-to-text in meetings, meeting notes, minutes and recaps from the text of the conversation, reading the whiteboard from board pictures and a shared screen from screen pictures, web research, Hybraen’s spoken replies, Hybraen in Chats, Calendar AI and suggested meeting times, pre-meeting briefs, Create artifacts, Help me write, Catch me up and Ask Hybraen, meeting suggestions, and Auto PRs | Gemini API terms |
| Google Cloud | Hosts the app, the database (notes, decisions, minutes, transcripts) and file storage (board pictures). Data is stored in the United States. | policies.google.com |
| Google (Sign in with Google, Sheets) | Signs you in with Google on the website and in the apps; holds the early-access list | policies.google.com |
| LiveKit | Carries voice (and camera video, if people turn it on) between the people in a room in real time | livekit.io |
| Vercel | Hosts hybraen.com | vercel.com |
| Resend | Sends Hybraen’s e-mail: sign-in and verification links, invitations, meeting e-mails, the recap e-mail after each meeting (on unless you unsubscribe) and the other notification e-mails you turned on | resend.com |
| Apple (Push Notification service, Sign in with Apple) | Delivers push notifications to the iPhone app; signs you in with Apple on iPhone | apple.com |
| Google (Firebase Cloud Messaging) | Delivers push notifications to the Android app | policies.google.com |
| Stripe | Handles payments for paid Workplace plans: checkout, subscriptions and the billing portal | stripe.com |
The same list, with the data each one processes and where, is on our subprocessors page. We may add or change providers as Hybraen grows; when that changes what you agreed to, we will update this page and the agreement screen.
Improving Hybraen
We do not use the content of your meetings to train AI models. The agreement screen has an optional box, “Help improve Hybraen”; we record your choice and saying no changes nothing about what you can do. If we ever start using meeting text to improve Hybraen, it will be only for people who said yes, after removing personal identifiers, and we will update this page first.
How long we keep it
- A team’s sessions (transcripts, notes, decisions, minutes, board pictures) are kept so the team can come back to them, until the team asks us to delete them, or for the retention period a team has agreed with us. Decisions and notes are kept on purpose, so a later meeting can recall them.
- Database backups are rotated after a set period. Data deleted from our database can remain in backups until they are rotated out.
- Early-access requests and trial sign-ins are kept until you ask us to delete them or we no longer need them to run the program.
- Usage counts are kept for about 13 months; the daily identifiers used to count active people are removed after 90 days.
- Agreement records are kept as long as the related meeting data, as proof of what you agreed to.
- Chat Recap: up to 7 days, at most 20 per person per chat, or until you press Dismiss, whichever is first.
- Pre-meeting briefs are kept by default. In Feed settings you can choose to have yours deleted 1 or 7 days after the meeting. They are deleted right away if the meeting is canceled or you are taken off it, and when your account is permanently deleted. Shared meeting outcomes and decisions are not deleted by this setting; it only hides them from your own feed.
- Older meetings on the Free plan are hidden after 30 days but stay stored as described above, and can be deleted on request.
- Reports are kept with the Workplace they belong to. If the person who sent a report, or its author, deletes their account, the report stays without their name.
- Terms of Use acceptances are kept until you delete your account.
- Billing records: our copy is kept while the Workplace exists; Stripe keeps its own records under its terms.
When you contact support
You can write to us from the Support page, either by chatting with Hybraen Customer Support or by sending us a message. You can also emailsupport@hybraen.com.
What you write in the support chat is processed by Google Gemini so that the assistant can ask follow-up questions and sort your report (for example, whether it is a technical problem, a security or payment matter, or something else). Google processes it as our service provider through the paid Gemini API. The assistant cannot see your account, your meetings or any other content; it only sees what you type in the chat.
When you send a report, we store it and email it to our support team, with your account’s email address so that we can reply. Security, privacy and payment reports go only to the person responsible for security. For technical problems, the details you give may be used to prepare a fix of the product.
Please do not send passwords, keys, card numbers or other secrets. If something looks like one, we hide it before we store your message and we ask you to change it.
Support chats are deleted 90 days after the last message, and when your account is permanently deleted. Reports you sent stay with our team as a record of the problem; after you delete your account they are no longer linked to you, but the text you wrote stays in them.
Your choices and rights
You can ask us what we hold about you, to correct it, to delete it, or to stop using it. You can also withdraw your agreement in the app at any time. Depending on where you live (for example the European Economic Area, the United Kingdom or California) you may have further rights, such as to object to or restrict processing, to receive a copy of your data, and to complain to your local data-protection authority. Contact us and we will reply within the time the law requires. We do not sell personal information.
When you delete your account
You can delete your account from your account page or in the app (how to delete your account). Your account is switched off as soon as you ask: you are signed out everywhere and cannot sign in, we revoke your connections to Google, GitHub and Google Drive, and we remove your push devices and the invitations sent to you.
30 days. For 30 days after that, an admin of a Workplace you belonged to can restore your account. You cannot restore it yourself, and we do not send a link for it. If you were alone in your Workplace, there is no admin who can restore it. After 30 days the deletion below happens automatically and cannot be undone.
What we delete after the 30 days. Your profile and profile picture; your sign-in details; your connections to Google, Jira and GitHub and the tokens we stored for them; your calendar and Workspace permissions; your invitations, mutes and your record of accepting the Terms; attachments in direct messages you sent to yourself; and any workspace or Workplace where you were the only person, with everything in it. Files that were only yours are queued for deletion from our storage and may remain there until our cleanup removes them. Database backups are rotated after a set period, and data deleted from our database can remain in them until then.
What stays. Work you created with other people stays so your team can keep using it: team chats and channels, feed posts and comments, meeting notes and transcripts, images and files you added to a meeting, and pictures of the board. It is no longer linked to your account and shows your name as “Former member”. Feed drafts you never published also stay as “Former member”. Reports you sent stay without your name.
Before you delete. If you are the only owner of a workspace that other people belong to, hand it over to someone first. If your Workplace has a paid plan, cancel or transfer it first.
Security
Data is encrypted in transit (TLS) and at rest with Google Cloud’s default encryption. It is not end-to-end encrypted, so Hybraen can process your meeting content to provide the service. Each workspace’s data is kept apart in our database so that one workspace cannot read another’s, access to our systems is limited to the people who need it, and secrets are kept in a managed secret store. More detail is on our security page. No online service is perfectly secure, so please share only what your team is comfortable sharing.
Where data is processed
Hybraen runs in the United States: our database and file storage are in Google Cloud’s United States region. If you use Hybraen from another country, your information is transferred to the United States and to the providers above. The Gemini API is a global Google service and we do not choose its region, so a request to it may be processed outside the United States.
For people in Korea and the European Economic Area or the United Kingdom. This is what is transferred abroad and on what basis:
- Who receives it and why: the providers in the table above (for the AI features, speech-to-text included: Google LLC for Gemini), only to provide the feature you use. Their contact details are in their linked policies.
- What and when: the items listed for each feature under AI features, sent over an encrypted network connection at the moment the feature is used.
- Countries: the United States for our own storage; for the Gemini API, the countries where Google processes requests, which we do not choose.
- How long: we keep your data as described under “How long we keep it”; the providers keep it only as their terms allow (see “How the providers may use it” above).
- Basis: where the law requires your consent, we ask for it in the app before the feature is used (the agreement screen in a meeting, the Google Workspace and Create artifacts notice, Calendar AI); otherwise the transfer is needed to provide the service you asked for. For transfers from the European Economic Area and the United Kingdom we rely on the safeguards in the providers’ data-processing terms, such as the European Commission’s standard contractual clauses, where those terms offer them.
- Saying no: you can refuse or withdraw at any time as described under “Turning AI features off”. The feature that needs the transfer then does not work for you; the rest of Hybraen does.
To use your rights or ask about transfers, contact us or write to support@hybraen.com.
Children
Hybraen is built for working teams and is not meant for children under 16. We do not knowingly collect their information; if you think we have, tell us and we will delete it.
Changes
When we change this policy we will update this page and the date above. If a change is material for a team using Hybraen, we will also tell the team.
Contact
Questions or requests about your information: contact us.