Effective and last updated: October 26, 2026
1. Who operates FinnBets
FinnBets Social is operated by FinnBets LLC, South Carolina, United States. This notice describes how we collect, use, disclose and retain information when people visit or use finnbets.app and related FinnBets Social features. For privacy questions, contact justinpeterson@finnbets.company.
2. Information we process
Account and profile: email address, account identifiers, login/authentication records, username and display name, profile and cover images, bio, and information you choose to add to your profile.
Community activity: posts, text, photos and videos you upload, predictions and polls, comments, reactions, following and other connections, public chat activity, direct messages, creator applications, subscription-only interactions, moderation reports and blocked or muted account records.
Payments and creator onboarding (when used): creator plan details, subscription amounts and status, transaction and billing identifiers, subscription-entitlement information, and records needed for payment support. Stripe handles payment processing and may collect card, bank, identity, tax or payout-verification details under its own privacy terms. FinnBets receives payment status and related limited billing information; we do not need your full card number to provide subscription access.
Optional support contributions: If you voluntarily send money to FinnBets LLC using the Venmo QR code, Venmo processes the transaction under its Privacy Statement. FinnBets may receive the sender information, memo, amount and transaction record Venmo shares with recipients and use those details for bookkeeping, fraud prevention and support. Contributions do not link your Venmo account to your FinnBets profile automatically.
Technical information: IP address, browser/device type, approximate region derived from technical data, referral and page-usage information, error and security logs, and browser storage or cookies needed for sign-in, preferences, performance and abuse prevention. We may also receive communications you send to support.
3. Why we use information
We use information to authenticate members, operate accounts and profiles, publish community activity according to visibility settings, deliver messages and notifications, manage polls and subscriptions, process payments and creator access, provide support, investigate abuse, enforce community rules, maintain security, troubleshoot errors, improve performance and comply with legal obligations. Where required, we seek consent for particular processing or cookies.
4. What other people can see
Public-facing profile information, public posts, selected comments, member names and public community chat may be visible to nonmembers as well as signed-in members. Other activity may be limited to signed-in members, followers or paying subscribers based on the particular feature and its access rules. Other people may capture or share information you make public. Direct messages are stored in Supabase with Row Level Security (RLS) and are NOT end-to-end encrypted. RLS limits ordinary account access to authorized participants; it is not end-to-end encryption. Access controls restrict ordinary member access, but authorized service personnel or providers may access data where necessary for support, security, legal requests or abuse investigations. Do not share passwords, seed phrases, private keys, full payment-card details or other secrets in messages or posts.
5. Service providers and third-party embeds
We use Supabase for authentication, database and file storage; Vercel for website hosting and delivery; and Stripe for creator payments and payout onboarding where available. These services process information as needed to provide their functions under their respective terms and privacy policies. We may disclose relevant information to service providers, professional advisers or authorities when necessary for service operation, fraud prevention, payment disputes, valid legal obligations or protecting people's rights.
Sports widgets: Where you load our SportBusy scores or schedules, SportBusy may receive your IP address, device/usage information and cookies or similar identifiers. See the SportBusy Privacy Policy. Closing or hiding the sports view stops loading that view, though information already collected by a provider may remain under its policy.
Market widgets: Where TradingView displays are loaded, TradingView may receive your IP address, displayed symbol, embedded page information and device/usage data, and may use cookies. See the TradingView Privacy Policy. Use the site's Hide prices option to unload those market displays where available. We do not intentionally supply your FinnBets password, authentication token or direct-message content to these embeds.
Tennis widgets: SportScore receives IP address and device information when its tennis embed loads. Its own privacy practices apply. Email: authentication and support email delivery services process addresses, message content and delivery information needed to verify accounts, reset passwords and answer requests. FinnBets Insights: we summarize platform activity, such as posts, reactions, followers and creator activity, for member/creator reports and restricted administrator reports. These are community activity summaries, not verified betting or brokerage performance.
6. Cookies and browser settings
Essential browser storage supports sign-in, security, interface preferences and your consent choice. Optional Vercel usage/performance analytics and third-party SportBusy, SportScore and TradingView embeds are disabled until you allow optional services. Choose “Essential only” to decline them or “Allow optional” to enable them; use “Cookie settings” in the footer to change your choice. Changing to essential-only reloads the page to stop optional scripts and embeds. Providers may retain information already received; withdrawing consent does not undo past lawful processing. Your choice is saved in this browser for up to six months. Browser settings can further restrict storage. Global Privacy Control causes optional services to remain disabled in that browser.
7. Retention and account deletion
We keep information for as long as reasonably needed to operate the service, secure accounts, meet legitimate support or moderation needs, and satisfy legal, accounting and payment obligations. When an eligible member deletes an account, we remove or disassociate active-service account data as supported by our systems. Deletion may require password verification and confirmed cancellation of ongoing billing; creators with active paid members or legacy billing issues may need assistance. Some payment, audit, abuse-prevention, legally mandated and backup records can remain for limited periods. Copies made by other users and data held by third parties may not be removable by FinnBets.
8. Privacy choices and requests
You can review and edit certain account/profile information, adjust available privacy or visibility settings, block or mute members, remove eligible posts, and request account deletion through the profile controls. You may also email justinpeterson@finnbets.company to request access, correction, deletion or other rights available under applicable law. We may verify the request, ask for enough information to locate an account, and explain where an exception applies. Billing cancellation and account deletion are separate steps when outstanding payment obligations exist.
9. Security, age limits and changes
We use access controls and service-provider security measures designed to protect data; no service can guarantee perfect security. Direct messages are not end-to-end encrypted. FinnBets accounts and member features are intended for people 18 or older. If you believe an underage person's information was submitted, contact us for review. We may update this notice as services, providers or laws change, showing the new effective date and giving additional notice or asking permission where required.
10. California privacy rights
Where the CCPA/CPRA applies to FinnBets and your request, California residents may request access to categories and specific pieces of personal information, correction, deletion, information about disclosures, opt out of sale or sharing for cross-context behavioral advertising, and limit qualifying uses of sensitive personal information. You may use an authorized agent, subject to legally permitted verification. We will not unlawfully discriminate for exercising these rights. The categories, sources, purposes and recipients are described above; we retain each category only as reasonably needed for those purposes.
FinnBets does not sell member account records for money. Third-party embeds may process identifiers under their own practices; our optional-service controls block those embeds unless allowed and honor Global Privacy Control by keeping optional services disabled. You can submit sale/sharing or sensitive-information requests to justinpeterson@finnbets.company. Rights and exceptions depend on applicable law; this notice does not assert that FinnBets meets every CCPA applicability threshold.
11. EEA / UK rights and international processing
Where the GDPR or UK GDPR applies, FinnBets LLC is the controller for its platform processing. Our legal bases, as applicable, are contract necessity for accounts, messages and subscriptions; legitimate interests in security, moderation, support and service improvement balanced against your rights; legal obligations for required records; and consent for optional services where required. You may request access, correction, erasure, restriction, data portability, object to processing based on legitimate interests, object to direct marketing, and withdraw consent without affecting earlier lawful processing. You may complain to your local data protection supervisory authority.
We and our providers may process data in the United States and other countries with different privacy protections. Where legally required, transfers require an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses. Contact us for information about the arrangements applicable to your data. We do not use community badges or Insights to make decisions producing legal or similarly significant effects solely through automated processing.
12. How to request deletion or exercise rights
Use You / Profile → Delete account, or email justinpeterson@finnbets.company with “Privacy request” and your request type. Include the email associated with your account; never send your password or identity documents unless we request necessary information through an appropriate secure process. We may verify identity and agent authority proportionately. If self-service deletion is blocked by billing or creator obligations, email us for assisted processing; that does not remove applicable privacy rights. We respond within the period required by applicable law and explain lawful extensions or exceptions. You may ask us to reconsider a denial and use applicable regulator complaint rights.
FinnBetsAI conversations
FinnBetsAI is an optional conversational feature powered by OpenAI. When you send a message, that message and a limited amount of recent conversation context are sent to OpenAI to generate a reply. FinnBetsAI does not automatically read community posts, direct messages, subscriber content or payment records. The API key is kept on the server, and requests ask OpenAI not to store the completion as an API application object; provider processing and retention remain subject to OpenAI’s terms and data policies.
If you enable “Save chats to my account,” recent conversation messages and their title, mode and update time are stored in Supabase. Row Level Security restricts ordinary member access to the owning account; authorized service personnel or providers may access information where necessary for service operation, security or legal obligations. Chats are not end-to-end encrypted. You can disable saving for new messages and delete a saved conversation using its delete control. Disabling saving does not delete conversations already saved. Account deletion removes chats linked to that account, subject to applicable backups and retention described in this notice. Request counts and conservative budget reservations may be retained for service limits, abuse prevention and cost controls. Do not send credentials or other sensitive information to FinnBetsAI.
