Privacy Policy

1. Introduction

This Privacy Policy explains how AlgoSwish LLC ("AlgoSwish," "we," "us," or "our") collects, uses, discloses, stores, retains, and protects information when you use the AlgoSwish mobile application, website, and related services (collectively, the "Service").

AlgoSwish is a sports analytics and research platform. We are not a sportsbook, gambling operator, or wagering service, and we do not process, place, or facilitate bets.

2. Scope

This Policy applies when you browse or use the Service, create an account, sign in with email, Google, or Apple, purchase or restore a subscription, contact support, or use settings and the Bet Tracking feature.

3. Information We Collect

Account information

We may collect your email address, display or profile name, authentication identifier, account status, sign-in method, and account lifecycle timestamps. Firebase Authentication manages your email address and display name. Our application database stores your verified Firebase user identifier and lifecycle timestamps but does not duplicate your Firebase email address or display name.

Saved bets and Bet Tracking

If you choose to save an entry in the Bet Tracking feature while signed in, we store that entry so you can review it later and access it across devices. Depending on what you save, this may include bet and leg identifiers, sport, selections, teams or players, game and market identifiers, over or under selections, lines, odds, stakes or units, currency, sportsbook, parlay legs, notes, status, results, settlement information, cashout information, source, and creation, update, or settlement timestamps. This category describes content you intentionally save; it is separate from optional analytics about how the Service is used.

Saved-bet synchronization information

We store preferences used by Bet Tracking, such as units or cash display mode, unit value, and currency, along with extensible application settings. We also maintain import receipts and counts used to migrate saved entries without duplicating them, and deleted-record identifiers used to stop an older device from restoring a bet that was deleted elsewhere.

Subscription and payment information

We may receive subscription tier, entitlement, trial, renewal or expiration status, product identifiers, billing email, transaction identifiers, and purchase or transaction metadata from Apple, Google, RevenueCat, and Stripe. Web subscriptions are managed through RevenueCat Billing with Stripe acting as the payment gateway. Apple and Google process purchases made in their respective mobile applications. AlgoSwish does not receive or store your full payment-card number. RevenueCat and Stripe may process payment-card, billing-address, tax, fraud-prevention, and transaction information to complete and manage a web purchase.

Support information

If you contact us, we may collect your name, email address, message, screenshots, attachments, and anything else you choose to provide.

Basic website audience measurement

On the website, we use Vercel Web Analytics by default to collect anonymous page-view information such as the route, filtered query parameters, referrer, approximate location, browser, operating system, device type, and timestamp for aggregated audience reporting. Vercel Web Analytics does not use cookies and does not associate page views with an AlgoSwish account or individual IP address.

Optional product analytics and session replay

If you allow optional analytics, PostHog may collect pages or app areas viewed, feature interactions, selected sport, general sportsbook-selection state, app platform, subscription tier, browser and device information, performance information, errors, and session-replay data to help us understand and improve the Service. PostHog session replay masks form inputs, private account and settings screens, saved Bet Tracking entries, and billing surfaces; redacts URL query strings; and does not record network request or response bodies or headers. We do not send saved-bet notes, stake amounts, passwords, payment-card details, support messages, or search text as custom analytics-event properties.

Technical information

We and our service providers may collect IP address, user agent, timestamps, request logs, basic server logs, and diagnostic or operational information needed to run and secure the Service.

Local device information

The Service may store preferences, settings, cached state, consent choices, anonymous analytics identifiers, and copies of saved Bet Tracking entries on your device to support migration, faster loading, temporary offline use, and, if allowed, analytics. PostHog may use browser local storage rather than an AlgoSwish analytics cookie; Vercel Web Analytics does not use cookies.

4. Information We Do Not Intentionally Collect

Unless we clearly disclose otherwise and update this Policy, we do not intentionally collect precise GPS location, contacts, photos, camera or microphone recordings, health information, biometric information, government identification numbers, or full payment-card details.

5. How We Use Information

We may use information to:

• operate, maintain, and provide the Service;
• create and authenticate accounts;
• support Google and Apple sign-in;
• process subscription status, restore purchases, and determine entitlements;
• save and synchronize Bet Tracking entries and related preferences across devices;
• import locally saved entries, prevent duplicates, resolve conflicting versions, and propagate deletions;
• respond to support requests;
• monitor, secure, troubleshoot, and measure basic website audiences;
• where optional analytics is allowed, understand usage and improve the Service;
• detect fraud, abuse, unauthorized access, and violations of our Terms;
• comply with legal obligations; and
• enforce agreements and protect rights, safety, and property.

6. How We Share Information

Service providers

We may share information with providers that help with authentication, analytics, session replay, app distribution, payment processing, billing, subscription management, hosting, database infrastructure, security, and operations. These may include Firebase Authentication, Google, Apple, PostHog, Vercel, RevenueCat, Stripe, Railway, the Apple App Store, and Google Play.

Legal, safety, and fraud matters

