Sub-processors
Last updated: July 11, 2026
MeowTarot runs on a small set of infrastructure providers. This page lists each sub-processor, what it does for us, and what data (if any) passes through it.
| Sub-processor | Purpose | Data handled | Location |
|---|---|---|---|
| Cloudflare, Inc. | Website hosting, content delivery (card artwork), and serverless compute for our chat-platform apps (Slack, Discord) | Standard web request metadata (IP address, headers) processed transiently to serve responses; our chat apps store no user data and keep no logs of message content | United States / global edge network |
| Supabase, Inc. | Account database and authentication for signed-in meowtarot.com accounts (reading history, deck ownership) | Account email, authentication identifiers, and app data (readings, decks) for users who choose to create a meowtarot.com account | United States (AWS) |
| Google LLC | Optional OAuth sign-in provider for meowtarot.com accounts; site analytics (Google Analytics) | OAuth identity for users who choose Google sign-in; standard analytics telemetry on the website | United States / global |
Scope note for our Slack app: MeowTarot for Slack is stateless. It requests a single scope (slash commands), stores no tokens, no messages, and no user data, and its only sub-processor is Cloudflare, which executes the app and serves card artwork. Supabase and Google are used solely by the meowtarot.com website for optional accounts.
Questions about this list: [email protected]. See also our privacy policy.