Cookie policy

This Cookie policy (the "Policy") describes each Cookie and Similar Technology that the Site uses, why it is used and how long it lasts, the third parties that can reach your Device through the Site, and the controls you have over all of them.

This Policy forms part of the Terms of service (the "Terms"). Capitalized words that this Policy leaves undefined, including Access Code Account, Account, Balance, Bet, Daily stake limit, Deposit, Deposit limit, Fun play, Game Aggregator, Levels, Loss limit, Masking Tool, Network Check, Originals, Play break, Round, Self-exclusion, Service, Session reminder, Site, Skins, Steam, Step-up Check, Studio, Studio games, Support, Time limit, Tip, Vault and Withdrawal, carry the meanings that the Terms give them.

The Privacy policy applies alongside this Policy. It governs how Peeks handles personal data, including personal data that a Cookie or Similar Technology helps to collect, and it prevails wherever the two documents deal with the same processing. "Campaign Attribution", "Law 8968", "PRODHAB", "Product Event Tracking" and "Product Events" carry the meanings that the Privacy policy gives them.

This Policy covers the Site at peeks.gg, on every Device and for every visitor, whether or not the visitor holds an Account and wherever the visitor is.

A link to this Policy appears at the foot of every page of the Site and beside the box you check to open an Account. This Policy, and not a banner, is how the Site informs you of the Cookies and Similar Technologies described in sections 6 to 10, and section 12 sets out the basis on which each is used. A visitor who does not accept them may block them in the browser, with the effects set out in clause 13.5, or stop using the Site.

Because it forms part of the Terms, this Policy is governed by Costa Rican law, and any dispute about it is dealt with under section 21 of the Terms.

This Policy takes effect on the date shown at its head and from that date replaces the cookie notice dated 13 October 2026 previously published at /cookies.

Throughout this Policy:

• "Browser Storage" means the local storage and session storage areas that a browser keeps for each website, in which that website's pages save named entries;
• "Cookie" means a small file of text that a browser keeps at the request of a website and returns to that website with later requests;
• "Device" means the computer, phone, tablet or other equipment, together with its browser, through which you reach the Site;
• "First-party Cookie" means a Cookie placed for the host shown in the browser's address bar while you use the Site, being peeks.gg or one of its subdomains;
• "Persistent Cookie" means a Cookie that carries an expiry time and stays on the Device until that time or until it is deleted, whichever comes first;
• "Preference" describes an entry in Browser Storage that is not Strictly Necessary and that keeps a setting or choice made on the Site, or a convenience you can see and undo;
• "Session Cookie" means a Cookie without an expiry time, which the browser discards when the browsing session ends;
• "Similar Technologies" means Browser Storage, software development kits, pixels and web beacons, device fingerprinting and every other means of storing information on a Device, reading information from it or recognizing it;
• "Storage Key" means the name under which one entry is saved in Browser Storage;
• "Strictly Necessary" describes a Cookie or Similar Technology without which a service you have asked for could not be provided; your Account or the Site could not be kept secure; Peeks could not meet a legal duty, prevent fraud or apply the rules of the Terms on where the Service may be used and on Masking Tools; or a safer play tool you have switched on, such as the Session reminder, could not work;
• "Studio Frame" means the frame within a page of the Site in which a Studio game loads from a host controlled by its Studio or by the Game Aggregator;
• "Third-party Cookie" means a Cookie placed for a host other than the one shown in the browser's address bar, including the host of a Studio Frame.

The Site is operated by 3-102-136856 Limitada, trading as Peeks Entertainment Limitada, a company organized under Costa Rican law with corporate identity number (cédula jurídica) 3-102-136856, whose registered address is Provincia 06 Puntarenas, Canton 11 Garabito, Jaco, Costado Este De La Municipalidad Garabito, Bufete Sanchez Chavarria, 61101, Costa Rica. References in this Policy to Peeks are to that company.

That company is the party responsible, for the purposes of Law 8968, for the databases that hold information obtained with the help of the Cookies and Similar Technologies in this Policy.

A Cookie is a small file holding a name and a value, with a limit on its size. Each Cookie also names the domain and path to which the browser will return it, an expiry time or none, and attributes that restrict when and how the browser sends it.

This Policy sorts Cookies in three ways, and sorts Similar Technologies by purpose in the same way:

