Privacy policy

Effective date: 4 October 2026

Playwin - Automation Bridge and the customer sign-in service are operated by Bookiesoftware for Playwin customer accounts. This policy explains what they collect, how they use it, where it is stored, and who receives it. The extension connects your account to Playwin services. Some automation runs in a server-hosted workspace on HTTPS page prefixes approved in the portal.

Information we handle

• Account and sign-in information: your username and password, account role and enabled state, subscription expiry, sign-in time, current active-session identifier and expiry, and the last time the extension checked in. Your password is sent to playwintech.shop over HTTPS for authentication and stored in the portal database as a salted scrypt hash. Temporary passwords are shown to the administrator once when an account is created or reset, and the portal does not keep a readable password copy. If the administrator chooses WhatsApp sharing, the login message is prefilled for the selected recipient in WhatsApp. Please use a unique password.
• Extension location: when you sign in through the Chrome extension, it reads the device's precise coordinates and reported accuracy using Chrome's geolocation feature and sends them to the Playwin portal over HTTPS. Authorized Playwin administrators can see this location in the user list. It is replaced at your next extension sign-in or removed when your account is deleted. If Chrome cannot provide your location, the portal shows that no extension location is available. We do not use your IP address to estimate your location.
• Extension settings: your action limits (1–5 for Line Market and 1–40 for Match Odds), automation enabled state, approved page URL prefixes, and signed-in access token. Action limits are saved in your portal account and synchronized with the extension.
• Automation workspace data: when you use the optional workspace, a browser running on the Playwin server loads approved websites and keeps its cookies, website sign-in state, and profile on the server. It sends screen images to your signed-in browser and forwards your clicks and keyboard input. Website passwords you type there pass through the Playwin server. Automation reads and changes page elements inside that workspace.
• Live Cricket monitoring: an operator-controlled VPS service reads the SSPlaywin and TomExch Cricket feeds for fixture details, market names and status, in-play and Fancy line-market details, runner names, and line ranges when supplied. It refreshes SSPlaywin's Fancy market list for live fixtures. It does not request separate price-book feeds or retain or display Back/Lay quotes, last traded prices, available sizes, or matched totals. A read-only browser watcher checks the live Match Odds page and records whether Ball Running or Suspended is visible, the number of bookmaker sections, and when the status was last verified. Administrators can view Fancy market details and watcher freshness in the portal; signed-in extensions receive the latest bookmaker state. The monitor does not place or change bets, and customer extensions do not need to open a page for this monitoring.
• Administrator workflow images: administrators may upload workflow screenshots or templates for managed workflows. These are stored in the private object-storage service configured for the portal and are provided to an assigned customer only when the portal workflow feature is used.

How we use information

We use account information to authenticate users, enforce subscriptions and one-device sessions, display subscription details, synchronize action limits, provide the server-managed automation policy, and let administrators manage account access. Extension location and sign-in time let administrators see where an extension account was last signed in. Extension check-ins let administrators distinguish an extension that is currently connected from one that is not active. The optional automation workspace lets you view and control its server-hosted session. The VPS status service checks live Cricket fixtures and shares only their current bookmaker state with signed-in extensions.

We do not sell personal information, use it for advertising, or use it to build a browsing profile. The extension does not download or execute remote code. Its packaged runner reads and changes the approved market page in your current browser tab after you enable the relevant features. It uses authenticated settings and declarative trigger selectors supplied by the portal. Automation in the optional workspace runs on the Playwin server. The separate live-status monitor reads the listed Bookmaker panels without changing them.

Who receives information

• Playwin operators and authorized administrators can access account records to provide the service and manage customer access.
• Hostinger provides the VPS hosting and network delivery for playwintech.shop and may process connection data needed to run and protect that service.
• MongoDB provides the portal database used for account records, subscription state, and action limits. The database is operated as a managed service for Playwin.
• The configured private S3-compatible object-storage provider stores administrator-uploaded workflow images and templates; it does not receive workspace website credentials through the extension.
• Chrome and your device provide the geolocation feature used by the extension. Your browser or operating system may process location signals to provide it. The extension sends the resulting coordinates only to the Playwin portal; Playwin does not send your IP address to a separate location-lookup provider.
• The approved website receives the normal page interactions and website sign-in details needed to use that website. Those site interactions are subject to that website's own privacy policy.

These providers process information to deliver hosting, storage, database, or browser location services. We do not authorize them to use it for Playwin advertising.

Storage and retention

Portal account records are retained while the account exists and are removed when an administrator deletes the account. Expiring a subscription blocks access but does not automatically delete the account. The last extension location remains in the account until the next extension sign-in or account deletion; extension check-in time is replaced by each successful check-in. Passwords are retained only as salted hashes; the temporary password entered by an administrator is not saved in readable form after the one-time sharing panel is cleared. The access token and settings remain in Chrome extension storage until you sign out, access is revoked or expires, or you remove the extension or its stored data. Optional workspace cookies and website sign-in state persist in the server profile until Playwin removes that profile. Live fixture, market-book and watcher snapshots are held in service memory for current display and status delivery, then replaced as feeds refresh and fixtures or page state change. Workflow images are retained with their managed workflow until an administrator removes them.

Your choices and account requests

You can sign out from the extension or customer page, clear the extension's local data in Chrome, and ask your Playwin administrator to correct or delete your account information. You can change your password from the customer page. For privacy questions or requests, contact the Playwin administrator who provided your account.

Children and policy changes

This product is not intended for children under 18. We do not knowingly create accounts for children. We may update this policy when the product's data practices change; the current version will remain available at this URL and will show its effective date.

Account security: Portal authentication uses salted password hashes. New and reset temporary passwords must be changed at first sign-in, whether you sign in through the website or the extension.