Pilot privacy notice · 7 October 2026

Only the context
the conversation needs.

Fat Cat helps subscription businesses manage cancellation conversations. The business you subscribe to chooses its offers and controls its customer relationship. Fat Cat records the conversation, available actions, customer decision and later billing outcomes.

What is stored

Merchant account identifiers, organization membership, brand settings, approved offer limits, Stripe customer and subscription identifiers, plan and renewal metadata, conversation text, decisions, and payment-event amounts. Fat Cat uses Supabase for authentication and storage. Merchant API keys and customer access tokens are stored as hashes. Stripe restricted credentials and webhook secrets are encrypted on the server.

Payment information

Fat Cat does not request or store raw card details. Stripe continues to hold payment methods. Do not enter card numbers, account numbers or private credentials in a conversation. Fat Cat attempts to redact recognizable payment details before storing a message.

Conversation processing

When configured, an external conversation model receives your message and the merchant’s style settings to acknowledge your cancellation reason. It does not receive Stripe credentials or card data and cannot set offer terms. If it is unavailable, Fat Cat uses guided responses.

Merchant AI connectors

If a merchant authorizes ChatGPT, Claude or another OAuth client, that client can request approved offer rules, limited subscription context, outcome summaries and negotiation previews for that workspace. Its own privacy terms apply to information returned to it. No billing credentials, names or email addresses are returned by these tools. Revoke the connection in Integrations. The connector cannot act as a shopper or approve billing.

Measurement and model development

Fat Cat records offer choices and 30-, 60- and 90-day outcomes. A merchant may enable a randomized group that uses the normal cancellation experience. Decision-model exports are limited to approved structured features and outcomes; raw conversations and payment credentials are excluded.

Access and deletion

For a customer request, contact the subscription business through its normal support channel. Merchants can revoke Fat Cat integration keys and ask the Fat Cat operator to remove the workspace and its conversation records. Billing audit records may need separate handling. Pilot data should be synthetic until operator contact details, retention schedules and commercial data-processing terms are finalized.