• by origin: First-party Cookies or Third-party Cookies;
• by duration: Session Cookies or Persistent Cookies;
• by purpose: Strictly Necessary Cookies; functional or preference cookies, which remember choices made on a website; analytics or performance cookies, which measure how a website is used; and advertising, marketing or targeting cookies, which record interests in order to select advertisements.

Browser Storage differs from a Cookie in two respects. The browser does not attach its contents to requests, so only code running on the Site's own pages can read what the Site has saved there. Its entries also have no expiry time: local storage keeps them until they are deleted, and session storage discards them when the tab or window holding them closes.

A pixel or web beacon is an image or snippet of code, usually invisible, that reports to a server when a page or an email is opened. A software development kit is a code library built into a mobile app, often to measure use or to show advertising. Device fingerprinting combines characteristics of a Device, such as its screen, fonts and settings, so as to recognize it without storing anything on it.

The categories of Cookie and Similar Technology, and whether the Site uses each, are these:

No outside analytics service, and no advertising, social media or tag management script, runs on the Site's pages, and no script that records sessions, tests versions of a page or reports errors to an outside service. Campaign codes added to links are used for nothing but the record of how you found us that clause 6.8 describes. The Site's content security policy tells browsers to run only scripts that come with the Site's pages, to open data connections only to the Site's own servers, to load pictures only from the Site, from the image servers of the Game Aggregator and from Steam's content servers, and to load frames only from secure (https) hosts. Cloudflare may add scripts of its own for security, as clause 9.5 describes. The table in clause 5.1 and this clause describe the Site's own pages; section 10 deals with what a Studio or the Game Aggregator does inside a Studio Frame.

Peeks does not use Cookies or Similar Technologies to follow you across other websites, to profile your interests or to choose advertisements, and the only measuring of campaigns it does is the record of how you found us that clause 6.8 describes. It does not sell personal data, and it gives none to advertisers, advertising networks or data brokers.

Peeks sends no marketing email, apart from the single email announcing the launch to those who joined the waitlist, as clause 22.4 of the Privacy policy provides. Its other emails concern your Account: confirming an email address; resetting a password; confirming a change of password or email address; reporting a change to your security settings, such as two-step login turned on or off, recovery codes replaced or used, or an Account recovered; sending a summary of your play statistics where one is requested; and, once Skins Deposits are open, reporting a change to your linked Steam account. Every one of them is plain text, carries no pixel or web beacon and sends none of its links through a service that records whether it was opened or followed.

Apart from the Cookies described in clauses 6.7 and 6.8, Peeks places only the First-party Cookies in the table below, and no Session Cookies. Each of those in the table is a Persistent Cookie with a fixed lifetime, and each is Strictly Necessary.

peeks_session, peeks_mfa_login, peeks_passkey_challenge and peeks_sg each hold a random value of 32 bytes and nothing else: no name, email address, Balance or other detail of your Account. Our servers keep only a one-way code (a hash) of each value, from which the value cannot be recovered. peeks_sg_hint holds only the value 1. peeks_device holds a random identifier of 16 bytes, the time it was set and a signature by which our servers recognize an identifier they issued, and nothing else. Our servers do not store the identifier: they count the support chats started with it against one-way codes made from it, as clause 8.9 describes.

With each session our servers keep the Account it belongs to, when it began, when it was last active and when it ends, when and why it ended, how you logged in (password, authenticator code or passkey, and which passkey) and until when a recent extra check stays valid. A session record can also hold the country of your connection, the type of your Device and the families of its operating system and browser, a keyed one-way code of your network address and, where the Network Check runs, the kind of network it found, as clause 5.6 of the Privacy policy describes; it never holds the address itself or the user agent. The record behind peeks_mfa_login holds the Account, its expiry and check values that cancel it if your password or two-step settings change before you finish. The record behind peeks_passkey_challenge holds the challenge your Device signs, the address of the Site that issued it and its expiry. Each login and log-out is also recorded with your Account and its time. Because a session ties your browser to your Account, Peeks treats the session and its records as personal data under the Privacy policy.

Each Account has one live session at a time. Logging in on another browser or Device ends the earlier session; the browser that held it is told so at its next request, and its peeks_session Cookie is then deleted. Logging out ends your session on our servers, which refuse the peeks_session Cookie for the rest of its lifetime, and the Cookie itself stays in your browser until that lifetime ends or you delete it.

