Imagine Imagine Intelligence

Privacy Policy

Last updated October 30, 2026

01

Who we are

Imagine Intelligence is an agent that joins your meetings — Google Meet, Zoom or Microsoft Teams — and turns them into a visual world you can revisit. It also includes a creative canvas. This policy explains how we handle information when you use the website at www.imaginei.ai, the live world and meeting app at /app, and related APIs.

Questions: email privacy@imagine-lab.tech.

02

Information we collect

Account. If you sign up, we store your email, a hashed password, and an optional name. Google Sign-In can create the same kind of account using the email and name Google shares with us. We also keep credits, Imagine Pro status, and optional content-filter settings on the account.

Calendar. If you choose Connect Calendar, we read your Google Calendar events so the agent can join a meeting at its start time. See Google user data, calendar access and Limited Use below for exactly what we read, what we do with it, and what we never do.

Meetings. When you add the agent to a call, we handle the meeting's audio so the world can be drawn and your questions answered during the call. We keep the meeting's transcript for 30 days after it ends, then delete it. The world is saved automatically and stays until its owner deletes it; what stays is the world — the drawing, the figures, the questions and answers in it, and short quotes from the call — not a recording of the conversation.

Guests. If you create without an account, the browser stores a random anonymous identifier. We use it to count a lifetime guest quota (five creations) and to apply rate limits. It is not your name or email.

Creations. We store canvases you save, sticker-book / library artwork, shared replay recordings, and (when memory is turned on for the product) an index that helps recall past creations.

Prompts and voice. When you generate artwork we send the prompt to our image provider and store the resulting picture so it can appear on the canvas. Listen sends microphone audio to OpenAI (gpt-live-1) for speech-to-text only; it does not speak back. When that daily allowance is used up, the audio goes to ElevenLabs (Scribe) for speech-to-text instead. Your browser's own speech recognition is used only if it is enabled; when it is, it listens once those allowances are used up, and in Chrome that sends the audio to Google. When it is not enabled, listening stops and you can type instead. During an explanation, a separate gpt-live-1 session speaks the lesson lines aloud and does not hear the microphone. Talk and Voice Director send audio to xAI's realtime voice service so characters can speak. Our own product analytics do not store those transcripts or prompts.

Payments. Credit packs and Imagine Pro go through Stripe Checkout. Stripe processes the card. We keep whether the purchase succeeded, credit balance, and Pro status—not the full card number.

Optional extras. Share feedback / the Imagine survey stores the answers you submit. Invite links store a referrer id. Shared rooms keep a session in this browser so you can rejoin.

Device and usage. We log allowlisted product events (for example creation completed or signup completed) with a hashed actor id, coarse click position, device class, and page. We do not allowlist prompt text or voice transcripts. Vercel Analytics and PostHog may collect visit metrics. Sentry receives crash reports with sendDefaultPii turned off.

03

Google user data, calendar access and Limited Use

Sign-in. Google Sign-In gives us your email address, your name and your profile picture, which we use to create and identify your account. We do not receive your Google password.

Calendar scope. Connect Calendar is optional. If you turn it on, you grant one read-only Google scope:

What we read. From each upcoming event we read only what is needed to be in the right call at the right time: the event title, the start and end times, and the conference join link (for example the Google Meet link attached to the event).

What we use it for. One purpose: so the Imagine agent joins the meeting you asked it to join, at that meeting's start time (auto-join). Nothing else.

What we never do. The access is read-only, so we never create, edit, move or delete your calendar events, never invite anyone on your behalf, and never change your calendar in any way. We do not use calendar data for advertising, we do not sell or transfer it, and we do not use it to train generalised artificial-intelligence or machine-learning models. No human at Imagine reads your calendar data except where you have given explicit permission for a specific support request, where it is necessary for security purposes (such as investigating abuse), or where we are required to by law.

Limited Use. Imagine Intelligence's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Sub-processors. Calendar data is stored in our own database (hosted in the United States) and is used by our meeting service to schedule the join. We do not pass it to our image, speech or voice providers.

Keeping and deleting. We keep the Google tokens and the upcoming-event details only while your calendar is connected. Disconnect your calendar in the app, or revoke access at myaccount.google.com/permissions, and we delete the tokens and the stored event details for your account. You can also email privacy@imagine-lab.tech and we will delete them for you.

04

How we use it

We do not sell personal information. We do not use your account to send third-party ads.

05

Who we share it with

We share data with services that help us run Imagine, only as needed for that job:

Those companies process data under their own terms. We do not pass Google Calendar data to any of them. If we are legally required to disclose information, we will, to the extent the law allows.

06

How long we keep it

07

Student data

Classrooms. A teacher can open the live world at /app without an account, so a class sees the talk drawn as it happens. Only the presenter's microphone is used.

Audio. Audio isn't stored by Imagine. It is passed straight to our speech-to-text service (OpenAI gpt-live-1, ElevenLabs or xAI) to turn speech into words and is not kept by us. Browser speech recognition is used only if it is enabled; when it is and your browser does the listening (when our service is unavailable or today's allowance is used up), it may send audio to its maker (for example Google): Chrome sends it to Google.

Words. What is said in a guest's live world is used to draw it and is then gone: no transcript is saved for a guest, our logs record only how long a line was, and our internal test traces are written for signed-in staff accounts only and keep lengths, never words.

Daily limits. To keep the free world fair, we count live worlds and listening minutes per device and per network each day, using the browser's random identifier and a one-way hash of the network address. These counters hold no names, words or audio.

Saved worlds. Outside meetings, a world is kept only when its owner saves it. A shared link leaves out who said what unless the owner chooses to include it. Session recordings are off; if we turn them on, typing, captions and spoken words are masked.

Visit links. A call with the meeting agent can have a public Visit link. Anyone with the link can view that call's saved questions and answers without signing in: each question word for word (up to 140 characters), a shortened answer, its source, any chart, card or picture shown with it, and the meeting owner's first name. The agent may post the link in the call's chat. The saved cards are removed 30 days after the meeting ends, or when the meeting is deleted, and the link stops working then. If the agent is still in the call when the meeting is deleted, the link keeps working until it leaves. The owner's own copy of those questions and answers stays in their meeting until they delete it.

08

Your choices

09

Security and where data lives

Passwords are stored hashed. Google tokens are held in our database and are never shown in the app or sent to the browser. Traffic to Imagine uses HTTPS. No method of transmission or storage is perfectly secure.

We operate Imagine from the United States. If you use the product from another country, your information is processed in the US.

10

Changes

If this policy changes in a material way, we will update the date at the top of this page. Continued use after a change means the new policy applies to that use.