Privacy Policy

Last updated: October 19, 2026. Pre-launch draft — the connector is in development. Operated by Snowball IMN LLC, a New York limited liability company ("the Platform," "we"). Contact: [email protected].

1. What data flows where

• Creator identity (name, date of birth, government ID, tax details): provided by the creator in Stripe's hosted onboarding, goes to Stripe only. We never see or store ID documents. Stripe performs KYC; we store only the resulting account ID and capability flags ("can accept charges," "can receive payouts").
• Creator payout details (bank account): provided in Stripe's hosted onboarding, goes to Stripe only. We never see bank account numbers.
• Tip amounts, timestamps, tip counts: from the fan's tipping actions in Muse, into our transaction records and Stripe. Creators see their own totals; fans see their own receipts.
• Fan payment details: provided via Link, go to Stripe / Link only. No card data ever touches our servers. Under Link and Shared Payment Tokens, the agent initiates payment without seeing card details.
• Webhook event records (charge, transfer, refund, payout IDs): from Stripe webhooks, into our event log. Used for reconciliation and dispute evidence.
• Creator's optional integrations (Notion page, Slack channel): from the creator's own configuration, to the creator's chosen tools via our event contract — only what the creator configured.
• Fraud-detection signals (card fingerprints, dispute and early-fraud-warning records, rolling-reserve ledger entries): used to enforce velocity limits, self-tip and collusion holds, payout holds, and reserve releases.

2. Data minimization

We request and store only the data each action needs. We do not download inboxes, contact lists, or anything beyond what the tip-jar tools and onboarding flow require. Nothing is collected speculatively.

3. How we use data

• To route tips, split them, and pay creators.
• To provide receipts.
• To detect fraud, reconcile accounts, and respond to disputes.
• To emit webhook events to the creator's own configured tools.

We do not use tip or identity data for advertising, profiling, or any purpose outside operating the service.

4. No sale of data

We do not sell, rent, or trade personal data to anyone, for any purpose.

5. Sharing

We share data only with:

• Stripe, to process payments, verify identities, and issue payouts and tax documents (governed by Stripe's Privacy Policy).
• Meta / Muse, as required for the connector to function inside Muse (governed by Meta's policies and the connector's authorized scopes).
• The creator's own tools (Notion, Slack, CRM), only when the creator configures them, and only the event data needed.
• Law enforcement or regulators, only when legally compelled.

6. Retention

• Transaction and event records are kept as long as needed for accounting, tax, dispute, and audit purposes, then deleted or anonymized.
• KYC capability flags are kept while the creator's tip jar is active and removed when the account is closed, subject to legal retention duties.

7. Your rights — access and deletion

• Creators may request a copy of the data we hold about them, or request deletion, by contacting [email protected].
• Deletion removes our records; data held by Stripe remains subject to Stripe's retention and legal obligations (we cannot delete what we never held — we never held your ID documents or bank details).
• Some records (completed transactions, dispute evidence) must be retained for legal and accounting purposes even after a deletion request; we will tell you what was kept and why.

8. Changes to this policy

Material changes will be communicated to creators in advance and take effect no sooner than 14 days after notice.