The Cookies in this section carry these restrictions, except that the Cookies described in clause 6.7 are neither HttpOnly nor Secure:

• HttpOnly: page scripts cannot read them, so code injected into a page cannot copy them. peeks_sg_hint is the exception: it holds nothing secret and stays readable so that the Site's pages can tell whether to load a guest chat;
• Secure: the browser sends them only over encrypted (HTTPS) connections;
• SameSite: the browser never sends peeks_passkey_challenge with a request that another website starts, and withholds the others from such requests, except that it sends those returned with the address you open when you follow a link from another website to the Site, such as peeks_session, peeks_sg_hint, peeks_device and peeks_touched for any page. Subdomains of peeks.gg do not count as another website for this purpose;
• Path: peeks_mfa_login, peeks_passkey_challenge, peeks_sg and peeks_touch return only with the requests named in the table or in clause 6.8, never with requests for pages.

Apart from the Cookies described in clauses 6.7 and 6.8, a visitor who has not begun to log in, to open an Account or to start a support chat receives no Cookie from Peeks. Browsing the Site and Fun play in the Originals need none. Cloudflare may still place the Cookies described in section 9.

Two further Cookies, peeks_season_preview and peeks_season_logo_preview, let Peeks staff preview seasonal designs of the Site. Peeks places one only when you open an address on the Site that carries a seasonal preview setting, so that the pages you open next show the design that setting asks for, and each is Strictly Necessary for that purpose. peeks_season_preview holds only the name of a season or the value off, and peeks_season_logo_preview only the value on or off; neither holds anything about you. Each is a First-party Cookie and a Session Cookie, and is sent with every request to the Site. Opening an address whose preview setting is not one of those values deletes the Cookie concerned.

Product Events and how you found us. While Product Event Tracking is switched on, Peeks also places a First-party Cookie that holds a random identifier for your browser and nothing else, so that the Product Events of one browser can be counted together, as clause 5.10 of the Privacy policy describes; our servers keep only a keyed one-way code made from it, and this clause will name that Cookie, with its lifetime, from the day it is first placed. When you reach the Site through a link that carries the code of a tracking link or campaign details, meaning a source, a medium or a campaign, Peeks keeps them, with the address of the page on which you arrived and the time, in a First-party Cookie named peeks_touch, which lasts 30 days and which your browser sends only with the request that opens an Account (/api/auth/register). With it Peeks places a second First-party Cookie, peeks_touched, which holds only the value 1, lasts 30 days and is sent with every request to the Site, so that a later link does not replace the first. Opening an Account through the sign-up form deletes both, and what peeks_touch held is recorded as clause 5.3 of the Privacy policy describes. None of these Cookies is Strictly Necessary, and blocking or deleting them changes nothing else on the Site.

The Site saves the entries listed in this section in Browser Storage on your Device. Every entry is first party: only the Site's own pages write and read it. The entries hold settings you choose or their defaults, notices already shown to you, the text of support messages not yet sent, and requests on their way to our servers. Peeks does not collect the contents of Browser Storage; an entry reaches our servers only inside a request that you make, such as the stake carried by a bet.

The Site never saves your password, an authenticator code or the secret behind it, a recovery code or an identity document in a Cookie or in Browser Storage, and it never receives the private key of a passkey. A request that needs your password or a code carries it only when you send it, and the copy kept in session storage so that the request can be resent leaves it out.

Local storage holds these entries until you delete them:

Session storage holds these entries until the tab closes, and a request or a message until it is answered or sent:

Every bet in the Originals, and every Tip, Vault move and other request that changes your Balance or your limits, carries a unique identifier. The pending entries in clause 7.4 keep that identifier until our servers answer, so that a request cut off by a lost connection is resent under the same identifier and applied only once. Where your browser refuses session storage, the Site cannot give that assurance, so it does not send the request and shows a message such as "Allow site storage, then refresh to play." or "Your browser blocked storage. Nothing was sent." Studio games do not use these entries: their bets are made inside the Studio Frame and settled between the Game Aggregator and our servers.

The Site also uses the browser's tab-to-tab messaging on four channels, peeks-session, peeks-game-library, peeks-account-inbox and pk-support-stream, to tell your other open tabs of the Site of a login or log-out, a change to your favorites, messages you have read, or which tab now holds the live support connection. Nothing sent on these channels is stored.

