Explore Scene Library
Product01How it works02Case study03Pricing04About05Open workspace ↗
Operational design

Searchable footage still needs control.

Source integrity, rights, access, retention, and honest usage reporting define the production pilot.

SCENE LIBRARY / TRUST
Current controls

Private footage needs clear boundaries.

Accounts use password hashes and session cookies. Organization and project IDs scope uploaded media, search, and saved selections. Owners, editors, and viewers have different permissions.

01

Source integrity

The original upload stays linked to its sampled frames. A result is a candidate frame; in/out points are chosen by the editor after preview.

02

Workspace access

Customer uploads require an account in that organization. Owners invite editors and viewers; media is served only after an access check.

03

Processing record

The pilot records indexing jobs. The internal ledger is not a cloud invoice and should not be presented as one.

04

Retention and removal

Owners select 7, 30, 90, or 365 days per project. An automatic daily sweep removes expired uploads; owners can delete a project sooner.

Infrastructure status

Keep usage claims traceable.

The hosted pilot runs on Namecheap shared hosting with Firebase Firestore. Azure billing is not connected. A grant review would require provider billing records showing the actual monthly cloud usage and credits applied.

03Public-domain sample films
63Indexed sample frames
—No verified Azure usage record

For pilot data handling, see Privacy. This is a limited trial; independent security review and larger-scale load testing remain necessary before handling sensitive client archives.

Agency pilot

Test with real tasks and clear rights.

Agree on access, retention, and retrieval measures before uploading client footage.

Open workspace ↗Contact us →