Zam! keeps visible
- The public providers used for support, billing, auth, hosting, and sign-in.
- The fact that email providers can process email delivery metadata.
- The support limit that Zam! cannot decrypt Cloud Sync without your recovery key.
Trust & Privacy Stack
Zam! should be clear about the outside services that make the app, billing, support, and website work. This page is a plain-English stack disclosure, not a replacement for the Privacy Policy.
| Provider | Used for | What it may process |
|---|---|---|
| Proton Mail | Public support email. | Email contents, headers, sender and recipient addresses, timestamps, delivery metadata, IP-related metadata, country or region hints, user agent or device hints, and security or abuse-prevention records needed to deliver and protect mail. |
| Stripe | Premium billing, checkout, invoices, billing portal, and subscription state. | Payment method details, invoices, subscription status, customer records, dispute or fraud-prevention metadata, and legally required billing records. Zam! does not store full card numbers. |
| Supabase | Authentication, account systems, and Cloud Sync storage. | Account email or OAuth identity metadata, authentication events, signed-in session metadata, app-owned account records, and encrypted Cloud Sync vault blobs. Zam! does not store readable synced budget contents. |
| Cloudflare | Website delivery, security, edge routing, aggregate web analytics/Insights, and feedback endpoint hosting. | Request metadata, IP-related security metadata, region hints, user agent or browser/device hints, aggregate traffic/performance signals, rate-limit and abuse-prevention records, and delivery logs needed to serve and protect the site. |
| Google / Apple | OAuth sign-in where available. | Sign-in identity metadata needed to authenticate the account. Apple sign-in remains paused until enabled. |
Zam! public mailboxes are hosted with Proton Mail. Email is a third-party support channel and is separate from encrypted Cloud Sync budget storage.