The Site registers no service worker and uses neither IndexedDB nor the browser's cache storage. An offer to add the Site to a home screen is held in the page's memory and discarded when the page closes.

A Preference entry stays on your Device and reaches our servers only inside a request you make. Peeks keeps Preference entries without asking first, because each holds a choice you made or a convenience you can see and undo. The Site writes some Preference entries without a choice by you: lastStakes, recent-searches-search-modal, soundSettings until you change it, peeks:notices:v1, peeks:promotion-wins, peeks-skins-seen, peeks-early-access, pk-eyes-woke, peeks:fun-round and peeks:autobet-left.

Logging out leaves Browser Storage as it is. Once live support loads in a tab for a logged-in Account, the Site deletes from that tab any support message drafted or queued while no Account was logged in, and the support entries of any other Account. Keys shown with (account) carry your Account's internal identifier, not your username or email address, and the notices entry keeps the title, amount and date of each notice. Anyone who later uses the same browser profile can find these entries. On a Device that others use, do not let the browser save your password, and delete the Site's data after logging out as clause 13.4 describes.

Peeks does not attach to your Account anything that a browser did before you logged in on it, and favorites chosen while logged out stay in that browser. There are two exceptions:

• a referral code carried in the link that brought you to the sign-up form is sent only if you open an Account, as clause 8.10 describes;
• a support chat started without an Account can move into your Account: after you log in, the Site offers to move it, accepting deletes the guest chat Cookies from your browser, and the chat moves only if it was last used within the previous two hours.

Every request that your browser sends to the Site carries your network (IP) address and standard technical details, including the address of the page requested and your browser's user agent, which names the browser, its version and the operating system. Peeks uses these details only as this section and the Privacy policy describe.

The Site reads the user agent to fit its pages to your Device, for example to load the phone version of a Studio game or to show the right steps for adding the Site to a home screen. When you log in, our servers also read from it the type of your Device and the families of its operating system and browser, which they keep with your session record without keeping the user agent itself. The user agent is kept, cut to 256 characters, only with each Skins Deposit or Withdrawal you ask for, as clause 5.13 of the Privacy policy describes.

Our web server keeps a log of the requests it receives, recording for each the time, the network address, the address requested, the response, and the referrer and user agent that your browser sent. Cloudflare keeps similar records of the traffic it carries and shows Peeks totals drawn from them, such as requests by country and attacks blocked.

While the Network Check is switched on, the Site's pages add the time zone setting of your Device to their requests to our servers, and the Network Check described in the Restricted countries and VPN policy examines your network address in up to three steps:

• it compares the address with published lists of Tor, VPN and hosting networks and of iCloud Private Relay, and with Cloudflare's report of Tor;
• where those do not settle the matter and a lookup provider is switched on, our servers send the address, and nothing else, to that one provider and hold its answer for up to six hours;
• it compares the time zone of your Device with the time zone of your network, as the provider or, failing one, Cloudflare reports it. A difference of an hour or more is recorded for review and blocks nothing.

The Network Check places nothing on your Device and does not combine characteristics of your Device into an identifier. A check that finds a signal other than a relay service makes a record, as clause 9.3 of the Privacy policy describes, of the checkpoint, a keyed one-way code and the network prefix of your address, the signals found, the provider's summary, the two time zones and the country of the network as the provider or Cloudflare reports it, with the amount and method of any Deposit or Withdrawal concerned. A visit is recorded only while you are logged in, and at most once for the same address in any six hours. You may ask for a person to review a refusal by the check, as clause 10.4 of the Privacy policy and clause 5.10 of the Terms explain.

Peeks may use the details described in this section, and the records described in this Policy other than the peeks_device Cookie, the Cookies described in clause 6.8 and what they hold, to prevent, detect and investigate fraud, the opening or use of several Accounts by one person, Accounts linked in the ways that clause 6.2 of the Terms describes, and the use of a Masking Tool, as clause 7.8 of the Privacy policy provides. It does so by comparing records it already holds, such as the keyed codes and network prefixes that the Network Check records and the details kept with each session. Apart from the time zone reading in clause 8.4, it places no Cookie or Similar Technology on your Device, and reads none from it, for those purposes. The peeks_device Cookie described in clause 6.1 recognizes a browser only to limit the support chats started from it without an Account, and Peeks uses it for nothing else.

