The outcome

Use files, image, video, or voice features without creating permanent public links, orphaned assets, rights violations, or inaccessible ZDR-dependent workflows.

Step by step

A workflow you can repeat.

  1. 01

    Define allowed media, source rights and consent, prohibited content, data classes, storage mode, audience, public-sharing rules, TTL, moderation, provenance, accessibility, and deletion owner.

  2. 02

    Confirm that the team's retention mode supports the chosen file or media feature, use a dedicated server key, keep uploads private by default, set the shortest useful expiration, and validate type and size.

  3. 03

    Sanitize filenames and metadata, isolate untrusted attachments, constrain generation parameters, request base64 or customer-controlled upload under ZDR, and never treat generated media as proof of an event.

  4. 04

    Review content policy, likeness and intellectual-property risks, hidden sensitive material, prompt injection, quality, captions, and intended audience before creating any public URL or publishing output.

  5. 05

    Inventory file IDs, output locations and public URLs, revoke links independently, delete underlying assets when finished, verify expiry, rotate exposed keys, and retain only approved provenance records.

Working standard

What good use looks like.

  • Keep assets private by default.
  • Expire both links and underlying files.
  • Verify feature compatibility with ZDR.

Official references

Check the current product documentation.