These are the third parties that process personal data for Zyro. Some help us run the service for our customers,
including the shopper data we process for merchants. Others run on our own website. Our
Privacy Policy explains what we collect and why, and our
Data Processing Addendum explains how we handle
sub-processors for customer data.
We update this page when we add or replace a sub-processor. Questions: hello@zyro.world.
1. Sub-processors that run the Zyro service
These providers process data for us, including data we process on behalf of merchants.
| Provider | What it does for Zyro | Personal data involved | Location |
|---|
| Amazon Web Services (AWS) |
Hosting: our web servers and database (Amazon EC2), sending email (Amazon SES), and storing and delivering images that customers upload (Amazon S3 and CloudFront). |
All data in the service: customer account data, data collected by the Zyro tracker and the Shopify app, and the names, addresses and content of emails we send. |
United States (US East). CloudFront delivers images from locations worldwide. |
| Anthropic |
AI features: test copy and test ideas, brand voice, matching ads to landing pages, automatic headline ideas, and notes in the free store audit. |
Text, headings and links from website pages, page addresses, element text with click counts, and ad text from a connected Meta account. Page text can include personal details if a page shows them. |
United States |
| OpenAI |
AI features: SEO action plan suggestions and the article writer. |
A page's address, title, description and up to 1,500 characters of its text, plus keywords, briefs and notes the customer types. |
United States |
| DataForSEO |
Search results data for content briefs and the AI readiness check. |
Keywords, search locations, the customer's website address and competitor addresses. Usually no personal data. |
Estonia (EU) |
| Stripe |
Payments for customers who pay Zyro directly: hosted checkout and billing portal. |
Name, email address, payment card details (entered directly with Stripe), billing address, and subscription and invoice records. |
United States |
| Google Fonts (Google) |
Fonts for Zyro pop-ups shown on merchants' stores. |
The shopper's IP address and browser details, sent by the browser when it loads the font. |
United States and other countries |
We find a visitor's country from their IP address on our own servers, using a MaxMind database. We do not send IP addresses to MaxMind.
2. Providers on our own website and sign-in
These run on zyro.world, where Zyro decides how data is used. Analytics and marketing tools load only after a visitor agrees
in our cookie banner. Visitors can change their choice with "Cookie settings" at the bottom of every page.
| Provider | Purpose | Personal data involved | Location | Cookie category |
|---|
| Google Analytics (Google) |
Website analytics. |
Pages viewed, device and browser, IP address, and events such as sign-ups. For signed-in users, a hashed user ID and plan type. |
United States and other countries |
Analytics |
| Contentsquare |
Session recording and heatmaps on our public pages. |
Clicks, scrolling, mouse movement, pages viewed, device and browser, IP address. |
European Union and United States |
Analytics |
| Google Ads (Google) |
Measuring our ads. |
Cookie IDs, pages viewed, IP address and browser details. |
United States and other countries |
Marketing |
| Meta Pixel and Conversions API (Meta) |
Measuring our ads on Facebook and Instagram. |
Cookie IDs, pages viewed, IP address and browser details. For signed-in users, the email address (hashed before it is sent) and the Zyro user ID. |
United States and other countries |
Marketing |
| Trustpilot |
Showing our reviews. |
IP address and browser details. Trustpilot may set its own cookies. |
Denmark (EU) |
Marketing |
| Google Fonts (Google), cdnjs (Cloudflare) and jsDelivr |
Fonts, icons and a date picker on our pages. |
IP address and browser details, sent by the browser when it loads the file. |
Global networks |
Essential |
| Sign in with Google (Google) |
Lets you sign in with your Google account, if you choose to. |
Name and verified email address. |
United States and other countries |
Essential, on the login page |
| Sign in with Microsoft (Microsoft) |
Lets you sign in with a Microsoft account, if you choose to and where the option is shown. |
Name, email address and a Microsoft account identifier. |
United States and other countries |
Essential, on the login page |
3. Sales research
| Provider | Purpose | Personal data involved | Location |
|---|
| Google (Custom Search and Places) |
Finding businesses that may want Zyro. |
We send search terms, such as a type of business and a place. Results can include published business contact details. |
United States and other countries |
| Gravatar (Automattic) |
Checking whether a published business email address is likely to be in use. |
A one-way hash of the email address. |
United States |
4. Services our customers connect
These are not our sub-processors. They are services a customer chooses to connect to Zyro, using the customer's own account.
We exchange data with them only on the customer's instructions, and the customer's agreement with each service applies.
Section 3.3 and section 4.3 of our Privacy Policy describe what we send and receive.
| Service | What Zyro does with it | Personal data involved |
|---|
| Shopify |
Reads orders and store events through the Zyro app, creates discount codes if the merchant turns that on, and bills Shopify merchants for Zyro. |
Order details without customer names, emails or addresses; Shopify's anonymous client ID; store and subscription details. |
| Klaviyo, Omnisend, Postscript, Attentive, Customer.io, Braze, Brevo, Drip, ActiveCampaign, Mailchimp |
Sends shopper activity to the merchant's email or SMS account. |
The shopper's email address, with event details such as page, product, intent score, coupon code or offer. |
| Meta (Facebook, Instagram, Ads, Conversions API) |
Reads the merchant's ads and ad spend, publishes posts, and sends Zyro events to the merchant's own Meta Pixel. |
The merchant's Facebook user ID and name. For Conversions API events, a hash of the shopper's email address and a hash of the visitor ID. |
| Google (Search Console, Analytics, Google Ads, YouTube) |
Reads the sites, accounts and channels the merchant gives Zyro access to. |
The merchant's Google account email address. |
| LinkedIn, TikTok, Pinterest, Reddit |
Publishes posts the merchant creates in Zyro. |
Account and page identifiers, and the posts themselves. |
| Stripe (the merchant's own account) |
Reads charges to show which channels brought in revenue. |
The buyer's email address on a charge, used to match it to a visit and not stored with the charge. |