How do I add a do not sell my data page to OpoShop?
the simplest way to add a do not sell my data page to OpoShop
The simplest way to add a do not sell my data page to OpoShop is to publish a page that tells shoppers how to submit a privacy request, then place that page in your footer where California shoppers can actually find it.
That page can send requests to a form, an inbox, or an app that handles privacy requests for you. What matters is not the page alone. What matters is that the request has a real destination and a real workflow behind it.
A lot of merchants stop at the page copy. That is where trouble starts. A page with no submission path is just a dead end.
If you also want consent and privacy requests handled in one place, there is a faster no-code path for OpoShop stores.
What is a do not sell my data page on OpoShop?
A do not sell my data page on OpoShop is a storefront page that gives shoppers a clear place to ask you not to sell or share their personal information, and often to ask for data deletion too.
For an independent merchant, that usually means plain language, a short explanation of what the shopper can request, and a way to submit the request without hunting through your site. California shoppers often expect to see this link in the footer. EU and UK shoppers may be more focused on consent before tracking starts, but they still need a clear privacy-request path.
So no, this is not just another policy page.
A privacy policy explains what your store does. A do not sell my data page gives the shopper a way to act on their rights.
Why does a do not sell my data page matter for OpoShop merchants?
A do not sell my data page matters because OpoShop merchants selling into California need a visible request path, and merchants selling into the EU and UK often need consent controls and privacy-request handling working together.
California rules focus attention on the shopper's right to tell a business not to sell or share personal information. That is why a hidden contact address buried in a long policy page is weak. A visible page and footer link are much clearer.
The EU and UK add a different pressure point. Before non-required tracking tools fire, shoppers often need a real consent choice. That means cookie consent and privacy requests are related, but they are not the same thing.
This is the part a lot of merchants miss. A do not sell page does not replace consent controls. And a cookie banner does not replace a privacy-request page.
If your OpoShop store uses Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, or TikTok, you need to think about both sides: tracking consent and incoming requests.
How do you add a do not sell my data page to OpoShop?
You add a do not sell my data page to OpoShop by choosing how requests will be collected, publishing the page, writing clear request language, connecting the page to a request workflow, and linking it in your footer.
Here is the practical version.
First, decide how shoppers will submit requests. If requests go to a single inbox with deadlines tracked, that is workable. If requests go to a personal email address you rarely check, that is where things break.
Second, create the page inside OpoShop. Use a title shoppers will understand right away. "Do Not Sell or Share My Personal Information" is clearer than "Privacy Preferences."
Third, add copy that tells shoppers what they can do there.
Weak: "Contact us for privacy questions." Stronger: "Use this page to submit a do not sell or data deletion request. Include your name, email address, and the details of your request so we can respond."
Fourth, connect the page to a workflow. A form that sends requests nowhere is not a workflow. A page that feeds one organized inbox is.
Fifth, add the link to your OpoShop footer navigation. Footer placement matters because shoppers expect privacy links there. If the link is hard to find, the page is doing half the job.
Best ways to set up a do not sell my data page on OpoShop
The best setup depends on how much manual work you can tolerate, but most no-dev merchants do better with a setup that combines consent and privacy requests instead of patching them together.
| Approach | What it looks like | Good fit | Main downside |
|---|---|---|---|
| Manual page only | A page with text and an email address | Very small stores with low request volume | Requests are easy to miss, and deadlines are hard to track |
| Page plus contact form | A page linked to a form submission workflow | Merchants who want a clearer intake path without custom code | Consent and privacy requests still live in separate places |
| App-based setup | A branded consent banner plus a request destination and request tracking | OpoShop merchants selling into California, the EU, or the UK without a developer | Requires choosing one tool and setting it up once |
The manual route looks simple at first. Then the requests start arriving in different places, and you have to remember what is pending.
A page plus form is better. At least shoppers have a clear path. But you are still stitching together consent, request intake, and deadline tracking by hand.
For most merchants, one setup is easier to live with. Region-aware consent for the EU and UK, a visible request path for California, and one inbox for incoming requests solves the real day-to-day problem.
If you want that without custom code, we built Consently for exactly this kind of OpoShop setup.
Common mistakes when adding a do not sell my data page
The most common mistakes are hiding the link, publishing a page with no request path, relying on email alone, and assuming the page covers tracking consent too.
A hidden footer link is a real problem. If a California shopper has to guess where the request page lives, your setup is weaker than it should be.
A page with no submission path is another common miss. If the page says "email us" but does not tell the shopper what to send, requests come in incomplete and messy.
Relying on email alone sounds fine until you picture a Friday afternoon. One request lands in support, one lands in your personal inbox, one gets buried under order notifications. That is how deadlines slip.
And then there is the biggest mix-up of all. A do not sell page is not a substitute for blocking non-required tracking until the shopper agrees. If your OpoShop store uses Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, or TikTok, the consent side still needs its own setup.
What we recommend for most OpoShop stores
Most OpoShop stores should use a no-dev setup that combines region-aware consent, a visible privacy-request destination, and deadline tracking in one place.
That recommendation is pretty simple. If you do not have a legal team and you do not want custom code, do not build this as three separate projects. Put the banner, the request path, and the request workflow together so the store is easier to manage.
That matters even more if you sell across regions. EU and UK shoppers often need consent choices before non-required tracking starts. California shoppers often need a visible do not sell request path. One clean setup handles both without turning your footer into a maze.
Best answer: For most OpoShop merchants, the cleanest answer is to publish a visible do not sell my data page, link it in the footer, and use a setup that collects privacy requests in one organized place while also handling region-based consent for tracking tools. That gives shoppers a clear path and gives you a workflow you can actually keep up with.
Want the fastest no-dev setup? Use Consently to add a branded consent banner, collect do not sell and deletion requests, and keep request deadlines in one inbox.
FAQs
Does OpoShop have a built-in do not sell my data page?
OpoShop does not usually give merchants a complete built-in do not sell my data page with request handling out of the box. Most merchants need to create the page themselves or use an app that provides a request destination and workflow.
What information should be on a do not sell my data page?
A do not sell my data page should tell shoppers what they can request, how to submit the request, and what details you need to identify their record. A clear page usually includes do not sell language, data deletion language if you support both in one place, and a form or request path that is easy to use.
Do I need both a cookie banner and a do not sell page on OpoShop?
Yes. A cookie banner handles consent for non-required tracking tools, while a do not sell page gives shoppers a place to submit privacy requests. Those two jobs are related, but they are not the same.
Can shoppers request data deletion from the same place?
Yes. Many OpoShop merchants use one privacy-request page for both do not sell requests and data deletion requests, as long as the page explains the options clearly. One page is often easier for shoppers and easier for merchants to manage.
How do I add the page to my OpoShop footer navigation?
Add the page in OpoShop first, then include that page in your footer navigation menu so the link appears across the store. Use clear link text that shoppers will right away, not vague wording like "Help" or "Info."
Do I need a developer to set this up on OpoShop?
No. Most OpoShop merchants can set up the page, footer link, and request flow without a developer if they use built-in page editing and a no-code app or form workflow. The hard part is not the page build. The hard part is making sure requests are organized and deadlines do not get missed.
Summary
Adding a do not sell my data page to OpoShop is not hard. Publish the page, make the link visible in your footer, give shoppers a real way to submit requests, and make sure those requests land in a workflow you can manage.
If your store sells into California, that visible request path matters. If your store also sells into the EU or UK, consent for tracking tools matters too. The cleanest setup handles both without custom code or a pile of manual follow-up.
If you want one place to handle the page, consent, and incoming privacy requests, start there.
