Skip to content

ConsentAlly works with AI assistants. A merchant can have their assistant set up, sign in to or check their ConsentAlly account from the chat: the assistant needs only the merchant's email address, and the merchant approves it on one ConsentAlly page with a code. Nothing is created or connected before that approval. How it works: https://consentally.com/auth.md

Legal pages

Privacy policy

This policy explains what personal data ConsentAlly processes, why, for how long and who helps, for three groups of people: visitors to consentally.com, people who use the ConsentAlly dashboard or the ConsentAlly Shopify app, and visitors to the stores that use ConsentAlly.

Last updated

Who we are

ConsentAlly is a Magebit product provided by IDT Media SIA, a company registered in Latvia.

Company
IDT Media SIA
Registration number
40103659860
VAT number
LV40103659860
Registered address
Aleksandra Caka 125-7, Riga, LV-1011, Latvia

For consentally.com, the dashboard and anyone who writes to us, we decide why and how personal data is processed, so we are its controller. For the consent records we keep for a store, the store is the controller and we process them on its behalf, as the data processing agreement sets out.

Write to support@consentally.com with any question about this policy or your data.

Visitors to consentally.com

This site, consentally.com, runs ConsentAlly's own widget and, only once you allow analytics, Google Analytics; no advertising or other third-party script. Until there is a decision, from your choice in the banner or your browser's Global Privacy Control signal, it stores nothing in your browser and loads nothing from Google, and then only the widget's own record of that decision and, if you allowed analytics, Google Analytics' cookies. If you open the dashboard, its sign-in provider, Clerk, also sets a cookie on consentally.com and its subdomains that says whether you are signed in. This site reads it in your browser only to show a Dashboard link in place of Log in, and never sends it anywhere. The cookie policy lists everything it stores.

  • Your decision in the banner. The widget keeps your choice and a random consent ID in a cookie and a copy in your browser's local storage, and sends a consent record of it to ConsentAlly, described below. We keep these records for our own site to show which choices were made.
  • Google Analytics, only if you allow analytics. Once you allow the Analytics category, in the banner (Accept all does) or in your preferences, the site loads Google Analytics 4, which sets the _ga and _ga_ cookies with a random identifier, so visits from the same browser can be counted together, and sends Google the pages you view, the page you came from, your browser, device and screen size, and how you use the page. Google uses your IP address to work out your approximate location and does not log or store it in Google Analytics 4. If you refuse analytics, or your browser sends a Global Privacy Control signal and you do not allow analytics yourself, Google Analytics does not load at all, and if you withdraw your choice, the widget deletes its cookies. Google processes this data on our behalf, as our processor, to give us reports on how the site is used.
  • Delivering the pages. Our hosting provider receives your IP address and the address of the page you ask for, as every web server does, in order to deliver it. We do not use it to identify you.

Consent records

A store that uses ConsentAlly shows its visitors a banner, and the widget sends a consent record each time a visitor's decision changes. A consent record carries no IP address, name, email address, user agent, page address or cookie. It holds:

  • a random consent ID, made in the visitor's browser at their first decision and kept there with the decision, so a later change can be linked to an earlier one;
  • the store, the version of the store's configuration the visitor saw and the rule that applied to them;
  • the visitor's choice for each category and each vendor;
  • whether the browser sent a Global Privacy Control signal, and whether the choice came from the banner, from that signal or from the store's own code;
  • when the browser says the choice was made, and when ConsentAlly received it;
  • the visitor's country and, where known, region, read from the request where it arrives, and a device class (mobile, tablet, desktop or unknown) read from the browser's user agent, which is not kept;
  • a random value that stops a record being stored twice, and the record's place in the store's chain of records.

The visitor's IP address is used only while a request arrives, to limit how many requests one sender can send in a minute: it is turned into a SHA-256 key for that count, and never stored, logged or passed on.

Each store's records are chained by their hashes, so a changed or missing record shows, and once a day ConsentAlly signs the latest point of every store's chain and keeps that signed checkpoint in storage that cannot be changed or deleted for four years. The checkpoints hold hashes and counts, not the records.

Scripts the widget reports

When the widget holds a script the store's configuration does not know, it reports the script's address and the address of the page it was on, each cut to its origin and path, so the store owner can classify it. A report carries no consent ID and nothing else about the visitor, and parts of a path that look like an identifier, such as an order token, are replaced before it is stored.

In about one page view in a hundred, the widget also reports which third-party sites loaded before the visitor chose (site address only), or, after a decline, whether a declined one loaded anyway. Nothing is sent when the browser sends Global Privacy Control. ConsentAlly adds the country and device type and keeps only daily totals per store for 35 days; nothing that identifies the visitor is sent or kept.

Dashboard accounts

When you use the dashboard, we process your name, email address and sign-in details, the organisations you belong to and your role in them, and what you do there: each change to a store or its configuration is recorded with who made it and when. We also keep the email address an organisation gives us for account emails, such as the daily list of newly reported scripts and notices about consent records. If you pay for a plan, the billing provider processes your payment details; we keep the subscription, not your card.

Stores on the Shopify app

