Sign in

Extension Data Collection Statement

When you grant site access, SpinVisor reads game telemetry only: bet amounts, wins, bonuses, multipliers, and session context. We never collect banking details, card numbers, passwords, cookies for tracking, deposit/withdrawal flows, or personal messages.

Effective Date: 21st Sep 2026
Last Updated: 28th Sep 2026

1. Purpose of This Statement

This Extension Data Collection Statement explains what information the SpinVisor browser extension accesses, observes, processes, transmits and stores when it is used on supported websites.

SpinVisor is operated by Dynemetry (Pty) Ltd, South Africa.

This Statement supplements the SpinVisor Privacy Policy and Terms of Service and is intended to provide clear information about the browser extension specifically.

SpinVisor is designed as a gameplay tracking and analytics companion. It observes supported gameplay telemetry after appropriate website access has been granted and converts that information into session records, historical statistics, gameplay metrics and other analytical information.

SpinVisor does not place wagers, control casino games or make gambling decisions on behalf of users.

Decisions concerning whether to gamble, continue or stop gambling, select a game, place a wager or otherwise participate in gambling remain the user's own decisions.

2. User Control Over Website Access

SpinVisor requires browser access to supported casino/game websites in order to detect supported gameplay telemetry.

Where the browser requires permission for SpinVisor to access a website, the user controls whether that permission is granted.

If the user declines or removes access to a supported website:

  • SpinVisor does not override that browser-level decision;
  • functionality requiring access to that website will not operate;
  • gameplay telemetry from that website cannot be processed through functionality requiring that access; and
  • the website may remain listed as technically supported even though the individual user has chosen not to permit SpinVisor access to it.

Users may manage extension website permissions through controls provided by their browser.

Granting access to one supported website does not mean that the user has intentionally authorised SpinVisor to collect unrelated information from other websites.

SpinVisor intends to use website access only for functionality reasonably necessary to provide the extension's stated purpose.

3. Why Website Access Is Required

Online casino games generally run within webpages, embedded game clients, frames or related browser contexts.

For SpinVisor to identify supported games and capture supported gameplay events, the extension may need permission to interact with the relevant webpage or browser context.

Depending on the technical implementation of the supported provider or website, this may involve:

  • detecting the supported website;
  • identifying the game or game provider;
  • observing supported gameplay events;
  • reading gameplay information exposed within the permitted browser context;
  • detecting session changes;
  • communicating supported telemetry to SpinVisor's backend; and
  • displaying SpinVisor's extension interface and analytics.

Website access is therefore required for the core purpose of the extension.

4. Gameplay Information the Extension May Process

When SpinVisor is active on a supported website and has the necessary permission, it may process gameplay information including:

  • game title;
  • game provider or studio;
  • casino or website;
  • game RTP metadata;
  • game volatility metadata;
  • maximum-win/game metadata;
  • displayed game or casino balance;
  • wager/bet amount;
  • spin sequence;
  • spin number;
  • spin result;
  • win amount;
  • loss or net result;
  • tumble or cascade events;
  • multiplier events;
  • bonus/feature triggers;
  • bonus spins;
  • bonus/feature results;
  • spin-in features;
  • purchased/bought features;
  • feature purchase price where applicable;
  • feature progress;
  • feature multipliers; and
  • related supported gameplay events.

The precise information available may differ between games, providers, casinos and technical implementations.

SpinVisor does not necessarily process every listed data element for every supported game.

5. Session Information Created From Gameplay Data

SpinVisor may combine observed gameplay events into session records.

These records may contain or generate information such as:

  • session identifier;
  • game;
  • provider;
  • casino/website;
  • session start time;
  • session end time;
  • duration;
  • session status;
  • starting displayed balance;
  • ending displayed balance;
  • total wagers;
  • total wins;
  • session profit/loss;
  • average wager;
  • largest win;
  • total spins;
  • normal spins;
  • tumble/cascade spins;
  • bonus spins;
  • winning spins;
  • win rate;
  • tumble statistics;
  • average win;
  • observed RTP;
  • net result per spin;
  • dry-spell statistics;
  • feature statistics; and
  • other historical or mathematical session metrics.

