Sub-processors
Who helps run Pushary, what they process, and what still needs verification.
This review inventory reflects the Team service integrations, not a final approved subprocessor schedule. Legal entities, contractual roles, processing locations and transfer safeguards remain under review. It is not an EU-only processing commitment or a complete vendor attestation.
English agreement copy · Version 2026-10-29-review-1
Service infrastructure
Providers supporting the application, its records and communications.
Clerk
- Purpose
- Account authentication and identity sessions. Pushary stores its own workspace membership records.
- Data involved
- Account identifiers, names, email addresses and authentication/session information.
- Processing region
- Not yet verified for our deployment.
- Provider information
- Clerk privacy information
Neon
- Purpose
- Application database, including Team records and encrypted transcript records.
- Data involved
- Workspace and membership records, questions, responses, session metadata and stored encrypted transcript records.
- Processing region
- Not yet verified for our deployment.
- Provider information
- Neon privacy information
Vercel
- Purpose
- Web application and API hosting, workflows and uploaded image storage.
- Data involved
- Request metadata and data processed by the application; uploaded images when used.
- Processing region
- Not yet verified for our deployment.
- Provider information
- Vercel privacy information
Railway
- Purpose
- Background delivery and recovery services. Cache and queue hosting must be confirmed against deployment configuration.
- Data involved
- Delivery payloads and identifiers processed by enabled workers, job state and operational logs.
- Processing region
- Not yet verified for our deployment.
- Provider information
- Railway privacy information
Resend
- Purpose
- Transactional and lifecycle email delivery.
- Data involved
- Recipient email addresses and email content, including Team summaries when enabled.
- Processing region
- Not yet verified for our deployment.
- Provider information
- Resend privacy information
Mobile delivery
Delivery depends on the device and channel. Contractual roles across Expo, Apple and Google need confirmation.
Expo
- Purpose
- Mobile push delivery, forwarding to Apple or Google for the device.
- Data involved
- Push tokens, notification payloads and delivery receipts.
- Processing region
- Not yet verified for our deployment.
- Provider information
- Expo privacy information
Apple APNs
- Purpose
- Final push delivery to Apple devices.
- Data involved
- Device push identifiers and notification payloads.
- Processing region
- Not yet verified for our deployment.
- Provider information
- Apple APNs privacy information
Google FCM
- Purpose
- Final push delivery to Android devices.
- Data involved
- Device push identifiers and notification payloads.
- Processing region
- Not yet verified for our deployment.
- Provider information
- Google FCM privacy information
Billing and product operations
These providers support accounts, purchases or analytics. Their controller or processor role depends on the activity; they are listed separately from service-content processing.
PostHog
- Purpose
- Product analytics where configured; browser analytics follow consent controls.
- Data involved
- Account/workspace identifiers and product event properties. The configured endpoint and processing terms need verification.
- Processing region
- Not yet verified for our deployment.
- Provider information
- PostHog privacy information
Stripe
- Purpose
- Web subscription billing and payment processing.
- Data involved
- Billing contacts, customer/subscription identifiers and payment information supplied at checkout.
- Processing region
- Not yet verified for our deployment.
- Provider information
- Stripe privacy information
RevenueCat
- Purpose
- Mobile purchase and entitlement management for app-store subscriptions.
- Data involved
- App-user identifiers, purchase/receipt information and entitlement events; relevant to mobile purchases.
- Processing region
- Not yet verified for our deployment.
- Provider information
- RevenueCat privacy information
Tools your team connects
AI tools and optional destinations such as Slack or Telegram depend on what your team connects. Their own agreements may apply. They are not automatically classified as Pushary subprocessors; the final review must identify who selects each service and which data is sent.
Version history
· 2026-10-29-review-1 — Clarifies that Clerk provides authentication while Pushary stores workspace membership. No provider location or contract has been marked verified.
· 2026-10-28-review-1 — Initial integration inventory. Contract, role and location verification pending.
This is a dated review record. Change notifications and an objection process must be agreed in the final DPA; this page does not enrol you in a notification service.