cinemasetfreeUsing your own bucket
A project can write its images and footage to your own Cloudflare R2 or Amazon S3 bucket instead of ours. The production's files then sit somewhere your contract already covers.
Why a production would want this
Footage and stills are the assets a production is most often contractually obliged to keep somewhere specific. A financier, a studio or a broadcaster may require the material to live in an account they can audit, and a delivery schedule usually names the place it is delivered from.
Pointing the project at your own bucket satisfies that without exporting anything: the files are written there in the first place.
Connecting one
You supply the provider, the bucket name, its region and a key pair with write access. R2 fills its own endpoint in from your account ID; S3 takes the endpoint for the region you chose.
The credentials are stored against the project and used server-side. Nothing in the browser ever holds them, and a crew member with media access never sees them.
Connecting a bucket changes where new files go. It does not move what is already there, and disconnecting does not bring anything back. Treat the switch as a line in the project’s history rather than a setting you toggle.
Where it sits
Storage lives on the Data tab beside export and deletion, which is the right neighbourhood: all three are answers to “where does this production’s material actually live, and how do I get it out”. The tab is visible only to the project owner.