We may disclose information where reasonably necessary to comply with law, legal process, or lawful requests; protect rights, safety, or property; investigate fraud or abuse; or enforce our agreements.

Business transfers

Information may be transferred as part of a merger, financing, acquisition, reorganization, bankruptcy, or sale of assets.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising or targeted advertising.

7. Saved Bets and Cross-Device Synchronization

When you are signed in, our PostgreSQL database is the authoritative source for the bets and parlays you save in Bet Tracking and the related display preferences associated with your account. Mobile AsyncStorage and browser local storage remain offline caches. Records are tied to the user identifier taken from a verified Firebase token, not an unverified identifier supplied by the client.

Existing locally saved entries may be imported after you sign in. Imports are additive, an empty new device does not erase server history, stable identifiers help prevent duplicate records, and the most recently updated version generally wins when two versions of a record conflict. Deleted-record identifiers override stale copies so an older device cannot restore a deleted bet. Synchronization is event- and refresh-based rather than live, so an already-open second device may need to refresh.

An entry saved while signed out may remain only on that device until it is imported into an account. Clearing storage before an unsynchronized entry is imported may permanently remove that entry.

8. Data Retention

Account information, saved Bet Tracking entries, related preferences, deleted-record identifiers, and migration receipts are generally retained while your account is active and for as long as needed to provide reliable synchronization. They are deleted through the account-deletion process, subject to limited legal, security, billing, dispute, fraud-prevention, enforcement, and backup-retention requirements.

Optional PostHog events and session recordings are retained according to the retention settings applied to our PostHog project and are deleted or de-identified when they expire, are no longer reasonably necessary for the disclosed purposes, or an applicable verified deletion request is completed. Anonymous Vercel Web Analytics page-view data is retained according to the reporting and retention settings applicable to our Vercel project and is not associated with a verified AlgoSwish user identifier. Withdrawing optional analytics permission stops future PostHog collection on that browser but does not disable basic Vercel Web Analytics audience measurement or by itself delete information collected before withdrawal.

Operational and security logs are retained only as long as reasonably needed for troubleshooting, security, fraud prevention, and legal compliance. Backups may retain deleted information for a limited period until overwritten or expired and are not used to restore a deleted account except where required for security or disaster recovery. Device-local guest or cached information remains until it is imported, removed, or the relevant application or browser storage is cleared.

9. Account and Data Deletion

You may request account deletion through the in-app deletion feature or our web account-deletion process. For an authenticated deletion, we request deletion of identified PostHog person data, events, and session recordings associated with the verified Firebase user identifier, delete the account's saved Bet Tracking entries, related preferences, deletion identifiers, and migration receipts from PostgreSQL, and then delete the Firebase account. PostHog event deletion may complete asynchronously.

We may need to retain limited information for legal, security, billing, dispute, fraud-prevention, enforcement, or temporary backup purposes. Guest entries, unsynchronized entries, anonymous analytics that cannot reasonably be linked to the account, or cached copies on other devices may remain separately and may require clearing application or browser storage or uninstalling the app.

10. Privacy Rights and Choices

Depending on where you live, you may have rights to access, correct, or delete certain personal information and to withdraw consent for optional processing. Residents of certain U.S. states and Canada may have additional rights under applicable law. To submit a request, email dusan@algoswish.com or use an available web request method. We may need to verify your identity before completing a request.

On the website, optional PostHog product analytics and session replay remain off until you choose to allow them. You can change that browser-specific choice at any time through Privacy choices in the website footer or through Settings. Turning analytics off stops future PostHog capture on that browser. Basic anonymous, cookie-free Vercel Web Analytics audience measurement operates by default, is used to count visits and page views, and is not linked to an AlgoSwish account. You may clear website local storage through your browser to remove locally stored choices, caches, and anonymous identifiers.

11. Children and Age Restrictions

The Service is intended for adults age 21 or older, or the higher minimum age required by applicable law. We do not knowingly permit use by anyone who does not meet that requirement. If we learn that an ineligible person has provided personal information, we may delete the information and disable the account.

12. Security

We use reasonable administrative, technical, and organizational safeguards designed to protect information. No system, transmission method, or storage method is completely secure, and we cannot guarantee absolute security.

13. International Processing

AlgoSwish LLC is based in the United States. If you use the Service from Canada or another location, information may be transferred to, stored in, and processed in the United States or other locations where our service providers operate. Privacy laws in those locations may differ from those where you live.

14. Third-Party Services

The Service uses third parties for authentication, analytics, billing, app distribution, and infrastructure. Those parties operate under their own terms and privacy policies. Except where required by law, we are not responsible for their privacy or security practices.

15. Changes to This Policy

We may update this Privacy Policy from time to time. We may provide notice through the app, website, email, or another reasonable method. Continued use of the Service after an updated Policy becomes effective acknowledges the updated Policy.

16. Contact

AlgoSwish LLC
Website: algoswish.com
Email: dusan@algoswish.com