Data Processing
Effective October 17, 2026
Why this looks different from a typical app's DPA
Passerity's Shopify access scopes are limited to read_products,
write_products and read_locales (which only tells us
which languages your store publishes, nothing about your customers). We never request Protected Customer Data
access, and there is no customer record anywhere in Passerity's database.
Most of what a typical DPA exists to govern — a vendor processing your
customers' personal data on your behalf — doesn't arise here. What we do
process on your behalf is your product catalog data and whatever
merchant/manufacturer profile information you enter; the sections below
cover that.
Sub-processors
| Sub-processor | Purpose | Data involved |
|---|---|---|
| Shopify | Platform Passerity is built on and embeds within | Product catalog data (via the Admin API) |
| Anthropic (Claude API) | AI-assisted passport drafting | Product title, description, and tags; when you use translation, also the passport text fields (materials, care and recyclability, safety warning, country of origin) — never customer data |
| Fly.io | Application hosting and database (PostgreSQL) | All merchant-entered data (company/manufacturer profile, passport content, uploaded safety certificates) |
| Sentry | Error monitoring | Application error context, with request bodies, query parameters, job arguments, and cookies excluded by default |
| Postmark | Transactional email delivery | Email address and message content for support correspondence |
Safety certificate uploads are currently stored on Passerity's own Fly.io application server, not a separate third-party storage provider. If that changes, this table will be updated.
Security measures
- All traffic to Passerity is served over HTTPS/TLS.
- Production data is stored in Fly.io's managed PostgreSQL, encrypted at rest by default.
- Backups follow Fly Managed Postgres's built-in automated schedule (full daily, differential every 6 hours, incremental hourly, up to 10 days' retention).
- Error monitoring (Sentry) is configured to exclude request bodies, query parameters, job arguments, and cookies from captured error data.
- There is no internal team or shared credential access to guard against — Passerity is operated by a single founder.
Security incident response
If a security incident is discovered — through automated monitoring or otherwise — we follow this process: detect, assess what's affected (which shop(s), and whether a Shopify access token or merchant-entered profile data was exposed — there is no customer data to expose), contain (revoke/rotate the affected credential and patch the underlying cause), fix and add a regression test where practical, and notify affected merchants without undue delay once a breach is confirmed.
Data subject requests
Shopify's mandatory customers/data_request and
customers/redact webhooks are implemented and always report
that Passerity holds nothing to export or redact for any given customer —
a structural fact, not a stub, since Passerity has no customer-scoped
data model at all. Uninstalling the app (app/uninstalled)
erases your shop's own data — company/manufacturer profile and every
product passport, including uploaded certificates — and
shop/redact acts as a safety net if that somehow didn't
already happen.
Contact
Questions about how Passerity processes data, or to request a signed DPA: support@passerity.com.