Changing or disguising the time zone, language, location or other details that your browser reports, in order to misstate where you are or the network you use, is the use of a Masking Tool under clause 5.2 of the Terms, and clause 5.8 of the Terms applies to it.

Before Peeks uses any technology that recognizes a Device in order to detect fraud or to link Accounts, it will describe that technology in this Policy and give notice of the change under section 19.

To slow attempts to guess passwords and other abuse, our servers count attempts against one-way codes of your network address, of the email address or username entered, and of your Account or guest support chat. A one-way code of the identifier held in peeks_device counts only the support chats started from your browser without an Account. Each code is deleted one day after the end of the window it counts, and each window lasts between one minute and one day.

A link to the sign-up form may carry a referral code. The Site's page reads the code from the link and enters it in the optional referral field of the form, and the Site's pages save nothing on your Device. The code reaches our servers only if you open an Account, together with the other details you enter, and it is then kept with your Account as clause 12.6 of the Terms provides. A code you type yourself is treated in the same way. If you type no code and your browser holds a Cookie named peeks_referral, our servers take the code from that Cookie when you open an Account and then delete it. The code of a tracking link and campaign details in a link are dealt with as clause 6.8 describes.

The Site never asks your browser for its precise location. It switches off the browser's location, camera, microphone and payment features for its own pages and for every frame those pages contain.

The Site tells browsers to send another host, as the referrer, at most the Site's own address, such as https://peeks.gg, and never the address of the page you are on. A Studio Frame receives no referrer at all.

The Site is delivered through the network of Cloudflare, Inc., which shields it from attacks and automated abuse. For that purpose Cloudflare may place Strictly Necessary Cookies of its own on the host you are using, which it uses for security alone and which Peeks does not read. Which of them your browser receives depends on the protections switched on at the time. None of them holds any detail of your Account.

Where a rate limiting rule or a check calls for them, Cloudflare may also place _cfuvid, which tells apart visitors who share one network address, and Cookies whose names begin with cf_chl_, which it uses to find faults in its checks. Cloudflare sets their lifetimes.

Blocking these Cookies can stop you from passing a Cloudflare check, and so from reaching the Site, for as long as that check is in place.

Cloudflare passes to our servers the country of your network address, which also marks a connection made through Tor, and, where its visitor location headers are switched on, the time zone of your network. The Network Check uses them as clause 8.4 describes. Whether or not the Network Check runs, our servers also use that country to apply the rules on where the Service may be used when you sign up, give the details of Verification Level 1, play, send a Tip, make a Deposit or request a Withdrawal, and keep it with your session record, together with the region that Cloudflare passes if Peeks switches on recording of it. Cloudflare handles your network address and request details on servers in many countries, as section 16 explains.

Cloudflare can add scripts of its own to the pages it delivers, such as the script of a security check. On the Site such scripts serve security alone.

The Site's servers are run for Peeks by a hosting provider. Each request your browser sends, with the Cookies and other details this Policy describes, passes through Cloudflare to those servers. The hosting provider keeps the servers running and does not use what passes through them for purposes of its own.

Studio games, which include slots, live casino and game shows, are supplied by Studios through the Game Aggregator. Each loads in a Studio Frame from a host that the Studio or the Game Aggregator controls, under its own terms and privacy policy.

Peeks does not control the content of a Studio Frame. Inside it, the Studio or the Game Aggregator may place its own Cookies, which are Third-party Cookies from the Site's point of view, and may use its own Browser Storage and scripts: for instance to keep the game session open, to remember the game's own sound and bet settings, to spread load across its servers, to measure how its game is played and how it performs, to detect fraud and cheating, and to keep the records its own licenses require. The Game Aggregator's launch page may also run a security check of its own, which can place further Cookies in the frame. These technologies are governed by the policies of the Studio or the Game Aggregator, not by this Policy.

The Site limits what a Studio Frame may do. The frame is loaded with no referrer; it may use three browser features, namely playback without a click, full screen and writing to the clipboard; and the browser's location, camera, microphone and payment features are switched off inside it.

Many browsers block or separate Cookies placed inside frames by default. Where yours does, a Studio game may fail to load or may forget its own settings. The Originals run on the Site itself and are not affected.

