Skip to main content
Compliance

Review permanent storage, managed processing, and AI transfers separately

In a BYOC setup with connected customer storage, sources and outputs are kept in customer Cloudflare R2. A free account without connected storage uses NULX-managed storage. During managed encoding, a NULX worker temporarily reads the source. If automatic captions are enabled, a low-bitrate audio extract is sent to Cloudflare Workers AI. Location hints are not residency guarantees.

For your review

What this means for your review

  • Review the BYOC R2 location and temporary NULX managed-worker processing location separately.
  • R2 Location Hint is a best-effort performance hint, not a data-residency guarantee.
  • Automatic captions send an audio extract to Cloudflare Workers AI and require separate subprocessor review.
  • Review current processors and retention or deletion rules in the Privacy Policy; enterprise customers needing a separate DPA can agree one before contracting.

Data flow

Where the bytes go, and where they don't

This flow describes BYOC with connected customer R2. Sources and outputs are kept in customer R2, managed encoding uses temporary NULX worker storage, and automatic captions send a low-bitrate audio extract to Cloudflare Workers AI.

Customer Cloudflare R2 bucket
NULX managed processing worker
Temporarily receives the source and writes results to R2
Your CDN → your viewers
Files for a free account without connected storage use NULX-managed storage. In every setup, NULX processes job metadata and media needed for managed transcoding; automatic captions send a low-bitrate audio extract to Cloudflare Workers AI when enabled.