Privacy policy

Sell Fries Wiki is an independent fan project run by one person, reachable at [email protected]. It is not affiliated with, authorised by, or endorsed by Roblox Corporation or by Pharting, the developer of Sell Fries! [Anomaly]. This policy covers sellfrieswiki.com and every page under it. It does not cover Roblox, YouTube or any other site you reach through a link here.

Because there is no company, no staff and no customer list behind the site, the practical scope of this policy is narrow: what the hosting layer records, what an embedded video can do after a click, and how to reach a human about either.

The following are not features that exist but are switched off — they were never built. There is no place on this site to type personal information and no mechanism to store it:

• No account system. No registration, no login, no password, no profile, no session that identifies you.
• No forms of any kind. No contact form, no report form, no feedback box, no survey, no file upload.
• No newsletter. Nothing to subscribe to, and no list of addresses.
• No comments or user content. No place to post a message, a name or a screenshot.
• No payment processing. Nothing is sold, so no card or billing data is ever requested.
• No advertising, affiliate or retargeting tags. No ad network, no conversion pixel, no affiliate identifier, no sponsor slot.
• One analytics tool, deliberately limited. Google Analytics 4 (measurement ID G-MEF79SXFX5) records page views and coarse session data. Advertising personalisation and Google Signals are switched off, IP addresses are not used to build a profile, and the planner inputs are never sent. No heatmap recorder, no session replay, no fingerprinting library.

The planner runs entirely in your browser. Numbers you type into it are not transmitted anywhere, not saved between visits, and not attached to a cookie. Closing the tab discards them.

The site is served by Cloudflare Pages, which acts as host and CDN. Like every web server, it processes the technical details of each request in order to return a page and to defend the site against abuse. For a request to this site that typically means:

• the IP address the request came from;
• the user-agent string, which names the browser and operating system;
• the path requested and the response status;
• the referring page, where the browser sends one;
• the date and time of the request, and basic timing and size data.

These records are used for three things only: returning content, keeping the site online under load or attack, and reading aggregate traffic counts — for example how many requests a page received this week. They are not used to identify a reader, not joined to any other data, not enriched with location beyond coarse region, and never sold or shared for marketing.

Retention is set by Cloudflare's own configuration and published policies rather than by this site, and can change without notice to us. This project keeps no separate copy of request logs and holds no database that a log could be imported into.

This site sets no advertising, tracking or preference cookies of its own. There is nothing to personalise, so there is no cookie for it. The only cookies that can appear are set by the two parties below, and only in the circumstances named.

Some pages list videos that explain the game loop. Each one appears first as a thumbnail with a play control. That thumbnail is served by YouTube's image host (i.ytimg.com), so opening a page with a video card does make one image request to Google — it carries no player, no script and sets no cookie. The player itself is a facade: it is not requested until you press play.

After a click, the player loads from youtube-nocookie.com, Google's privacy-enhanced domain. Even so, Google receives the fact that a video was requested, along with your IP address, browser details and the page you came from, and may set cookies subject to its own policy. What Google does with that data is outside this site's control; the relevant policy is Google's privacy policy (opens policies.google.com in a new tab).

Videos are embedded from YouTube rather than downloaded or re-hosted, and the creators retain all rights in them. If a creator wants an embed removed, an email to the address above is enough.

Sell Fries! [Anomaly] is played by a young audience, and this site is written with that in mind. It is a general-audience reference, not a service directed at children under 13, and it does not knowingly collect personal information from anyone — child or adult. There is no account to create, no comment to leave and no form to fill in, which is what makes that possible to state without qualification.

Read against the US Children's Online Privacy Protection Act, the position is straightforward: no personal information is collected from users of any age, so none is collected from children under 13. No personalised advertising is served, no behavioural profile is built, and no purchase or in-game spending is promoted. The same is true under the UK and EU GDPR provisions on children's data, and under app-store and platform rules that apply to child-directed content.

If a parent or guardian believes that a child's personal information has reached this site — for example inside an email sent to the address above — write to the same address and it will be deleted. There is no other route by which such information could arrive.

The game itself is rated Minimal by Roblox in its maturity settings, but it contains horror-flavoured content after 8 PM in-game. That judgement belongs to a parent, not to this site; the reference pages describe the mechanics rather than the scares.

Depending on where you live, you may have rights over personal data held about you — under the GDPR and UK GDPR, under state privacy laws in the United States, and under comparable regimes elsewhere. Those rights typically include access, correction, deletion, restriction, objection, portability, and the right not to be discriminated against for exercising them.

To use any of them, email [email protected] with the right you are invoking and enough detail to identify what you are asking about. Requests are answered within 30 days. In most cases the honest answer will be that no personal data is held, because the site has nowhere to put it — but a written confirmation is still a valid response to an access request, and you will get one.

Where the only record of a visit is a Cloudflare request log, deletion requests are handled by Cloudflare under its own procedures; this site has no copy to delete and no ability to edit the edge logs. If you are in the EU or UK you also have the right to complain to your national data protection authority.

Pages are static files served over HTTPS. There is no database, no admin panel reachable from the internet, no upload path and no user session, which removes most of the ways a site can lose data it should not have had. There is no backup containing personal information, because there is no personal information to back up.

Correspondence sent by email is kept only for as long as the thread is open and is used only to resolve the issue raised. Addresses are not added to a mailing list, not shared with third parties, and not used for marketing. If you ask for a message to be deleted after the issue is closed, it will be.

Pages link out to Roblox, to YouTube and occasionally to a creator's channel. Once you follow a link, the destination's own privacy policy applies. This site does not control those services, does not receive data back from them, and does not place tracking parameters on outbound links.

The date at the top of this page is the date the policy last changed. Wording may be tightened or clarified at any time; that is not a change in practice and does not reset the date unless the substance moves. If the substance does change — a new embed, a new logging tool, an ad network, anything that touches data — the change is published here first, noted on the updates page, and dated before it goes live. The site will not quietly begin collecting something this page says it does not.

Continuing to use the site after a revised policy is published means the revised version applies. If you object to a substantive change, stop using the site and, if you wish, ask for any correspondence to be deleted.

Email [email protected] with any question about this policy, or about what a visit to the site records. There is no contact form; the contact page explains what the inbox handles and how quickly. The rules for using the material on this site are in the terms of use.