Some pictures of Studio games load from the image servers of the Game Aggregator, to which every page of the Site opens a connection in advance so that pictures appear quickly; others are served by the Site itself. Once Skins Deposits are open, pictures of Skins and Steam profile pictures load from Steam's content servers. Like any server that supplies a picture, these servers receive your network address and user agent, and as the referrer at most the Site's own address (clause 8.12). Peeks places no Cookie for them.

Once Skins Deposits are open, depositing or withdrawing Skins requires a linked Steam account. To link one, the Site sends your browser to Steam's own sign-in page at steamcommunity.com, where Steam places and reads its own Cookies under its own terms and privacy policy, and Steam then confirms your Steam account identifier to the Site. Peeks places no Cookie for the link. The one-time value that ties Steam's answer to your request travels in the address to which Steam returns you, and our servers check it against a record that expires after 10 minutes.

Skins Deposits and Withdrawals are processed through AssetPay, which our servers contact directly. Your browser does not connect to AssetPay through the Site, AssetPay places no Cookie through the Site, and trade offers reach you inside Steam.

The Site offers no login through another service.

Identity checks beyond the details you enter on the Site will be carried out by the Identity Partner, whose check opens on the provider's own pages and not inside the Site. Those pages may place their own Cookies under the provider's policies.

Live support messages are part of the Site and use no outside chat service.

The Site links to other websites, including the help organizations linked from every page and, once Skins Deposits are open, Steam. A website reached through such a link places its own Cookies under its own policies, which this Policy does not cover.

The Cookies and Similar Technologies of a Studio, the Game Aggregator, Steam, the Identity Partner or a linked website lie outside Peeks's control. Peeks is not liable for those technologies, nor for what those parties do with the information they collect, which can include purposes of their own. Cloudflare and the hosting provider are not such parties, because they act for Peeks. Cloudflare, Steam and the Identity Partner publish their policies on their own websites, and the Studio that makes each Studio game is named with the game and publishes its policy on its own website.

For the Cookies in section 6 other than those described in clause 6.8, and for the Strictly Necessary entries in section 7, Peeks relies on the performance of its agreement with you under the Terms and on its interest in keeping the Site and your Account secure, and not on your consent. They are needed to log you in, to keep your Account secure, to apply each bet only once, to deliver support messages, to limit how many support chats one browser can start without an Account, to run the safer play tools you switch on and to show the seasonal design that a preview address asks for.

The information described in sections 8 and 9 is also Strictly Necessary, including the time zone setting that the Site's pages read from your Device while the Network Check runs. For it Peeks relies on its legal duties; on the performance of its agreement with you, including the rules on Masking Tools (Terms of service, section 5); and on its interest in protecting the Site, its players and itself. It does not rely on your consent.

Clause 7.8 sets out the basis on which Peeks keeps Preference entries.

Peeks uses nothing for advertising or for following you across websites, and its Preference entries hold only choices you make or conveniences you can see and undo. For the Cookies described in clause 6.8, Peeks relies on its legitimate interests in understanding how the Site is used and in knowing how players find the Service, as clause 8.4 of the Privacy policy describes. You may object to that use under clause 17.2 of the Privacy policy, or block those Cookies with no effect on the rest of the Site. The Site therefore shows no cookie banner and offers no consent settings.

Before Peeks begins to use any Cookie or Similar Technology that is not Strictly Necessary, not a Preference entry and not one of the Cookies described in clause 6.8, it will amend this Policy, ask for your consent through a consent tool on the Site, and place nothing of that kind until you agree. That tool will ask about each category separately, make refusing as quick as accepting, check no box in advance and leave the Site usable if you refuse. A link to it will appear at the foot of every page, and Support will record any withdrawal of consent that you ask for.

The Site will keep your choice in a Strictly Necessary entry on your Device. The choice applies only to the browser in which you made it, and deleting the Site's data deletes it too. You may withdraw consent whenever you wish, as easily as you gave it; from then on the items concerned are no longer used, but what was done while your consent stood is not undone, and items saved earlier remain in your browser until their lifetime ends or you remove them. Peeks will keep a record of each choice, its date and the version of this Policy to which it relates.

Whether to keep the Site's Cookies and Browser Storage is your decision, and you may change it at any time. Refusing or deleting them does not breach the Terms and is never held against your Account; its only effects are those set out in clause 13.5. Changing what your browser reports in order to misstate your location is a different matter, which clause 8.7 covers.

