Subprocessors

Vendors that may process customer data on Renply staging. Customer ESPs you configure are yours, not ours.

Render
Compute, PostgreSQL, Key Value, TLS
Application data, metadata, encrypted secrets
Cloudflare
DNS (grey-cloud); R2 object storage
Inbox/visual bodies (R2); DNS queries
GitHub
Source, Actions, PR metadata
Source; GitHub webhook ingest fields (owner/repo/PR), not raw payloads
Sentry
Exceptions (org bytelon)
Stack traces; payloads and secrets stripped
Better Stack
Uptime, status, OTLP logs/spans/metrics
Health URLs; traces/metrics (3d logs/spans, 30d metrics). No full bodies
Paddle
Prepaid billing (sandbox today)
Billing identity / transactions
Postmark
Company dogfood / support mail
Support and verification mail, not customer ESP send
SonarCloud
SAST / quality gate
Source (not runtime customer data)

When you configure Sender, your ESP account is your processor. Renply stores those credentials encrypted and sends through your account. This list is not a signed DPA.