We never receive your video. There is no cross-border transfer to assess.
Most video vendor reviews stall on one question: where does the asset go? With Nulx, the asset does not go anywhere. Your source file is written to your bucket, in your region, under your account. Processing reads and writes in place. Playback is served from your CDN. Nulx receives job metadata — file keys, durations, encoding parameters. Nulx does not receive, store, or transmit the media itself.
For your review
What this means for your review
- No Chapter V transfer analysis is needed for the media itself — the asset stays in the region you chose.
- {"Your bucket, your region, your account": "residency is a configuration you already control."}
- Nulx processes job metadata only (file keys, durations, encoding parameters), which keeps the processor scope narrow.
- A DPA, subprocessor list, and retention policy are available below as drafts pending legal review.
Data flow
Where the bytes go — and where they don't
The media path never touches Nulx-operated storage.
Legal documents
Supporting documents
Data Processing Agreement
Standard DPA structure scoped to orchestration metadata, with the no-media-custody principle stated explicitly.
Subprocessors
The third parties that touch account or billing data, with 30-day advance notice of changes.
Data retention
What metadata is kept, for how long, and how deletion requests are handled within 30 days.