Who runs UM Voices
UM Voices is an independent, student-operated petition platform for the Universiti Malaya community. It is not an official university service.
For questions about your data, reports or appeals, contact the site owner:
- Primary email
- hjon3456@gmail.com
- Alternate email
- 25005754@siswa.um.edu.my
The pilot is checked three times a week. It is not monitored continuously and does not provide emergency help or a guaranteed response time.
Reading and participating
You can read approved petitions without a UM Voices account. Access and participation may be restricted during private testing or a read-only preview.
When participation is enabled, you need an eligible, verified Google-managed SiswaMail account to create, support or report a petition. Account verification does not establish current student enrolment. Signing in never adds support automatically; you choose whether to support each petition and can withdraw.
Information we use
For sign-in and account security, we use your verified email address, Google and Firebase account identifiers, account-domain verification, verification times and session registration. Google and Firebase Authentication also process the Google account information used for sign-in. We never ask for or store your campus password, and the app does not retain raw Google tokens long term.
We store an account profile, the public display name you choose, your petitions and updates, support/withdrawal state and associated times, reports, and restricted records needed for moderation, account cleanup and security. We use them to operate the service, check permission, count valid support, handle reports and prevent abuse.
The hosting provider processes request metadata for operation and security. The app does not use advertising analytics or tracking cookies. Google services have their own processing arrangements. Our application database and hosting are configured in Singapore; this does not mean all Google authentication or infrastructure processing takes place only there.
What other people can see
Approved petitions show their authored text, recipient, chosen public author name, references, approved updates and aggregate support count. Do not include private information in text you intend to publish. Changing interface language does not translate or rewrite user-authored content.
Public pages, creator views, normal moderator views and petition PDFs do not provide a supporter directory or disclose supporter names, email addresses, account identifiers or individual support times. Your own account view can show your own support state and available history.
Authorized operators may access restricted records to maintain security and handle specific investigations. Exceptional identity access requires a separately authorized and recorded process. Google-hosted services process the information needed to provide authentication, hosting and storage.
Creators download a summary and deliver it themselves. UM Voices does not automatically send petitions or supporter identities to the university.
Cookies and temporary browser storage
When sign-in is enabled, a temporary sign-in cookie lasts up to ten minutes. The app-session cookie can last up to 14 days. Signing out removes that session's server registration and clears the browser cookie.
The homepage can keep your starting idea in the current tab's browser storage to carry it into the writing form. It is not a saved petition or AI writing. The app stops reusing it after 30 minutes; this is an expiry check, not a timer that guarantees browser storage is erased at that exact moment. Saving a draft is a separate action. Google sign-in and any private access gate may use their own essential cookies.
Retention and removal
The approved retention targets are:
| Record | Retention target |
|---|---|
| Restricted support/withdrawal action history | 90 days, except documented investigation holds. |
| Restricted moderation/security history covered by routine expiry | 90 days; documented investigation holds are reviewed every 30 days. |
| Withdrawn-support records | 90 days after withdrawal, except documented holds. Active support is unaffected. You can support again. |
| Completed account-cleanup jobs | 90 days after both database and authentication cleanup are confirmed complete. Pending or failed jobs remain until resolved. |
| Resolved report cases | 90 days after the case and any appeal are closed, except documented investigation holds. Open cases remain until resolved. |
| Production database backups | Daily backups are scheduled with seven-day retention. A schedule does not prove that a backup has completed. |
Production expiry under these targets is not yet enabled. These are retention targets, not a claim that older records have already been deleted or that deletion happens automatically at an exact deadline. Legacy records with unconfirmed status require review. Contact the owner about retained data.
While an account remains active, profile, identity linkage and current support state are kept to operate it. Account removal blocks further participation and excludes that account from public support counts. Separate cleanup withdraws active support, removes private drafts, deletes the account profile and authentication account, and removes the author link/name from published petitions. Published petition text and updates are not automatically rewritten or deleted; private information you placed in them may need separate review.
Minimal restricted revocation records remain to prevent old account access from returning. Current roles, unresolved security/cleanup work and recovery evidence are not erased by the general 90-day history rule. No blanket expiry period for those records is promised here. Their continued necessity and any data request must be reviewed separately. Account removal does not instantly erase copies in retained backups or copies already downloaded by other people.
Your choices
When participation is available, you can withdraw support, download the account data available through My activity, sign out and request account removal. For other access, correction or removal requests, contact the owner. We may need to verify that the request concerns your account; do not email passwords, sign-in codes, cookies or tokens. We do not disclose another person's private records to fulfil a request.
If you contact us by email, your address and message are used to handle the request. The case-retention process does not currently delete mailbox copies automatically. Any mailbox cleanup needs a separate reviewed action.
Opening an external reference takes you to another service with its own privacy practices. We will date material changes to this notice and make the updated notice available on the site before relying on the changed policy.