Privacy Policy

Last updated May 25, 2026

Who we are

El Ojo is a free Chrome screen-recording extension. It is made by ai2flows. This policy covers the extension and the website at elojo.app.

What the extension does with data

Recordings

When you click Record, the extension captures the active browser tab (video + tab audio) and optionally your microphone and camera. These streams are processed entirely on your device and assembled into a WebM file.

When you stop, you choose how the file is saved:

• Download .webm — the file is saved to your local machine.
• Upload to Google Drive (if you connect a Google account) — the file is uploaded directly from your browser to your Drive over Google’s API. We never receive the file.
• Upload to a custom backend (advanced option, if you configured a URL) — the file is uploaded to the backend you operate.El Ojo does not run that backend; you do.

Microphone, camera, and screen permissions

These are granted via Chrome’s native permission prompts. The extension uses them only while recording, never in the background.

Google Drive integration

If you choose to connect Google Drive:

• We use the drive.file OAuth scope — the most restrictive Drive scope available. El Ojo can only see, create, and manage files that the extension itself creates. We cannot read your other Drive files.
• We also request userinfo.email and userinfo.profile so the popup can display “Signed in as your-email@example.com”.
• The OAuth access token is stored by Chrome locally on your machine. We never see it.
• You can revoke El Ojo’s access at any time at myaccount.google.com/permissions.
• El Ojo’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the user-facing features of El Ojo (uploading recordings to your Drive and showing your account name in the UI). It is not transferred to any third party, used for advertising, used to train AI/ML models, or accessed by humans except (a) with your explicit consent, (b) for security purposes, or (c) to comply with applicable law.

Settings

Your extension preferences (camera on/off, beauty level, etc.) are stored locally via chrome.storage on your machine. They never leave your device.

Custom backend (opt-in)

If you point El Ojo at a custom backend URL (a self-hosted FastAPI service shipped with this project), that backend may store:

• An anonymous device-account email (auto-generated by the extension, e.g. device-abc123@elojo.io) and a random password, used for JWT authentication on that backend.
• Recording metadata: filename, size, duration, timestamps.
• The recording file itself, in the Cloudflare R2 (or compatible) bucket you control.

This backend is opt-in and runs under your account, not ours. The default experience uses Google Drive (or local download only) and never contacts a server we operate.

What the website does with data

elojo.app is a static landing page hosted on Vercel. Vercel may log standard request metadata (IP address, user-agent, timestamps) for operational and abuse-prevention purposes, per Vercel’s own privacy policy. We do not run analytics or third-party trackers on the site.

Children

El Ojo is not directed at children under 13. We do not knowingly collect data from children.

Your rights

Because we don’t collect or store your data ourselves, there is nothing for us to provide, correct, or delete on your behalf. To delete your recordings:

• Locally saved: delete the .webm from your machine.
• Uploaded to Drive: delete from drive.google.com.
• Uploaded to your custom backend: delete from your R2 bucket / database.

To revoke the extension’s Google Drive access: myaccount.google.com/permissions.

Changes to this policy

If anything material changes, we will update this page and the “Last updated” date above.

Contact

For questions about this policy, write to info@ai2flows.com or visit https://ai2flows.com.