Your media stays yours. Here is exactly how.
What silken does with your video, your keys and your account, stated as the service works today. The privacy notice and the terms of service carry the full detail, and a security review talks to the people who build silken.
A free test on your own files · or book a meeting
Read where it is. Removed when the job ends.
silken needs the file to convert it, and holds it no longer than the job does, except for the outputs you ask it to keep for you.
- Sources
- Read from your storage through a presigned URL you issue, or, for s3:// sources, through a read-only IAM role you grant with an external ID unique to your account. The temporary credentials live only in memory for the read.
- Working files
- A worker downloads the source to a scratch file on its local disk, writes the result beside it, delivers it, and removes both when the job ends, whether it succeeded or failed. If a worker stops abruptly, it removes what it left behind when it next starts.
- Outputs
- A single file goes straight to the presigned URL you supply, and no copy remains in the ordinary course. Ladders go to your own registered S3, R2, B2 or Wasabi storage, or are held on silken storage for authenticated download for seven days by default after settlement; progressive playback output is kept for seven days after the stream closes.
- Only your requested outputs
- Preview images are generated only when requested. Hosted thumbnails and sprite sheets expire after seven days. No fingerprints or unrelated media archive.
- No training
- Your media is never used to train, evaluate or improve any model.
Servers silken operates.
The API, your account and the job records run on a server silken operates. Conversions run on silken’s own worker servers, each job in a staging directory of its own that is removed when the job ends.
We name the hosting providers and the countries your media passes through on request, before you send a file. Ask for them
Keys hashed, webhooks signed, no trackers.
Found a problem? Email support@silken.io. Security reports are read by the people who build silken.
- API keys
- Stored as a SHA-256 hash with a short prefix, and shown to you once. Revoking a key also revokes it for the MediaConvert-compatible endpoint.
- Webhooks
- Signed with HMAC-SHA256, so your endpoint can check each one came from silken.
- Sign-in
- Two cookies, both necessary, sent only over HTTPS; the server keeps only a hash of the session token.
- The website
- No analytics, no advertising or social-media trackers, and no tracking cookie on any silken page.
- Billing
- The payment and metering providers receive minutes of usage, never a file, its name or its content.
Questions
Does silken keep a copy of my video?
For a job delivered to your own storage, no copy remains in the ordinary course: the worker removes its working files when the job ends. Ladders and progressive playback are held on silken storage for you to collect: a ladder for seven days by default after settlement, progressive output for seven days after the stream closes.
Is my media used to train models?
No. silken does not use your media to train, evaluate or improve any model.
How do I report a security issue?
Email support@silken.io. Security reports go to the same mailbox as support and are read by the people who build silken.
Running a security review?
Send us your questionnaire or book a meeting, and you go through it with the people who build silken.