Privacy Policy

Last updated: 2026-07-20

Asistente_Prof (“we”, “our”, “us”) is provided by ARI BEN RAMIREZ VILLEGAS. This Privacy Policy explains how data is handled when you use the Asistente_Prof Zoom app.

How the app works

Asistente_Prof has two components that work together:

A browser assistant (“sensor”) that joins your meeting as an ordinary participant. It never becomes host or co-host. Its only job is to read whether each participant’s camera is on or off.
An in-meeting Zoom App that reads that information and applies the class policy you configured (chat reminder, remove, or move to waiting room), using your own host privileges.

Because the two components run in different places, the camera information must be transmitted between them through a service we operate (the “bridge”). This is described in detail below.

What data is processed

Data	Why	Where it goes
Participant display name, participant identifier (a UUID assigned by Zoom), and camera on/off state	So the in-meeting Zoom App knows who has their camera off and can apply the policy you configured	Transmitted to our bridge (see “Where data is stored”)
Zoom OAuth tokens (access and refresh) for the Zoom account you connect	To keep you signed in and to request the token that lets the assistant join your meeting on behalf of the app	Stored in our database
Session identifier (cookie)	To keep you signed in and to verify that only you can publish the camera state of your own meeting	Our database, plus a short-lived cache in the bridge
Meeting ID you enter	To join the meeting you choose	Used for the request; also saved locally in your browser for convenience
Your settings: reminder message, permanent exceptions (display name and participant identifier), grace period, theme, last meeting ID and display name	To remember your preferences between sessions	Stored only on your device (browser `localStorage`); never sent to us

No meeting content is ever recorded, stored, or processed: no audio, no video, no screen sharing, and no chat history. The app reads only the on/off state of a camera — never the image itself.

Where data is stored, and for how long

Bridge (camera state). Hosted on Upstash Redis in the United States (US East – N. Virginia). Each snapshot expires automatically 120 seconds after the last update and is continuously overwritten while the meeting is running. When the assistant stops publishing, the record disappears on its own. It is not backed up and never exported.
Session validation cache. Kept in the same bridge store for up to 30 minutes, to avoid querying the database on every update.
Zoom OAuth tokens. Stored in our database, hosted in the United States (AWS US East 1 – N. Virginia), and retained until you disconnect your account (“Cambiar cuenta de Zoom”) or revoke access from your Zoom account settings, at which point they are deleted. Deleted records may persist for up to 24 hours in the database provider’s automated point-in-time history before being purged.
Your settings. Remain on your own device until you clear them with the “Borrar datos guardados” button or clear your browser data.

What we do not do

No audio, video, screen-sharing, or chat recording.
No attendance or presence history stored on our servers (attendance features, when enabled, are generated and kept on your own device).
No tracking technologies or analytics cookies.
No advertising, profiling, or automated decision-making about participants beyond the camera policy you explicitly configure and enable.
No selling or sharing of personal data with third parties.

Service providers

We use the following providers strictly to operate the service. They process data on our behalf and are not permitted to use it for their own purposes.

Vercel — application hosting.
Upstash — the bridge described above (US East – N. Virginia).
Neon — database for account tokens and sessions (AWS US East 1 – N. Virginia).
Zoom — the meeting platform itself.

Participant transparency

The assistant joins the meeting as a clearly named, visible participant, so everyone can see it is present. Hosts are responsible for informing their participants that a camera policy is in effect, and for complying with any local rules that apply to their meetings.

Legal bases

If you are located in the EEA or UK, data is processed as necessary to provide the service requested (Article 6(1)(b) GDPR) and for legitimate interests related to the secure operation of the app (Article 6(1)(f) GDPR).

Your rights

Depending on your jurisdiction (e.g., GDPR, UK GDPR, CPRA, LFPDPPP), you may have rights to access, correct, or delete personal data, or to object to certain processing.

How to exercise your rights: email us at dev@ariiben.com.

Security

All traffic uses HTTPS. Publishing camera state requires an authenticated session, so only you can write the state of your own meeting. We apply reasonable technical and organizational measures appropriate to the limited nature of the data processed.

Changes to this policy

If we change how data is handled, we will update this page and the “Last updated” date above.

Contact

ARI BEN RAMIREZ VILLEGAS
Email: dev@ariiben.com