Skip to main content
Start trial

Subprocessors

Last updated: 2026-10-14

These are the companies that process customer data on Persequor's behalf to run the service. Each one handles only what its job needs. The platforms you connect, like Shopify or Meta, are listed separately: you choose them, and we read from them on your instruction.

1. Subprocessors

  • Supabase

    Based in United States
    Purpose
    Database and sign-in
    Data
    Everything the product stores: your account and workspaces, orders, leads, site sessions, synced ad data, and the tokens for the integrations you connect.

  • Vercel

    Based in United States
    Purpose
    Hosting and serverless functions
    Data
    Every request to persequor.ai and the app, including IP address and browser details, and the data those requests carry while our code handles them.

  • Resend

    Based in United States
    Purpose
    Email delivery
    Data
    Recipient email addresses and the content of the emails we send: team invitations, trial and billing notices, and support replies; and, where you switch them on, the morning brief, setup and activation emails, and client reports, which carry your workspace's figures (a client report goes to the recipients you name).

  • Stripe

    Based in United States
    Purpose
    Billing for plans bought on persequor.ai
    Data
    Your billing contact and subscription. Card details go to Stripe directly and never reach us. Stores that install from the Shopify App Store are billed by Shopify instead.

  • Sentry

    Based in United States
    Purpose
    Error monitoring
    Data
    Error reports from the site and the app: the page, the browser and what failed, without your IP address. Session replay starts only after you accept analytics cookies.

  • PostHog

    Based in United States
    Purpose
    Product analytics, only after you accept the cookie banner
    Data
    Page views, clicks and form submissions in the app, linked to your user ID, email and name once you sign in.

  • Crisp

    Based in France (EU)
    Purpose
    Support chat
    Data
    The messages you send in the chat, and your email and name when you are signed in.

  • GitHub Actions

    Based in United States
    Purpose
    Schedule triggers only
    Data
    No customer data. It sends timed, authenticated requests that start our sync, alert and report jobs, which run on Vercel.

  • Notion

    Based in United States
    Purpose
    Internal business metrics
    Data
    Weekly totals only (signups, trials, paying accounts, monthly revenue, site sessions). No customer personal data.

  • QR Server (goQR.me)

    Based in Germany
    Purpose
    QR codes in the UTM builder
    Data
    When you show a link's QR code: the tagged link you built (its landing page and campaign names), and your browser's IP address and the page it was on, as any image request carries them. Nothing else from your workspace.

“Based in” is where each company is headquartered, not necessarily where it stores data. To ask where a provider hosts our data, email privacy@persequor.ai.

2. Data sources you connect

Not our subprocessors: each is a platform you connect yourself, under your own account with it, and nothing is read from one until you do. Our Data Deletion page explains how to stop each one.

  • Shopify

    We read
    Orders, refunds, discounts and taxes, the customer email and name on each order, and product costs.

  • Meta Ads

    We read
    Spend and platform-reported conversions by campaign, ad set and ad.
    We send
    Only if you add a Conversions API dataset: lead events, with email, phone and name hashed (SHA-256), and the visitor's IP address, browser user agent, the page URL and Meta's click cookies (fbc, fbp) unhashed, as Meta requires. No purchase events are sent today.

  • Google Ads

    We read
    Spend, clicks and platform-reported conversions by campaign.

  • TikTok Ads

    We read
    Spend and platform-reported purchases by campaign, ad group and ad.

  • LinkedIn Ads

    We read
    Spend and platform-reported conversions by campaign.

  • Klaviyo

    We read
    Campaign and flow results, and the orders and revenue Klaviyo reports.

  • Calendly

    We read
    New bookings, as leads, with the UTMs of the link that drove them.

  • GoHighLevel

    We read
    New contacts, as leads, with their UTMs and ad ID.

  • WooCommerce

    We read
    Orders and refunds, with the UTMs saved on each order.

  • Stripe (your own account)

    We read
    Successful payments and refunds, with the payer's email and name and the UTMs in each payment's metadata.

3. Changes to this list

When we add or replace a subprocessor, we update this list and the date at the top of the page.

4. Contact

Questions about this list or how we handle your data: privacy@persequor.ai. Our Privacy Policy has the rest.