Snapshot 110421

Document
Subprocessor list
URL
https://www.rwx.com/docs/security/subprocessors
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
173672 bytes
SHA-256 (raw)
75b8e26fde815df6dca9535a7a8890a949ab20119302803c51e0c75a6d9f0ce8
SHA-256 (normalized text)
3d5322472954a25c58a792954e4c285a3846e0e41e1e0eaa092bef8715ddd2ca

Raw (normalized text)

Scripts and page chrome removed; this is what change detection compares.

RWX Documentation
Subprocessor list
Last updated: 2026-10-16
RWX uses the following third-party subprocessors to support delivery of our services. A subprocessor is a third party engaged by RWX to process personal data on behalf of our customers in connection with the RWX services.
Infrastructure & data storage
Subprocessor	Purpose	Data Categories	Processing Location
Amazon Web Services
Cloud infrastructure hosting, artifact storage (S3), application logs
Customer content, build artifacts, logs, account metadata	United States
Networking & DNS
Subprocessor	Purpose	Data Categories	Processing Location
Cloudflare
DNS, network services, and application request and response proxying
IP addresses, network metadata, application request and response content
United States
Monitoring, logging & observability
Subprocessor	Purpose	Data Categories	Processing Location
ClickHouse	System log storage and analysis	System logs, service metadata, identifiers	United States
Datadog
Metrics, logging, performance monitoring, browser analytics and session replay
Logs, service metadata, user IDs and email addresses, page URLs, browser interactions and session recordings
United States
Website analytics
Subprocessor	Purpose	Data Categories	Processing Location
Plausible Analytics	Website analytics and signup conversion tracking	IP address, user-agent string, page URLs, event names	European Union
Plausible processes IP addresses and user-agent strings to derive analytics without storing those raw values. See Plausible's data policy.
Customer support & incident management
Subprocessor	Purpose	Data Categories	Processing Location
Slack Technologies	Customer support communications and operational notifications	Messages, identifiers, log excerpts	United States
Google (Gmail / Google Groups)	Email-based customer support communications	Email addresses, message content	United States
PagerDuty	Incident management and alerting (limited to incident metadata)	Incident metadata, service identifiers	United States
SavvyCal	Scheduling onboarding and migration support meetings
Name, email address, scheduling details, browser and network metadata
United States
Email & communications
Subprocessor	Purpose	Data Categories	Processing Location
Postmark	Transactional email delivery
Email address, message content (including submitted feedback), message metadata
United States
Billing & payments
Subprocessor	Purpose	Data Categories	Processing Location
Stripe	Payment processing and subscription management	Billing contact info, payment metadata	United States
Bill.com	Invoicing and accounts payable	Billing contact info, invoice data	United States
Authentication & security
Subprocessor	Purpose	Data Categories	Processing Location
GitHub	Authentication (OAuth)	User identifiers	United States
WorkOS
Enterprise SSO, identity management, and directory synchronization
User identifiers, names, email addresses, authentication metadata, organization names and domains, directory groups
United States
hCaptcha	Bot detection and abuse prevention	IP address, challenge metadata	United States
MaxMind	Fraud prevention and signup abuse detection (minFraud service)	Email address, IP address, user-agent string at signup	United States
Internal applications
Subprocessor	Purpose	Data Categories	Processing Location
Render	Application hosting of internal operational tooling	Account metadata	United States
Neon	Managed database services	Account metadata	United States
Customer-configured identity integrations
RWX supports optional integrations with third-party infrastructure and compute providers via OpenID Connect (OIDC). These integrations are configured and controlled by the customer, and RWX does not engage these providers as subprocessors.
Developer integrations
RWX integrates with customer repositories via customer-installed applications or webhooks, such as GitHub, GitLab, Forgejo, and Cursor Origin. These integrations are initiated and authorized by the customer, and operate under the customer's applicable terms with those providers. RWX only receives the events that the customer grants access to through these integrations.
Optional analytics integrations
When enabled for an organization, the DX integration sends build analytics to the configured DX instance. This includes repository, branch, commit and pull request details, run identifiers, URLs, timing and status, and associated email addresses and GitHub or GitLab usernames.
Use of AI-assisted development tools
RWX employees may, on a limited and case-by-case basis, use AI-assisted development tools (such as Cursor or Claude Code) to debug or analyze customer-provided data for support or operational purposes. Such access is subject to RWX's internal access controls, logging, and data handling policies, and is limited to the minimum data necessary to perform the relevant task.
For questions regarding this list, please contact [email protected].