Privacy Policy
Last updated May 26, 2026
This page describes what data AppMate collects, why, where it lives, and how you delete it. We aim for honesty over legalese.
Two roles to keep straight:
- Admins — people with an AppMate account who configure flows. We are the data controller for admin data.
- End-users— people who visit a cancel flow or waitlist landing page that an admin built with AppMate. We process their data on the admin's behalf (we're the processor; the admin is the controller).
What we collect — admins
The minimum needed to operate the dashboard:
- Account — email, name (if you set one), hashed password (we use bcrypt — we never see the plaintext), passkey credentials if you registered any.
- Sessions — HTTP-only cookie holding a signed JWT, IP address at sign-in time, user-agent string. Used for session validity and to alert you to suspicious logins.
- Configurations— the flow / waitlist JSON blobs you author. These are the “product” content you create — yours.
- API tokens— the hash of any tokens you issued, plus the label you gave them. We can't recover the cleartext value after creation, only revoke them.
What we collect — end-users
When someone visits a cancel flow or waitlist page you set up:
- Session metadata— a randomly generated session id, timestamps, which screens were visited, which buttons were tapped, which reason was chosen. No name, no email, no device identifier — just “someone tapped Continue at 14:02 UTC from the ‘Too expensive’ response.”
- Waitlist email — only when an end-user voluntarily submits an email through your waitlist form. We store it against your app so you can export it. Source IP is kept for 30 days for spam protection.
We don't set any cross-site cookies, run any third-party analytics scripts, or load any tracking pixels on the public flow / waitlist surfaces.
Third-party processors
To run AppMate we rely on a small set of vendors. Each only receives the data needed to do its job:
- Postgres host — stores all admin and end-user data described above. Data is encrypted at rest and in transit.
- Coolify— runs the application servers. Sees HTTP traffic in transit but doesn't persistently store application data.
- Resend — sends transactional emails (invites, password resets, signup confirmations). Receives the recipient email + the message body.
We don't share, sell, or rent your data to anyone outside this list. We don't train AI models on your data.
How long we keep it
- Admin account data — for the life of your account; deleted within 30 days of account closure.
- Flow / waitlist configs — same as account.
- End-user session events — 180 days, then aggregated into anonymized counts and the raw rows deleted.
- Waitlist signups — until you delete them, or until the parent app is deleted.
- Server logs — 30 days.
Your rights
You can request a copy of all data we hold about your admin account, correct anything inaccurate, or delete the whole account and everything tied to it. Email hello@appmate.cloud — we aim to respond within 7 days.
End-users on flows you built should contact you first (you're the controller); we'll route any direct requests we receive to you.
Children
AppMate is not intended for children under 13 (or 16 in the EU). We don't knowingly collect data from children. If you believe a child has signed up, email hello@appmate.cloud and we'll delete the account.
Changes to this policy
We'll update this page when material things change and email admins at least 14 days before any change that reduces user rights. The “Last updated” date at the top reflects the most recent edit.
Contact
Anything privacy-related: hello@appmate.cloud.