Gambit Odds Companion

PRIVACY POLICY · UPDATED 2 NOVEMBER 2026

Your poker records stay on your device.

This policy covers Gambit Odds Companion and this support website. Public support contact: scony2200@gmail.com.

What the extension reads

On Gambit, the extension reads visible cards, visible chip stacks, active-player counts and the current game route. It creates local hand/session identifiers and timestamps to organize your learning history. It does not read hidden opponent cards, collect player names or automate bets.

What is stored locally

Hand cards, observed boards, probability snapshots, chip changes, game numbers, saved flags, notes, corrections, deletion markers, interface preferences and the latest successful Pro verification are stored using the browser extension’s local storage. Free users’ statistics are also calculated locally; Pro unlocks their display.

The extension retains up to 500 recent unsaved hands plus manually saved hands. A migration backup of older extension records is retained to protect against migration failures. Records are not synchronized between browsers.

Payments and third parties

ExtensionPay handles paid-access identity, purchase restoration and entitlement verification. It uses Stripe for checkout. These services receive the purchase email and payment information you supply, extension/payment identifiers and network information needed to operate their services. The extension contacts ExtensionPay over HTTPS and keeps a local paid-access cache for up to 24 hours of offline grace. It never sends poker hands or notes to ExtensionPay, Stripe or the developer.

Payment information remains with the payment providers; the extension does not collect card numbers. Provider data is governed by their policies and applicable retention requirements.

Export, import and deletion

Settings provides free JSON backup and import. Backups include hand records, notes, saved flags, legacy manual sessions and whitelisted display preferences. They exclude payment credentials and entitlement caches. You control where exported files are stored and who can read them.

Use Settings → Delete saved hands to remove local records, older journals, migration backups and deletion markers. Individual History rows can also be deleted. Browser removal usually removes extension storage, so export a backup before uninstalling. Local deletion does not delete payment-provider records or cancel an ongoing subscription; use Manage subscription or contact support for those requests.

Security and limited use

No advertising trackers or analytics SDKs are included in the extension. Data is used only to provide and improve the features you request, never sold or used for advertising. The use of data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Local data is protected by your browser profile and device protections; exported JSON backups are not encrypted by the extension.

This website and support requests

This website contains no application analytics or contact form. The hosting provider may process routine request information to serve and secure the pages. If you email support, the developer and email provider receive your email address and the information you choose to send. Do not email passwords, payment-card details or private backups unless specifically needed and agreed.

Questions and changes

Contact scony2200@gmail.com for access, correction or deletion questions. This page will be updated when data handling changes, with a revised date.