Security and data handling
Who can see your files and results, what your analysis services receive, how requests are signed and how long Editframe keeps your files.
- HMAC-SHA256signs each request to your service and each notification to you
- 4 hoursis the longest a media link in a request can read its file
- 30 daysis the furthest ahead you can set a file to expire
- US and Canadaare where the privacy policy places hosting and processing
Access
Your organization only
In Editframe Factory, each organization sees only its own pipelines, runs, results and rendered files, and a database check refuses any run on another organization's file.
Editframe administrators
Editframe administrators can view your pipelines and results, and cancel or retry runs.
Decision records
Every decision and change is recorded with who made it, and an accepted result can't be changed afterwards. The records are deleted with their video and aren't an exportable audit log.
Analysis services
Inputs sent to your service
Endpoint steps send file details, earlier results and media links to the HTTPS service configured for that step. Your service controls which model providers, if any, receive those inputs.
Built-in analysis
Built-in steps, including transcription and finding faces and spoken personal details, run on Factory's workers. An external analysis service runs where you host or configure it.
Recorded with each run
Each run records the version of its pipeline file, including the endpoint IDs used by its service steps.
| step | service | inputs | runs on |
|---|---|---|---|
probeprobe | built-in | the file | Factory |
transcripttranscribe | built-in | audio | Factory |
framessample_frames | built-in | video | Factory |
scenesdetect_scenes | built-in | video | Factory |
objectsendpoint | Configured service | frames | Your service |
momentsendpoint | Configured service | transcript, frames | Your service |
sentimentendpoint | Configured service | transcript | Your service |
summaryendpoint | Configured service | transcript, moments | Your service |
Signing
Requests to your service
Requests to your service carry Standard Webhooks signature headers (HMAC-SHA256), so your service can verify Editframe sent them.
Media links
Media links Editframe serves in those requests are signed and read one file for at most 4 hours.
Notifications to you
Notifications to you are signed differently: an X-Webhook-Signature header (HMAC-SHA256 of the body).
POST /tags HTTP/1.1
Host: models.example.com
content-type: application/json
webhook-id: 7b30e9d4-…:1
webhook-timestamp: 1793282400
webhook-signature: v1,Qm7cX2LkD0rT9a4ZsWvE1yHn8uJbPf3oKg6iNcRtYxA=Retention
Files
Files are kept until you delete them, or expire on a date you set when you create them, up to 30 days ahead. A re-rendered video expires when its source does, and deleting a file deletes its runs.
Videos read by URL
Editframe doesn't copy a video it reads by URL. Sampled frames, step results and re-rendered videos made from it are stored by Editframe.
Hosting
Where data is processed
Editframe's privacy policy states that it hosts and processes information in the United States and Canada and encrypts it in transit.
Staff access
The policy also states that staff access is limited to those who need it and that production access requires multi-factor authentication.
Factory is hosted by Editframe, with on-prem options available.
Security questionnaires
Email your security questionnaire to hello@editframe.com.