You can block, delete or limit Cookies and Browser Storage in your browser settings, and most browsers can also act on the data of a single website. Most browsers accept Cookies and Browser Storage until you change those settings. Turning on a block stops new items from being saved but leaves in place those already on your Device; to remove those too, delete the Site's data as clause 13.4 describes.

Apple Safari, Google Chrome, Microsoft Edge, Mozilla Firefox, Opera and Samsung Internet each explain these settings in their help pages. Browsers call the Site's data "site data", "website data" or "cookies and site data". You can see each Cookie and Browser Storage entry that the Site has saved through the site information panel beside the address bar, or through the browser's developer tools, and compare them with sections 6, 7 and 9. These steps are a guide only: the maker of each browser decides how its settings work and may change them.

Deleting the Site's data in your browser removes its Cookies and its Browser Storage together. You are logged out, and the settings listed in clause 7.3 return to their defaults.

Blocking has these effects on the Site:

• Cookies from the Site blocked: you cannot log in by any method, and a support chat without an Account shows "Turn on cookies to chat." Browsing the Site and Fun play in the Originals still work, and Support can still be reached at support@peeks.gg;
• Browser Storage blocked: your settings are not kept between visits, the Session reminder does not run, and the Site sends no bet in the Originals and no Tip, Vault move or other request that changes your Balance or your limits. Studio games do not depend on the Site's Browser Storage;
• Cloudflare's Cookies blocked: you may be unable to pass a Cloudflare check, and so to reach the Site, while that check is in place;
• Third-party Cookies blocked: a Studio game may fail to load or may forget its own settings, as clause 10.4 explains.

Common browser settings affect the Site as follows:

• blocking only Third-party Cookies leaves logging in, live support and the Originals working, and may affect Studio games;
• allowing the Site's address as an exception keeps the Site working while you block Cookies on other websites;
• a content blocking extension can stop parts of the Site from working, and allowing the Site's address in that extension restores them;
• deleting website data each time the browser closes, or using a private or incognito window, logs you out and resets your settings whenever that browser or window closes;
• a setting that asks before each Cookie is saved will ask when you log in, when you start a support chat, when Cloudflare runs a check and, while they are in use, when the Site places a Cookie described in clause 6.8.

Deleting Cookies or Browser Storage, or being logged out as a result, does not cancel or change a Bet already placed. That Bet settles as clauses 11.7 and 11.13 of the Terms provide, and an open Round of an Original waits for you to log in again. If a tab closes, or its session storage is cleared, while a request is waiting for an answer, the Site can no longer resend that request; your Bets and transactions show whether our servers applied it. A Studio game cut off because your browser refused or deleted that game's own Cookies is settled under the game's rules and the Game Aggregator's record of the Round.

Clearing Cookies or Browser Storage changes nothing kept with your Account. Your Loss limits, Daily stake limit, Deposit limit, Time limit, Play break and Self-exclusion stay in force, and your favorites, recently played games and public profile and public stats settings stay as they were.

The Session reminder is kept on each Device. Clearing the Site's data, or moving to another browser or Device, switches it off there until you set it again.

Your choices apply to the browser in which you make them and do not carry over to another browser or Device.

Peeks publishes no mobile app. On a phone the Site runs in the browser, contains no software development kit and does not read the phone's advertising identifier.

Do Not Track is a browser setting by which a user asks websites not to follow them from site to site. Peeks follows no visitor from site to site, so the Site already behaves for everyone as that setting asks, whether or not the setting is sent.

Global Privacy Control is a browser signal by which a user asks websites not to sell their personal data or to share it for advertising. Peeks does neither for anyone, so the Site already behaves for everyone as that signal asks.

Should Peeks ever begin processing of either kind, it will treat either signal, when your browser sends it, as your objection to that processing.

Each Cookie lasts for the lifetime given in sections 6 and 9, and the browser then deletes it. Entries in local storage remain until you delete them: settings are overwritten whenever you change them, and lists such as recent searches and notices keep only their latest entries, up to the limits shown in clause 7.3. Entries in session storage are deleted when the tab closes, and pending requests and messages as soon as they have been answered or sent.

The records that our servers keep for these Cookies stop working when the Cookie expires or you log out, and are deleted as follows:

