TRUST & SECURITY
Subprocessors
This is the real list — every third party that processes Press Run customer data in production today, what they process, and why. "Customer data" means account data, organization/brand data, content (drafts, media, published posts), credentials/tokens, and payment data. Providers marked not yet enabled are listed for transparency and process nothing today.
Accurate as of November 19, 2026 · Part of Security & Trust at Press Run
Infrastructure
| Provider | What they process | Why |
|---|---|---|
| Render | Everything in production: the Press Run API and background workers run on Render, and the production Postgres database (account data, organization trees, campaigns, content, sealed credentials) is hosted there. | Production hosting. Transitional: Press Run is mid-migration to Cloudflare Containers + Neon (see below); this row is updated when the cutover completes. |
| Cloudflare | Network traffic (DNS, TLS termination, CDN/WAF) for Press Run's web and API domains; media files in R2 object storage (uploaded and generated images/video); image generation via Workers AI (prompts + generated images); the public web app and hosted customer blogs run on Cloudflare Workers. Also our domain registrar. | Edge network, media storage, AI image generation, web hosting. |
| Neon | Staging only. A copy of the production database structure restored from backup for migration testing of the Cloudflare move. | Staging database for the hosting migration. Not a production system; it holds a point-in-time backup snapshot, and it is decommissioned or promoted as part of the cutover — this row gets rewritten either way at cutover. |
| GitHub (Microsoft) | Source code and CI build artifacts. No customer content or credentials (secrets are referenced, never stored in the repo). | Code hosting and the build/deploy pipeline. Listed for completeness; GitHub does not process end-customer data. |
Payments & email
| Provider | What they process | Why |
|---|---|---|
| Stripe | Payment details (card data goes directly to Stripe — it never touches Press Run servers), billing identity, subscription and invoice records. | All subscription, credit top-up, and add-on billing. |
| Resend | Recipient email addresses and the content of transactional emails (address verification, password reset, team invites). | Press Run sends its own account email from its own service — verification and reset mail goes from Press Run to the account holder, nowhere else. |
AI & content services
These services process content you ask Press Run to create.
| Provider | What they process | Why |
|---|---|---|
| Meta Model API (Meta) | The text prompts and brand/topic context needed to draft posts, and the drafts returned. | Standard text generation for campaigns and loops. |
| Cloudflare Workers AI | Image prompts and generated images (also listed under Cloudflare above). | Standard AI image generation. |
| Tavily | Research queries (topics) and the web results returned. Queries are topics, not customer records. | Web research that backs Press Run's cited-source drafting. |
| Pexels / Pixabay | Stock-media search queries only. No customer data is sent; results are licensed stock photos/video. | Stock media library for posts that use library imagery. |
| Venice / Runware — NOT YET ENABLED | Nothing today. The premium-generation integration is built, but the provider keys are not installed in production and the feature is dark. | Premium text/image (Venice) and video (Runware) generation, pay-per-use, when the owner enables it. This row moves to active status — and the trust page is updated — before the feature turns on for any customer. |
Publishing destinations
At your direction — not subprocessors in the classic sense. When you connect an account and approve a post, Press Run sends that post — and only that post — to the destination you chose. These platforms receive your published content and hold the connection tokens (sealed on our side) that make publishing possible:
- Meta — Facebook Pages, Instagram, Threads: post content, media, scheduling; account tokens from the connection you authorize.
- LinkedIn: post content and media to the profile/page you connect.
- TikTok: video posts to the account you connect.
- Google — YouTube: video posts to the channel you connect.
- Your own website/blog: if you connect the hosted-blog destination, article content is published to it.
Each platform processes that content under its own terms and privacy policy. Disconnecting a destination in Press Run revokes our access going forward.
First-party systems
Same operator — not third parties:
- Vajgrt Brain (operated by Vajgrt Labs, Press Run's operator): Press Run mirrors its financial transactions — subscriptions, top-ups, refunds — into the operator's central business ledger, with provenance. This is the same company's books, not a third-party disclosure; it exists so every dollar is accounted for in one place.
- Fleet error reporting: if the app hits an error, a technical error report (what broke, in which part of the app — not your content) goes to the operator's error inbox so it gets fixed.
Change policy
We update this page before a new provider starts processing customer content, and the "accurate as of" date at the top changes with every edit. Enterprise pilot customers get the same notice by email to their named contact.