Privacy policy

Last updated 19 September 2026

Draft — must be reviewed before launch. The controller details below are placeholders and the text has not been checked by a lawyer. Replace this box and the placeholders before the app is submitted for review.

Who is responsible

Canary is operated by [LEGAL NAME], an individual entrepreneur registered in Georgia, [REGISTERED ADDRESS]. For any question about this policy or your data, contact contact@jimapps.dev.

What Canary accesses

Canary is a monitoring tool. It reads status information in order to tell you when something has stopped working. Specifically:

What Canary does not access

Canary holds read permissions only. It cannot post, send, modify settings or delete anything in your account.

Why

The sole purpose is to detect failures and notify you. Your data is not used to train models, build profiles, or generate analytics beyond what is shown in your own account. It is never sold and never shared with advertisers.

How long it is kept

DataRetention
Access tokensUntil you uninstall, then deleted
Check results and uptime history13 months, then deleted
Alert delivery logs90 days
Account and contact detailsUntil you uninstall, then deleted within 30 days

Uninstalling the app revokes Canary's access immediately. Stored data is deleted within 30 days. To have it deleted sooner, write to contact@jimapps.dev.

Where it is stored

Data is stored on Cloudflare infrastructure. Access tokens are encrypted at rest. All traffic is over TLS.

Sub-processors

ProviderPurpose
CloudflareHosting, storage and delivery
[EMAIL PROVIDER]Sending alert emails

Your rights

You can request a copy of the data held about you, ask for it to be corrected, or ask for it to be deleted. Requests go to contact@jimapps.dev and are answered within 30 days. If you are in the EU or UK, you also have the right to complain to your local data protection authority.

Changes

If this policy changes in a way that affects what is collected or how it is used, existing users are notified by email before the change takes effect. The date at the top always reflects the current version.