GitLab Presence / Privacy
Privacy information for extension users
GitLab Presence provides editing awareness for configured GitLab repositories. This policy explains what information the extension handles, why it is needed, and how users can contact the project team.
01 / Scope
Scope
This privacy policy applies to the GitLab Presence browser extension developed for the Macao Pui Ching Middle School iGEM team and to the Presence API used by the extension.
02 / Information
Information we handle
The extension may process the following information:
- A display name entered by the user or the username shown by GitLab.
- The configured GitLab repository and the repository-relative path of the file being viewed or edited.
- A randomly generated presence session identifier, together with session start and last-active timestamps.
- Extension settings, including the configured Presence API URL and enabled repository prefixes.
- Standard network information, such as an IP address, browser user agent, and request time, which may appear in HTTP server logs.
The extension does not collect GitLab passwords, authentication cookies, source code, file contents, keystrokes, personal communications, financial information, or health information.
03 / Use
How we use information
Information is used only to provide the extension's collaboration functionality: showing which team members are currently editing the same GitLab file, maintaining active presence sessions, releasing sessions when an editor closes, and operating and securing the service.
We do not use user data for advertising, profiling, credit assessment, lending, or purposes unrelated to GitLab Presence.
04 / Sharing
Disclosure and sharing
A user's display name and active editing presence may be shown to other extension users viewing the same configured repository and file. Presence information is processed by the project team's API hosted on Macao Pui Ching Middle School infrastructure.
We do not sell user data. We do not transfer user data to third parties except where necessary to provide the extension's user-facing functionality, comply with law, or protect the security of the service.
05 / Retention
Storage and retention
Extension preferences are stored using Chrome storage. If Chrome Sync is enabled, Chrome may synchronize those preferences between the user's browsers under Google's applicable terms.
Active presence records are stored on the school's server. A session stops appearing as active after 120 seconds without a heartbeat. Expired session records are removed during subsequent server cleanup. Standard server logs may be retained temporarily by the school's hosting infrastructure for security, troubleshooting, and service reliability.
06 / Security
Security
Data sent to the production Presence API is transmitted over HTTPS. Access to stored information is limited to operating, maintaining, and securing the service. No method of storage or transmission is completely secure, but the team uses reasonable safeguards appropriate to this limited-purpose service.
07 / Your choices
Your choices and deletion
Users may change or clear extension settings through the extension popup. Uninstalling the extension removes its extension-managed local data. Closing or leaving the GitLab editor releases the active presence session; if release fails, the session expires automatically.
Users may contact the project team to request access to or deletion of server-side personal data. Requests may require enough information to identify the relevant display name or session.
08 / Changes
Changes to this policy
We may update this policy when the extension or its data practices change. The date at the top of this page identifies the latest revision.
09 / Contact
Contact
Questions, privacy requests, and deletion requests can be sent to the Macao Pui Ching Middle School iGEM Team.
ansonlotiniat@gmail.com