Processor List
Premwise Processor List
Version 2026-09-25.2. PUBLISHED at `https://premwise.ai/legal/processors`, the location stated in §5.1 of the Privacy Policy, as MSA §8.2(e) requires. This document is incorporated by reference into the Premwise Master Services Agreement at §1.1(6) and §8.2(e).
Purpose. MSA §8.2(e) commits Premwise to engage subprocessors only under written terms no less protective than §8.2, to remain responsible for their performance, and to identify each subprocessor here, with notice of additions before they begin processing. This list is that identification.
Scope, stated precisely. A subprocessor is a third party Premwise engages that processes Customer Personal Data — personal information contained in Customer Content, or account and contact data — on Premwise's behalf. Vendors that never touch Customer Personal Data are deliberately excluded and are not made to look like subprocessors: the code host and CI (GitHub), and the rating-bureau and regulator sources from which public filed rating values are obtained, are sources and tooling, not processors — no Customer Content is sent to them.
Subprocessors
| # | Provider | What it does for Premwise | Categories of data processed |
|---|---|---|---|
| 1 | Supabase, Inc. | Application database, authentication, and object storage for customer-uploaded documents | Customer Content including uploaded worksheets, loss runs and payroll files; account identifiers; authentication events |
| 2 | Vercel Inc. | Application hosting and serverless compute — the product itself runs here | Customer Content in transit and in request/response processing; account identifiers; request metadata |
| 3 | Anthropic PBC | AI-assisted extraction of fields from customer-supplied documents | The contents of documents submitted for analysis, which may include employee, payroll, policy, claim and loss-run information |
| 4 | Cloudflare, Inc. | Object storage (R2) for encrypted copies of customer-uploaded documents | Encrypted copies of customer-uploaded documents, and an encrypted index of those copies (path, size and checksum). The `documents` bucket is synchronised to Cloudflare R2 daily, encrypted before it leaves, with a per-object readback digest and a retention rule of 30 days (ceiling 90). |
| 5 | Stripe, Inc. | Payment processing, subscription billing, and invoicing | Billing contact details and transaction records. Premwise does not receive or store full payment-card numbers |
| 6 | Resend, Inc. | Transactional and operational email delivery | Recipient email address, name where included, and message contents |
| 7 | Functional Software, Inc. (Sentry) | Application error monitoring | The error's type and message, the code locations where it occurred, and the request's method and URL with its query string and fragment removed. Customer values are removed before transmission by an allowlist filter: no request headers, cookies, bodies, query strings, breadcrumbs, session replay or user identifiers are sent, and performance tracing is off. An error message may incidentally name a value present in the failing operation |
| 8 | HubSpot, Inc. | Customer-relationship records for prospects and customers | Business contact data — name, email, company, and self-declared premium band |
| 9 | Plausible Insights OÜ | Product and site analytics | Page paths and aggregate usage, per scope. Signed-out product pages: page path only — the query string is removed in full, so authentication tokens and continuation values are never transmitted. Marketing site: page path plus only the campaign parameters named here — `ref` and any `utm_` parameter (`utm_source`, `utm_medium`, `utm_campaign`, and the like) — every other query parameter is removed. No signed-in product page is measured at all. |
Additions require notice to Customers before the new subprocessor begins processing, per MSA §8.2(e).