Skip to content
Log inStart free

Customer Privacy

Customer privacy is spread across three places in the admin: a settings page for what applies to everybody, the actions on one customer for what one person has asked, and a queue of requests waiting to be approved or rejected. This article maps the settings page row by row and says which of the three you want.

Updated
Reading time
5 min
On this page

Customer privacy in Tanqory is not one screen, and knowing which of the three you want saves most of the hunting.

Where What it is for
Settings > Customer privacy What applies to everybody: your policy, checkout consent, where data lives
More actions on a customer What one person has asked you to do about their own data
Customers > Data requests The queue of requests waiting for somebody to approve or reject them

This article is the settings page. Handle Customer Privacy Requests takes the other two, the actions and the queue, from start to finish.

The settings page, card by card

Go to Settings, then Customer privacy. Changing anything here takes the Edit privacy settings permission, which the roles screen lists under Customer privacy settings beside View privacy settings; writing the policy itself takes Edit privacy policy, which is separate again.

The Customer privacy settings page in the admin, headed Customer privacy. A Privacy compliance card holds Privacy policy with its last updated date and an Automated badge, Cookie banner reading Visible in 15 regions, and Data sharing opt-out page reading 0 regions selected with an Active badge. A Marketing consent card holds Email and SMS marketing in checkout, reading Email Disabled and SMS Disabled, and Double opt-in for marketing with a toggle switched off. Below them a Data storage hosting location card shows the hosting region with a note to contact support to change it, and a Tanqory Network Intelligence card reads Network protection disabled beside an Enable button (opens full size)

Four cards, and the controls are not all the same kind. Most rows carry a chevron and open something else, but Double opt-in for marketing is a toggle you switch here, the hosting region is a label with no control at all, and network protection has its own Enable button. Read the right-hand end of a row before you expect it to open.

Card What it holds
Privacy compliance Privacy policy, with the date it last changed and a badge saying it is maintained automatically; Cookie banner, with the number of regions it is visible in; and Data sharing opt-out page, with the number of regions it is switched on for and a badge saying whether it is active
Marketing consent Email and SMS marketing in checkout, which reads enabled or disabled for each channel separately; and Double opt-in for marketing, a toggle described on the page as requiring customers to confirm their email address before being added to your marketing list
Data storage hosting location The region your customer data is stored in, shown as a chip. It is reported, not chosen: the line beside it says to contact support to change it
Tanqory Network Intelligence A network protection setting, off on this store, with an Enable control

Double opt-in is the row to look at first if you send marketing. It is the difference between a list of people who typed an address at checkout and a list of people who confirmed one, and it is off until you turn it on.

The hosting region is worth reading even though you cannot change it here. Where customer data is held is a question you will be asked eventually, and this page is where the answer is written down.

Where these settings show up elsewhere

Privacy is not a corner of its own. Three of these rows are the same thing you will meet under another name.

On the privacy page Where else it appears
Privacy policy The policy itself is written under Settings > Policies, alongside the terms of service and the return rules. This page only reports its date and whether it is automated
Email and SMS marketing in checkout Decides whether shoppers are asked to opt in while buying. What each of them then agreed to is recorded per person, on the Marketing lines of their record
Double opt-in for marketing Governs how someone joins the marketing list at all, so it sits behind the email and SMS consent you read on each customer

Reading the policy's date here tells you whether it is current; changing it happens on the Policies page.

What the per-customer side does

A privacy request is about one person, so it is handled on their record rather than here. More actions at the top of a customer's page carries three privacy entries among its seven: Request customer data, Erase personal data and Delete Customer.

Requests that arrive from elsewhere do not appear on this settings page either. They queue under Customers > Data requests, each with a due date and an Approve and a Reject, and nothing in the admin chases them.

An erasure is scheduled rather than immediate, and it can be cancelled up to its date. After that date the dialog says the data cannot be retrieved. It is repeated here because it is the one thing worth knowing before anyone on your team opens that menu.

Which one you want

The situation Where to go
A customer has emailed asking for their data Their record, More actions
Something is already waiting for an answer Customers > Data requests
You are asked what your store does with data in general This page
You want to stop adding unconfirmed emails to marketing This page, Double opt-in for marketing
Someone asks where the data is held This page, Data storage hosting location
You need to hand someone a spreadsheet of their record Export Customers

If something goes wrong

  • The privacy actions are missing from More actions. Your role may lack Edit customers, which is what those actions sit behind rather than the privacy permissions on this page.
  • A row will not open. Check what is at its right-hand end. A toggle, a chip and an Enable button all look like rows that should open something, and none of them does.
  • You cannot change the hosting region. It is not editable from this page by design, and the page says to contact support.
  • You can read the page but nothing on it responds. Your role may hold View privacy settings without Edit privacy settings.

Next steps

Still stuck?

More in Customers

  • Customer Segments

    A segment is a saved question about your customers rather than a saved list, so its members change as they do. Tanqory gives you two ways to write that question, a query builder and a form of Field, Operator and Value filters, and this article covers both, plus the panel that starts closed, the AI Refine field and what to do when it answers with nothing, the forty-nine fields you can filter on, and everything the row menu lets you do to a segment afterwards.

  • Adding a Customer

    Creating a customer record by hand, from the Add Customer button to the saved record. Three fields are required and everything else can wait, the three marketing consents start unticked and are a record of what the customer agreed to rather than a way to opt them in, and the Save bar is on the form from the moment it opens.

  • Search the Customer List

    Finding one customer and finding a group are different jobs with different tools. The search box matches name, email and phone and nothing else, it searches inside the tab you are standing on rather than the whole store, and the thing people most often type into it, a tag, comes back as No customers found rather than as an error.

  • Customer Tags

    A tag gives a group of customers a name so it is already assembled when you need it. This article covers where tags are set, one record at a time or in bulk from the list, what a tag is actually good for once it exists, and the one thing it will not do, which is answer the search box.

All 49 articles in Customers

We use cookies

Necessary cookies keep the site working. With your permission we also use analytics and marketing cookies. Change your choice any time in Cookie settings.