Cookies Policy
This website uses cookies to better the user's experience while visiting the website. This policy explains which cookies StackRoll sets, who owns them, how long they last, what they are used to measure, and how you can refuse or remove them.
Your choice on your first visit.
A cookie is a small file that a website asks your browser to keep, so that the site can recognise the same browser the next time it sees it. Some cookies are written by the site you are visiting; others are written by a company whose service the site uses.
Where applicable this website uses a cookie control system, allowing you on your first visit to allow or disallow the use of cookies on your computer or device. This complies with legislation requiring websites to obtain explicit consent from users before storing or reading files such as cookies on a user's computer or device.
The analytics cookies described below are only set after you allow them. If you disallow them, or make no choice, the measurement described in this policy does not run and no analytics cookie is written. You can change your answer at any time through the cookie controls on this site, and you can delete cookies that have already been set using your browser, as described under Disabling cookies.
Refusing these cookies does not restrict your use of the site. Nothing on StackRoll is withheld from you because you said no.
What these cookies measure.
The cookies above let Google Analytics tell one browser from another and group a series of actions into a single visit. Against that, StackRoll records a fixed list of events. No event outside this list is sent, and the list is set in our tag container rather than decided page by page.
Before launch none of this occurs: this site runs no measurement at all, so no event is recorded and nothing is sent to Google. On the full platform the complete list is:
| Event | When it is recorded |
|---|---|
| page_view | You open a page on StackRoll. |
| register_click | You select a control that begins account registration. |
| login_click | You select a control that begins sign-in. |
| sign_up | An account is created. |
| sign_up_error | An attempt to create an account does not succeed, with the reason. |
| login | You sign in. |
| login_error | A sign-in attempt does not succeed, with the reason. |
| logout | You sign out. |
| verify_email | An email address is verified. |
| deposit_started | You begin a deposit. |
| deposit_completed | A deposit completes, with the amount and the asset. |
| withdraw_started | You begin a withdrawal. |
| withdraw_requested | A withdrawal is submitted, with the amount and the asset. |
| out_of_funds | Play stops because the balance available is not sufficient. |
| select_game | You choose a game from a list or a search result. |
| game_start | A game is opened. |
| first_round | The first round of a game session is played. |
| game_end | A game is closed, with the rounds played and how long the session lasted. |
| search | You run a search, with the term you entered. |
| claim_rakeback | Rakeback is claimed, with the amount and the asset. |
| app_installed | The StackRoll app is installed on your device. |
| api_error | A request between the site and StackRoll does not succeed, with the reason. |
Each event carries some of the fields below. A field is only sent when it is relevant to that event — a search term is not attached to a deposit, and an amount is not attached to a search.
| Field | Applies to | What it holds |
|---|---|---|
| page_location | The event | The address of the page, after the sign-in parameters described below are removed. |
| page_title | The event | The title of the page. |
| path | The event | The route within the site, without the domain. |
| location | The event | The part of the page the action was taken from, such as a named section or menu. |
| source | The event | What led to the action, such as the list or screen it was started from. |
| method | The event | The method used, such as the sign-in method or the payment route. |
| reason | The event | Why an attempt did not succeed, on the error events above. |
| code | The event | A short status or error code accompanying the event. |
| asset | The event | The currency or asset an amount is denominated in. |
| amount | The event | The value attached to a deposit, withdrawal or rakeback claim. |
| game_name | The event | The name of the game. |
| game_slug | The event | The game's short identifier. |
| game_category | The event | The category the game sits in. |
| game_provider | The event | The studio or provider supplying the game. |
| play_mode | The event | Whether the game was played for real or in a demo mode. |
| rounds_played | The event | How many rounds were played in the session. |
| duration_sec | The event | How long the session lasted, in seconds. |
| search_term | The event | The text you typed into the search box. |
| user_id | The event | Your StackRoll account identifier. See The account identifier sent to Google. |
| debug_mode | The event | Marks the event as coming from a StackRoll developer or from our staging site, so it can be excluded from the reports. |
| vip_level | You | Your VIP tier. |
| login_method | You | The method you last signed in with. |
| language | You | The display language you use. |
| platform_currency | You | The currency your account is displayed in. |
The four fields marked "You" are attached to your profile in Google Analytics rather than to a single event, and the most recent value replaces the previous one.
Google Analytics is not given your name, your email address, your wallet address, your balance, your password, or the details of any individual bet or game outcome.
The account identifier sent to Google.
When you are signed in, StackRoll sends your account identifier to Google Analytics as the user_id field shown in the table above. It is a machine identifier, not your username or email address, and Google cannot resolve it back to you. Its purpose is to let us recognise that the same person used StackRoll on a phone and on a laptop, so that the two are counted as one player rather than two.
This has a consequence worth stating plainly: for signed-in visits, measurement is no longer limited to the anonymous browser identifier in the _ga cookie. Clearing your cookies ends the cookie-based association, but signing in again re-establishes the account-based one.
The identifier is only sent while you are signed in. Signed-out browsing, including everything on this pre-launch site, carries no account identifier.
What we do not use cookies for.
StackRoll's Google Analytics property is configured for two purposes only: understanding website traffic, and understanding user engagement and retention. In particular:
- We do not run advertising, remarketing or audience-building features in Google Analytics, and no advertising or retargeting cookie is set by this site.
- We do not load any third-party advertising network on this site.
- We do not use separate marketing, session-replay or live-chat services on this site, so none of their cookies are set here.
- Google Tag Manager itself stores nothing on your device.
If that changes, this policy will be updated before the new cookies are used, and you will be asked again for your consent.
What we remove before it reaches Google.
Two deliberate settings reduce what is sent:
- Sign-in codes are stripped from web addresses. Some links — for example sign-in links sent by email — carry a one-time code in the address. StackRoll removes these before measurement, and Google Analytics is separately configured to redact the
code,signandtokenparameters from any address it receives, as a second safety net. - Our own testing traffic is excluded. Visits from StackRoll developers and from our staging site are marked and filtered out, so they never enter the reports.
Google uses the IP address of the request to work out an approximate location, such as country or city. Google states that Google Analytics 4 does not log or store IP addresses. StackRoll never receives an IP address through Google Analytics and cannot retrieve one from it.
How long any of this is kept.
The two cookies above expire two years after they are last set, unless you delete them sooner. Deleting them ends the association: the next visit is counted as a new, unrelated browser.
Inside Google Analytics, the detailed event records described above are kept for 14 months and are then deleted automatically. Aggregate totals — how many visits a page received in a month, for example — are not tied to an individual browser and are kept for longer.
Opt-out.
In order to provide website visitors with more choice on how data is collected by Google Analytics, Google has developed the Google Analytics Opt-out Browser Add-on. The add-on stops data being sent to Google Analytics from any site you visit, not only this one, and does not affect usage of the website in any other way. A link to further information is provided below for your convenience.
https://tools.google.com/dlpage/gaoptout
For more information on how Google uses data from sites that use its services, a link to Google's own advice is provided below for your convenience.
https://policies.google.com/technologies/partner-sites
You can also decline these cookies on this site at any time using the cookie controls described under Your choice on your first visit, which does not require installing anything.
Disabling cookies.
If you would like to restrict the use of cookies you can control this in your internet browser. Links to advice on how to do this for the most popular internet browsers are provided below for convenience, and will be available for the browser of your choice either online or via the software help.
- Google Chrome — https://support.google.com/chrome/answer/95647
- Mozilla Firefox — https://support.mozilla.org/kb/enhanced-tracking-protection-firefox-desktop
- Apple Safari — https://support.apple.com/guide/safari/manage-cookies-sfri11471/mac
- Microsoft Edge — https://support.microsoft.com/microsoft-edge/delete-cookies-in-microsoft-edge
Blocking all cookies in your browser affects every website you visit, and some sites will stop working correctly as a result. StackRoll will continue to work.
Contact and communication.
Users contacting this website and/or its owners do so at their own discretion and provide any such personal details requested at their own risk. Your personal information is kept private and stored securely until a time it is no longer required or has no use. Every effort has been made to ensure a safe and secure submission process, but users are advised that they use such processes at their own risk.
This website and its owners use any information submitted to provide you with further information about the products and services they offer, or to assist in answering any question you may have submitted. This includes using your details to subscribe you to the launch-updates email list, but only where this was made clear to you and your express permission was granted when you submitted the form. You can unsubscribe from that list at any time using the link in any email we send.
Questions about this policy, about the cookies described in it, or about a request to access or delete information held about you, can be sent to privacy@stackroll.com.
External links.
Although this website only looks to include quality, safe and relevant external links, users are advised to adopt a policy of caution before clicking any external web link mentioned throughout this website.
The owners of this website cannot guarantee or verify the contents of any externally linked website despite their best efforts. Users should therefore note that they click external links at their own risk, and this website and its owners cannot be held liable for any damages or implications caused by visiting any external link. Cookies set by another website are governed by that website's own cookie policy, not this one.
Changes to this policy.
StackRoll is still in development. As the platform grows, the measurement described here may change. When it does, this page is updated and the date at the top of it changes with it. Where a change introduces a new cookie, or a new purpose for an existing one, your consent will be requested again before it takes effect.
Built by dreamers. Backed by degens.
Social media platforms.
Communication, engagement and actions taken through external social media platforms that this website and its owners participate on are subject to the terms and conditions as well as the privacy policies held with each social media platform respectively.
Users are advised to use social media platforms wisely and to engage with them with due care in regard to their own privacy and personal details. Neither this website nor its owners will ever ask for personal or sensitive information through social media platforms, and users wishing to discuss sensitive details are encouraged to contact us through our primary communication channels.
Users are also advised to take caution and use good judgement before clicking any shortened URL published on a social media platform by this website or its owners. Despite best efforts to ensure only genuine URLs are published, many social media platforms are prone to spam, and this website and its owners cannot be held liable for any damages or implications caused by visiting any shortened link.