Check your website’s privacy policy, cookies, terms and refund policy
A first-pass check of a small business website’s legal pages and consent: what the privacy notice must say, when cookies need consent, the refund and withdrawal rules for online sales, and what to put in terms, for the EU, UK, US (California), India and the UAE, with gaps listed for a lawyer.
This is a practical, copy-paste process for you are launching or redesigning a website that collects personal data or sells online. Use it when you want a clear structure, then add your own details.
Verified on 2026-10-2922 sources cited
Quick start
1. List every form, account, order or chat that collects personal details, and every tool on the site (analytics, ad pixels, email pop-ups, chat). 2. Your privacy page must name your business and say what you collect, why, who gets it, how long you keep it, and people's rights. A copied template will be wrong. 3. In the EU and UK, ad pixels and most analytics need a "yes" before they load. Offer "Reject" as clearly as "Accept", and check nothing loads before a choice. 4. EU and UK consumers can cancel most online orders within 14 days (for goods, from delivery), even if they have opened them. Refund within 14 days; for goods you may wait until they come back or the customer shows proof of sending. 5. EU online shops also need a "withdraw from contract here" button, then a "confirm withdrawal" button and an email receipt (since June 2026). 6. In the US only California was checked: sites collecting Californians' details need a posted privacy policy. India's new rules phase in by about May 2027 (the government has considered bringing this forward), so prepare your notice now. The UAE was not checked in detail. 7. This is a first-pass check, not legal or tax advice. Confirm with a qualified accountant or lawyer for your country.
Before you start
- You need a full data map, records of processing or a security review across the whole business. Check data-privacy compliance gaps
- You are reviewing a specific contract with a customer or supplier. Review a contract for risks (first pass)
- You process health, financial or children’s data at scale, or you have had a data breach or a regulator’s letter. Speak to a lawyer now.
- You want a policy written for you to publish without review. This method drafts and checks; a lawyer should sign off.
Full method
How to use this method
- 1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
- 2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
- 3. Add your materialAttach your own files, data or brief so the AI works from your facts, not guesses.
The prompt
Paste it as-is. The AI will ask for anything still in [BRACKETS].
# Check your website’s privacy policy, cookies, terms and refund policy Method by Deepstory Research: deepstoryresearch.com/method/website-privacy-terms You are a privacy and consumer-law specialist who reviews small business websites before a lawyer signs them off. Follow the method below step by step. Goal: A first-pass check of a small business website’s legal pages and consent: what the privacy notice must say, when cookies need consent, the refund and withdrawal rules for online sales, and what to put in terms, for the EU, UK, US (California), India and the UAE, with gaps listed for a lawyer. ## My inputs - Website and what it does: [WEBSITE_AND_WHAT_IT_DOES] (example: online shop selling candles, Shopify) - Where customers are: [WHERE_CUSTOMERS_ARE] (example: UK and EU consumers) - Data and tools used: [DATA_AND_TOOLS_USED] (example: GA4, Meta Pixel, Klaviyo, contact form) - Current legal pages: [CURRENT_LEGAL_PAGES] (example: privacy page from a template, no terms, 30-day returns) - Who runs the business and where: [WHO_RUNS_THE_BUSINESS_AND_WHERE] (example: sole trader based in Manchester, UK) Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source. ## Steps to follow 1. Confirm who runs the site, where the business and customers are, what it sells and to whom (consumers or businesses). 2. List the personal data collected and every tool that stores or reads data on the visitor’s device. 3. Check the privacy notice against the required contents for each jurisdiction involved. 4. Check cookie consent: which tools need consent first, which are exempt, and whether the banner blocks tags until a choice is made. 5. Check the refund, cancellation and withdrawal rules for online sales, including the EU withdrawal function. 6. Check the terms for the basics, then list gaps, a fix for each and the questions for a lawyer. ## Deliver the output in this structure - Jurisdictions covered and not checked - Data and tools map - Privacy notice gaps - Cookie consent check - Refunds, cancellation and withdrawal - Terms gaps - Fix list and questions for a lawyer ## Quality rules - Tie every gap to the rule and jurisdiction it comes from. - Never write a promise into a policy that the business does not keep. - Label the result a first-pass check, not legal or tax advice, and name the jurisdictions covered. - Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION. - If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED]. - End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.
What you need to give the AI
| Input | Placeholder | Example |
|---|---|---|
| Website and what it does | [WEBSITE_AND_WHAT_IT_DOES] | online shop selling candles, Shopify |
| Where customers are | [WHERE_CUSTOMERS_ARE] | UK and EU consumers |
| Data and tools used | [DATA_AND_TOOLS_USED] | GA4, Meta Pixel, Klaviyo, contact form |
| Current legal pages | [CURRENT_LEGAL_PAGES] | privacy page from a template, no terms, 30-day returns |
| Who runs the business and where | [WHO_RUNS_THE_BUSINESS_AND_WHERE] | sole trader based in Manchester, UK |
Use it when
- You are launching or redesigning a website that collects personal data or sells online.
- Your privacy page or terms were copied from a template or another company.
- You added tracking (analytics, ad pixels, email tools) and are not sure the cookie banner covers it.
Best with: A chat AI that can open web pages, or paste the current privacy page, terms and a list of the tags or apps installed.
What you get
- Jurisdictions covered and not checked
- Data and tools map
- Privacy notice gaps
- Cookie consent check
- Refunds, cancellation and withdrawal
- Terms gaps
- Fix list and questions for a lawyer
The AI will ask you first
Answer these before the AI advises you; each one changes what it recommends.
What is the website address, and can you paste the current privacy policy, terms and returns or refund pages (or say there is none)?
Each required item is checked against what the page actually says.
If unknown: Mark every item "not seen", ask for the pages before giving a final fix list, and treat any copied or template page as needing a rewrite.
Who runs the website (legal name, country) and where are your customers or visitors?
The privacy notice must name the business. The rules follow where customers are as well as where you are, and a business with no office in the EU or UK that sells there may need a local representative.
If unknown: Apply the rules of the business’s own country and of every country it sells or ships to, and list the rest as not checked.
Do you sell to consumers, to businesses, or both? Online, by phone or in person?
Withdrawal and cancellation rights apply to consumers buying at a distance, not to business buyers.
If unknown: Treat buyers as consumers buying online, the stricter case.
What personal data do you collect (forms, accounts, orders, chat, newsletters), and which tools are installed: analytics, ad pixels, chat widgets, email, payment?
The notice must list purposes and recipients, and every tool that stores or reads data on the device needs consent unless an exemption applies.
If unknown: Ask for a list of installed apps or plugins, or the page source; do not guess the tools.
Does the cookie banner stop tracking tags from loading until the visitor chooses, and is "Reject" as easy as "Accept"?
Consent must come before non-exempt cookies are set, and withdrawing consent must be as easy as giving it.
If unknown: Assume tags load before consent and flag it as the first thing to test.
What is your current returns or refund policy, and what do you sell (physical goods, digital content, services, sealed hygiene products)?
EU and UK consumers have a 14-day right to withdraw from most distance sales, with listed exceptions.
If unknown: Assume physical goods with no exceptions.
Do you send data outside the country (for example to US-based tools), and do you process data for your own customers (as a software provider)?
Transfers must be disclosed, and processing customer data on their behalf needs a separate data processing agreement.
If unknown: Assume US-based tools are used and list transfers as a question for the lawyer.
For US visitors: does the business have gross annual revenue of USD 26.625 million or more, buy, sell or share personal information of 100,000 or more California residents or households, or make half or more of its revenue from selling or sharing Californians’ personal information?
Meeting any one of these brings in the California Consumer Privacy Act.
If unknown: Assume the CCPA does not apply but California’s privacy-policy law does, and say so.
The procedure, step by step
Read this before you run it, so you can check the AI actually followed the method.
Scope
Business, location, customers, consumer or business sales, what is sold.
Map data and tools
Forms, accounts, orders, chat, email; every tag, pixel and plugin; where data goes.
Privacy notice
Check each required item per jurisdiction; mark missing, wrong or copied.
Cookies
Classify each tool (exempt or consent); test that the banner blocks tags before a choice; check Reject and withdrawal.
Refunds and withdrawal
14-day rules, exceptions, refund timing and return costs; EU withdrawal function.
Terms
Business identity, prices and taxes, delivery (or, for software, access and support), payment, complaints contact, governing law and courts, business-only clause if relevant; for subscriptions also renewal, free-trial conversion, refunds on cancellation, liability limits and what happens to customer data at the end.
Fix list
Each gap, the rule behind it, the fix and owner; questions for a lawyer.
Re-check
After any new tool or market, and at least every 90 days.
Platform settings(show)
| Platform | Path | Setting | Note |
|---|---|---|---|
| Google Analytics 4 | Admin > Property column > Data Settings > Data Retention | User-level and key event data: 2 or 14 months. Other event data: 2 or 14 months, or 26, 38 or 50 months on Analytics 360. Age, gender and interest data are always kept 2 months. | Match the retention period to what the privacy notice says. Standard aggregated reports are not affected. |
| Google tags (consent mode) | Consent banner or tag manager configuration | Basic consent mode blocks Google tags until the visitor interacts with the banner; advanced mode loads tags and sends cookieless pings while consent is denied. | Choose a mode with your lawyer; basic sends nothing to Google before a choice. |
Worked example
The figures below are illustrative. Use your own numbers and facts.
Scenario: The figures and tools below are an illustration; use only the user’s own facts. A UK sole trader sells candles from a Shopify store to consumers in the UK and EU.
Input: Tools: GA4, Meta Pixel, Klaviyo pop-up, Shopify checkout. Banner: "We use cookies. OK". Privacy page copied from a US company and naming that company. Returns: "unused items within 30 days, buyer pays return postage". No withdrawal button.
Output excerpt: Jurisdictions covered: UK (UK GDPR and PECR), EU (GDPR, ePrivacy, consumer withdrawal rules). Not checked: any other country. Privacy notice: names the wrong business and lists none of your tools; rewrite it with your legal name and contact details, each purpose and legal basis (orders: contract; newsletter: consent; analytics: per your cookie choice), recipients (Shopify, Google, Meta, Klaviyo), transfers to the US and the safeguard, retention periods, rights and the right to complain to the ICO or an EU authority, plus how to complain to you (since 19 June 2026 UK law requires you to make complaints easy and acknowledge them within 30 days). You sell to EU consumers without an EU office, so you probably need an EU representative named in the notice; ask the lawyer whether the occasional-processing exception could apply. Email: the Klaviyo pop-up signs up visitors who have not bought, so it needs an unticked opt-in; the UK existing-customer exception covers only people who bought or negotiated to buy, and only for your similar products. Cookies: the banner has no Reject choice and tags fire before any choice. The Meta Pixel and Klaviyo tracking need consent in both the UK and EU. GA4 needs consent for EU visitors; for UK visitors it may fall under the statistics exemption only if you explain it, offer a simple way to object, and data is not shared beyond help to improve the site. Google’s own data use makes this unclear, so ask the lawyer and use consent meanwhile. Refunds: 30 days is longer than the 14-day minimum, which is fine, but "unused items" is not: you cannot limit the legal 14-day right to unused goods, and may deduct only for loss in value from handling beyond what a shop would allow. Keep the 30-day offer if you like, but state the 14-day legal right separately. State that customers pay the direct return cost, refund within 14 days (for UK customers, 14 days after the goods come back or they show proof of sending; for EU customers, 14 days after they tell you, though you may wait for the goods or proof of sending), and add the EU "withdraw from contract here" function with its "confirm withdrawal" step and email receipt, required since 19 June 2026. Fix first: banner with Reject, tags blocked until choice; then the notice; then the withdrawal function. This is a first-pass check, not legal or tax advice. Confirm with a qualified accountant or lawyer for your country.
Check your result
Before you trust the AI's output, confirm each of these.
- ☐ Jurisdictions covered and not checked are named at the top.
- ☐ Every gap names the rule and jurisdiction behind it.
- ☐ Every installed tool is classified as exempt or needing consent, with a reason.
- ☐ Refund and withdrawal terms meet the 14-day rules where they apply, and the EU withdrawal function is checked.
- ☐ The output says it is a first-pass check, not legal or tax advice.
What you'll get(show template)
## Website legal check: [WEBSITE], [DATE] Jurisdictions covered: [only those involved among EU, UK, US (California only), India]. Not checked: [every other jurisdiction involved, for example Switzerland, other US states, and the UAE beyond a flag]. ### Data and tools Tool or form | Data | Purpose | Recipient | Stores or reads on device? | Consent needed? ### Privacy notice gaps Required item | Jurisdiction | Present? | Fix ### Cookie consent Check | Result | Fix ### Refunds, cancellation and withdrawal Rule | Your policy | Gap | Fix ### Terms gaps Item | Gap | Fix ### Fix list (in order) # | Fix | Owner | By ### Questions for a lawyer 1. [Question] This is a first-pass check, not legal or tax advice. Confirm with a qualified accountant or lawyer for your country.
Quality checks built into the prompt
- • Tie every gap to the rule and jurisdiction it comes from.
- • Never write a promise into a policy that the business does not keep.
- • Label the result a first-pass check, not legal or tax advice, and name the jurisdictions covered.
- • Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].
Decision rules
If/then rules the AI should apply. Heuristic rules are a practitioner's rule of thumb, not a platform rule.
| If | Then | Type |
|---|---|---|
| You collect personal data from people in the EU (and, under the UK’s version of the same law, the UK). | At the time you collect it, tell people: who you are and how to contact you; your data protection officer’s contact details if you have one; the purposes and legal basis for each use; your legitimate interests where you rely on them; who receives the data; any transfer outside the EU and the safeguard used; how long you keep it; their rights of access, correction, erasure, restriction, objection and portability; the right to withdraw consent where you rely on consent; the right to complain to a supervisory authority; whether people must give the data (for example to complete an order) and what happens if they do not; and any automated decision-making with significant effects. | Legal rule |
| You have no establishment in the EU (or in the UK) but offer goods or services to people there, or monitor their behaviour there. | Designate in writing a representative in the EU (or the UK) and name them in the privacy notice, unless your processing is occasional, does not include large-scale special-category or criminal-offence data, and is unlikely to put people at risk. Whether your processing is occasional is a question for a lawyer. | Legal rule |
| You sell regularly to EU or UK customers and use tracking pixels, with no office there. | Assume the occasional-processing exception does not apply until a lawyer confirms it does. | Heuristic |
| You collect personal data of people in the UK. | Since 19 June 2026 people can complain to you directly about how you use their data. Make complaints easy (for example an online form, and another way for people who cannot use it), acknowledge each complaint within 30 days, look into it, keep the person updated and tell them the outcome without undue delay.Threshold: 30 days to acknowledge | Legal rule |
| You rely on consent (for example for marketing emails or tracking). | Consent must be freely given, specific, informed and unambiguous, given by a statement or clear affirmative action, so pre-ticked boxes and "by using this site you agree" do not count. People must be able to withdraw it at any time, as easily as they gave it. | Legal rule |
| You send marketing emails to individuals in the UK (for example from a newsletter pop-up). | You need their prior consent, with one exception: for people whose details you got when they bought, or negotiated to buy, from you, you may market your own similar products and services if you gave them a simple, free way to refuse when you collected the details and in every message. In the EU the rule is similar: prior consent, or, for your own customers whose email you got in the context of a sale, marketing of your own similar products with an easy, free way to object at collection and in every message. National laws add detail; check the country. | Legal rule |
| A tool stores or reads information on a visitor’s device in the EU (cookies, pixels, local storage, SDKs). | Get consent first, after clear and comprehensive information about the purpose. The only exemptions are storage needed to transmit a communication, or storage strictly necessary for a service the visitor explicitly asked for. | Legal rule |
| You use analytics or advertising tags with EU visitors. | Treat them as needing consent: the Directive has no analytics exemption, although a few national regulators accept narrowly set-up audience measurement without consent. Check the visitor’s country with your lawyer before relying on that. | Heuristic |
| A tool stores or reads information on a visitor’s device in the UK. | Since 5 February 2026, consent is still the rule, with exemptions for communication, for what is strictly necessary for a service the user requested (including security, fraud prevention, fault detection, log-in and remembering choices), for statistics to improve your own service or website, and for adapting the site’s appearance or functions to the user’s preferences. The statistics and appearance exemptions apply only if you give clear information and a simple, free way to object; for statistics, the data must not be shared except with someone helping you improve the service. Advertising tags still need consent. | Legal rule |
| You use Google tags or Google advertising products with visitors in the EEA, the UK or Switzerland. | Google’s EU user consent policy requires legally valid consent for cookies where the law requires it and for personalised ads, records of consent, clear instructions on how to withdraw it, and naming each party that collects or uses the data. Google can limit or suspend the product if you do not comply. | Platform rule |
| EU or EEA consumers buy goods, services or digital content from you online. | They can withdraw within 14 days without giving a reason (for goods, counted from the day they receive them). If you did not tell them about this right, the period runs up to 12 months longer. Refund all payments, including standard delivery, within 14 days of being told; you may wait until the goods come back or the customer shows proof of sending. The customer pays the direct return cost only if you told them so beforehand. Exceptions include sealed goods unsealed after delivery that cannot be returned for health or hygiene reasons. | Legal rule |
| Consumers can buy from you through a website or app in the EU. | Since 19 June 2026 you must also offer an online withdrawal function, labelled "withdraw from contract here" or something equally clear, prominently displayed, easy to reach and available throughout the withdrawal period. It must let the customer give or confirm their name, which contract they are withdrawing from, and the email (or other electronic means) for the confirmation, then submit it with a second button labelled "confirm withdrawal" or equally clear wording. Then send an acknowledgement on a durable medium (for example email) without undue delay, with its content and the date and time it was sent. Your withdrawal information must also say where the function is. | Legal rule |
| Your returns policy says "unused only", "original packaging only" or "store credit only", or charges a restocking fee. | For EU and UK consumers the 14-day right cannot be limited this way. Customers may handle goods as they could in a shop; you may deduct only for loss in value caused by handling beyond what is needed to check the goods. In the UK, refund using the same payment method unless the customer expressly agrees otherwise, and with no fee; if you did not tell the customer about the right to cancel, you cannot deduct anything for handling. | Legal rule |
| EU consumers buy digital content that is not on a physical medium (downloads, streaming, online courses). | The right to withdraw ends once supply has begun only if all three apply: the customer gave prior express consent to start during the 14 days; they acknowledged that they lose the right; and you sent confirmation on a durable medium (for example in the order confirmation email). If any is missing, they keep the 14-day right. | Legal rule |
| UK consumers buy a service and ask you to start it within the 14 days. | You may start early only at their express request. If they then cancel, they pay a proportionate amount for what you supplied before they told you, unless you did not give them the required information about the right to cancel or about paying for an early start; then they pay nothing. They lose the right to cancel only once the service is fully performed, and only if they acknowledged they would lose it then. | Legal rule |
| UK consumers buy digital content that is not on a physical medium. | The right to cancel ends once supply has begun only if they gave express consent and acknowledged that they would lose the right. If consent or acknowledgement is missing, or you did not send the required confirmation, they pay nothing for content supplied during the cancellation period. | Legal rule |
| UK consumers buy from you at a distance. | They can cancel within 14 days: for services and online digital content, from the day the contract is made; for goods, from the day the goods (or the last item of a split order) arrive. Refund all payments, including the cheapest standard delivery, using the same payment method and with no fee. For goods you do not collect, refund within 14 days after the goods come back or the customer shows proof of sending; otherwise within 14 days after the customer tells you. If you did not give the required information about the right to cancel, the period runs up to 12 months longer. | Legal rule |
| Your website or app collects personally identifiable information from California residents. | California law requires the operator of a commercial website or online service that collects personally identifiable information from California consumers to post a privacy policy conspicuously. The cited guidance names no size threshold. | Legal rule |
| A for-profit business does business in California. | The California Consumer Privacy Act applies if it meets any one of: gross annual revenue of USD 26.625 million or more in the preceding calendar year (from 1 January 2025); buys, sells or shares personal information of 100,000 or more California residents or households; or makes 50% or more of annual revenue from selling or sharing California residents’ personal information. If it applies, the privacy policy must explain people’s CCPA rights and how to submit requests. In most cases a business that sells or shares personal information (for example through advertising pixels) must also put a clear "Do Not Sell or Share My Personal Information" or "Your Privacy Choices" link on the site, and it must honour opt-out preference signals such as Global Privacy Control. | Legal rule |
| You process personal data of people in India. | Under the Digital Personal Data Protection Act 2023, each request for consent must come with a notice describing the personal data and purpose, how to exercise rights and withdraw consent, and how to complain to the Data Protection Board, and people must be able to read it in English or any language in the Eighth Schedule to the Constitution. The DPDP Rules were published in the Gazette on 13 November 2025, and most duties apply 18 months later, from about 13 May 2027. Check the Gazette for any change to that date before relying on it. | Legal rule |
| You collect personal data in India before the DPDP duties apply. | Older rules under the Information Technology Act (section 43A and the 2011 rules on sensitive personal data) may still apply until replaced. This method did not check them; ask an Indian lawyer. | Heuristic |
| Your product stores or processes personal data for your customers (for example contact lists in a CRM). | Treat that data as handled on your customers’ instructions: offer a data processing agreement, a list of subprocessors, security measures, and export and deletion when a customer leaves. This method did not check processor duties or what your own privacy notice should say about this role; ask a lawyer. | Heuristic |
| Customers send health information through forms, email, chat or tickets (for example allergic reactions or pregnancy questions). | Treat it as special-category data: list it in the notice, limit who can see it, set a retention period, and ask a lawyer which legal condition you rely on, before adding an AI agent to that channel. | Heuristic |
| You run an online shop in the EU. | Also check with a lawyer for your country: a legal-notice page where national law requires one (for example the German Impressum), checkout button wording that makes clear the order must be paid for, and accessibility duties. This method does not state those rules. | Heuristic |
| You rely on the India May 2027 date. | Build the India notice now: secondary sources report that the government consulted in 2026 on bringing the date forward, and no notified change had been found when this method was checked. | Heuristic |
| The business is in the UAE. | The federal Personal Data Protection Law (Decree-Law 45 of 2021) applies on the mainland, but its executive regulations had not been confirmed as issued when this method was checked, and the DIFC and ADGM free zones have their own data protection laws. This method does not state UAE rules; mark UAE as not checked and ask a UAE lawyer. | Heuristic |
| The EU’s Digital Omnibus proposals mention cookie changes. | They are proposals, not law (EU governments agreed a negotiating position in October 2026; the European Parliament had not agreed its own). Keep following the current ePrivacy consent rule and re-check at the next review. | Heuristic |
| Your privacy page or terms were copied from another company or a template. | Rewrite them from your own data map: a copied policy names the wrong business, tools and purposes, and it promises things you may not do. | Heuristic |
| You write any policy. | Say only what the business actually does. A promise in a privacy policy that the business does not keep can itself be a breach of consumer or privacy law. | Heuristic |
| Your banner offers "Accept" on the first layer but hides "Reject". | Put "Reject all" on the first layer with the same prominence as "Accept all", and test with a fresh browser that no analytics or ad requests fire before a choice. | Heuristic |
| You sell to businesses only, or part of your sales are to businesses (for example wholesale). | Consumer withdrawal rights do not apply to business buyers. For business-only sites, say so in the terms and check buyers are businesses. For mixed sites, apply the consumer rules to the shop and keep business sales on separate terms. | Heuristic |
| Customers are outside the jurisdictions listed above. | Say that their rules were not checked. | Heuristic |
Failure modes
Common mistakes with this method, how to spot them, and how to fix them.
| Mistake | Symptom | Fix |
|---|---|---|
| Copying another company’s privacy policy. | The policy names the wrong business, tools and purposes. | Write it from your own data map and tool list. |
| A banner that informs but does not ask ("We use cookies. OK"). | Tracking runs without valid consent; ad platforms may restrict features. | Offer Accept and Reject with equal prominence and block non-exempt tags until a choice. |
| Testing the banner only as a returning visitor. | Tags fire on first load and nobody notices. | Test in a fresh private window and watch network requests before choosing. |
| Assuming the UK analytics exemption covers every analytics tool. | Third-party analytics run without consent where the data is shared for the provider’s own purposes. | Use the exemption only when its conditions are met (information, a simple objection, no sharing except to help improve the site); otherwise ask for consent. |
| A returns policy shorter than 14 days for EU or UK consumers, or "no refunds". | Unenforceable terms and complaints; the withdrawal period can run 12 months longer if consumers were not told. | Give at least the 14-day right with the legal exceptions, and say how to use it. |
| Returns allowed only for "unused" or "unopened" items, or refunds as store credit only. | The legal 14-day right is effectively refused; complaints and chargebacks follow. | Accept returns of handled goods within 14 days, refund the way the customer paid, and deduct only for loss in value from excessive handling. |
| No EU withdrawal function on an online shop. | Non-compliance since 19 June 2026. | Add a clearly labelled "withdraw from contract here" function with a "confirm withdrawal" step, send an email acknowledgement with the content, date and time, and say in the returns information where the function is. |
| Adding every customer or pop-up sign-up to marketing emails without a clear opt-in. | Complaints and regulator fines for unsolicited marketing. | Use an unticked opt-in at sign-up; use the existing-customer exception only for buyers, for similar products, with an opt-out at collection and in every email. |
| Promising things the business does not do ("we never share data"). | The policy itself becomes evidence of a breach. | Describe actual practice and update the policy when tools change. |
| Forgetting a software product processes its customers’ data. | No data processing agreement; customers’ due diligence fails. | Add a data processing agreement and a list of subprocessors, reviewed by a lawyer. |
| Treating this check as legal sign-off. | Policies published with gaps a lawyer would catch. | Use the fix list and questions with a qualified lawyer before publishing. |
Agent mode: if an AI agent runs this unattended
May do without asking
- • Read the live site’s privacy page, terms and banner, and list the tags that load before and after a consent choice.
- • Draft a revised privacy notice, cookie table and returns wording for the owner and a lawyer to review.
- • Compare the current pages with the required items and produce the fix list.
Must stop before (the user decides and does these)
- • Publishing or replacing any privacy policy, terms, returns policy or banner on the live site, including committing or merging changes to a repository that deploys automatically.
- • Changing tag, pixel, consent-mode or analytics settings, including data retention.
- • Installing, uploading or removing apps, plugins or scripts.
- • Accepting terms or data processing agreements with any vendor, or changing billing.
- • Spending money on a consent platform or other tool.
- • Replying to a customer, data subject request or regulator.
Evidence for this method
This method runs on your own material: your files, brief or code. If your task needs market or economic numbers, attach a sourced context file from the evidence library alongside the prompt.
Browse evidenceRun next
Methods that chain well after this one.
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.