Privacy Policy

Read how sledrider.app delivers its pages, when the embedded game connects to AZGames, and what happens when you email the site team.

Reading this site

You can read the controls guide, look at gameplay screenshots and move between pages on sledrider.app without identifying yourself. We do not offer visitor accounts, ask you to create a player name or keep a site leaderboard. The pictures on the guides are files served with the pages. Looking at a picture of the starting screen does not open a connection to the game inside it.

We serve the guides, images and fonts from this site. Each page also requests a Google Tag Manager script from Google when the page opens, even if you never start the game. Google receives the connection details needed to deliver that script, including your IP address. Tags configured in the container can measure page visits and interactions. The information they send and the cookies they use depend on the active tags and your browser settings.

How a page reaches your device

When you open a link, your browser requests the page and the files needed to display it. The services delivering those files receive technical details about the request. These can include an IP address, the requested address, the time, browser information and a response status, such as a successful response or a missing file. A request for an image can reach the host separately from the request for the article containing it.

Cloudflare describes the information its network processes for visitors to customer sites in the End Users section of its privacy policy. Examples include routing information and system configuration data. Hosting and delivery services can use request information to route traffic, maintain availability, investigate errors and protect their networks. The information visible to a site operator can differ from what a provider processes to deliver a request. We do not specify a retention period on a provider's behalf.

What happens when you start Sled Rider

If you stay on the page and read, our code leaves the external game frame unloaded. Choosing Play now, or starting in Fullscreen, creates an embedded page supplied by AZGames. Your browser connects directly to gamea.azgame.io for the player and to games.azgame.io for game files. The address in your browser bar can still say sledrider.app while the contents of the player come from those other hosts.

For the external frame request we set a referrer policy that ordinarily sends the site's origin, such as https://sledrider.app, on a secure cross-site connection. The provider can then see which site opened its player. It also receives the connection information needed to respond to your browser. Browser privacy settings and policies applied to your device may limit the information your browser sends.

The game provider supplies the code that draws the slope, handles your inputs and shows the results of a run. Its player can request additional resources, including fonts and scripts from Google services. The player build we reviewed references Firebase components and analytics functions. Which services receive a request can depend on the build, browser and actions you take. Our site's own reading pages do not add these scripts.

Cookies, game data and browser settings

A browser can store several kinds of information from a page. It can cache a picture to avoid downloading it again, accept a cookie from a service or let a game keep data in storage belonging to its origin. These have different purposes. A cached mountain illustration tells you that the browser has a copy of an image. It does not tell you whether the game saved a score.

Browser rules generally restrict a page's access to information belonging to a different origin. This site has no account screen where we can look up a player's collection, migrate a best run to another profile or export all data held by an embedded service. When asking about lost gifts, please say whether you changed devices or browser profiles. A description is enough. We do not need a copy of your browser storage.

You can review site data and cookie permissions through your browser settings. Look for entries for the site you visited and, where your browser lists them, the game host. Deleting data may remove game progress or preferences and require files to load again. Some browsers partition storage used by embedded pages, so the same game opened elsewhere can have different saved data. Clearing your local data does not delete records already received by a service.

Leaving the game or sharing a device

Use Close game to remove the active player from the page. You can keep reading the guide after closing it. Leaving fullscreen only changes how the player is displayed. If you want to end the session before handing a device to someone else, close the player or close the tab. This ends that running instance without reversing requests the browser has already made.

On a shared computer, other people using the same browser profile may see recently visited pages or game information left in that profile. A guest or private window can reduce traces retained locally after the session, although services contacted during the visit still receive requests. Schools and workplaces may operate their own device or network logging. Ask the person managing that equipment about its settings and retention practices.

Information in messages you send

The Contact page links to [email protected]. Choosing that link opens your configured email service. You can review the message before sending it. If you send an email, we receive your sender address, the subject, the message and any files you attach. We use those details to understand the request, investigate it and reply. Your own mail service handles the outgoing message under its terms.

Usually a page address, a browser name and a short description of the issue are enough. For example, tell us whether a loading message appeared before or after you started the player. Leave out passwords, school login details, private browsing history and other people's names. Crop screenshots to the affected area so open tabs, bookmarks and personal notifications stay out of the picture.

A reply may quote part of your original message so you can follow the conversation. If you copied other recipients, check the recipient list before adding sensitive information to a follow-up. Closing the browser tab after sending an email leaves the delivered message in the email systems involved. For questions about that correspondence, reply to the same conversation where possible so we can identify it without asking for unrelated details.

Privacy requests and further information

For a question about information you previously sent, use the Contact page and describe the earlier communication in your own words. You may ask what information we hold about the request or ask us to correct or delete information you supplied. Include the approximate date and the subject so we can identify the relevant material. Applicable privacy rights and the information needed to act on a request depend on the circumstances.

If a concern relates to activity inside the game, identify the provider and the screen where it happened. This helps distinguish a message sent to this site from data processed by AZGames or another service. A parent or guardian can also raise a concern about information a child shared. Please describe the situation without including a child's full name or school in the initial message.

For information about the software on your device, your browser publisher's privacy and site data documentation describes the controls it provides. For an external service, check the privacy information published by that service. If you notice a difference between this notice and the behavior of a page, include the page address and the step that produced the unexpected request when you contact us.