Polsia Subprocessors
Polsia uses third-party subprocessors to deliver its service, with actual usage depending on enabled product features, account settings, and environment configuration.
- Subprocessors
- 22
- Categories
- 12
- Last scanned
| Name | Category | Purpose | Location | Data processed |
|---|---|---|---|---|
| Stripe | Payment Processing | Payments, subscriptions, billing portal, checkout, daily ad spend charges | – | Billing identifiers, transaction metadata, subscription status, saved payment methods |
| Render | Cloud Infrastructure | Application hosting for platform and customer-provisioned web services | – | Service/runtime metadata, operational logs, deployment configuration |
| Neon (PostgreSQL) | Database | Managed database hosting for platform and customer-provisioned databases | – | Application-stored customer/account and product data, database credentials |
| Redis provider | Database | Queueing, pub/sub, short-term operational state | – | Transient job and session-related operational metadata |
| Cloudflare R2 | Cloud Infrastructure | Object storage for uploaded/generated assets including ad creatives | – | Files, media assets, AI-generated video/image content, related metadata |
| Anthropic | AI | Primary LLM execution for agent tasks, chat, and content generation | – | Prompts, tool context, generated outputs, model telemetry |
| AWS Bedrock | AI | LLM execution fallback and model routing | – | Prompts, tool context, generated outputs, model telemetry |
| OpenAI | AI | LLM execution and video generation (Sora 2) | – | Prompts, video generation prompts, generated content, model telemetry |
| Fal.ai | AI | AI media generation (video, image, audio) across multiple models | – | Generation prompts, generated media, model metadata |
| Meta | Social Media | Advertising campaign management, ad creation, budget management, audience targeting; marketing attribution, ad conversion measurement, and server-side conversion events | – | Campaign config, ad creatives, targeting parameters, budget data, performance metrics; hashed identifiers (SHA-256 email/user ID), event metadata, _fbp/_fbc, IP/UA |
| Postmark | Transactional, operational, and outbound email delivery and inbound processing | – | Email addresses, message content, delivery metadata | |
| Photon | Communications | iMessage transport for private messaging with Polsia | – | Phone number, account email, display name, message content and attachments, delivery and status metadata |
| Hunter.io | Email verification and deliverability lookup | – | Email addresses and verification metadata | |
| GitHub | Developer Tools | Repository integration, code automation, and customer-provisioned source code repositories | – | OAuth tokens, repo metadata, source code, action logs |
| Cloud Infrastructure | Authentication and optional connected account functionality | – | OAuth profile fields, authorized account metadata, tokens | |
| Slack | Communications | Optional workspace integrations and notifications | – | OAuth tokens, channel metadata, message metadata |
| Late.dev | Marketing | Social media posting/scheduling across multiple platforms | – | Social account IDs, post content, media, OAuth credentials |
| Expo | Developer Tools | Mobile application builds and distribution | – | App source code, build configuration, EAS build metadata |
| Browserbase | Developer Tools | Cloud browser automation for agent tasks | – | URLs visited, page interactions, screenshots, extracted content |
| ScreenshotOne | Media | Automated screenshot generation | – | Requested URLs/pages and generated image metadata |
| Sentry | Error Tracking | Error monitoring and diagnostics | – | Application errors, stack traces, technical telemetry |
| IPinfo | Data Enrichment | IP geolocation (optional enrichment) | – | IP address, coarse location metadata |
No subprocessors match your filters.
Your data may flow beyond direct subprocessors. Click to expand and see the chain.
Loading data flow...
No changes recorded yet. Changes will appear here after the next scan detects updates.