Privacy policy
Last updated November 2, 2026.
PizzaPug LLC operates SideBets. This policy explains how our iPhone app, Android app and website handle information when you create an account, use social challenge and Toolkit features, view advertisements or contact us. SideBets is for friendly social challenges and shared records; it does not permit real-world money or prizes. Contact us at dev@sidebets.me about this policy or your data.
Information you provide
- Your account: email address, phone number if you use phone sign-in, account identifier, display name, username and any profile photo you choose to add. Our authentication provider processes sign-in credentials. If you use an available Apple or Google sign-in option, that provider supplies account information needed to sign you in.
- Your activity: challenge terms, participants, responses, outcomes, scores, receipts, groups, friendships, messages, blocks and other content you choose to enter. Golf and toolkit features can also store your selected courses, tees, measurements, wheel choices and draft settings. Timed physical challenges, such as Wall Sit, Plank-Off and Grip Challenge, can store submitted exercise-attempt durations with the challenge; a standalone local stopwatch run is separate.
- Photos: profile images and challenge evidence you choose to upload. Evidence photos can contain personal information; share only what is needed for your challenge.
- Support requests: your contact information and the information you send when asking for help or exercising privacy choices.
Device information and local storage
We use session storage and local app data to keep you signed in, remember preferences, display saved information and retry pending work. Our hosting and service providers process connection and operational information, such as IP addresses and request information, to deliver and protect the service.
Standalone Toolkit measurements store optional local labels and saved readings on your device for your signed-in account. On Android, unfinished names and distance entries are also stored before Save. Readings include distance, method, recorded time and quality details, including reported GPS accuracy or a measured reference length when used. Saved readings do not contain raw tee or ball coordinates or measurement images. GPS points and measurement previews are temporary app state. Android camera measurement uses a preview from an installed camera app, whose photo storage follows that app’s settings.
Archive keeps read-only Toolkit history. Records labelled On this device are local snapshots; records labelled Synced, including archived scorecards and brackets, remain on the server and are loaded using your current access. Existing collaborators or bracket members can retain access under those features’ rules. Optional labels and other entered text are not anonymous data.
Shared-bet GPS and proof photos use separate flows. Confirmed GPS positions are stored, with the tee shared with authorized participants and the ball position stored privately. Proof photos can upload to SideBets when selected or captured, before you submit the result or challenge. They become attached through that feature’s submission flow.
When notifications are configured, a device notification token helps deliver alerts to your account. You can manage notification permission in your device settings. Android photo selection uses the system picker rather than access to your entire photo library.
Some Android versions may offer optional Firebase Crashlytics reporting. It is off by default and requires an available reporting option and your consent. Reports can include exception messages and device, operating-system and installation information; they are not guaranteed to exclude every piece of app data. Turning reporting off prevents future sends, but cannot recall reports already sent. If your version does not offer this setting, optional reports cannot be enabled.
Why we use information
We use information to provide your account and requested features, maintain shared challenge history, communicate results and notifications, respond to support requests, and protect accounts and the service. SideBets does not process payments or hold money for challenges. We also use advertising-related information as described below.
Advertising and Google AdMob
SideBets uses Google AdMob to display banner and full-screen advertisements in the mobile apps. Google’s advertising and consent software communicates with Google when these features run. This processing is separate from information you enter into a challenge.
Advertising software can process your IP address and approximate location, device and app identifiers, advertisements shown, ad interactions, and diagnostic and performance information. On Android, this can include advertising and app-set identifiers and, where applicable, identifiers related to signed-in device accounts. On iPhone, available identifiers depend on device settings and permissions. Google uses advertising-related information for ad delivery and measurement, analytics, service improvement and fraud prevention. The information processed depends on the platform, SDK version, permissions and applicable choices.
Ad choices and messages vary by location and available configuration. Where a privacy message is required, the app uses Google’s consent software before requesting ads. When available, use Ad privacy options in the app’s settings to review or change your choices. Your device also provides advertising-identifier and privacy controls. A choice limiting personalized ads does not necessarily stop all information processing needed to deliver ads, measure performance or prevent fraud.
Changing a setting affects future processing; it does not recall information already sent. Advertising providers may retain records under their own policies. Learn more in Google’s Privacy Policy and how Google uses information for advertising. If you open an advertiser’s website or app, that service’s privacy practices apply.
Apple and Google sign-in
If you choose Apple or Google sign-in, the provider authenticates you and supplies the account information and authentication tokens needed to sign in to SideBets. Depending on the provider and your choices, this can include your name, email address and account identifier. Apple may supply a private relay email address. SideBets uses this information with its authentication provider to establish and maintain your account.
Google sign-in does not request access to your Gmail messages, Google Drive files or Google Contacts. Google’s sign-in software can also process technical, device and usage information under Google’s Privacy Policy. Apple’s handling is described in Apple’s Privacy Policy. Signing out or deleting SideBets does not by itself erase the records these providers maintain.
Who can receive information
Other users can see information made available through the features you use, including profiles and discovery, conversations, groups and challenges they can access. Attached evidence can be viewed by authorized participants. Sending content to another person or using a share action makes that content available to its recipients.
Supabase provides account authentication, database, file storage and realtime services. Google/Firebase supports Android notifications and, where enabled with consent, crash reporting. Apple and Google handle their respective sign-in options. Google also provides mobile advertising and consent services as described above. Our website hosting and delivery services and email provider process information needed to operate the site and answer messages. These providers may process data in countries other than your own.
Access controls restrict private records to authorized users. Network connections use encrypted transport. These protections do not prevent recipients from retaining information you share with them.
Retention and account deletion
We keep account and feature data while it is needed to operate your account and preserve the shared records described below. Account deletion does not erase every historical record. See Delete your SideBets account for what the current deletion process removes, what can remain and how to request a review.
The signed-in deletion-request workflow stores an account identifier, request/review status and request/update dates for processing and checking the request. It keeps this minimal record separately from the live profile so cleanup cannot silently erase a pending request. Saving a request alone does not erase the account. A separate final deletion confirmation starts removal and records progress, a hashed recovery capability and its completion status. The device keeps the private recovery capability until cleanup is acknowledged; it is not placed in links or shared records. Request records do not yet have a fixed automatic expiry and can be reviewed with other retained information.
Local Toolkit work and history have no fixed automatic expiry. Signing out retains them. When account deletion is confirmed in the mobile app, the app attempts to clear that account’s local Toolkit work, history and pending snapshots on that device. Follow the app’s retry guidance if cleanup is interrupted; some storage failures require you to keep the app open until retry succeeds. The iPhone app retains a small account deletion status record to block delayed writes from restoring deleted work. Other accounts and unattributed legacy device setups are preserved. This device cleanup does not establish removal from other devices, backups or provider records.
For supported Apple sign-in flows, an Apple refresh token is encrypted on the server and used to revoke authorization when you delete your account. It is removed after revocation. Older accounts with no saved token receive Apple removal instructions after account deletion.
Unfinished shared challenges close without a winner and reserved SideBucks are returned under existing rules. Identity-labelled names and contact fields are replaced in preserved shared records, while completed scores and outcomes remain. Opaque identifiers, privacy-change proof digests, free text and evidence under a moderation hold may remain. Shared historical records and technical or security records may remain after account deletion. Records without a scheduled expiry can remain until reviewed for removal; we do not promise that all data is removed after a fixed number of days. Provider backups and operational logs may follow separate retention schedules. Contact us for a review of information relating to you.
Your choices and requests
You can edit your profile, manage relationships and device permissions, sign out, and request account deletion. Depending on where you live and the law that applies, you may have rights to access, correct or delete personal information, obtain a copy, or limit certain uses, including targeted advertising. Use available ad privacy controls for advertising choices. You may also contact us to make a request or ask us to review a response. For access, correction, deletion or other privacy questions, email dev@sidebets.me. A request starts review and is not confirmation of completed deletion. Ask us for the status or timing of your request. We may need to verify account ownership before releasing or deleting information.
If you believe a child has provided personal information that needs review or removal, contact us at the same address. This policy does not establish a store age rating or authorize use contrary to the service’s applicable rules.
Policy changes
Updates will appear on this page with a revised date. Contact us if you have questions about a change or how it affects your account.