Subprocessors

Subprocessors without unsupported claims.

These pages describe the intended product policy surface while formal legal, security, vendor, and Enterprise reviews are still gated by the operational readiness register.

Reviewed by: GetFileURL technical team
Last updated: June 5, 2026

Open dashboard Security model

subprocessorsvendorsCloudflareConvexClerk

Current statusAPI-ready

Published as a placeholder until formal review is complete.

SourceFileRelayPOSTOutputURL

Status: Placeholder pending legal and vendor review
Core vendors: Cloudflare, Convex, Clerk
Optional vendors: PostHog, Sentry-style error reporting, scanner provider, Stripe later

Claims gate:
no SOC 2 claim
no regulated privacy framework claim
no regional residency claim
no malware-free claim
legal review required

Short answer

What this page answers

Current GetFileURL subprocessor placeholder for Cloudflare, Convex, Clerk, PostHog, and future scanner/payment vendors pending legal review.

Use this page when the workflow needs file bytes available at a direct URL with predictable metadata, lifecycle controls, and a cleanup path.

Updated June 5, 2026

Current vendors

Core product architecture depends on a small vendor set.

Cloudflare handles Workers, R2, CDN, Turnstile, Email Sending, and Web Analytics. Convex handles database, sync, functions, workflow state, and source-of-truth product records. Clerk handles authentication.

Cloudflare

Used for web runtime, upload API worker, delivery worker, storage, CDN, Turnstile, email, and public web analytics when configured.

Convex

Used for workspace data, realtime dashboard state, audit events, operational records, workflows, and control-plane functions.

Clerk

Used for user authentication and JWT identity delivered to Convex.

Future review

Optional vendors must pass review before claims depend on them.

PostHog, error reporting, scanner providers, Stripe, and Enterprise regional services need privacy, logging, retention, DPA, and regional review before public compliance claims rely on them.

Analytics

PostHog events are sanitized and disabled when no project token is configured.

Scanner

Scanner provider selection remains a validation item before scanner-safety claims.

Billing

Stripe is deliberately deferred and should be listed only when implemented.

FAQ

Answers before the workflow breaks

Is this the final subprocessor list?

No. It is a placeholder and must be approved before Enterprise commitments.

Is PostHog always enabled?

No. Product analytics is disabled unless a PostHog project token is configured.

Will Enterprise customers get vendor review?

Yes, Enterprise commitments require contract-specific vendor and regional review.

Keep building the file URL path

Back to home