These metrics allow the user to understand and review what occurred during their gameplay.

They do not determine the result of future random game events.

6. Bonus and Feature Information

Where supported by the game implementation, SpinVisor may process information concerning bonus or feature events.

This may include:

  • whether a feature occurred;
  • whether the feature was triggered through normal gameplay or purchased;
  • the triggering spin;
  • spins before the feature;
  • spins after the feature;
  • feature purchase price;
  • trigger-spin result;
  • number of feature spins;
  • feature progress;
  • individual feature-spin results;
  • awarded multipliers;
  • missed multipliers;
  • running feature value;
  • final feature value;
  • feature profit/loss; and
  • historical feature statistics.

This information may be associated with the user's SpinVisor account while that account remains active.

7. Derived Analytics

Some information displayed by SpinVisor is calculated by SpinVisor rather than directly supplied as a completed statistic by the casino.

Derived information may include:

  • session profit/loss;
  • observed RTP;
  • win rate;
  • average wager;
  • average win;
  • net result per spin;
  • tumble/cascade rates;
  • dry-spell statistics;
  • feature frequency;
  • spins-before-feature statistics;
  • session-performance measurements;
  • variance-related measurements;
  • historical trends; and
  • aggregate statistical measurements.

These calculations describe observed or historical information.

They do not predict future RNG outcomes and should not be interpreted as a statement that a future spin, feature or other random event will produce a particular result.

SpinVisor provides metrics and analytical information. The user remains responsible for their own gambling decisions.

8. Displayed Casino Balance

SpinVisor may process a balance displayed within a supported game or casino interface where that information is required for session analytics.

Processing a displayed gameplay balance does not mean that SpinVisor has access to:

  • the user's bank account;
  • the user's complete casino financial account;
  • payment-card credentials;
  • online-banking credentials; or
  • the ability to deposit or withdraw funds.

SpinVisor uses supported displayed balance information for gameplay/session analytics.

9. Information the Extension Is Not Designed to Collect

The SpinVisor extension is not designed to collect or store:

  • casino passwords;
  • casino login credentials;
  • online-banking usernames or passwords;
  • bank account login credentials;
  • complete credit/debit card numbers;
  • CVV/card security codes;
  • cryptocurrency private keys;
  • government identity documents;
  • passport information;
  • casino KYC documentation;
  • private casino messages;
  • personal emails;
  • unrelated private communications; or
  • unrelated information from websites outside the extension's stated functionality.

Users should never provide casino passwords, banking credentials or payment-card security information to SpinVisor.

10. SpinVisor Does Not Control Casino Transactions

The extension does not:

  • initiate casino deposits;
  • initiate casino withdrawals;
  • transfer casino funds;
  • place casino wagers on the user's behalf;
  • press a game's spin control on the user's behalf;
  • alter a wager on the user's behalf;
  • determine RNG results;
  • modify a game's RNG;
  • change casino payouts; or
  • guarantee gambling results.

SpinVisor observes supported gameplay information and provides tracking, statistics and analytics.

The user's gambling decisions remain their own.

11. Account Information

Use of the extension may require authentication with a SpinVisor account.

Account-related information may include:

  • internal SpinVisor account identifier;
  • pseudonymous SpinVisor handle;
  • subscription tier;
  • authentication/session information;
  • account status; and
  • information required to associate permitted gameplay records with the user's SpinVisor account.

The broader collection and processing of registration information, including email address, date of birth and registration IP address, is described in the SpinVisor Privacy Policy.

12. Technical Information

SpinVisor may process technical information required to operate, secure and troubleshoot the extension.

