Cookie Policy
Last updated: 24 August 2026.
What cookies are
Cookies are small text files that a website stores on your device so it can remember you between page loads. Similar technologies, such as local storage, serve the same purpose. This policy covers ace.authoritas.com, and also the cookies Rezolve Ai software sets on a merchant's own storefront when they switch on A/B testing. It explains exactly what is set, by whom, and why.
Cookies we set on ace.authoritas.com
We set only strictly necessary first-party cookies. They exist so the product can work at all, and they are exempt from the consent requirement under the ePrivacy rules. That is why you do not see a cookie banner on this site: there is nothing optional to consent to.
| Cookie | Purpose | Lifetime |
|---|---|---|
| sb-*-auth-token (and numbered chunks) | Keeps you signed in. Holds your encrypted session and refresh token, issued by our authentication provider (Supabase). | For the session, refreshed while you stay signed in |
We use no third-party analytics cookies, no advertising cookies, and no cross-site tracking on this site. If that ever changes we will add a consent banner first and update this policy.
Storefront analytics on merchant stores
Separately from this website, a merchant can switch on Rezolve Ai storefront analytics for their own Shopify store. It measures how their product pages and articles perform after their content is updated. It runs as a Shopify web pixel, which means Shopify loads it only when the shopper has given analytics consent through the store's own banner, and it stops immediately if that consent is withdrawn.
Storefront analytics on its own sets no cookie. It records which page was viewed, whether an item was added to the basket, and the products and totals in a completed order, together with an identifier Shopify supplies to distinguish one visit from another, which we convert to a keyed hash before storing and erase after 35 days. It never receives or stores a shopper's name, email address, phone number or postal address, and our systems reject any event that arrives carrying one.
On their storefront the merchant is the data controller and their own privacy and cookie policies apply. Rezolve Ai processes this data on their behalf as described in our Data Processing Addendum.
A/B testing cookies on merchant stores
A merchant can also switch on A/B testing, which shows different versions of a product description to different shoppers and measures which one performs better. This is the only Rezolve Ai feature that stores a cookie on a shopper's device, and nothing is stored until the merchant has both switched it on and started a test that is actually live. On Shopify that means enabling the Rezolve Ai app embed in their theme; on WordPress, the Rezolve Ai plugin from version 4.5.0 with the A/B setting turned on, which is off by default and stays off through upgrades. A store with the feature available but no test running stores nothing.
Consent comes first, and there are two separate permissions. Nothing is stored until the shopper has given preferences consent, because remembering which version to show someone is a personalisation choice rather than a measurement one. Reporting what they then did needs analytics consent, asked and answered independently. Consent is read from the store's own mechanism: Shopify's Customer Privacy API, or the WordPress Consent API, which is what the common consent plugins implement. If a store has no consent mechanism at all, the answer is treated as no: nothing is stored, nothing is reported, and every shopper sees the store's normal copy.
| Cookie | Purpose | Lifetime |
|---|---|---|
| _ace_vid | A random identifier, generated in the browser, so the same shopper is shown the same version on a later visit rather than a different one each time. It is not derived from anything about the shopper and is not used to build a profile. | 365 days |
| _ace_arm_<test> | Which version of the copy this shopper is being shown, for one specific test. One cookie per test the store is running. | 90 days |
Both are first-party cookies on the merchant's own domain, and neither is readable by us or by anyone else across sites. On WordPress the identifier is scrambled with a secret unique to that store before anything is sent to Rezolve Ai, so the same shopper visiting two different stores produces two unrelated values that cannot be matched. What reaches Rezolve Ai is the scrambled identifier, which version was shown, and whether that shopper reached checkout. We erase the identifier after 35 days and the underlying events after 90.
Search engines and AI crawlers are never included in a test. They carry no cookie and give no consent, so they always receive the store's normal copy. That is the same rule applied to a first-time shopper, not a separate rule for crawlers: nothing in this feature examines who or what is asking for the page.
As above, the merchant is the data controller on their own storefront. It is their responsibility to obtain consent and to describe these cookies in their own cookie policy, and Rezolve Ai processes what results on their behalf under our Data Processing Addendum.
Controlling cookies
You can block or delete cookies in your browser settings at any time. Because our only cookies are the ones that keep you signed in, blocking them means you will not be able to stay logged in to Rezolve Ai. Instructions for common browsers are available in each browser's help pages.
Questions
Contact our data protection team at DPM@rezolve.com (Rezolve Ai Limited, 21 Sackville Street, London W1S 3DN, England), or see the full Privacy Policy.