Subprocessors
Last updated: September 17, 2026
Aglyn LLC uses the third-party subprocessors below to provide the Services. This list supports the Data Processing Addendum and Privacy Policy. We update this list and the change log below to reflect the subprocessors currently engaged. Section 7 of the DPA governs Aglyn's use of subprocessors.
Core infrastructure & platform subprocessors
| Subprocessor | Provider entity | Purpose | Data processed | Location |
|---|---|---|---|---|
| Google Firebase Authentication | Google LLC | User authentication, sign-in, session, and auth emails (verification, password reset) | Account identifiers, email, auth tokens, OAuth identities | United States (Google operates a global service) |
| Google Cloud Firestore | Google LLC | Primary application database (multi-tenant) | Account, org, content, commerce, CRM, and configuration data | United States (nam5 US multi-region) |
| Google Cloud / Firebase Storage | Google LLC | Media and asset storage | Uploaded images, video, files | United States (US multi-region) |
| Vercel Inc. | Vercel Inc. | Application hosting, edge/CDN, custom-domain SSL and provisioning | Request/usage data, IP, content served | United States (primary compute), with a global edge network for cached content |
| Stripe, Inc. | Stripe, Inc. | Subscription billing and, via Stripe Connect, facilitation of Customer merchant sales | Billing contact, subscription/transaction metadata, payment data (processed by Stripe) | United States |
| Resend | Plus Five Five, Inc. (d/b/a Resend) | Transactional and app-generated email delivery (invites, receipts, usage summaries, campaigns) | Recipient email, message content/metadata | United States |
| Google reCAPTCHA | Google LLC | Bot protection / anti-abuse (via Firebase App Check) | IP, device/browser signals, interaction data | United States (Google operates a global service) |
| Google Analytics | Google LLC | Product and site analytics for aglyn.com, the console, and the documentation site (a single GA4 property). The property is linked to Aglyn's Google Ads account with personalized advertising enabled, and Google signals and ads personalization are allowed in every region, so analytics data may also be used to build and export advertising audiences. Data retention is 14 months. The same Google tag host also serves a Google Ads tag on those three surfaces, and a Google Tag Manager container where one is configured; what a container carries is configured in Google’s interface and is not enumerated here. | IP address, device/browser signals, page and event interaction data, a cookie-based pseudonymous identifier | United States (Google operates a global service) |
| Google Fonts | Google LLC | Serving web-font files to visitors of published sites whose theme selects a Google font, and to the console editor surfaces | Visitor IP address and browser user-agent, sent by the visitor's browser when it requests the font file | United States (Google operates a global service) |
| Google Cloud Logging | Google LLC | Collecting uncaught browser errors from the console and from published sites, for diagnosis and reliability | Error message and stack trace, source file, line number, and the origin and path of the page (query strings are removed before transmission) | United States (Google operates a global service) |
| Anthropic | Anthropic, PBC | AI-assisted features in the console and the site editor: the Aglyn Assist helper, including changes it proposes to a page, component, or layout open in the editor; editor assistance (rewriting element copy, drafting blog bodies, generating a section layout); and AI generation, which creates drafts and proposals for a customer's site from a brief or from what the site already holds, such as copy, layouts, templates, automations, search titles and descriptions, theme changes, product descriptions and tags, draft products, and store categories and discounts; explanations of a site's automations, including why an automation's run failed; AI insights, which answer a customer's questions about its own figures, such as site traffic, sales, bookings, forms, campaigns, A/B tests and datasets, and write a weekly summary of them for members who ask for one; and AI assistance in the CRM, which summarizes a contact, company, deal or lead for a user and suggests a next step, drafts a one-to-one email for the user to review and send, and suggests how the columns of a spreadsheet the user imports match CRM fields | The text the user submits to the feature — their question, instruction, or brief, with the earlier messages of the same Aglyn Assist conversation — and the content of the element, post, section, or page being worked on, together with the generated response. On some plans, the organization's name and the console page and site the user is working in. For a change proposed in the editor, an outline of the open page, component, or layout: its elements, their names, their shortened settings and text, and the styles of the selected element. For AI generation, a summary of the site: the names and addresses of its screens and collections, the names of its components, layouts, templates, forms, and datasets and of their settings and fields, and the theme's summary, colors, and fonts. For a theme change, the site's current theme settings, and brand colors taken from the organization's brand settings, the site logo in its media library, or a public web page the brief links to (only the colors are sent). For features that review or write search information, the text and structure of the pages concerned. For product copy, the store's name, the product's name, type, description, tags, options and search listing, the names of the store's product categories, and the product's first photo from the site's or organization's media library, sent as a copy at most 768 pixels on its longer edge with the original file's metadata removed; no other media library content, price, stock, order or customer information is sent. For draft products, categories and discounts proposed from a brief, the store's name and, for categories, the names of the store's existing categories. For an automation drafted from a brief, which of the CRM, webhooks and bookings the workspace's plan includes. For an explanation of an automation, an outline of how it is set up: what starts it, its conditions, and each step with the text it was given, the names of the lists, campaigns, workflows, webhooks and datasets it uses and whether each still exists, and for a workflow its function names and expressions; and for a run that failed, when it ran, what it did and the errors it recorded. Email addresses are removed from the outline before it is sent, and the details of the event that started a run are never sent. For a question about a customer's own figures, a list of the figure reports available to it and tables of totals, counts and rates computed from its records: page views and visitors, with the most viewed page paths, referring sites and campaign tags; each form's name with its views and submissions; revenue, orders and the best-selling products' names; bookings by service name; campaign email subjects with delivery, open and click rates; A/B test and variant names with their conversions; and, for a dataset the member can see, its fields' names and types, record counts, how many records fill each field, number ranges, and totals grouped by the values of one field that at least three records share. Email addresses and phone numbers are removed from these tables, and no individual visitor, contact, customer, order, booking, form submission, email recipient or dataset record is sent. For AI assistance in the CRM, the contact, company, deal or lead a user opens, as the CRM shows it to that user: its name and, for a contact, job title, company, lifecycle stage and tags; how the person was captured, with the counts and dates of their captures, orders and email engagement; for a company, its domain, industry and number of people; for a deal, its pipeline's stages, status, amount, dates, lost reason and the names of the person and company it is with; for a lead, its status and whether it is assigned or converted; its notes; its newest timeline entries, with activity kinds, dates, email subjects and delivery states, and the start of what was logged; and its open tasks and deals. Email addresses and phone numbers written in this text are replaced before it is sent, and no email address, phone number or postal address field, marketing consent, custom field value, team member or record identifier is sent. For an email draft, also the user's request and the names of the merge fields the record can fill. For an import, the import's field names and types and each column's header with the kind of values under it, never a row of the file. No account identifiers, email addresses, or authentication tokens are transmitted. | United States |
| Linear | Linear Orbit, Inc. | Filing and triage of issue reports submitted through the console's "Report an issue" dialog | The report text the reporter writes, their email address and account identifier, their organization's name and identifier, and technical context about the session (the console page, browser and viewport, and application build identifiers) | United States |
| Meta Pixel | Meta Platforms, Inc. | Advertising measurement and retargeting on Aglyn’s own marketing site, console and documentation site, and on a customer site where the site owner has enabled the advertising question and configured a pixel | Page views and conversion events from a visitor whose consent state permits advertising on a surface that asks about it, with the identifiers the pixel sets. On the console that visitor may be signed in, so the page views describe an identified account holder using the product, and the page addresses reported carry their organization’s identifier | United States |
| LinkedIn Insight Tag | LinkedIn Corporation | Advertising measurement and retargeting on Aglyn’s own marketing site, console and documentation site, and on a customer site where the site owner has enabled the advertising question and configured a partner id | Page views and conversion events from a visitor whose consent state permits advertising on a surface that asks about it, with the identifiers the tag sets. On the console that visitor may be signed in, and the point made in the Meta Pixel entry above applies here in the same way. LinkedIn additionally sets cookies on its own domain, which a page on our origin cannot read or clear | United States |
| Google Ads | Google LLC | Advertising measurement and retargeting on Aglyn’s own marketing site, console and documentation site, and on a customer site where the site owner has enabled the advertising question and configured a Google Ads id | Page views and conversion events from a visitor whose consent state permits advertising on a surface that asks about it, with the identifiers the tag sets, including the _gcl_au cookie that any Google tag on the page writes — a Google Tag Manager container included. On the console that visitor may be signed in, and the point made in the Meta Pixel entry above applies here in the same way. Advertising audiences built in the linked Google Analytics property are also exported to this account. | United States (Google operates a global service) |
| Wistia | Wistia, Inc. | Hosting and streaming Aglyn’s own films on its marketing site, aglyn.com. The player loads when a visitor presses play on a film. On a page built to show a single film, it loads with the page for a visitor whose privacy choices on aglyn.com permit analytics. For every other visitor and page, nothing is requested from Wistia before a press | Visitor IP address and browser user-agent, sent by the visitor’s browser when it loads the player and the film, and viewing data such as which film was played and for how long. Unless the visitor’s privacy choice on aglyn.com permits analytics, the player is loaded with Wistia’s do-not-track option, and Wistia does not record that visitor’s viewing session | United States |
Related services
- Google Workspace (Google LLC) — inbound/human email for @aglyn.com (e.g., support, contact). May process email you send to us.
- Google Cloud DNS (Google LLC) — DNS management for aglyn.com domains.
Change log
- September 17, 2026 — Updated Anthropic, PBC: the row now names automations among the drafts AI generation creates, and explanations of a site's automations and their failed runs; product copy, draft products, and store categories and discounts among what AI generation proposes; AI insights, which answer a customer's questions about its own figures and write a weekly summary for members who ask; and AI assistance in the CRM — record summaries with suggested next steps, one-to-one email drafts, and import column matching. It also names the data each of these sends, including a product's first photo as a reduced copy with its metadata removed and the tables of totals AI insights sends.
- September 15, 2026 — Updated Anthropic, PBC: its purpose and the data it receives now cover AI generation, which creates drafts and proposals for a customer's site from a brief, and the changes the Aglyn Assist helper proposes in the site editor. Updated Wistia, Inc.: on a page built to show a single film, the player now loads with the page for visitors whose privacy choices permit analytics; otherwise it still loads only when a visitor presses play.
- September 13, 2026 — Added Wistia, Inc. (hosting and streaming Aglyn’s own films on aglyn.com, loaded only when a visitor presses play).
- August 27, 2026 — Added Meta Platforms, Inc. (advertising measurement through the Meta Pixel) and LinkedIn Corporation (advertising measurement through the LinkedIn Insight Tag); the Meta Pixel was already in use when this entry was published. Updated the Google Analytics entry: the property is linked to Aglyn's Google Ads account with personalized advertising enabled, and Google signals and ads personalization are allowed in every region.
- August 24, 2026 — Added Linear (filing and triage of issue reports submitted through the console's "Report an issue" dialog); this subprocessor was already in use when this entry was published. Removed the thirty-day advance-notice commitment for new subprocessors and the objection window that ran with it; Section 7.2 of the DPA is amended to match.
- August 18, 2026 — Added Google Analytics (analytics for Aglyn's own properties), Google Fonts (web fonts on published sites), and Google Cloud Logging (browser error reports); added Anthropic for AI-assisted features, including the Aglyn Assist helper. Aligned this list with the DPA, the Privacy Policy, and the trust page. Stated the 30-day advance-notice period for new subprocessors and the objection route, matching DPA Section 7.2.
- August 13, 2026 — Verified provider entities and processing locations; corrected the Resend entity name; reconciled this list with the trust page.
- August 5, 2026 — Initial publication.
Notes
- Payment card data is collected and processed directly by Stripe under its own terms; Aglyn does not store full card numbers.
- For commerce features, sales are processed through Aglyn's own Stripe account and the Customer merchant's share is transferred to a connected Stripe Connect account held in the merchant's name (Terms of Service Section 10.2). Stripe acts as an independent controller/processor for that payment processing under its own agreements with Aglyn and with the merchant.
© 2026 Aglyn LLC. All rights reserved.