LEGAL — PROVIDERS & PLATFORMS
Service providers & connected platforms.
Retrics uses core infrastructure, supports optional delivery and AI providers, and connects to platforms a merchant chooses. This page explains those categories without implying that every optional integration is enabled.
LAST UPDATED · 31 JUL 2026
MATERIAL CHANGES TAKE EFFECT · 14 AUG 2026
01This revision
This document was last updated on 31 July 2026. Where this revision makes a material contractual change, that change takes effect on 14 August 2026. Until then the previous version governs the point it changed. Corrections that only make an existing practice clearer — naming a provider more precisely, describing a capability that is switched off — describe what is already true and are not held back to that date.
Sending from Retrics is unavailable in this release. Direct email to your customers, SMS, WhatsApp, scheduled delivery and the Klaviyo audience handoff are all switched off in code; no plan, setting, account connection or onboarding step turns them on. Where this document describes those channels, it describes a capability that is built and dormant, not one operating today. What is available is the campaign-safe CSV export: you download the frozen audience — with your global control already dropped — and send it from your existing platform.
Retrics also does not draft customer-facing message copy, does not upload any customer list to Google, and does not create, edit, pause or change any advertising campaign. Those are described in place below.
02Core infrastructure
Vercel
Application hosting and content delivery for the Retrics web app and API.
Supabase
Managed PostgreSQL database and authentication. Stores workspace configuration, synced commerce records, and derived analytics. Customer contact fields may be stored alongside irreversible matching hashes.
Resend
Delivery of transactional and authentication email addressed to YOU — sign-in links, account notices, and the retention digests you choose to receive. Resend does not carry messages to your customers in this release: customer sending from Retrics is switched off, so no customer address is passed to it for marketing delivery.
03Optional providers
Optional features can involve the providers below. A provider receives data only when the relevant feature is enabled and a merchant takes the required action; listing a supported integration here does not claim it is configured for every workspace or currently in use.
Anthropic
Optional AI audience building. Where a workspace has the AI composer available, Retrics sends the plain-English audience description you write and an aggregate factual brief — top product and collection titles, currency — so it can be turned into a rule Retrics then validates and runs itself. The same provider also produces the one-line summary shown at the top of an audience, from that audience's name, its rule, how many customers currently match, and the value at stake. Your stored message style is not sent for either. Customer contact details and individual purchase histories are never sent. Customer-facing message and reply copy is not generated at all today: that capability is switched off in code platform-wide, so no draft request is made for a send.
04Delivery providers that are not active
Sending from Retrics is unavailable in this release. The delivery providers below are integrated in the product and receive no customer data at all today, because the code path that would reach them is switched off. No plan, setting, account connection or onboarding step turns it on. They are listed so their status is stated rather than inferred from an omission, and this section will be corrected before any of them begins carrying customer data.
Resend (customer messaging)
Would deliver marketing email to your customers from your own verified domain. Not active: customer sending from Retrics is switched off in this release, so no customer email address or message body is sent to Resend for marketing delivery. Resend's transactional role above is unaffected.
Twilio
Would deliver SMS after you approve an audience and a message. Not active: no recipient phone number or message body is sent to Twilio in this release.
Meta WhatsApp Business
Would deliver WhatsApp messages on your own WhatsApp Business account after your approval. Not active: no contact or message data is sent to the WhatsApp Business platform in this release.
Klaviyo
Would receive an approved audience as a named list in your own Klaviyo account, for you to mail from there. Not active: no customer profile is imported into Klaviyo by Retrics in this release. Klaviyo remains available to you directly — the campaign-safe CSV export is shaped for its import.
05Merchant-connected platforms
These services act in the role created by the merchant's own account and chosen workflow. That role can differ from the role of infrastructure used to operate Retrics, so this page does not assign a single legal classification to every integration.
Shopify / Square
Merchant-authorized commerce sources. Retrics reads the connected store records required for the enabled analytics and operational workflows.
Slack
A merchant-selected destination for workspace notifications and digests.
Meta Ads
A merchant-connected advertising account. Retrics reads reporting and insights, and — when a merchant asks for it — uploads a custom audience as irreversible email hashes. That upload is the only write Retrics makes to any ad account. Campaign creation and budget or status changes are switched off in code, so an approved recommendation is applied by the merchant in the ad platform rather than sent there by Retrics.
Google Ads
A merchant-connected advertising account, read-only. Retrics reads reporting and insights so ad spend can be measured against store-verified revenue and budget changes recommended. No customer list is uploaded to Google — hashed or otherwise — and Retrics writes nothing to the account.
Merchant email platforms
Merchant-selected destinations for approved audiences or exports. Raw email is provided only when the merchant chooses a contact-capable handoff or export.
06Data and lifecycle limits
The base Shopify analytics connection uses read scopes. A separate, merchant-triggered loyalty authorization can add write_discounts solely to create requested discount codes; Retrics does not write orders, themes, or checkout. Contact fields are sent in raw form only to a delivery channel or export the merchant approves. Advertising audience uploads use irreversible email hashes and go to Meta only; a connected Google Ads account is read-only.
Disconnecting a store inside Retrics stops sync but retains its history. Uninstalling the Shopify app revokes access and leads to Shopify's later shop/redact process for the exact disconnected installation. A verified workspace-deletion request is handled manually with a target of completion within 30 days.
07Inventory and changes
Supported and enabled providers can change as features are configured. For the provider inventory and processing terms applicable to your workspace at a particular time, contact legal@retrics.ai.
08Contact
Questions about a provider, connected platform, or the processing terms that apply to your workspace: legal@retrics.ai.