Depending on the implementation, this may include:

  • browser type;
  • browser version;
  • operating system;
  • device-related technical information;
  • extension version;
  • installation identifier;
  • supported website/domain;
  • API request information;
  • authentication/session tokens;
  • application logs;
  • error information;
  • security events;
  • failed authentication information; and
  • diagnostic information.

This information may be used for:

  • compatibility;
  • troubleshooting;
  • fraud prevention;
  • abuse prevention;
  • service reliability;
  • account security;
  • infrastructure security; and
  • diagnosing extension failures.

13. IP Addresses

When the extension communicates with SpinVisor's servers, SpinVisor's infrastructure may receive the IP address from which the request originates.

IP addresses may be processed for:

  • network communication;
  • security;
  • fraud prevention;
  • abuse prevention;
  • logging;
  • troubleshooting; and
  • approximate country or regional determination.

SpinVisor does not use this process to obtain precise GPS location.

IP-derived location is approximate and may be inaccurate.

14. Browser Storage

SpinVisor may use browser-provided storage mechanisms where reasonably necessary to operate the extension.

Such storage may be used for information such as:

  • authentication state;
  • extension settings;
  • user preferences;
  • installation or configuration information;
  • temporary operational information; and
  • information required for reliable extension operation.

Browser storage is not intended to be used by SpinVisor to store casino passwords, complete payment-card credentials or online-banking credentials.

15. Data Transmitted to SpinVisor

Information required for account-linked analytics, session history and community functionality may be transmitted from the extension to SpinVisor's backend infrastructure.

This may include:

  • supported gameplay telemetry;
  • session events;
  • game/provider/casino information;
  • feature events;
  • account identifier;
  • pseudonymous handle where required;
  • technical information;
  • extension version;
  • timestamps; and
  • security/diagnostic information.

SpinVisor's backend may then use this information to create and maintain:

  • session history;
  • spin history;
  • feature history;
  • historical analytics;
  • community statistics;
  • account-linked statistics; and
  • anonymised aggregate information.

16. Community and Aggregate Use

Gameplay information may contribute to SpinVisor community and aggregate statistics.

Community functionality may include:

  • trending games;
  • game activity;
  • provider activity;
  • significant wins;
  • bonus/feature statistics;
  • aggregate gameplay measurements; and
  • historical community statistics.

Where individual community activity is displayed, SpinVisor uses the user's pseudonymous SpinVisor handle rather than intentionally displaying their private account information.

SpinVisor does not intend to expose a user's:

  • email address;
  • date of birth;
  • IP address;
  • optional first name;
  • optional last name; or
  • other private account information

as part of public gameplay/community metrics.

17. Social Sharing

Where SpinVisor allows a user to create or share a gameplay result externally, the user decides whether to initiate that sharing.

SpinVisor-generated sharing content is designed to avoid including private account information and may display the user's pseudonymous SpinVisor handle.

Users should review information before sharing it publicly.

Once information is voluntarily shared to an external social platform, that platform's own privacy practices apply.

18. No Advertising Profiling

SpinVisor does not use the browser extension to build advertising profiles of users for sale to advertisers.

The SpinVisor browser extension does not use:

  • Google Analytics;
  • Meta Pixel; or
  • comparable third-party advertising pixels

as part of its gameplay telemetry model.

Google Analytics is used on the SpinVisor website to measure website usage, as described in the Cookie Policy and Privacy Policy. That website measurement is separate from extension gameplay telemetry.

Gameplay telemetry collected through the extension is intended for providing, securing, maintaining and improving SpinVisor's gameplay analytics and related functionality rather than unrelated behavioural advertising.

19. Commercial Use of Gameplay Telemetry Data

SpinVisor's business model may include the commercial use, licensing or sale of gameplay telemetry event data and statistical datasets to third parties, including casino-industry and gameplay-data aggregators.

Telemetry supplied for these purposes may include information concerning:

  • games and game providers;
  • gameplay events;
  • spin activity and outcomes;
  • wager values;
  • win and loss values;
  • bonus and feature events;
  • multiplier events;
  • game-related telemetry;
  • casino or website context associated with the gameplay event; and
  • statistical information derived from gameplay telemetry.

