Privacy Policy
Draft privacy notice describing how UpPage handles personal data as built. Not yet in force; legal review pending.
Who handles data
TODO: controller name, registered address, privacy contact, effective date, applicable jurisdictions, and how to make a rights request. For data that customers put on their own status pages, the customer is the controller and UpPage processes it on their behalf (see the Data Processing Agreement).
What we collect
Account: email address and sign-in identity from Google, GitHub or an email link (handled by Supabase Auth), plan, and team membership and invitations (invitee email).
Service data: page content, monitors and their results, incidents, notification channel settings (alert email addresses the team adds, with whether and when each confirmed or unsubscribed; Slack and webhook URLs are stored as secrets and never shown back in full), audit history of changes, and daily usage counts. API tokens and ping/webhook secrets are stored only as hashes.
Waitlist: email address, join time and consent version. Abuse reports: the report text and, if given, the reporter’s email.
We do not store raw IP addresses in application records. Rate limiting uses short-lived counters.
Cookies
Only cookies needed to run the service: a session cookie and a refresh cookie for signed-in users, a short-lived sign-in verification cookie, and a cookie that remembers which workspace you last opened. No analytics or advertising cookies, and public status pages set none.
How data is used and shared
To run the service: authenticate you, publish your page, run checks, send your team’s notifications, prevent abuse, and bill subscriptions. Service providers are listed on the Subprocessor List. Page names, descriptions and incident text may be screened for phishing and impersonation; a person makes every enforcement decision.
Emails we send: team alerts you configured; to addresses a team adds, one invitation, and alerts only after you confirm (every email has an unsubscribe link, and unsubscribing is honoured for that team permanently unless you opt back in); invitations a teammate sent you, and account notices (renewal reminders, inactivity warnings). No marketing email without separate consent.
Retention and your choices
Account data is kept while the account exists. Deleted accounts are purged within 30 days; backups expire within 35. Owners can download a complete export from Settings. Public page history is kept for the plan’s history window.
TODO: legal bases per purpose, waitlist retention period, rights-request channel and response time, international transfer details, and security-incident contact.