Transparency Statement
1. Purpose
GEMC2 aims to explain what information it processes, how moderation works, and how it responds to legal and safety requests. We will not publish statistics or incident claims that have not been checked against available records.
2. Information the service may hold
- Account information: username, email address, password hash, registration answer, profile details, account status, and verification status.
- Public content: posts, replies, edit history, hashtags, mentions, reactions, reposts, follows, and blocks.
- Technical information: registration/session IP addresses, browser user-agent strings, session token hashes, expiration and revocation data, rate-limit identifiers, and error diagnostics.
- Notifications, reports, moderation records, and security/audit events.
- Push subscription endpoints and keys if a user opts in to browser push notifications.
- Data held by technical providers used to host, deliver email, protect, or provide push notifications for the service.
3. Cookies and sessions
The intended production lifetime for authentication and CSRF cookies is up to 30 days, controlled by the server configuration. The authentication cookie uses Secure, HttpOnly, and SameSite=Lax attributes; the CSRF cookie is readable by the browser application and uses Secure and SameSite=Lax. The session may end earlier due to logout, revocation, browser storage removal, or security action. See the Cookie Policy for details.
4. Private messaging commitments
Private messaging is not included in the reviewed application release. GEMC2 commits that when it is introduced, it will be one-to-one text messaging protected by end-to-end encryption, with no groups or attachments. The server will keep only an encrypted temporary queue for undelivered messages, delete the server copy after valid delivery-and-storage confirmation or at a maximum of 30 days, and not maintain permanent message history. Each participant will keep a separate local copy; there will be no cross-device history migration or recovery. Messaging will have delivery confirmations but no read receipts, and push notifications will not contain message text. The feature will not be represented as available until these safeguards have been implemented and tested.
5. Legal requests
GEMC2 reviews requests from authorities to determine whether they appear authentic, sufficiently specific, and supported by an appropriate legal basis. We disclose only information we actually hold and are legally required or permitted to disclose. We may challenge or narrow requests where appropriate and lawful, and notify affected users where appropriate unless prohibited by law or a valid order.
6. Moderation and reports
Users may report posts or accounts through the available reporting tools or by emailing [email protected]. The operator may dismiss reports, hide content, reject a pending registration, or suspend an account. Users may request a review of a moderation decision, but a reversal is not guaranteed. We do not promise a fixed response time for every report.
7. Retention and statistics
GEMC2's intended retention schedule is described in the Privacy Policy. Some automated cleanup procedures are still to be completed; expired database records may remain stored until those procedures are implemented. We will publish aggregate statistics about legal requests, copyright notices, moderation reports, and security incidents only when reliable records are available. This page does not claim that the number of requests or incidents is zero.
8. Security incidents
No online service can guarantee absolute security. If a personal-data incident occurs, GEMC2 will investigate, take reasonable steps to contain and remediate it, and notify affected people or authorities where and as required by applicable law. We do not promise an arbitrary fixed notification period.
9. Updates and contact
This statement may be updated as the service and its records evolve. Contact [email protected].