Commercial telemetry datasets do not include user-referenced or account-linked information.

SpinVisor does not provide third parties receiving these commercial telemetry datasets with:

  • SpinVisor handles or nicknames;
  • pseudonymised or anonymised user handles;
  • SpinVisor account or user IDs;
  • email addresses;
  • dates of birth;
  • IP addresses;
  • first or last names;
  • profile photographs;
  • authentication information; or
  • other identifiers intended to associate telemetry events with a particular SpinVisor user.

User identifiers are excluded from the commercial telemetry dataset. The purpose of the dataset is to provide information about gameplay events and statistical activity, not information about individual SpinVisor users.

SpinVisor may receive financial or other commercial consideration for providing such telemetry datasets.

Further information concerning SpinVisor's processing of personal information and applicable privacy rights is provided in the SpinVisor Privacy Policy and applicable jurisdiction-specific privacy notices.

20. Data Minimisation

SpinVisor seeks to limit extension access and data processing to information reasonably necessary for its disclosed functionality.

SpinVisor's objective is not to monitor a user's general browsing activity.

When a user opens SpinVisor on a website that is not currently supported, SpinVisor may inform the user that extension functionality is unavailable for that website and provide access to a SpinVisor page containing information about supported casino websites. SpinVisor will not represent an unsupported website as supported.

Website access should be limited to supported contexts and functionality required to identify games, observe supported gameplay telemetry, provide the SpinVisor interface and deliver the features described in this Statement.

21. Browser Permissions and Changes

The permissions requested by SpinVisor may change as browser APIs, supported providers or technical requirements evolve.

SpinVisor will seek to request only permissions reasonably necessary for disclosed functionality.

Where a new browser permission requires user approval, the applicable browser may present an additional permission request.

Users may decline permissions, although doing so may prevent functionality dependent on those permissions from operating.

SpinVisor will not treat a declined browser permission as authority to bypass the user's browser security controls.

22. Manifest V3

SpinVisor is designed for modern Chromium-based extension environments using Manifest V3.

Manifest V3 and Chromium browser APIs impose technical requirements concerning extension permissions, host access, background processing, script execution and other extension behaviour.

SpinVisor's implementation may evolve as browser platforms change their technical requirements.

Use of Manifest V3 does not remove the user's ability to manage extension permissions through browser controls.

23. Supported Websites Only

SpinVisor functionality is intended to operate only where:

  • the relevant game/provider implementation is supported;
  • the casino/website implementation is supported;
  • the required browser permission has been granted;
  • the user is authenticated where authentication is required; and
  • the relevant SpinVisor functionality is enabled.

Technical support for a casino website does not constitute an endorsement of that casino or confirmation that gambling on that website is lawful in the user's jurisdiction.

24. Third-Party Website Changes

Casino operators and game providers may modify their websites, games, data structures, network behaviour or technical implementations without notice to SpinVisor.

Such changes may affect:

  • data detection;
  • session accuracy;
  • compatibility;
  • feature detection;
  • displayed statistics; and
  • extension functionality.

SpinVisor may temporarily or permanently disable support where a technical implementation becomes incompatible, unreliable or inappropriate.

25. Accuracy

SpinVisor attempts to process supported gameplay telemetry accurately.

However, extension-derived information may occasionally be:

  • delayed;
  • incomplete;
  • duplicated;
  • unavailable; or
  • incorrectly interpreted

because of circumstances such as connectivity problems, browser behaviour, provider changes, casino changes, interrupted sessions, unsupported versions or software defects.

SpinVisor analytics should not be treated as an official casino account statement or authoritative game record. Where SpinVisor-displayed information differs from information provided directly by the applicable casino operator or game provider, the casino operator's and game provider's applicable records and values are the source of truth.

26. Retention

