Privacy policy

saycheese is run by Say Cheese Tips Ltd, a company registered in England and Wales (number 17376134), 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom. That company is responsible for the personal information processed to operate saycheese. Reach us at support@saycheese.tips.

If you connect a YouTube account, saycheese uses YouTube API Services. We ask Google for one read-only permission (youtube.readonly) and use it for one thing: to learn which YouTube channel is yours, so tips sent from or to that channel reach the right person. We store the channel id, its public name and picture, and the sign-in token Google gives us.

We read public comments on public videos using our own server key. That does not use your Google account or your permission. This integration does not post, edit or delete YouTube content. We use channel information and relevant public comments for the connected-account and tipping features, not advertising or sale of Google user data. Service providers can process the information needed to deliver those features, as described below. YouTube tipping remains in testing.

Access tokens are used by the server-side integration and are not published on creator pages. Saycheese's use of information received from Google APIs must adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to develop, improve, or train any generalized artificial intelligence or machine learning models.

You can disconnect YouTube in your dashboard and revoke saycheese's access directly from your Google account at myaccount.google.com/permissions. Google's own privacy policy is at policies.google.com/privacy.

To request deletion of stored Google account data, contact support@saycheese.tips. Revoking access does not by itself delete separate payment records we must retain, or remove the original content you posted on YouTube.

We keep it to what the product needs:

• Account and social information. Handles, platform identifiers, display names, profile pictures, profile links and connection permissions. Where a platform requires them, we also store access or refresh tokens to operate the connection. Several socials can belong to the same account, which can both send and receive tips.
• Your email address, including an address supplied through Stripe, for account and service messages.
• Tip records. Amount, which post, which creator, when, and what happened to the tip: completed, pending, declined, refunded or expired. This includes payment and account references, privacy choices, payment authorization records and relevant recovery or dispute information.
• Messages. Conversations between a creator and a supporter, which exist only after a completed tip connects them.
• Creator profiles, campaigns, follows, notification preferences and moderation settings.
• Live alert settings, selected voices, playback records and generated tip audio when those features are used.
• Support requests, replies, optional contact details and uploaded PNG, JPEG or WebP screenshots.
• Technical basics. Session cookies, IP addresses, device or push-notification identifiers where applicable, security and two-factor records, and operational logs.

We receive information from you, the socials you connect, supported platform APIs or bot events, Stripe, and activity in the service. Tip detection uses the relevant post, reply, chat or channel information made available through the supported integration. Some of that information, such as a public profile or comment, is already public. Linking an account does not give saycheese unrestricted access to all of its private data.

Full card numbers and security codes go directly to Stripe through its payment forms, not to saycheese's servers. We use payment-method and customer references and can receive limited card information, such as brand and last four digits, to identify the saved method. Saving a tipping card is separate from setting up a payout bank account.

Stripe collects and reviews the identity documents required for creator payouts. Saycheese does not collect, store or review those documents. We do receive connected-account information, verification status, outstanding requirement names and payout status so we can show what remains to be completed and operate payouts. Stripe explains its own processing in its privacy policy.

We use the data above to:

• Run your account, match eligible tip replies, process payments and manage creator payouts.
• Deliver enabled receipts, public thank-yous, live alerts, speech, messages and notifications.
• Detect abuse, investigate disputes and protect accounts and payment processing.
• Answer support requests, including automated assistance and human review.
• Keep records required for accounting, legal obligations and payment investigations.

Where UK or EU data protection law applies, core account, tipping and requested support processing is necessary to provide the service under our contract. Security, abuse prevention and operational troubleshooting serve our legitimate interests in protecting users and keeping the service reliable. Legally required records are kept to meet legal obligations. Where a feature relies on consent, we explain it when asking for that consent. Payment authorization is not blanket consent for unrelated uses of personal information.

We cannot enable a requested account, social or payment feature without the information it needs. Public profile extras, optional notifications and providing screenshots to support are choices, not conditions for every use of the site.

A 🧀 comment keeps the visibility of the platform or chat where you posted it. Public comments stay public; a saycheese privacy option cannot hide or delete them on the original network. The recipient can access the transaction information needed to manage received tips, including the message and amount. Anonymous presentation does not make the payment anonymous to saycheese or Stripe.

Creator pages may show your supporter name, comment and individual tip amount. Choosing “Send anonymously” hides your name on the creator page. An individual amount is shown only when the creator has enabled public amounts and you have not chosen “Hide the amount.” Supporter counts appear only when the creator enables them. Your card and bank details are not displayed on creator pages.

Similar public information may appear on shared tip links, receipt cards, social replies and live alerts. Selecting anonymity does not remove identifying words you include in a message, nor does hiding the amount erase an amount you wrote in the original public comment. Creators and viewers may record or reshare public material; changing a setting cannot recall copies already made outside saycheese.

