Cookie policy
This website, ouxp.com, sets no cookies of its own and runs no analytics, advertising or tracking scripts. The only cookies you might get come from Cloudflare, our network provider, which can set a short-lived security cookie to keep bots and attacks off the site. If we ever add analytics, it stays off until you say yes.
Draft – pending legal review before launch. This policy describes how the site works today; its wording may change after review.
Does ouxp.com use cookies?
Not of our own. The site is plain HTML, CSS and a small amount of our own JavaScript, all served from ouxp.com, and none of that code sets or reads a cookie. The only code we didn’t write is a small script Cloudflare adds to hide our email address from spam bots – it’s served from ouxp.com and sets no cookies – and, on the contact and migration assessment pages, Cloudflare Turnstile, the spam check on our forms, which loads once you start filling in a form.
| Technology | On ouxp.com |
|---|---|
| Cookies set by OUXP | Not used Nothing in our code writes or reads a cookie |
| Analytics – Google Analytics, tag managers, heatmaps, session recording | Not used No analytics script runs on any page |
| Advertising and retargeting pixels | Not used No Meta, Google Ads, LinkedIn or similar tags |
| Embedded video, maps, chat or social widgets | Not used Other sites load only when you click a link to them |
| Fonts and scripts from other domains | Form pages only Our fonts are hosted on ouxp.com; the forms’ spam check comes from Cloudflare – see the form spam check |
| Browser storage – localStorage, sessionStorage, IndexedDB | Not used See other storage on your device |
| Security and delivery cookies from Cloudflare, our network provider | Possible Strictly necessary – see which ones and why |
| Network error reporting from Cloudflare | Some browsers No cookie – see what it reports |
Checked against the site’s code on October 12, 2026.
Why you don’t see a cookie banner
A cookie banner asks permission for cookies a site doesn’t strictly need, and we don’t set any. Cloudflare’s cookies only protect and deliver the site, and EU and UK rules (the ePrivacy Directive and the UK’s PECR) let strictly necessary cookies run without consent, as long as a page like this one explains them. If that ever changes, you’ll be asked first: see what changes if we add analytics.
Which cookies can Cloudflare set?
Cloudflare sits between your browser and our server. It delivers pages from a data center near you and filters out attacks and automated traffic. To do that job it may set a cookie on ouxp.com – these cookies are Cloudflare’s, and we don’t read or use them.
| Cookie | What it does and how long it lasts |
|---|---|
__cf_bm | Bot protection: helps Cloudflare tell people from automated traffic. Its contents are encrypted, and Cloudflare says it doesn’t track you from site to site or between sessions. Lasts: until 30 minutes after your last activity |
cf_clearance | Security checks: remembers that your browser passed one, so you aren’t checked again on every page. Lasts: 30 minutes by default |
cf_chl_rc_* | Security checks: help Cloudflare diagnose problems with the checks themselves. Lasts: not stated by Cloudflare |
__cflb | Load balancing: keeps you on the same server when traffic is spread across several. Lasts: from a few seconds up to 24 hours |
_cfuvid, __cfruid | Rate limiting: tells apart visitors who share an IP address when a rate limit applies. __cfruid belongs to Cloudflare’s older rate limiting.Lasts: not stated by Cloudflare |
__cfseq | Sequence rules: tracks the order and timing of your requests, to spot abuse such as skipped steps. Lasts: not stated by Cloudflare |
__cfwaitingroom | Waiting room: holds your place in a queue while traffic spikes. Lasts: not stated by Cloudflare |
cf_ob_info, cf_use_ob | Always Online: shows a saved copy of a page while our server is down. Lasts: 30 seconds |
You may receive none of them. Each appears only when its Cloudflare feature is switched on for ouxp.com: bot protection can set __cf_bm on an ordinary visit, while cf_clearance appears after a security check – for example, when traffic from your network looks automated. Cloudflare classes all of its cookies as strictly necessary and notes that their data may be processed in its US data centers.
Cloudflare’s own cookie reference (external site)
Cloudflare also handles request data, such as IP addresses, to deliver and protect the site. That data isn’t stored in your browser, so our privacy policy covers it rather than this page.
The spam check on our forms
The contact and migration assessment forms use Cloudflare Turnstile to keep out automated spam. Its script loads from challenges.cloudflare.com only after you start filling in a form, and it runs in a small frame from that address – most people never see it, and a checkbox appears only when Cloudflare needs one click to be sure. It checks signals such as your IP address and browser details; Cloudflare states that they are strictly necessary and used to detect and block bots, not to identify, profile or target anyone. Our own code sets no cookie for it, and what Turnstile keeps in its own frame is Cloudflare’s – see Cloudflare’s Turnstile privacy addendum (external site).
Does the site store anything else on your device?
Nothing that tracks you. Cookies aren’t the only way a site can remember you – browser storage (localStorage, sessionStorage, IndexedDB), tracking pixels and device fingerprinting can do the same job. Our site uses none of them, including in the two places where you might expect it to.
The Pause motion button saves nothing
The button in the footer stops animation on the page you’re reading. The choice isn’t saved, so the next page starts with motion again – unless your device is set to reduce motion, which the site always respects.
Forms keep nothing in your browser
What you type into the contact or migration assessment form exists only in the open page. When you send it, your browser posts the answers to ouxp.com with cookies switched off for that request, and the site saves nothing on your device. What we do with the answers is in the privacy policy.
Cloudflare’s network error reports
One setting comes from Cloudflare rather than our code. Browsers that support Network Error Logging, such as Chrome and Edge, keep an instruction for up to 7 days to report failed connections to ouxp.com – the page requested, the error and its timing – so Cloudflare can spot network problems. Successful visits aren’t reported, no cookie is involved and Cloudflare says the reports contain no personal information.
What about links to other sites?
Some links lead to other companies’ sites: our reviews on the Shopify Partner Directory (external site), our agency profile on Upwork (external site) and the client stores named in reviews. Nothing from those sites is embedded on our pages – no badges, widgets or review feeds – so they can’t set cookies until you click through. Once you’re there, their own cookie policies apply.
Email and phone links open your own mail or phone app. Nothing reaches us until you send the email or place the call.
How can you check this yourself?
You don’t have to take our word for it. Any desktop browser shows what a site stores:
- Open ouxp.com, then your browser’s developer tools: F12 or Ctrl+Shift+I on Windows, Cmd+Option+I on a Mac. In Safari, turn on the developer features under Settings › Advanced first.
- Open the stored data: the Application tab in Chrome and Edge, the Storage tab in Firefox and Safari.
- Under Cookies, select ouxp.com. You’ll see no cookies, or only the Cloudflare cookies listed above. Local storage and session storage are empty too.
- In the Network tab, reload the page. Every request goes to ouxp.com. Paths starting with
/cdn-cgi/are Cloudflare’s, served on our own domain – today the script that hides our email address from spam bots, plus a security check if Cloudflare runs one. On the two form pages, requests to challenges.cloudflare.com appear once you click into a form: that’s the spam check.
Leaving out analytics, ad tags and widgets also keeps these pages light. In Shopify performance optimization, we trace each slow metric on a client store to its cause – often an app script or a third-party tag – and you decide what stays.
How do you block or delete cookies?
There is nothing to opt out of on ouxp.com, because nothing on it tracks you. Browser privacy signals such as Global Privacy Control have nothing to switch off here today.
If you want to block or clear cookies anyway, every major browser lets you do it for a single site in its privacy or site-data settings. Most visits work fine without Cloudflare’s cookies. The trade-off: when Cloudflare decides to check a connection, its security check needs a cookie to remember that you passed – with cookies blocked, you may see the check again and again or be unable to get through.
What changes if we add analytics later?
One day we may want to measure which pages help buyers decide. If we add analytics, or any other tool that isn’t strictly necessary, consent comes first:
- Before the tool goes live, we update this page and the date at the top, naming each cookie, who sets it, what it’s for and how long it lasts.
- Nothing optional loads until you choose – analytics stays off unless you opt in.
- A Global Privacy Control signal counts as a no – optional tools stay off without you having to click anything.
- Rejecting is as easy as accepting: same screen, same number of clicks.
- You can change your choice at any time from a link in the footer.
- Names, email addresses, store URLs and message text never go into analytics.
| If we add | What it could set, and what happens first |
|---|---|
| An embedded booking calendar or chat widget | The provider’s own cookies. Its code runs only after you consent or click to load it. |
| Advertising or retargeting pixels | Cookies that follow you across sites. Not used today – and only ever with your opt-in consent. |
Questions about this policy?
This policy covers ouxp.com, run by OUXP (Outstanding Experience), a Shopify Plus agency. Questions about it go to the same team that answers everything else – by email, by phone or through the contact form.
- hello@ouxp.com
- Phone
- +1 (818) 651-3226
- Hours
- Mon–Fri, 9 AM–9 PM ET (6 AM–6 PM PT)
- Based in
- Los Angeles, California
During business hours, an engineer replies within 30–60 minutes.