Sergio Comerón Sánchez-Paniagua
Spain
Contact: [email protected]
The mod_jitsi Account (portal.sergiocomeron.com) is a service associated with the mod_jitsi Moodle plugin. It currently provides:
In future, the portal will also manage plugin licences.
This section applies to Moodle administrators and end users of the mod_jitsi plugin. The data described here is processed inside your own Moodle instance. The Moodle site administrator is the data controller for this processing.
| Service | Data sent | When |
|---|---|---|
| Jitsi Meet server | Username, profile avatar URL, email address | Each time a user joins a Jitsi session. Used to identify participants inside the conference. |
| Google Vertex AI (Gemini) | Recording file (via Google Cloud Storage URI) | Only when an administrator explicitly triggers AI features (summary, transcription, quiz) on a recording. Requires AI features enabled and a GCP service account configured by the administrator. |
| mod_jitsi portal (portal.sergiocomeron.com) | Anonymous site hash, plugin version, Moodle branch, server type, activity count, enabled features | Periodic telemetry ping, only if the site administrator has opted in. No individual user data is included. See section 5 for full details. |
| Table | Data stored | Purpose |
|---|---|---|
jitsi_presence |
User ID, display name | Real-time presence of participants in a session, shown to other participants. Cleared when the session ends. |
jitsi_usage_daily |
User ID, session count, minutes, connection timestamps | Per-user daily usage statistics within each Jitsi activity. |
jitsi_recording_segments |
User ID, watched video segments, play counts | Track which parts of a recording each user has watched. |
jitsi_source_record |
User ID of the recording creator, AI-generated summary, transcription, quiz ID | Store recording metadata and AI-generated content linked to the user who initiated the recording. |
jitsi_push_subscriptions |
User ID, Web Push endpoint, encryption keys | Send browser push notifications for private session calls. Stored only if the user explicitly enables notifications. |
jitsi_tutoring_schedule |
User ID, day of week, start time, end time | Store tutoring availability for private session scheduling. |
Users can export and delete all their plugin data via Moodle's built-in privacy tools (Profile → Privacy and Policies → Data requests).
This section applies to users of the mod_jitsi Account portal. Sergio Comerón Sánchez-Paniagua is the data controller for this processing.
| Data | Purpose | Legal basis |
|---|---|---|
| Email address | Send invitation link; identify your portal account | Consent (you provide it voluntarily) |
| Username and password hash | Portal authentication | Contract performance (portal account) |
| Anonymous site hash (SHA-256 of your Moodle URL) | Identify your installation in usage statistics without storing the actual URL | Consent (opt-in in plugin settings) |
| Licence key (unique token assigned to your installation) | Link usage statistics pings to your portal account; survives site URL migrations | Consent (opt-in in plugin settings) |
| Plugin version, Moodle version, server type, activity count, enabled features | Understand how the plugin is used to prioritise development | Consent (opt-in in plugin settings) |
| Aggregated weekly usage counts (sessions, minutes, unique active users, active activities, total recordings, peak simultaneous participants) | Understand usage patterns to prioritise development; all are site-level aggregates — no individual user data | Consent (opt-in in plugin settings) |
| Site timezone | Usage statistics context | Consent (opt-in in plugin settings) |
| Site name (Moodle site full name) | Identify your installation; personalise support | Consent (provided at registration) |
| Site URL (your Moodle address) | Identify your installation; personalise support | Consent (provided at registration) |
We do not collect individual user data, course content, session content, or any other personal information beyond what is listed above.
When you enable the "Share anonymous usage data" option in the mod_jitsi plugin settings, a weekly ping is sent to portal.sergiocomeron.com containing:
No individual user data, course content, or session content is sent. All usage counts are site-level aggregates that do not identify any individual. You can disable telemetry at any time from the plugin settings.
| Data | Retention |
|---|---|
| Portal account (email, username) | Until you request deletion, or automatically 30 days after account deactivation |
| Usage statistics pings | 1 year, then deleted automatically |
| Expired invitation records | Deleted within 7 days of expiry (invitations expire after 48 hours) |
We do not sell, rent, or share your personal data with third parties. Data is stored on a server located in Spain (European Union). Daily backups are encrypted on our own server with AES-256 (using a key we hold) before being uploaded to Google Cloud Storage (region: europe-west3, Frankfurt, Germany); the storage provider only ever holds the encrypted files and cannot read their contents. Google is subject to a Data Processing Agreement under GDPR. Data is not transferred outside the European Economic Area (EEA).
Under the General Data Protection Regulation (GDPR) you have the right to:
To exercise any of these rights, contact us at [email protected]. We will respond within 30 days.
You also have the right to lodge a complaint with the Spanish data protection authority: Agencia Española de Protección de Datos (AEPD).
This portal uses a single session cookie strictly necessary for authentication. No analytics, advertising, or third-party tracking cookies are used.
Passwords are stored as bcrypt hashes. All communication with the portal is encrypted via HTTPS (TLS). Access to the server is restricted. Daily backups are encrypted client-side with AES-256 (PBKDF2) before leaving the server, so backup copies stored off-site are unreadable to the storage provider.
We may update this policy as the portal evolves. The date at the top of this page will reflect the most recent revision. Significant changes will be communicated to registered users by email.