Account-linked gameplay information is generally retained while the user's SpinVisor account remains active, subject to the retention and inactivity rules described in the Privacy Policy.

Relevant technical, IP and security logs may generally be retained for between 90 days and 12 months, depending on the applicable security or operational requirement.

If a SpinVisor account is deleted, personal/account information is removed from active production systems in accordance with the Privacy Policy.

Historical gameplay information may then be retained only after the association with the former account has been irreversibly anonymised.

Properly anonymised historical statistics may be retained indefinitely.

27. Account Deletion and Anonymisation

Users may delete their SpinVisor account using the functionality provided by SpinVisor.

Following account deletion:

  • account access terminates;
  • account-linked personal information is removed from active production systems;
  • the user loses access to their historical gameplay information;
  • retained historical gameplay information is anonymised;
  • the former handle may be replaced with a generic SpinVisor identifier; and
  • the historical information cannot subsequently be restored to the former user.

SpinVisor's anonymisation process is intended to sever identifiers capable of reconnecting retained historical gameplay information to the former account.

Temporary residual information may remain in restricted rolling backups as described in the Privacy Policy.

28. Security

SpinVisor uses technical and organisational measures intended to protect extension and account information against unauthorised access, alteration, disclosure, loss or misuse.

Measures may include:

  • authenticated API access;
  • access controls;
  • password hashing;
  • restricted administrative access;
  • security logging;
  • infrastructure controls;
  • backups;
  • security monitoring; and
  • browser permission controls.

No browser extension, Internet service or computer system can guarantee absolute security.

Users should maintain the security of their device, browser and SpinVisor account credentials.

29. Infrastructure

SpinVisor is operated by Dynemetry (Pty) Ltd and uses infrastructure and service providers described more fully in the SpinVisor Privacy Policy.

These may include infrastructure provided by:

  • Vander Host;
  • Amazon Web Services (AWS); and
  • Cloudflare.

SpinVisor may use regional or distributed infrastructure to provide performance, availability, storage and security for a global user base.

Information may be processed or accessed internationally as described in the Privacy Policy.

30. User Decisions

SpinVisor's purpose is to provide users with information about their gameplay through tracking, metrics, statistics and analytics.

SpinVisor does not make gambling decisions for users.

A user's decision to:

  • gamble or not gamble;
  • select a casino;
  • select a game;
  • place a wager;
  • purchase a game feature;
  • continue gambling; or
  • stop gambling

remains the user's own decision.

SpinVisor does not execute those decisions on the user's behalf.

31. Changes to This Statement

SpinVisor may update this Extension Data Collection Statement where:

  • extension functionality changes;
  • browser permissions change;
  • supported technology changes;
  • data-processing practices change;
  • infrastructure changes;
  • legal requirements change; or
  • browser-platform requirements change.

The “Last Updated” date will be revised when this Statement changes.

Material changes to data collection or permissions will be communicated where required by applicable law or browser-platform requirements.

32. Relationship With Other SpinVisor Policies

This Statement should be read together with:

  • SpinVisor Privacy Policy;
  • SpinVisor Terms of Service;
  • GDPR Compliance & Rights Notice;
  • POPIA Compliance Notice;
  • CCPA/CPRA Privacy Notice;
  • Cookie Policy;
  • Responsible Gambling / Responsible Play Policy;
  • Subscription, Cancellation & Refund Policy; and
  • Gambling & Analytics Disclaimer.

The Privacy Policy is the primary document explaining SpinVisor's overall processing of personal information.

This Statement provides additional detail specifically concerning the browser extension.

33. Contact

Questions concerning SpinVisor extension permissions, data collection or privacy may be directed to:

SpinVisor
A division of Dynemetry (Pty) Ltd
South Africa

Website: www.spinvisor.com
Support Email: support@spinvisor.com

Users may also exercise applicable privacy rights through the processes described in the SpinVisor Privacy Policy and applicable jurisdiction-specific privacy notices.

← Back to home