When a creator uses text-to-speech, the configured read-aloud text can include the permitted supporter name, amount and tip message. We send that text to Replicate, using its hosted MiniMax speech model, to generate audio. We retain generated clips for delivery and replay. Applicable anonymous-name, hidden-amount and read-aloud settings determine the text supplied to the speech feature.

Creators can broadcast tip alerts and audio through their streaming setup, including OBS or X Spaces. This is a public presentation feature, not a private voice message. Do not put confidential information into a tip message. A change to visibility cannot remove audio already broadcast or recorded by somebody else.

Where supported and authorized, saycheese can publish receipt replies, creator thank-yous or notices that invite an unregistered recipient to claim a tip. Some automatic reply options start enabled, but posting also requires the relevant platform permission and settings. Review those controls in your dashboard. Disconnecting a platform or disabling an automatic reply does not delete a post already published there.

Our support workflow stores the request, reply history, supplied contact information and attachments. It may use an AI service through OpenRouter and its selected model provider to draft answers and identify matters needing human review. This can send the subject, message text, screenshots and a limited account label to that service. Support staff and authorized operators can review relevant records to investigate the issue.

Automated answers can be wrong. Ask for human review of a payment or account issue when needed. Do not send full card details, passwords, sign-in codes, identity documents or secret keys through chat, email or screenshots. Use Stripe's secure forms for its verification requirements.

• Stripe, to process payments and payouts.
• Hosting and database providers, including Vercel and Supabase, to store and operate the service.
• Connected social networks and their APIs, for the connections and replies you use.
• Speech and AI-support services described above, for the requested audio or support workflow.
• Configured email and notification delivery providers, for service messages and enabled notifications.
• Authorized staff and operators, for support, security, payment review and service operation.
• Authorities, when the law genuinely requires it.

We do not sell your data. We do not share it with advertisers.

We use cookies to keep you signed in, secure account connections and remember necessary session information. Browser storage can also keep interface preferences and recovery state. Stripe and social sign-in services may use their own necessary cookies or storage when you interact with their forms. We do not use cookies for third-party advertising.

• Payment, payout and authorization records: retention depends on accounting and tax obligations, payment disputes, fraud investigations and legal claims, including after account closure where necessary.
• Account and connection information: for operating the account and handling disconnection, closure or deletion requests, subject to necessary retained records.
• Messages, support tickets and attachments: according to the need to provide the conversation, resolve the case and keep evidence of disputes or service decisions.
• Generated audio and technical logs: according to delivery, replay, security, troubleshooting and investigation needs.

Closing an account or disconnecting a social is not a promise that every record, attachment or backup disappears immediately. To ask about a category's retention or request deletion, contact us. Copies held by Stripe, the original social network or another independent service follow that service's own policy and legal duties.

You can ask us what we hold about you, ask us to correct it, or ask us to delete it. Email support@saycheese.tips and we will assess your request, verify identity where appropriate and explain any lawful limitation. Some records, mainly payment and accounting records, must be kept for the required period even after a deletion request.

Depending on the applicable UK or EU law and the basis for processing, your rights include:

• Access to your data, and a copy of it in a portable format.
• Correction of inaccurate data.
• Erasure, where no legal duty requires us to keep the data.
• Restriction of processing, and objection to processing based on our interests.
• Withdrawal of consent, where processing is based on consent.
• A complaint to your local supervisory authority, at any time.

You can object to processing based on our legitimate interests. You can also withdraw consent for consent-based processing without affecting its earlier lawfulness. Contact support to exercise these rights. You may complain to the UK Information Commissioner's Office or your relevant local data protection authority without contacting us first.

Our service providers and connected platforms may process information outside your country, including outside the UK or European Economic Area. Transfers subject to data protection law require an appropriate legal mechanism, such as an applicable adequacy decision or approved contractual safeguards. Contact support@saycheese.tips for information about the applicable destinations and safeguards, and how to obtain a copy.

Rules match eligible replies to accounts, check payment and account status, and can block or hold processing for duplicate requests, security or financial review. Stripe and your bank also perform their own payment checks. If a restriction seems wrong, contact support for review. A generated support answer is not a final determination of your legal rights or a guarantee that a payment or refund succeeded.

saycheese is for adults. You must be 18 or older, and we do not knowingly collect data from anyone younger. If you believe a minor is using saycheese, tell us and we will close the account.

If we change this policy in a way that matters, we will tell you before the change takes effect.

Privacy questions and requests go to support@saycheese.tips. Postal mail goes to Say Cheese Tips Ltd, 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom.