Sub-processors

These are the service providers that process personal data for Pixelary. Sub-processors handle the website visitor data we process on our customers’ behalf under the Data Processing Agreement; they also hold our customers’ account data. Service providers for our own data handle only data for which Pixelary is the controller (customers’ accounts, emails and dashboard use), as the Privacy Policy describes. We tell customers about new or replaced providers by email to account owners and an update of this page, 30 days before the change (DPA section 8). Below them we list the companies that receive data as independent controllers, and the platforms our customers choose.

Sub-processors (website visitor data and account data)

Cloudflare

• Entity: Cloudflare, Inc. (USA), under Cloudflare’s Customer Data Processing Addendum, part of its self-serve agreement.
• Data: website visitor data and customer account data.
• Transfer safeguard: the EU-U.S. Data Privacy Framework where Cloudflare is certified under it, and otherwise the European Commission’s Standard Contractual Clauses included in Cloudflare’s data processing terms.

Supabase

• Entity: Supabase, Inc. (USA), under the Supabase DPA (https://supabase.com/legal/dpa).
• Services: PostgreSQL database and Supabase Auth.
• What it does for Pixelary: stores accounts and sign-in identities, sites, domains, pixels, access tokens (in tables only Pixelary’s server can read), triggers, consent defaults, site settings, subscription status, team members and invitations, and delivery errors for Meta and TikTok. Supabase Auth runs sign-in with Google and with email codes. Its sign-in emails are sent through Mailgun (below).
• Personal data: customers’ email addresses, sign-in identities and records, site configuration and access tokens; for visitors, only the event IDs that appear in the destinations’ error messages.
• Location: data stored in AWS region eu-west-1 (Ireland). Supabase runs on Amazon Web Services. Supabase’s own sub-processors are listed at https://supabase.com/legal/subprocessors.
• Transfer safeguard: for access from outside the EEA, the EU-U.S. Data Privacy Framework where Supabase is certified under it, and otherwise the European Commission’s Standard Contractual Clauses included in the Supabase DPA.

Service providers for our own data (account data only)

Mailgun (Sinch)

• Entity: Mailgun Technologies, Inc. (USA), part of Sinch, under the Mailgun DPA.
• What it does for Pixelary: sends team invitation emails, sign-in emails (as the SMTP server of Supabase Auth) and our replies from hello@pixelary.app, from a sending domain for pixelary.app.
• Personal data: the recipient’s email address and the content of the email (for an invitation, the inviter’s email address and the role; for a sign-in email, the one-time code and link; for a reply, the support conversation); delivery events (sent, delivered, bounced).
• Data: customer account data and support emails.
• Location: EU region (data stored in the EU). Support access from outside the EEA is covered by the transfer safeguard below.
• Transfer safeguard: the EU-U.S. Data Privacy Framework where Mailgun is certified under it, and otherwise the European Commission’s Standard Contractual Clauses included in the Mailgun DPA.
• Status: in use; team invitations are live.

Microsoft Clarity

• Entity: Microsoft Corporation (USA) or Microsoft Ireland Operations Limited, as the Clarity terms name them.
• What it does for Pixelary: records how signed-in users use the dashboard (app.pixelary.app), with session recordings, heatmaps, clicks and scrolling, so we can find and fix problems. It loads only after the user agrees in a prompt, and the choice can be changed in Settings. Not on pixelary.app, not in the current Framer plugin and not on customers’ websites. Earlier versions of the Framer plugin loaded Clarity when opened and tagged recordings with the Framer project ID and the site’s domain; the current plugin does not.
• Personal data: interactions with the dashboard and what the page shows, with access tokens, API keys, site keys, email addresses and team lists masked; device and browser details; IP address as processed by Clarity; a hashed user ID that identifies the session, not the email address. Clarity sets the cookies _clck (1 year) and _clsk (1 day) on app.pixelary.app, only after consent.
• Retention: Microsoft keeps recordings for 30 days and heatmap and usage data for up to 13 months.
• Data: customer account data only.
• Location: USA.
• Transfer safeguard: the EU-U.S. Data Privacy Framework where Microsoft is certified under it, and otherwise the European Commission’s Standard Contractual Clauses included in Microsoft’s terms.

Google (support mailbox)

• Entity: Google Ireland Limited for users in the EEA, otherwise Google LLC (USA).
• What it does for Pixelary: hosts our support mailbox (Gmail), to which Cloudflare Email Routing forwards mail sent to hello@pixelary.app. This is the only service Google provides to Pixelary as our provider.
• Personal data: the email addresses of people who write to hello@pixelary.app, their messages and attachments.
• Data: customer account data and support emails.
• Location: EU and USA (Google’s global infrastructure).
• Transfer safeguard: the EU-U.S. Data Privacy Framework where Google is certified under it, and otherwise the European Commission’s Standard Contractual Clauses included in Google’s terms.

Independent recipients we share data with

These companies receive personal data about our customers, but process it as independent controllers, under their own privacy policies.

Google (Sign in with Google)

• Entity: Google Ireland Limited for users in the EEA, otherwise Google LLC (USA).
• Role: independent controller for Sign in with Google, under Google’s own privacy policy. Google also hosts our support mailbox as our service provider (above).
• What it does for Pixelary: “Sign in with Google” for the dashboard and the Framer plugin.
• Personal data: the customer’s Google account email address and the profile details Google shares at sign-in: name, profile picture URL and Google account ID.
• Data: customer account data only.
• Location: EU and USA (Google’s global infrastructure).
• Transfer safeguard: the EU-U.S. Data Privacy Framework where Google is certified under it, and otherwise the European Commission’s Standard Contractual Clauses included in Google’s terms.

Lemon Squeezy

• Entity: Lemon Squeezy, LLC (USA), a Stripe company.
• Role: merchant of record and independent controller for the payment and tax data it collects, under its own privacy policy. Lemon Squeezy sells the subscription to the customer, takes payment, charges tax, issues invoices and runs the customer portal.
• Personal data: what the customer enters at checkout (name, email, billing address, payment details, VAT ID), collected by Lemon Squeezy directly. Pixelary sends the internal site ID and, for plugin sites, the Framer project ID with each checkout, and receives the subscription ID, status and renewal date.
• Data: customer account data only.
• Location: USA.
• Transfer safeguard: the EU-U.S. Data Privacy Framework where Lemon Squeezy is certified under it, and otherwise the European Commission’s Standard Contractual Clauses included in its terms.

Recipients our customers choose (not sub-processors)

The destinations below receive data because a customer connects them to a site and gives Pixelary its access token or API key. Pixelary sends them data on the customer’s instruction, and the customer’s own agreement with each platform governs what happens to it. They are recipients chosen by the customer, not Pixelary’s sub-processors.

Other services

Cloudflare Email Routing, which forwards hello@pixelary.app, and the DNS for pixelary.app are part of the Cloudflare entry; the Gmail mailbox that receives the forwarded mail is part of the Google entry. Namecheap is only the registrar of pixelary.app and processes no personal data for us. Code hosting (GitHub) and Framer, where customers run the plugin under their own Framer agreement, are not listed because Pixelary does not give them personal data to process.

Changes to this list