Privacy Policy

Alertzky · Effective date: June 25, 2026 · Last updated: July 15, 2026

1. What Alertzky does

Alertzky is a wellness check-in app. The person being monitored installs the app and adds the names and contact details (email address, or a phone number for SMS) of contacts they want notified if they go quiet. If the monitored person does not check in within their configured window, Alertzky sends a reminder to them and, if they still do not respond, an alert to their chosen contacts by email or SMS.

2. What we collect and why

• Email address and password (optional) — used to create and authenticate your account. You can use Alertzky without signing up; an anonymous, device-only profile is created automatically. Adding an email and password lets you recover your account, use it on another device, and add more contacts.
• Display name (optional) — used to personalise your experience and to identify you in alert emails sent to your contacts.
• Contacts' names and email addresses — stored to know who to notify if you go quiet. Contacts are added by you and are only used to deliver wellness alerts on your behalf.
• Contacts' phone numbers (optional) — only if you choose to alert a contact by SMS instead of email. Stored to send that contact an alert text message via Twilio, and used for nothing else. You should only add someone as an SMS contact if they have agreed to receive alert texts.
• Last-seen timestamp — updated each time you open the app or tap "I'm OK". This is the signal the watchdog evaluates.
• Check-in log — a record of each check-in (time and source: app open or manual tap). Used to evaluate your silence window.
• Expo push notification token — obtained after you grant notification permission. Used to send you check-in reminders. Stored on our server so the watchdog can reach you.
• Monitoring settings — your configured check-in window, reminder buffer, quiet hours, and timezone. Used to evaluate silence and schedule alerts correctly.
• Anonymous usage analytics — aggregated, anonymous events (e.g. "checked in", "completed onboarding") to understand how the app is used and improve it. These are not linked to your identity, contain no personal information, and you can turn them off in Settings → Privacy.
• Crash diagnostics — if the app crashes we collect technical data (device model, OS version, and the error/stack trace) to find and fix bugs. We do not attach your identity or personal data to crash reports.
• Feedback you send — if you use "Send feedback" in the app, your message (with your account email if you have one, plus the app version and platform) is emailed to the developer so we can respond and improve the app.

3. How we use your data

All data is used solely to operate the wellness-alert service:

• To evaluate whether you have checked in within your configured window.
• To send you a push notification or email reminder when your window is approaching.
• To send alerts (by email or SMS) to your chosen contacts if you do not respond to the reminder.

We do not sell, rent, or share your data with third parties for advertising or any purpose other than delivering the service described above.

4. Who sees your contacts' data

Your contacts' names, email addresses, and any phone numbers are stored in our database (Supabase, hosted on AWS). They are accessed only by the server-side watchdog function to send alerts — email via Resend (our email delivery provider), or SMS via Twilio for contacts you choose to alert by text. Your contacts receive a message that tells them who added them and how to opt out.

Contacts can opt out of future alerts at any time by clicking the unsubscribe link included in any alert they receive.

5. Third-party services

• Supabase (supabase.com) — database, authentication, and server-side functions. Data is stored in the AWS region chosen at project creation.
• Resend (resend.com) — transactional email delivery for alert and reminder emails.
• Twilio (twilio.com) — SMS delivery for alerts sent to contacts you choose to notify by text message.
• Expo (expo.dev) — push notification delivery infrastructure.
• PostHog (posthog.com) — anonymous product analytics. No personal information is sent; opt out in Settings → Privacy.
• Sentry (sentry.io) — crash and error diagnostics, to find and fix bugs.

6. Data retention

Your data is retained for as long as you have an account. When you delete your account (in-app via Settings → Delete account, or by requesting deletion), all of your data is permanently deleted immediately, including your profile, monitoring settings, contacts, check-in history, and alert records.

7. Security

All data is transmitted over HTTPS. Passwords are hashed by Supabase Auth and never stored in plain text. Your session token is stored in your device's secure keychain (iOS Keychain / Android Keystore). Server-side access is restricted by row-level security — each user can only read and write their own data.

8. Children's privacy

Alertzky is not directed at children under 13 (or under 16 in the EU). We do not knowingly collect personal information from children.

9. Your rights

You may at any time:

• Access or correct your data by updating it in the app.
• Delete your account and all associated data via Settings → Delete account.
• Opt your contacts out — contacts can unsubscribe via the link in any alert email, or you can remove them from the app.

For any other privacy requests or questions, email us at grerkk@gmail.com.

10. Changes to this policy

We may update this policy from time to time. The "Last updated" date at the top of this page reflects the most recent revision. Continued use of the app after a change constitutes acceptance of the updated policy.

Contact

Alertzky
grerkk@gmail.com