Privacy Policy
Last updated: August 30, 2026
This explains what illari collects, why, and your choices. illari is operated by an individual (sole proprietor) based in Texas, USA. Contact [email protected] for any privacy question or request.
What we collect
- Account — your email address, and, if you sign in with GitHub, your GitHub account identifier and primary email, provided through our authentication provider Clerk. Optionally, a separate alert-email address you set.
- Monitor configuration — names, optional command/script text, cron expressions, timezones, grace periods, and alert-channel settings, including the webhook URLs and API tokens/keys you enter for Slack, Discord, Telegram, PagerDuty, incident.io, ntfy, Pushover, or generic webhooks.
- Check-in (“ping”) data — the time each ping is received, the source IP address it came from, optional exit codes and run durations, and, if your job sends one, the request body, stored as text and truncated (currently ~10 KB). Don't send secrets or personal data in ping bodies that you don't want stored.
- Billing — handled by Stripe. We store a Stripe customer ID and your subscription status. We never see or store full card numbers.
- Support — the content of emails you send us.
- Diagnostics — our error-monitoring tool (Sentry) records application errors, which can include your IP address, browser, and the page where an error occurred.
How we use it
To run the service — evaluate schedules, send alerts, show your dashboard and history; to process subscriptions; to debug and improve reliability; to contact you about your account or service changes; and to enforce our Terms.
Cookies
illari uses a session cookie from Clerk to keep you signed in. There is no advertising or third-party analytics tracking on the site.
Who we share it with
We don't sell your data. We use these providers to operate illari:
| Provider | Purpose |
|---|---|
| Clerk | Authentication and account records |
| Stripe | Subscription billing (merchant of record) |
| Resend | Sending alert and notification emails |
| Sentry | Application error monitoring |
| Railway | Application hosting and database (United States) |
| Cloudflare | Content delivery and network protection |
When you configure an alert channel, alert contents are also sent to that third party (for example Slack or PagerDuty) at your direction.
Where data is stored
Primarily in the United States. If you access illari from outside the US, your data is transferred to and processed there.
Retention
- Check-in history is pruned to your plan's window — currently 14 days (Free) or 90 days (Pro).
- Account and monitor data is kept while your account is open. Deleting your account (Settings → Danger zone) removes your account, monitors, and check-in history from our database and deletes your user record at Clerk. Provider logs and backups may persist for a short period afterward.
Your rights
Depending on where you live — for example the EEA or UK under the GDPR, or California under the CCPA — you may have the right to access, correct, export, or delete your personal data, and to object to certain processing. You can do most of this yourself in Settings; for anything else, email [email protected] and we'll respond within a reasonable time. You may also complain to your local data-protection authority.
Children
illari isn't directed to children and isn't for anyone under 16, or the age of digital consent where you live.
Changes
We may update this policy from time to time. When we do, we'll post the new version here and change the date above. Changes take effect when posted; please check back periodically.