PhrexxonthodB2B workplace facilities (U.S.) Request details

Storage on your device

Cookie and similar technologies

This page explains how we use small files, tags, and local storage in your browser in connection with phrexxonthod.world, how those tools relate to the banner you see, and what you can do if you want to change a choice later. We group technologies into the same three lanes that appear in the interface: strictly necessary, analytics, and marketing. For a wider view of how any associated personal data is handled, read our Privacy policy, which the banner text also references when you read it carefully end to end. Nothing here removes your statutory rights, and the dynamic date in the box below is simply a browser-side clock so you can note when you read the page, not a statement that the file text was revised at that same second.

Viewed on
Local storage opt-in Three clear lanes Withdrawal explained

What cookies and similar technologies are

A cookie is a text string that a website sends to your browser and that your browser can send back on later requests to the same site or, in the case of third-party cookies, to another domain. Similar technologies include pixel tags, small scripts, and storage APIs such as local storage and session storage. Session storage is cleared when a tab is closed, while local storage can persist for a long time and is often the place a site stores a “remembered” preference that should survive days or months. A few technologies also work through mobile WebView containers, where the same principles apply, though the “settings” screen may be deeper in a phone’s operating system. We use the term “storage” in this page to cover cookies and the storage APIs together, because a reader may not see a separate cookie file in every environment.

How we use them in practice

We use these technologies in a restrained way, aligned with a B2B site that is mostly read-only content plus a form and a consent banner. Necessary items keep a session together when needed, help prevent basic abuse, and store your consent string so the banner is not needlessly shown on every new tab if you have already made a clear choice. Analytics items, if you opt in, help us understand navigation paths, scroll depth, and which sections get attention, in aggregated views that do not focus on a single person’s employment record. Marketing items, if you opt in, can help us see whether a campaign label on a link was associated with a visit at an aggregate level, not to call out any individual. We do not use this stack to set prices, change benefits, or make automated choices about a human being’s job.

The three categories in our banner

Strictly necessary — These are required to display the page correctly, to carry security tokens in certain flows, to remember a fraud-prevention flag for a few minutes, and to read or write a minimal record that your consent to optional categories was set. They cannot be turned off in our interface, because the site and your choices would not function sensibly without them. When we say “always on” in the UI, that is the narrow lane we mean, not a license to do anything.

Analytics — These are off until you allow them, either with “Accept all” in the sense that includes all categories, or with “Cookie settings” and a checked analytics box, followed by “Save.” When off, we avoid placing analytics tags that would have sent identifiers to a supplier. The exact tools may change over time; the category description stays the same, and the privacy policy is where we will name specific vendors as they are active, so procurement teams can map subprocessors in their records.

Marketing — These are also off by default, and you can enable them in the same settings sheet. We use the marketing lane sparingly, for light measurement of our own announcements, not for cross-site ad auctions on a mass market consumer site. If we ever reclassify a tag from marketing to necessary because the law or our architecture changes, we will update the banner and this page, not silently move a tag between lanes.

The consent record may include a timestamp, the version of the banner, and a compact representation of which lanes are on, stored in localStorage on your device with a key name such as thisdomain-cookie-choices if you are inspecting developer tools, because technicians sometimes ask. Clearing site data in your browser removes that record, and the banner will ask again on the next visit.

Vendors and subprocessors

The hosting provider, analytics suite, and email provider each have their own subprocessors, published on their own sites, which are updated with their product lines. We do not make those lists part of this document line by line, but we are responsible, under our agreements, for the chain that processes personal data in connection with our use of the services, where data is involved, and the privacy policy is the appropriate place to see how data subjects can exercise their rights. For cookies that never leave your device, there is no cross-border “transfer” in the data-protection sense, but a tag that later sends a hit to a server in another country may be a transfer, and the privacy text covers the safeguard we rely on in that case.

Durations and refresh

Many session features expire when the browser session ends, while consent and preference values may be stored for up to twelve months before we re-prompt, unless the law in your area requires a shorter or longer interval. A vendor’s cookie with its own name may have an expiration in its content; your browser will describe that in its storage panel. We periodically review whether older cookies from prior vendors can be purged in documentation and, where we control a script tag, in deployment.

How to change your choices

You can open the banner on a fresh visit, clear the site in browser settings, or write to contact@phrexxonthod.world for a plain-language set of steps for your device if you are stuck. We do not charge for helping with genuine accessibility or privacy questions, except where a law allows a small fee in narrow circumstances that have not so far arisen in our practice. Withdrawing a consent is free and does not change the lawfulness of processing that happened before, but you may need to clear storage yourself if a browser already cached a tag before you turned a lane off; we are happy to help interpret what you are seeing in a short email exchange.

Browser and device controls

Major browsers let you block third-party cookies, delete all site data, or ask sites not to track, although the meaning of a “do not track” header is not uniform. Mobile Safari, Chrome, Firefox, and Edge all include storage viewers that show the names of keys, which can be helpful when debugging with us. In corporate environments, an MDM policy may block certain tags entirely; if your internal policy prevents analytics, tell us, and we can suggest a read-only handout instead of a live demo that depends on that tag.

U.S. state notice links and sensitive selling language

Where a US state law requires a “Do not sell or share my personal information” or similar line, the core operation of this site is not a sale in the “money for a list” sense, and our cookie text is aimed at a business reader. We still want you to know that the optional marketing lane is where any narrow definition of “sharing” for cross-context behavioral advertising would be most likely to sit, if a vendor ever interpreted an event in that way, and you can keep that lane off. For rights requests under a state statute, the privacy policy lists how to make a request and verify it; this cookie page is not a substitute for that.

Questions

If something on this page does not match what you see in the banner on your device, take a short screen capture, note the browser and version, and email us. We will compare it to our test matrix and, if it is a bug, fix the banner in a way that is fair to all visitors. The contact address is contact@phrexxonthod.world, and the office line is +1 212-732-0560. Thank you for reading the whole file; a careful reader is always welcome at Phrexxonthod.

Short technical names and keys in this page are for transparency with IT readers; you are not required to look at any line of code to use the public site in a normal way.