Privacy Policy
Short version: we keep the minimum needed to run escrow, we never sell data, there are no ads or third-party trackers, and all card details go directly to Stripe — we never see or store your card number.
1. What we store
- Account: name, email, and sign-in credentials (password hash, passkey credentials, Google link if you connect it).
- Groups: listings, pledges and amounts, comments, disputes, and delivery notes — everything needed to hold escrow and resolve disputes.
- Payments: Stripe customer and payment IDs so we can charge, refund, and reconcile. No card numbers, ever.
- Agent tokens: if you enable the agent API, a token tied to your account.
- Support emails you send us.
2. Payments
Checkout and card processing are handled entirely by Stripe. Your card and bank details go directly to Stripe and are subject to Stripe's privacy policy. Planpool only receives payment IDs, amounts, and card metadata (such as debit vs. credit) needed to enforce its payment rules.
3. What we do not do
We do not sell or rent your data, run ads, or embed third-party analytics or trackers. Data is shared only with the infrastructure that runs the service (Cloudflare for hosting, Stripe for payments) and only as needed to operate it.
4. Cookies
Planpool sets a session cookie to keep you signed in, a last-sign-in-method cookie to highlight your usual option, and a short-lived credential-reset notice cookie. No tracking cookies.
5. Retention and deletion
Escrow records are kept while a group is active and as long as needed for disputes and accounting afterwards. Email a@amos.codes to request an export or deletion of your account data; Stripe retains its own payment records under its policy.
6. Security
Passwords are hashed, passkeys are origin-bound, and traffic runs over HTTPS. No system is perfectly secure; report suspected issues to a@amos.codes.
7. Changes
Material changes will be posted here with a new date. Continued use after changes means you accept them.