Amberscript
Amberscript · Audio and voice · NL · www.amberscript.com
Last verified 2026-09-16
Entry
services/amberscript.yamlTraining on your data (default tier)
Audio and generated transcripts are never used to train the language models; Google Workspace data is likewise excluded
Retention
Files and accounts permanently deleted from servers when the user deletes them
Data residency
Data never stored outside Europe; corporate customers may use their own servers
Vendor data-handling terms
Training on your data (default tier)
Audio and generated transcripts are never used to train the language models; Google Workspace data is likewise excluded
“The audio and transcripts that are being generated, will never be used for training purposes of the language models that are used.”
Retention
Files and accounts permanently deleted from servers when the user deletes them
“If you delete your account or files within your account, they will be permanently deleted from our servers.”
Data residency
Data never stored outside Europe; corporate customers may use their own servers
“Your data is never stored in locations outside of Europe. / A different privacy policy may apply to corporate customers, for example, because they use their own servers.”
Domains and endpoints
observed means seen in Unseen deployments; vendor-documented means listed by the vendor. Vendors do not publish complete lists.
| Host | Role | Source |
|---|---|---|
| amberscript.com | app | observed |
Assessment
Web app and API: low
Reasoning: A Dutch transcription and subtitling service. No training on audio or transcripts, EU-only storage and user-controlled deletion. Human transcription tiers mean people may hear the audio, which the policy acknowledges.
Flags: Human transcribers may process audio on professional tiers · Assessed 2026-09-16. The assessment is Unseen's; the terms above are the vendor's.
Changelog
- 2026-09-16Documented. Training, retention and storage terms verified against the Amberscript privacy policy.
- 2026-09-15Listed from the Unseen catalogue with observed domains.
Corrections
Pull request on GitHub, or the form below. Changes are reviewed and recorded in the changelog.