Subprocessors
Third parties Forgeon uses to provide the platform, and what they process.
Heads up: This list reflects how Forgeon operates its PaaS today and will evolve as we add regions, features, and providers. We’ll update this page when we make material changes. See Change notifications.
Last updated: 2025-10-20
Subprocessors
Forgeon uses carefully selected service providers (“subprocessors”) to help deliver our platform—compute, storage, email, analytics, and reliability tooling. Each subprocessor only receives the minimum data needed for its function, and we require appropriate contractual and technical safeguards.
Data roles: For your account and platform usage, Forgeon is a controller. For data processed through your apps hosted on Forgeon, we act as a processor/service provider.
Current subprocessors
Legend — Data Categories
Account: name, email, org info, auth metadata
Ops: logs, metrics, runtime/build events & artifacts
Billing: subscription metadata, invoice references (no full card data)
Comms: transaction emails, support mail routing
Analytics: pseudonymous product analytics/telemetry
| Provider | Service | Data Categories | Processing Location(s) | DPA / Terms | Retention | Notes |
|---|---|---|---|---|---|---|
Cloud Hosting Provider (e.g., Linode / DigitalOcean / AWS) | Compute for control plane VMs, object storage for artifacts/logs | Ops, limited Account (service auth), artifacts | Primary region(s) you select | Link to provider DPA | As configured (artifacts/logs lifecycle) | Hosts control-plane services, backups, and object storage buckets |
Email Delivery (e.g., AWS SES / Resend) | Outbound transactional email | Comms, limited Account | Provider regions | Link to provider DPA | Provider defaults; message metadata per policy | Password resets, verify emails, receipts |
Error Tracking (e.g., Sentry) | App/server error telemetry & traces | Ops (diagnostics), limited metadata | Provider regions | Link to provider DPA | Configurable (e.g., 30–90 days) | Sensitive payload filters enabled; PII scrubbing |
Product Analytics (e.g., PostHog / Plausible) | Product usage analytics (pseudonymous) | Analytics | Provider regions / self-hosted | Link to provider DPA | Minimal, aggregated; per config | Used to improve UX and features; can be disabled in certain plans |
Git Integration (e.g., GitHub App) | Repo metadata, installation IDs, minimal tokens | Account (integration), Ops (build metadata) | Provider regions | Link to provider terms | Until revoked / uninstall | Limited scopes; no blanket repo read unless authorized |
Payment Processor (e.g., Stripe / Xendit) | Billing & subscription processing | Billing (no full card data on Forgeon) | Provider regions | Link to provider DPA | As required by law / provider | PCI handled by processor; we store references only |
Monitoring/Status (e.g., Uptime service) | External uptime checks & incident comms | Ops (status pings), limited Account (subscriptions) | Provider regions | Link to provider terms | Provider defaults | Public status page & incident updates |
Replace placeholders above with your actual providers and links before launch. If you self-host analytics or error tracking, note that explicitly.
Purpose & data detail
Compute & Storage
- Purpose: Run control-plane services, store artifacts, logs, backups.
- Data: runtime/build logs and artifacts, limited internal metadata, tenant IDs where required.
- Safeguards: network segmentation, encryption in transit, encrypted volumes/buckets, role-scoped access.
Email Delivery
- Purpose: Transactional emails (verification, resets, receipts).
- Data: recipient address, templates/variables, delivery metadata.
- Safeguards: DMARC/DKIM/SPF, suppression lists, least privilege API keys.
Error Tracking & Monitoring
- Purpose: Crash reports, performance traces, uptime checks.
- Data: stack traces, request metadata (with PII scrubbing), synthetic pings.
- Safeguards: payload filters, data retention caps, access controls.
Analytics (Product)
- Purpose: Understand usage to improve features and docs.
- Data: pseudonymous event data (pages, clicks, flows), no sensitive payloads.
- Controls: disable/limit tracking for certain plans or upon request.
Payment Processing
- Purpose: Subscriptions, invoices, receipts, taxes.
- Data: billing contact info, subscription metadata, payment reference IDs.
- Note: Card data is handled by the processor (PCI). Forgeon does not store full card numbers.
Subprocessor selection & review
We assess security posture, reliability, data residency, and contract terms (including DPAs and SCCs where applicable). We require appropriate confidentiality, breach notification, and deletion/return of data at termination.
International transfers
Data may be processed outside your country where our providers operate. We implement reasonable safeguards required by applicable law (e.g., SCCs), and minimize data sent to each provider.
Change notifications
We plan to update this page for material changes—adding a new subprocessor or changing purpose materially. For paid customers, we may also send email or dashboard notices with a reasonable lead time, subject to urgent security or availability needs.
- How to get updates: Watch this page, enable Releases notifications, or subscribe to our status page (placeholder).
- Questions or objections: Email privacy@forgeon.io or security@forgeon.io with your org details.
Contact
- Privacy: privacy@forgeon.io
- Security: security@forgeon.io
- Legal: legal@forgeon.io
- Support: support@forgeon.io
Before launch: Replace provider placeholders, add real DPA
links, specify regions (e.g., “Singapore (ap-southeast-1)”), and align
retention windows to your internal policies. If you maintain a
status page, link it here.