Privacy
What Cronwize stores, why, how long it is kept and who else processes it.
This page states what the service is built to do. The controller's legal name, contact address and your rights under data protection law are added before launch.
What Cronwize stores
| Data | Why | Kept until |
|---|---|---|
| Account email, sign-in provider ID | Sign-in and email alerts | Account deletion |
| Monitor names, schedules, settings | The service itself | Monitor or account deletion |
| Ping records: time, signal, HTTP method, source IP, user agent, up to 10 KB of body | Ping log and alert context | Overwritten by newer pings (ring of 100 or 1,000 per monitor), or monitor deletion |
| Alert channel settings; Slack webhook URLs and webhook secrets encrypted | Alert delivery | Channel or account deletion |
| Push device tokens | Push alerts | Sign-out, token invalidation or account deletion |
| Alert delivery log | Shown to you for debugging | 30 days |
| Subscription state from Polar | Entitlements | Account deletion |
Ping bodies
Ping bodies are stored as text and are never parsed, executed or shared. Your job decides what it sends, so do not send secrets.
Deleting your account
Deleting the account deletes all monitors, pings, channels and devices. Polar keeps its own invoice records as merchant of record.
Where data is processed
Data is processed in the EU, on Vercel Functions in Frankfurt and Supabase in Frankfurt. Push goes through Google FCM and Apple APNs. Email goes through ZeptoMail.
Analytics
The apps contain no analytics SDK. The sign-up funnel is measured on the server. This website uses Vercel Web Analytics.
Third parties
Vercel (hosting), Supabase (authentication and database), Polar (payments), ZeptoMail (email), Google FCM and Apple APNs (push), the Slack and webhook endpoints you configure, and GitHub, Google and Apple when used for sign-in.