• a session record is deleted 30 days after the session ends, whether you log out or it runs out, and the note that a session ended because you logged in elsewhere is deleted when that session's 7 days would have run out;
• two-step login and passkey records are deleted one day after their 5 or 10 minutes run out;
• a Steam link record is deleted no later than one day after its 10 minutes run out;
• the codes used to limit attempts are deleted one day after the end of the window they count;
• the record that ties a guest support chat to a browser stops working when the chat moves into an Account and is then deleted, and is otherwise deleted 30 days after it was last used;
• the record of a guest who started a support chat, which holds a one-way code of the guest's network address and the times of first and last use, is deleted 30 days after its last use once no chat or other request of the guest remains, and is otherwise kept as long as the chat.

Information recorded while you use your Account, such as logins, bets and transactions, is kept as section 14 of the Privacy policy describes. Product Events, which hold the keyed one-way code made from the identifier described in clause 6.8, are deleted 90 days after they are recorded, as clause 14.2 of the Privacy policy provides.

The periods in this section and in clause 8.9 do not apply to a record needed for an open investigation, dispute, complaint or legal proceeding, or to one that an authority requires Peeks to keep. Such a record is kept as clause 14.6 of the Privacy policy provides, and Peeks may disclose any record described in this Policy as clauses 7.14, 11.11 and 11.13 of the Privacy policy allow.

Cloudflare, the hosting provider, the Studios, the Game Aggregator, Steam and the lookup provider of the Network Check, if one is switched on, may process outside Costa Rica the details that your browser sends them or that our servers send them. Cloudflare usually handles your traffic at a location near you. Cloudflare and Steam are run from the United States.

Section 13 of the Privacy policy describes these transfers and the safeguards that apply to them. You may ask the privacy officer to describe the safeguards that apply to any of them, as clause 13.5 of the Privacy policy provides.

The Site is for adults. Opening an Account, placing a Bet or using any part of the Service beyond browsing the Site requires you to be at least 18, or older still where the law of the place where you live or where you are sets a higher age for gambling, as clause 4.1 of the Terms provides. Peeks uses no Cookie or Similar Technology to single out or address minors, and it deals with an Account that belongs to a minor under the Terms (clause 4.2).

Parents and guardians can block the Site, and gambling websites generally, with the parental controls of a Device, a browser or a home network.

Law 8968 gives you the rights to be informed, of access, of rectification and of deletion, and the right to revoke consent, including over personal data that a Cookie or Similar Technology helps to collect. Peeks also gives you the rights to restrict and to object to processing, to portability, and to have a person review an automated decision, including a refusal by the Network Check. Sections 17 and 18 of the Privacy policy explain each right and how to use it: through Support or at support@peeks.gg, marked for the attention of the privacy officer.

Entries that exist only in Browser Storage on your Device never reach Peeks, and Peeks does not hold them. You can see and delete them yourself, as clauses 13.3 and 13.4 describe.

You may complain to PRODHAB about the way Peeks uses your personal data, as section 19 of the Privacy policy explains.

Peeks may amend this Policy when the Cookies or Similar Technologies used on the Site change, when a service that uses them is added or withdrawn, or when the law requires. The current version is always at /cookies, and the effective date at its head shows when it last changed.

Peeks gives at least 14 days' notice of a material change, as clause 1.7 of the Terms provides, by email to your Account's registered address and by a notice on the Site, unless the law or the security of the Site requires the change sooner, as when a protection must be switched on during an attack. A material change is one that adds a category of Cookie or Similar Technology, a third party able to reach your Device through the Site (such as the provider of a new payment method or the Identity Partner), a new purpose for an existing item, or a longer lifetime.

Once a change takes effect, the amended Policy governs your further use of the Site. A change that needs your consent applies to you only once you have given it.

The tables in sections 6, 7 and 9 describe the Site on the date at the head of this Policy. Peeks checks them against the Site and amends this Policy when they no longer match. Until then, an entry renamed without a new purpose or a longer lifetime is covered by the row that describes it. Cloudflare sets the names and lifetimes of its own Cookies and may change them; section 9 follows the list that Cloudflare published on the date at the head of this Policy.

Peeks keeps earlier versions of this Policy and sends any of them on request through the contact details in section 20.

Questions about this Policy, or about any Cookie or Similar Technology on the Site, can be sent through Support or to support@peeks.gg, marked for the attention of the privacy officer.