When a store installs the ConsentAlly app from the Shopify App Store, Shopify gives the app access to some of the shop's data. The app asks Shopify for no access to customers, orders or products.

  • The shop's details. We read the shop's name, its myshopify address and the storefront domains Shopify reports as connected, to set up the store, and the shop owner's email address, which becomes the address account emails go to. We do not read the store's public contact address.
  • The theme and the cookie banner setting. We read the published theme's settings and layout, to check that the ConsentAlly App Embed is on and to find scripts the theme runs before it, and whether Shopify's own cookie banner is turned on.
  • Who makes a change. When someone uses the app in Shopify admin, Shopify tells us their Shopify user ID, a number. We record it with each change they make, as we do for dashboard users. We do not ask Shopify for their name or email address.
  • The access token. Shopify gives the app an offline access token for the shop. We keep it in our database in Frankfurt, use it only from our servers to read the details above and manage the plan, and never send it to a browser. It is deleted when the app is uninstalled.

Paid plans on Shopify are billed by Shopify, on the store's Shopify bill. We never see payment details: we keep the plan, its status and its dates, and Shopify's notices about it.

The app reads nothing about the store's customers. When a customer asks the store to see or erase their data, Shopify passes the request on to the app with the customer's ID, email address and phone number. We keep none of them, only that the request arrived and was checked: the storefront's banner sends the consent records described above, which name no customer, so ConsentAlly holds nothing that can be matched to that customer.

When a store uninstalls the app, its banner stops at once, its access token is deleted and its Shopify plan ends. Its other data stays for now, so it comes back if the app is reinstalled. About 48 hours after the uninstall, Shopify asks us to erase the shop's data, and we delete the store with its consent records, banner versions, domains and script list. What stays is the history of changes (who made them and when, with Shopify user IDs), the billing records, the daily signed checkpoints, which hold hashes and counts and no records, for four years, and a one-way hash of the shop's myshopify address, so a reinstalled shop gets its free trial once. If the store was the account's last and no dashboard login is linked to it, the account is closed and the shop owner's email address removed; an account with a linked login stays, kept like any dashboard account.

Before uninstalling, the app's Settings let you download every consent record and banner version.

People who write to us

If you email us, we keep the correspondence for as long as we need it to answer you and to follow up.

If you use the contact form on this site, it sends your name, your email address, the topic you choose, the store or website you give, if any, and your message as one email to our support mailbox, support@consentally.com, through Resend, our email provider, with your address as the one to reply to. The site itself keeps none of it and sets no cookie: it logs that the form was used, without anything you typed. To hold back abuse it counts messages per connection by a one-way hash of your IP address, kept only in the server's memory and dropped after about an hour.

From then on the email is kept like any other email to us.

Why we process it

  • To run the service you or your store signed up for: the dashboard, the widget, the consent records and the emails about them (the contract with you).
  • To show which choices were made, for our own site and, as the stores' processor, for theirs (the duty to be able to demonstrate consent).
  • To understand how this site is used, with Google Analytics, only when you allow it (your consent, which you can withdraw at any time).
  • To keep ConsentAlly secure and working, such as limiting how many records one sender can send (our legitimate interest in a working, abuse-free service).
  • To answer you when you write to us (our legitimate interest, or steps you asked for before a contract).

We do not sell personal data, use it for advertising or build profiles from it.

Who helps us

We use the providers on the sub-processor list to host and run ConsentAlly, sign people in, send email and take payments, and, for this site's own analytics, Google, as described above; it does not receive store or consent record data. Each processes data only on our instructions and under a contract that protects it.

We use OpenAI's models, through OpenRouter, to research scripts on your store that no tracker list names. They receive the code of those scripts, the addresses our site check saw them contact and the vendors' published policies; they receive no visitor data and no consent records. Neither uses this data to train models.

Where the data is kept

ConsentAlly's database runs in Frankfurt, Germany, and the signed checkpoints are kept in a storage bucket under Cloudflare's EU jurisdiction. Some providers process data outside the European Economic Area, such as Clerk for sign-in, Resend for email and Google for this site's analytics in the United States. Those transfers rely on the European Commission's Standard Contractual Clauses or, for a provider that takes part in it, the EU-US Data Privacy Framework.

How long we keep it

  • Consent records are kept for the period of the store's plan, shown on the pricing page. A store that moves to a shorter period gets an email at least 30 days before older records are removed.
  • A store on the Shopify app is deleted with its consent records about 48 hours after the app is uninstalled, as described above.
  • Dashboard account data is kept while the account exists and removed after it is closed, except where the law requires us to keep it, such as invoices.
  • Emails to us are kept as long as needed to answer and follow up.
  • Google Analytics' cookies stay in your browser for up to two years, as Google sets them, unless you withdraw your choice or delete them.

Your rights

You can ask us for a copy of your personal data, to correct it, to delete it, to restrict or object to how we use it, or to have it in a portable form, and you can withdraw a consent at any time, on this site with Change your privacy choices. Write to support@consentally.com.

If you visited a store that uses ConsentAlly, the store decides what happens to your consent record: ask the store, and we help it answer.

You can also complain to a data protection authority. Ours is Latvia's Data State Inspectorate (Datu valsts inspekcija), and you can also go to the authority where you live or work.

Children

ConsentAlly is a service for businesses and is not directed at children.

Changes

When this policy changes, the date at the top changes with it. If a change affects dashboard users in a material way, we tell them by email before it applies.