Sub-processors

Backend platform: database, server functions and internal file storage.

Application hosting and delivery, custom-domain certificates, and the visitor's country used for storefront markets.

Media storage and CDN delivery (R2), storefront bundles, image resizing, and bot protection (Turnstile) on guest chat.

Uploaded media (pictures, and short videos for marketing posts), store logos, review and conversation images; the browser signals Turnstile checks.

Platform billing (subscriptions, credit packs) and store payments (checkout, saved cards, payouts, refunds, disputes).

Payment and payout data, billing contact details, transaction metadata. Stripe handles card data directly; loving never stores full card numbers. Stripe is an independent controller for its own payment processing.

AI model provider for the loving AI agent: the store builder, the dashboard assistant and the AI in Studio.

Prompts, attached files and images, and the store records the agent reads to answer a merchant's request — which can include customer and order records.

AI model provider for the storefront shopping assistant, AI features in storefronts (such as virtual try-on), inbox and WhatsApp reply drafts, marketing copy, customer persona and segment suggestions, translation, the writing assistant and "Enhance with AI", and image generation and editing.

Prompts and images submitted to those features; the catalog and, for a signed-in shopper, their own orders, tracking and returns for the shopping assistant; photos a shopper submits to try-on; the recent messages of a conversation a reply is drafted for; a summary of a customer's purchases and activity, without their name or contact details, for persona suggestions; text to translate.

Transactional email and sign-in codes, the inbox's email channel, marketing email merchants send, and loving's own outreach email.

Sender and recipient email addresses, email content, delivery events.

Optional dashboard sign-in (OAuth). Web fonts are fetched by loving's servers, so no visitor's data reaches Google when fonts load.

Google account identity (name, email, photo) when a merchant chooses Google sign-in.

Sender and delivery addresses, the recipient's name, phone and email, package details, tracking events.

Delivering the parcels a merchant ships on a label bought through loving.

The delivery address, the recipient's name and contact details, and package details. Each carrier processes them as an independent controller to deliver the parcel.

Label documents (which carry the delivery address) sent to the merchant's printers.

The registrant's contact details required by domain registries, which receive them too.

Netherlands (EU); the registry of the domain's extension, wherever it is

Placing a store's own locations on a map, and the map tiles in the dashboard.

Business addresses a merchant enters for its locations; the viewer's IP address when map tiles load.

Meta (Facebook, Instagram, Messenger, WhatsApp, Threads, Meta Ads)

Catalog and posts (pictures and short videos), ads and their measurement, customer conversations.

Products and posts; messages customers send the store and its replies; purchases with hashed email and phone.

Catalog sync, TikTok Shop customer service, posts, ads and their measurement.

Products and posts; buyer messages and the store's replies; purchases with hashed email and phone. Disconnecting TikTok Shop deletes the conversations and contacts it brought in.

Search performance, product listings, ads and their measurement, and short videos posted as YouTube Shorts.

Products and store pages; search and ad performance data; the short videos the merchant posts; purchases with hashed email and phone.