1Who we are
Olvio is an AI advisor for Shopify stores: it answers shoppers on product pages, in a guided advice flow and on the contact page, and lets the Merchant's team answer them directly. It is published and operated by:
Topicimes
3 Avenue René Laennec, 72000 Le Mans, France
SIRET: 90496525800018
President: Louis Jodon de Villeroché
Contact: help@olvio.ai
In this policy, "Olvio", "we" and "our" refer to Topicimes acting as the publisher of the Olvio Shopify application.
2Data Protection Officer
Topicimes has voluntarily designated a Data Protection Officer (DPO) responsible for ensuring compliance with this policy and with applicable data protection regulations:
Louis Jodon de Villeroché
Data Protection Officer, Topicimes
Email: help@olvio.ai
You may contact the Data Protection Officer at any time with any question relating to this policy, to exercise your rights or to report a data protection concern.
3Scope of this policy
This policy describes the data processed when the Olvio Shopify application is installed on a Merchant's Shopify store, when Shoppers use Olvio on the Merchant's storefront, when the Merchant's team uses Olvio's admin at app.olvio.ai, when visitors browse olvio.ai and when partners use the affiliate portal.
Five categories of people are covered:
- Merchants: owners of a Shopify store who install Olvio.
- Team members: the people the Merchant invites into Olvio, with a role (Owner, Admin or Member) and, for those who answer Shoppers, agent status.
- Shoppers: visitors to the Merchant's storefront who use Olvio.
- Site visitors: visitors to olvio.ai.
- Affiliate partners: the businesses enrolled in Olvio's affiliate program (affiliate.olvio.ai).
Olvio does not require Shoppers to create an account or sign in. The AI is instructed never to ask for a name, email, phone number or address. Three features ask for an email address, and only when the Shopper uses them: order tracking, the Inbox and the Advisor's results, which can also go by WhatsApp (section 5.2). This information is never required to chat with the assistant: without it, only the feature concerned is unavailable.
4Our role (Data Controller and Data Processor)
Topicimes acts in two distinct capacities under the GDPR, depending on the data category:
- Data Controller: for the Merchant's account data (Shopify identifiers, plan, configuration, encrypted credentials), for team member accounts, for the data of olvio.ai visitors and affiliate partners, and for the technical logs needed to run the service.
- Data Processor (article 28 of the GDPR): for Shopper data processed on the Merchant's behalf (conversations with the AI and with the team, session identifier and conversation token, email addresses, files, page viewed and cart shared in the Inbox, emails and numbers typed to receive Advisor results, widget events, question logs, orders, order lookups). The Merchant remains the controller of this data; it is the Merchant's responsibility to inform Shoppers, in particular in its own privacy policy, and to collect any required consent on its storefront.
The processor clauses required by article 28(3) of the GDPR are set out in section 4.1 and form part of our Terms of Service. A standalone Data Processing Agreement (DPA) is available on request at help@olvio.ai.
4.1Processor clauses (article 28 of the GDPR)
For the data it processes on the Merchant's behalf, Topicimes undertakes to comply with the following clauses:
- Subject and duration: process this data only to provide Olvio to the Merchant, for as long as the application is installed. The nature of the processing, the data and the people concerned are described in section 5.2, the periods in section 11.
- Instructions: process it only on the Merchant's documented instructions, meaning these clauses, the Terms of Service and the settings it chooses in Olvio, unless a legal obligation applies, of which Topicimes informs it beforehand where the law allows. Topicimes warns it if an instruction appears to breach the regulations.
- Confidentiality: give access only to authorized people bound by confidentiality.
- Security: apply the measures described in section 13.
- Subprocessors: the Merchant authorizes those in section 12. Topicimes informs it of any planned addition or replacement, so that it can object, imposes the same obligations on them and remains liable for their failures.
- Data subject rights: help it answer access and erasure requests, which Shopify forwards to us (customers/data_request, customers/redact).
- Assistance: help it meet its obligations on security, breach notification (section 14), impact assessments and consulting the supervisory authority.
- End of service: delete the data on uninstall (section 11). A Merchant who wants a copy asks help@olvio.ai before uninstalling.
- Audit: make available the information needed to demonstrate compliance with these clauses and allow audits, including inspections, conducted by the Merchant or an auditor it appoints, on written request and with reasonable notice, while respecting confidentiality.
5Information we collect and store
Olvio retains only the data strictly necessary to provide the service. The sections below enumerate every category of data we store in our own infrastructure.
5.1Merchant data
When a Merchant installs and configures Olvio, we store:
- Store identifiers: the .myshopify.com domain, the storefront's primary domain and the access tokens issued by Shopify, encrypted with AES-GCM (256-bit) before they are stored.
- AI provider credentials: the API key the Merchant supplies for the AI provider they have selected. Keys are encrypted with AES-GCM (256-bit) and cryptographically bound to the store domain as additional authenticated data before being written to our database. They are never displayed in plaintext again. The same goes for the Kanal service key, if the Merchant connects one: only its last four characters are shown again.
- Widget configuration: colors, typography, corner radii, custom CSS, label, title, avatar image, translation overrides, the chat bubble's settings and welcome messages, the store's logo for emails, and the promo code at the end of the Advisor's diagnosis with its conditions, read from Shopify.
- AI context: the business description, product categories and answer guidelines entered by the Merchant on the AI Setup page.
- Billing state: current plan, Shopify AppSubscription identifier, billing cadence (monthly / yearly) and trial period status.
- Session data: Shopify authentication sessions issued during OAuth, used to call the Admin API on the Merchant's behalf. Automatically deleted when the application is uninstalled.
- Team member accounts: each member's email address, name, optional photo, chosen language, role, agent status and notification preferences, and the five stores they last opened in Olvio; one-time sign-in codes, stored hashed; sign-in sessions; the log of access to Inbox conversations and Shopper addresses.
- Newsletter: the email address, first name and language of the team members who receive it, and their unsubscribe if they asked for it.
- Live chat add-on: its state, the number of billed agents and the monthly cap the Merchant chose.
- Affiliation: if the Merchant came through an affiliate partner's link, the partner concerned, and the store's installs, plans and billing passed to the affiliate portal to compute the commission.
5.2Shopper interaction data
Shopper data is pseudonymous: it is stored under random identifiers, with no field for a name, email, phone number or address. It is nonetheless personal data, because a conversation can be linked to a Shopify customer through their order. The exceptions below apply only when the Shopper uses the feature concerned.
- Session identifier: a random identifier that links the widget events, conversations and orders of one visitor. With the Shopper's marketing consent on the storefront (read from Shopify's Customer Privacy API), it is kept in their browser (key "olvio_sid") for 13 months at most and written to their cart, and so to their order (attribute "_olvio_session"). Without this consent, it lives only as long as the page. If the Shopper withdraws their consent, the identifier is no longer read, but stays in their browser until it expires or they erase it.
- Conversation token: a random identifier created at the Shopper's first message and kept in their browser; we keep only a fingerprint of it. It lets them find their conversations on the storefront, and never goes into their cart or order. It does not depend on marketing consent, because it serves only the conversation the Shopper started.
- Widget events: widget impressions (in 15-minute slots) and add-to-cart signals (product and date), with the session identifier when there is one.
- Conversations: the messages exchanged between the Shopper and the assistant on a product page, in the Advisor, on the contact page or in the chat bubble, with their date, the language, the product page or surface the conversation came from and the products shown. Before being sent to the AI and stored, the Shopper's messages are filtered: email addresses, phone, card and ID numbers and, on the contact page and in the bubble, order numbers and postal addresses are masked. This filter does not recognize everything: a name or other freely written information can remain in a message.
- Question logs: the text of each question sent by a Shopper, filtered as above, with the product concerned and the date. They power the Merchant's dashboard (recurring topics, unanswered questions, question map). The AI also uses them to write the suggested questions shown on the product page.
- Orders: for every order in the store, Shopify sends us the order (orders/create webhook). We keep only its identifier and number, its lines (product, variant, quantity, unit price), its total, its currency and, when it carries one, the session identifier. This link makes it possible to tie a conversation to an order, and so to a customer: that customer's rights apply to it (section 17). We do not keep the buyer's name, email, phone number or address, nor any text they entered on an item.
- Order tracking: the Shopper enters the order number and the email address the order was placed with, or Shopify gives us their customer id when they are signed in to their account on the storefront. Olvio asks Shopify (read_orders permission, last 60 days) and shows the delivery status only: status, carrier, tracking number and link. The email address entered is only compared with the order's: it is neither stored nor logged. To stop anyone from walking through someone else's orders, Olvio counts attempts per address as a fingerprint (HMAC), never the address itself. The number of the orders found is noted in the conversation.
- Inbox (live chat add-on): when the Shopper writes to the Merchant's team, Olvio keeps their messages, the team's replies, the files exchanged (photos and PDFs), the rating they leave and, if the Shopper gives it to receive the reply after leaving, their email address. While the team follows the conversation, the widget also passes on the page the Shopper is viewing and the content of their cart (items, quantities and amounts). The team also sees their earlier conversations with the assistant on this browser. Replies are sent by email from an address unique to the store, on chat.olvio.ai; if the Shopper replies to it, their reply joins the conversation, without its attachments. Messages written to the team are not filtered. The email address and personal fields are encrypted with a key unique to each store (AES-GCM, 256-bit); a fingerprint of the address (HMAC) is used to find the conversation for erasure requests. The Owner, the Admins and the agents see the address in full; any other Member sees it masked. The team can block a browser that abuses the chat. If the Shopper is signed in to their customer account on the storefront and the Merchant granted the optional read_customers permission, the team sees who they are (name, email, phone, orders and amount spent): this is read from Shopify each time it is shown and never stored; only the Shopify customer id is noted in the conversation.
- Advisor results: at the end of a diagnosis, when the Merchant has turned this on and the Shopper asks for it, the email or WhatsApp number they type is used to send them their results (the recommended products and, where the Merchant offers one, a promo code). The email is sent in the store's name, from an address on chat.olvio.ai; the number is passed to Kanal, the WhatsApp service the Merchant connected. The Shopper is added to the store's customers in Shopify, tagged "Olvio" and with no marketing consent; this customer record is then the Merchant's, who must say so in its own privacy policy. Olvio keeps neither the email nor the number: the conversation only notes the channel and time of the sending, the promo code offered and whether it was applied. When the Shopper is signed in to their customer account on the storefront, Olvio reads their email or number from Shopify when sending, without keeping it, and checks in their orders whether they already used a once-per-customer code.
5.3Catalog data
In order to answer Shoppers' questions accurately, Olvio ingests the content of the Merchant's Shopify catalog:
- Products: title, description (HTML and plain text), vendor, product type, tags, status, price range, currency, images, SEO fields, variants, metafields and collections.
- Online Store content: public pages, store policies and blog articles from the Merchant's storefront.
- File-type metafield content: text extracted from documents attached via the Shopify metafield "custom.olvio_knowledge_file" (PDF, DOCX, XLSX).
- Knowledge base: the documents and web pages the Merchant adds on the AI Setup page.
Catalog data is ingested at first installation, kept up to date in real time via Shopify webhooks (products/create, products/update, products/delete) and reconciled nightly.
5.4Site visitor data (olvio.ai)
A consent banner is shown on the first visit to olvio.ai. Nothing from Google or any advertising tool loads before your choice; only Cloudflare's visit measurement, with no cookie, runs on arrival. Only after your agreement: Google Analytics 4 (traffic measurement), Google Ads, Meta Pixel, OpenAI (ChatGPT ads) and Reddit (measuring our ads), and Intercom (help messenger). These providers, some of them based in the United States, receive your IP address, cookie identifiers and the pages viewed. If you book a demo, the name and email you enter are collected by our scheduling provider, Lemcal, and used to reply to you.
5.5Data sources
We collect data from the following sources, in accordance with article 14 of the GDPR:
- Directly from the Merchant: when installing Olvio, entering API keys, configuring the widget and inviting team members.
- From Shopify: via OAuth, the Admin API and webhooks, under the authorization granted by the Merchant at installation. This includes the store's staff who open Olvio from the Shopify admin, orders and, for a customer signed in on the storefront, their customer id.
- Directly from Shoppers: via the widget on the Merchant's storefront, under a pseudonymous identifier.
- Directly from team members, site visitors and affiliate partners: what they enter themselves.
5.6Affiliate partner data
The affiliate program (affiliate.olvio.ai) is for businesses only. For each partner, we keep their email, name, country, tax identity (including their VAT number), encrypted bank details, sign-in sessions, the stores they brought in and their commissions. When a visitor clicks a partner's link, we set a cookie on affiliate.olvio.ai and record that cookie's identifier, their IP address, browser, referring page and country, to attribute the install and count visits. These clicks are deleted after 180 days.
5.7Referral invitations
A Merchant can invite another store to try Olvio by entering an email address. We send that address one message, on the Merchant's behalf, with their code and the first name of the person who entered it. The address is used for this send and nothing else: it is not kept. We keep only its fingerprint (a code that cannot be reversed without our key) for one year, so that the same address never gets a second invitation, and the number of invitations each store sent. The legal basis is the legitimate interest in making the service known (article 6(1)(f) of the GDPR).
A store that uses a referral code sees the name of the store sharing it. That store sees the name of the store that used it and where it stands (trial, first invoice, departure). The affiliate portal keeps this information to send the credit the Terms of Service provide for.
6Special category data
Olvio does not need special categories of personal data within the meaning of article 9 of the GDPR (health, biometric, genetic, political opinions, religious beliefs, racial or ethnic origin, sexual orientation, trade union membership) and does not ask for them.
The AI is instructed never to ask for personal data and not to repeat any a Shopper gives. A Shopper may still write such information themselves in a free message, for instance about their health in a food supplement store. That message is then sent to the AI provider and stored like the others, for the period in section 11. We recommend that Merchants invite their Shoppers not to share sensitive information in the widget, and that those whose products touch on health take it into account in their own assessment.
7How we use this data
- Deliver the core features of the application: show the chat on product pages, in the Advisor, on the contact page and in the bubble, answer Shopper questions and recommend products.
- Operate the merchant admin: display catalog sync status, conversation history, analytics and billing state.
- Sync with Shopify: react in real time to product create/update/delete events, app subscription updates and order creation.
- Inform the Merchant: group Shoppers' questions to surface recurring topics and catalog blind spots.
- Comply with legal obligations: apply Shopify's GDPR compliance webhooks and our contractual obligations as a Data Processor.
- Let the Merchant's team answer Shoppers directly (Inbox), live or by email.
- Tell a Shopper the delivery status of their order, at their request.
- Send a Shopper their Advisor results, at their request, and add them to the Merchant's store customers.
- Send team members the emails the service needs: invitations, sign-in codes, an alert when Olvio hands a conversation to the team (with the Shopper's last message), an alert when the AI key is refused and the summary of unanswered questions for those who asked for it.
- Send team members a newsletter, at most once a month, on what is new in Olvio. Each one holds an unsubscribe link.
- Protect the service: rate limits per IP address, checks on where requests come from and technical logs.
We do not sell personal data. We do not use Shopper data or conversation content to train AI models.
7.1Legal bases
For the data of which Topicimes is the Controller:
- Performance of the contract (article 6(1)(b) of the GDPR): Merchant and team member accounts, the service's emails, the affiliate program.
- Legitimate interest in protecting, maintaining and promoting the service (article 6(1)(f)): security, technical logs, abuse prevention, the admin's help messenger, Topicimes's access to a store for support, attributing installs to affiliate partners, the newsletter on what is new in Olvio.
- Legal obligation (article 6(1)(c)): accounting and tax obligations, answers to rights requests.
- Consent (article 6(1)(a)): analytics and advertising cookies and the messenger on olvio.ai. You can withdraw it at any time, with no effect on what was done before.
For Shopper data, the Merchant, as Controller, determines the legal basis: most often carrying out a request from the Shopper (their question, tracking their order, sending their results) or its legitimate interest. The session identifier rests on the marketing consent collected on its storefront.
8AI provider (Anthropic, Merchant-supplied key)
Olvio operates on a bring-your-own-key model. Each Merchant supplies their own Anthropic API key (Claude models) and connects it to power the Service.
When a Shopper sends a message via the widget, the prompt, the conversation context and the page they are viewing are routed from our Worker to the AI provider chosen by the Merchant using their own API key, through the Cloudflare AI Gateway, which records each call's date, model, duration and token count, but not its content. The same key is used to write suggested questions, translate the widget's copy and group unanswered questions: filtered Shopper questions are then sent to the provider too. We use this content neither for ourselves nor for training purposes. We have no commercial or contractual relationship with the AI provider on behalf of the Merchant: the Merchant has their own agreement directly with the provider they selected.
Processing, retention and international transfer of the prompt and the response by the AI provider are governed by that provider's own terms and privacy policy. Before entering an API key, Merchants are required to review the data practices of the selected provider.
Olvio retains the conversation history (messages and timestamps) in its own database as described in section 5.2, in accordance with the retention rules in section 11. Olvio does not retain raw API request or response payloads beyond this conversation history.
9EU AI Act (Regulation 2024/1689)
Olvio is an AI system within the meaning of article 3 of the EU AI Act. Topicimes and the Merchant exercise complementary responsibilities under this regulation:
- Topicimes (provider): responsible for the technical compliance of the AI system, its documentation, and its availability as a safe and compliant tool. This includes maintaining technical documentation, applying risk management, implementing human-oversight mechanisms and cooperating with supervisory authorities, as required.
- Merchant (deployer): responsible for the use of the system on their storefront, for defining the purposes of use, and for the compliance of the deployment with applicable regulations and their own terms of service.
Olvio qualifies as a limited-risk AI system under the AI Act. In accordance with the transparency obligations of article 50, the widget permanently displays, in the Shopper's language, the notice "You're chatting with an AI" while the AI is answering, and every message written by the AI carries a machine-readable marking. Once a team member has taken over, the notice goes away, since the Shopper is then talking to a person. This notice is locked and cannot be removed by Merchants through widget customization.
10Automated decision-making and profiling
Olvio uses AI to generate product recommendations and contextual answers. These responses are informational and do not constitute an automated decision producing legal or similarly significant effects on Shoppers within the meaning of article 22 of the GDPR. Shoppers remain free at all times to add to cart, continue browsing, leave or ignore any recommendation.
Olvio does not build Shopper profiles, and no information passes between stores. During a visit, on a product page, the AI reads the last 20 messages of that visit. The conversation token lets the Shopper find their earlier conversations on the same store and lets the team see them in the Inbox; they are not sent back to the AI. Conversations are retained only for the duration applicable to the Merchant's plan (section 11).
11Data retention
Retention applies to conversations, question logs and unanswered questions, and depends on the Merchant's plan. Retention periods are enforced by automatic deletion and reflect the data-minimization principle of article 5(1)(e) of the GDPR:
Plan
Conversation data retention period
Starter
30 days from the event timestamp.
Growth
90 days from the event timestamp.
Scale
365 days from the event timestamp.
Custom
Negotiated by contract (by default, no automatic purge).
A daily scheduled job enforces these durations by deleting records older than the applicable threshold. Catalog data (products, sync state) is retained for the full duration the application is installed.
Whatever the plan, widget events and orders are retained for 90 days. Beyond that, the link between an order and a session identifier is kept only while a conversation carrying that identifier still exists, so that customer erasure requests can be answered, and never longer than the plan's period.
The dashboard's figures are also summarized per day: numbers of visits, conversations, cart additions and orders, and order amounts. These summaries hold no visitor identifier and no order number, and identify no one. They are retained for the full duration the application is installed.
Inbox conversations follow the same period as the plan: a closed conversation is deleted at the end of that period, with its files and the email address it holds; a conversation still open is not deleted. A conversation marked as spam is deleted after 30 days. A block expires after 90 days. A conversation's reply address stops working 90 days after it closes. The log of access to conversations is kept for 13 months.
Team member accounts are kept while they belong to a store, then deleted after 90 days. A sign-in session expires 30 days after its last use. A sign-in code expires after 10 minutes and is erased within 24 hours. An invitation is deleted 30 days after it expires. The agent seat ledger is kept for 13 months.
An address stays on the newsletter list while the person has an active account on a store and has not unsubscribed; it is removed before the next sending at the latest. After an unsubscribe, we keep that address solely so as not to write to them again.
A customer's access request is kept for 30 days after its export, and 60 days at most. Technical logs are kept for 7 days at Cloudflare; they may contain the IP address and the page requested, not the content of messages.
When a Merchant uninstalls Olvio, Shopify delivers a "shop/redact" webhook approximately 48 hours later. Upon receipt, we permanently delete all data associated with that store in our database, our file storage and our vector index: conversations, question logs, widget events, orders, knowledge files, products, embeddings, team accounts on that store and the store record itself. Only its domain stays in our list of stores, marked as erased. Cached copies expire on their own within 30 days at most. Customers added in Shopify by the sending of Advisor results stay in the Merchant's store: they are the Merchant's.
12Subprocessors
Topicimes uses the following Subprocessors to deliver the Olvio service. All of them are bound by data processing agreements offering protections equivalent to those of the GDPR, including, where required, the European Commission's Standard Contractual Clauses of June 4, 2021.
Provider
Purpose
Primary data storage location
Cloudflare, Inc.
Application hosting (Workers), databases (D1 and one database per store, Durable Objects), file storage (R2), vector index (Vectorize), edge cache (KV), processing queues (Queues), gateway to the AI provider (AI Gateway), sending and receiving email (Email Service), rate limiting and embeddings (Workers AI).
European Union for each store's database, the shared accounts database and the files exchanged (EU jurisdiction). KV, Vectorize, Workers AI, AI Gateway and Queues cannot be limited to the European Union: see section 16. Edge compute may run in the data center closest to the requester.
Intercom R&D Unlimited Company
Support messaging and help center, in the Olvio admin and on olvio.ai.
Ireland (European Union).
Shopify Inc. is the application distribution platform on which Olvio runs. The Merchant has a direct agreement with Shopify for their store and grants Olvio authorized access via OAuth. Shopify is not a Subprocessor of Topicimes within the meaning of article 28 of the GDPR.
Anthropic, the AI provider connected by the Merchant, is not a Subprocessor of Topicimes. It is the Merchant's own Subprocessor under the Merchant's direct agreement with Anthropic. See section 8 for details.
Kanal, the WhatsApp service a Merchant may connect to send Advisor results, is not a Subprocessor of Topicimes either: the Merchant chooses and connects it themselves, under their direct agreement with Kanal.
For the data of which Topicimes is the Controller, other recipients are involved: Google LLC, for the fonts of the admin and of team emails (Google Fonts), which then receives the person's IP address, Plus Five Five, Inc. (Resend), in the United States, which sends the newsletter and keeps the list of its recipients (see section 16), and, on olvio.ai, the providers in section 5.4.
13Data security
- Encryption in transit: all traffic to and from the Olvio Worker uses HTTPS/TLS.
- Encryption at rest: AI provider API keys, the Kanal key and Shopify tokens are encrypted with AES-GCM 256-bit, bound to the store. Inbox personal data is encrypted with a key unique to each store.
- Isolation: each store has its own database. Shared data (team accounts, the list of stores) is always read by the store's identifier.
- Team access: sign-in with a one-time code sent by email, or from the store's Shopify admin. Each member reaches only what their role allows.
- Topicimes access: for support, maintenance and the security of the service, Topicimes's authorized staff (today, its founder) can open a store without being on its team, with an Admin's rights, including the Inbox and the conversations in it, except for the team and a plan already chosen, which they cannot change. This access goes through a two-factor sign-in limited to a list of addresses, lasts eight hours at most, and every opening is logged.
- Rate limiting and origin controls: widget requests from the storefront are validated against the store's declared domain. Rate limits per store and per IP address protect against abuse; the IP address is not recorded in any database of the Olvio application.
- Webhook authentication: every Shopify webhook is HMAC-verified before any data is written.
- Principle of least privilege: Olvio asks Shopify for read_products, read_orders, read_themes, read_locales and read_metaobjects. The read_customers permission is optional: only a Merchant who grants it from the Inbox gives it. The write_customers, read_discounts and read_all_orders permissions are optional too: only a Merchant who turns on the end of the Advisor's diagnosis gives them.
14Security incidents and breach notification
In the event of a personal data breach, Topicimes will notify affected Merchants without undue delay and, where feasible, no later than 72 hours after becoming aware of it, in accordance with article 33 of the GDPR. The notification will describe the nature of the breach, the categories and approximate number of records concerned, the likely consequences and the measures taken or proposed to address the incident.
Where a breach is likely to result in a high risk to Shoppers, Topicimes will assist Merchants in notifying the affected Data Subjects as required by article 34 of the GDPR.
To report a suspected breach, contact the Data Protection Officer at help@olvio.ai.
15Cookies and browser storage
Olvio uses browser storage in a targeted and transparent way:
- Admin (app.olvio.ai): a session cookie, strictly necessary to keep the member signed in, a cookie that remembers the language they chose and short-lived technical cookies when signing in from Shopify. The Intercom help messenger, present on every page, sign-in pages included, sets its own cookies (intercom-id, intercom-session, intercom-device-id). No analytics or advertising cookie.
- Shopper widget: the widget sets one cookie, "olvio_chat", on the Merchant's domain: a random identifier set only when the Shopper uses the chat, never when a page is shown, and erased when the browser closes. In localStorage: the conversation token, a random identifier of which we keep only a fingerprint, and the list of the visit's conversations ("olvio_ai", for as long as the plan keeps conversations); a conversation handed to the team ("olvio_ct", 7 days while it is open, 24 hours after it closes); a block by the team ("olvio_blocked", 90 days); and, with marketing consent only, the session identifier ("olvio_sid", 13 months at most). In sessionStorage, erased when the tab closes: a copy of the messages and the chat's state. These serve only the chat the Shopper is using, not cross-site tracking. No third-party analytics or advertising script is injected on the Merchant's storefront; the widget only loads Shopify's Customer Privacy API to read the Shopper's consent.
- Public olvio.ai pages: analytics and advertising cookies and the messenger load only after acceptance via the banner (section 5.4): Google Analytics (_ga, 13 months), Google Ads (_gcl_*, 90 days), Meta (_fbp, 90 days), OpenAI (12 months), Reddit (90 days) and Intercom. Your choice is remembered for 6 months. Consent can be withdrawn at any time.
16International data transfers
Each store's database, the shared accounts database and the files exchanged are stored under European Union jurisdiction. Other Cloudflare services cannot be limited to the European Union: the KV cache (settings, catalog, suggested questions and the dashboard's question map, which holds the text of filtered Shopper questions), the Vectorize index (the store's catalog and content, no Shopper data), Workers AI (computing vectors, including from Shopper questions, with no retention), AI Gateway (routing to the AI provider, with no retention of content) and Queues (technical identifiers). Support interactions through Intercom are stored in the European Union. The affiliate portal's database is not under European Union jurisdiction.
Cloudflare's edge compute may process requests from the data center closest to the requester; such transit processing does not result in lasting storage of the databases above outside the European Union.
Transfers of personal data outside the European Economic Area, when they occur, rely on an adequacy decision or on the Standard Contractual Clauses approved by the European Commission on June 4, 2021, supplemented by technical measures (encryption in transit and at rest for secrets) and the contractual commitments of each Subprocessor.
The list of the newsletter's recipients (email address, first name, language, unsubscribe) is stored in the United States at Plus Five Five, Inc. (Resend). This transfer relies on the EU-U.S. Data Privacy Framework and on the Standard Contractual Clauses. No Shopper data is passed to it.
Transfers to AI providers selected by the Merchant (Anthropic is based in the United States) are not governed by this policy and fall under the responsibility of the Merchant and the provider they have chosen (see section 8).
17Your rights under the GDPR
If you are located in the European Economic Area, the United Kingdom or Switzerland, you have the following rights regarding your personal data:
- Right of access to the data we hold about you.
- Right to rectification of inaccurate or incomplete data.
- Right to erasure ("right to be forgotten") in the cases provided for by law.
- Right to restriction of processing.
- Right to data portability.
- Right to object to processing based on legitimate interest.
- Right to withdraw your consent at any time, for processing based on it.
- Right to set instructions for what happens to your data after your death.
- Right not to be subject to a decision based solely on automated processing (see section 10).
- Right to lodge a complaint with a supervisory authority. In France, the competent authority is the Commission Nationale de l'Informatique et des Libertés (the CNIL, cnil.fr).
Shoppers: your data is pseudonymous, but a conversation can be linked to you through your order, your email address or your customer account. The Merchant is responsible for this data: send your request to them. Shopify forwards its customers' access and erasure requests to us (customers/data_request, customers/redact), and we handle them on the Merchant's behalf, across your conversations with the AI and with the team. If you write to us directly, we pass your request on to the Merchant. You can also erase the widget's data on your device by clearing your browser's cookies, localStorage and sessionStorage for the Merchant's domain. Every reply email from the team lets you stop receiving them.
Merchants: you can exercise your rights by uninstalling Olvio (which triggers automatic deletion via Shopify's shop/redact webhook approximately 48 hours later) or by contacting the Data Protection Officer at help@olvio.ai. We respond to requests within one month of receipt, extendable once by an additional two months for complex requests, with notification.
Team members, site visitors and affiliate partners: write to the Data Protection Officer at help@olvio.ai. A member can also change their name, photo, language and notifications in their preferences, and a visitor can change their cookie choices from the link in the footer.
18Children's privacy
Olvio is a B2B product intended for Shopify Merchants and their Shoppers. It is not directed at children under 16, and we do not knowingly collect personal data from children. If a Merchant operates a storefront targeting children, it is their responsibility to comply with applicable law.
19Changes to this policy
We may update this policy from time to time. The "Last updated" date at the top of this document reflects the most recent revision. For any material change affecting Merchant data, we will notify active Merchants via the Olvio admin interface before the change takes effect.
20Contact
For any question relating to this policy or to your personal data:
Louis Jodon de Villeroché
Data Protection Officer, Topicimes
3 Avenue René Laennec, 72000 Le Mans, France
Email: help@olvio.ai
We endeavor to respond to any Data Subject request within one month of receipt, as required by the GDPR.