Privacy Policy

Last updated: 28 August 2026

downDATA (“we”, “us”) lets you track the status of services like GitHub, Supabase, Cloudflare, and other Atlassian Statuspage-based providers, group them into boards, and get incident history and Slack notifications. This policy explains what information we collect when you use downDATA, why, and what choices you have about it.

1. Information we collect

Account information. When you sign up with email/password or Google, we (via our authentication provider, Supabase) store your email address and an encrypted password or your Google account identifier.

Tracked services, boards, and integrations. Which services you choose to track, how you group them into boards, and any Slack workspace you connect via “Add to Slack” are stored so we can show your dashboard and, if you’ve connected Slack, post status notifications to the channel you picked.

Incident history. For tracked services, we keep a durable history of status changes and incidents (polled periodically from each provider’s public Statuspage feed) so past incidents remain visible even after they’re resolved. This is public status data about the services you track, not personal data about you.

Support conversations. If you opt in to live chat (see Cookies below) and message us, those conversations are handled by Tawk.to.

Usage data. If you opt in to analytics (see Cookies below), we collect anonymized, aggregate usage data via Vercel Analytics and Speed Insights — page views and performance metrics, not the specifics of what you track.

2. How we use this information

• To provide the service — your dashboard, tracked services, boards, and incident history.
• To operate your account — authentication and, where connected, your Slack integration.
• To send the Slack notifications you configured when a tracked service’s status changes.
• To protect the service from abuse.
• With your consent, to understand aggregate usage and improve the product, and to provide live chat support.

We do not sell your personal information, ever.

3. Cookies

We use three categories of cookies/local storage, matching the choices in the “Cookie preferences” link in the footer of this site:

• Necessary — keeps you logged in and protects login forms from bots. Always on: the site can’t function without these, and GDPR/ePrivacy don’t require consent for strictly necessary technology.
• Analytics — Vercel Analytics and Speed Insights. Off by default; only loads once you opt in.
• Support chat — the Tawk.to live chat widget. Off by default; only loads once you opt in.

You can change your choice at any time using the “Cookie preferences” link in the footer of any page. Your decision is stored in your browser’s local storage, not a tracking cookie.

4. Third-party services we use

• Supabase — authentication and database hosting for your account, tracked services, boards, and incident history.
• Vercel — hosting, and (opt-in only) analytics and performance monitoring.
• Slack — optional notification integration, only if you connect a workspace.
• Tawk.to — live chat support (opt-in only).
• Each tracked service’s own status provider — live status shown on downDATA is fetched directly from that service’s public Statuspage API, on demand; we don’t store it beyond the incident history described above.

Each of these providers processes data under their own privacy policy, only for the purposes described above.

5. Data retention

We keep your account, tracked services, boards, and Slack connection for as long as your account exists. Incident history is kept for the services being tracked and isn’t tied to any individual account.

6. Your rights

Depending on where you live, you may have the right to access, correct, export, or delete your personal information. downDATA doesn’t yet have a self-service account page for this — contact us at [Insert your support email here] and we’ll act on your request.

7. Children’s privacy

This service is not directed at children under 16, and we don’t knowingly collect information from them.

8. Changes to this policy

If we make material changes to this policy, we’ll update the “Last updated” date above.

9. Contact

Questions about this policy? Email us at [Insert your support email here].