Privacy policy · Guidie

Guidie turns a recording of a task in your browser into a step-by-step guide. This policy explains, in plain English, what data that involves. Guidie is in a free beta, and this policy describes the product as it works today.

The short version

The Chrome extension records only after you press Start, and only in the tab you started it in, until you press Stop.
Text you type is never sent to us. Password fields are skipped completely.
Recordings are sent only to Guidie: to guidie.ai and to our private file storage. We use a small number of providers to store data, host the app and generate the guide text and voice-over.
We don't sell your data, show ads, or use analytics or tracking cookies.
You can ask us for a copy of your data or ask us to delete it at any time: [CONTACT EMAIL].

Who we are

Guidie is operated by [COMPANY NAME], [COMPANY ADDRESS] ("we", "us"). We are the data controller for the personal data described here. For any privacy question or request, email [CONTACT EMAIL].

What we collect

Your account

Your name, email address and password when you sign up with email. Passwords are stored only as a salted hash; we can't read them.
If you sign in with Google: your name, email address and profile picture from your Google account. We don't get access to your Gmail, Drive, contacts or anything else.
Your sessions: a session ID, when it expires, and the IP address and browser (user agent) it was created from, so you stay signed in and we can spot misuse.
Your workspaces: workspace names, members, roles and invitations.

Recordings from the Chrome extension

The extension does nothing until you press Start. While a recording runs, for each step it captures:

A screenshot of the visible part of the tab you are recording. Before each screenshot, the extension masks text you've typed into fields, and the guide blurs those areas again in case a page didn't repaint in time.
What you clicked or chose: the element's type and role, its visible label or text, its placeholder or accessibility label, the nearest heading, a CSS selector, and its position on the screen.
The page's address (URL) and title, the window size and the time of each step.
Where sensitive-looking text appears (for example email addresses, phone numbers or API keys), so the editor can suggest blurring it. Only the position of that text is sent, never the text itself.

The extension never sends what you type into fields, never records password fields, and never records other tabs, your browsing history, or anything outside a recording. It sends step data only to guidie.ai, and uploads screenshots straight to our private file storage (Cloudflare R2) through short-lived upload links that guidie.ai issues for each screenshot.

A screenshot shows whatever is on the screen at that moment. Before recording a task in a system with other people's data, check that you're allowed to share it, or blur it in the guide.

Guides you create

The guides made from your recordings: step instructions, tips, titles, summaries, narration audio, rendered videos and any edits you make.

Technical data

Our hosting providers keep standard request logs (IP address, browser, requested page, time) for security and troubleshooting. We use them only for those purposes.

The demo

The demo at guidie.ai/demo runs entirely in your browser and stores its data in your browser's local storage. Nothing you do in the demo is sent to us.

How we use your data and why we're allowed to

To provide Guidie (create your account, store your recordings, generate and show your guides, render videos): this is necessary to perform our contract with you (GDPR Art. 6(1)(b)).
To keep Guidie secure and working (sign-in sessions, rate limits, abuse prevention, fixing bugs): our legitimate interest in running a safe service (Art. 6(1)(f)).
To reply when you contact us: our legitimate interest, or our contract with you.
To meet legal obligations, for example tax records or lawful requests from authorities (Art. 6(1)(c)).

We don't use your recordings or guides to train AI models, and we don't sell or rent personal data.

AI processing

To write your guide, the step details (clicked element labels, page titles and page paths) are sent to the Anthropic Claude API. When a click is ambiguous from its label alone, a small crop of the screenshot around the clicked element is sent as well. To create the voice-over, the narration text of each step is sent to the OpenAI text-to-speech API.

Both providers process this data on our behalf under their commercial API terms, which do not allow them to use it to train their models. They may keep it for a limited time (typically up to 30 days) to detect abuse, then delete it.

Who processes your data

We share data only with the providers we need to run Guidie. Each acts on our instructions under a data processing agreement.

Provider	What it does	Data
Supabase	Database (Postgres), hosted in the EU (Frankfurt, Germany)	Account, workspace, recording and guide data
Cloudflare (R2)	File storage	Screenshots, audio and videos
Vercel	Hosts the website and app	Requests passing through, request logs
Railway	Runs background jobs (guide writing, voice-over, video)	Recording and guide data while a job runs
Anthropic	Writes guide text (Claude API)	Step details, occasional screenshot crops
OpenAI	Voice-over (text-to-speech API)	Narration text
Google	Sign-in with Google, if you use it	Your Google sign-in

Some of these providers are based in, or have support staff in, the United States. Where data leaves the EU/EEA, it is protected by the EU Standard Contractual Clauses or the EU–US Data Privacy Framework.

Other members of a workspace can see the guides in that workspace. We may also disclose data if the law requires it.

Cookies

We use only the cookies needed for Guidie to work:

Session cookies (set by our sign-in system, Better Auth) that keep you signed in. During Google sign-in, a short-lived cookie protects the sign-in flow.
A workspace cookie (tm_ws) that remembers which workspace you're working in.

There are no analytics, advertising or third-party tracking cookies, so there is no cookie banner. The extension keeps its recording status (whether a recording is running, and its step counter) in the browser's session storage, which is cleared when you close the browser.

How long we keep data

We keep your account, recordings and guides for as long as your account exists. When you ask us to delete your account, we delete it, your recordings and your files within 30 days. Database backups roll over and are gone within a further 30 days. Request logs at our hosting providers are kept for a short period set by each provider.

Your rights

Under the GDPR you can:

Access your data and get a copy of it.
Delete your data or your whole account.
Correct data that is wrong.
Take your data with you in a common format (portability).
Object to processing based on our legitimate interests, or ask us to restrict it.
Complain to your local data protection authority.

During the beta, email [CONTACT EMAIL] from the address on your account to use any of these rights. We'll reply within 30 days. A self-service delete button in the app is on our roadmap.

Security

All traffic to Guidie and to our database is encrypted (TLS). Passwords are hashed. Screenshots, audio and videos are stored privately and are only served through short-lived signed links to people who are allowed to see them. Access to your guides is checked on every request.

Chrome Web Store and Google user data

The use of information received from the Guidie Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Guidie's use of information received from Google APIs (Sign in with Google) adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use that data only to provide and improve Guidie's user-facing features, never for advertising, and we don't transfer it except as described in this policy.

Children

Guidie is a work tool and isn't meant for children under 16. We don't knowingly collect their data.

Changes to this policy

If we change this policy, we'll update the date at the top. If a change is significant, we'll tell you by email or in the app before it takes effect.

Contact

[COMPANY NAME], [COMPANY ADDRESS]. Email: [CONTACT EMAIL].