1Video storage & retention
Source videos you upload are processed and stored only long enough to complete your render and let you download the result. Once processing is complete, you control how long your videos stay in your account: from your dashboard settings, you can choose a retention period — 24 hours, 7 days, 30 days, or 90 days — after which they're permanently deleted from our systems.
If you delete a video or your account before that window, we remove the associated files from active storage right away.
2Infrastructure
NimbleAI runs on established third-party cloud infrastructure rather than self-hosted hardware — this means the physical security, power, and network redundancy of the underlying servers are handled by providers who specialize in exactly that, not by us. As NimbleAI grows, our infrastructure is expected to evolve to match — including moving to higher-capacity providers as needed.
3Encryption
- In transit: TLS 1.2+ on every connection to our API, dashboard, and storage endpoints.
- At rest: Video files and database records are encrypted at rest by our storage and database providers.
- Secrets: API keys, tokens, and credentials are stored as environment variables on our server, never committed to source control or logged in plaintext.
4Access controls
Your account is protected by authenticated sessions and, for API and MCP access, short-lived bearer tokens (see the MCP Legal Terms for details on that specific flow). Every request — whether from the dashboard, the API, or an MCP tool call — is checked against the requesting account's own data only.
Internally, production access is limited to engineers who need it for support or maintenance.
5Sub-processors
We rely on a small number of specialized providers to run NimbleAI. Each only receives the data necessary to perform its function.
| Provider | Purpose | Data involved |
|---|---|---|
| Database & auth provider | Account data, video metadata, authentication | Account info, video metadata — not raw video files |
| Object storage provider | Storing uploaded and exported video files | Video/audio files |
| AI transcription & language model provider | Generating subtitles, titles, and descriptions | Audio transcript text, short text snippets |
| Payment processor | Billing and subscription management | Payment details — never touches our own servers directly |
| Email delivery provider | Transactional emails — onboarding, notifications, reminders | Email address, name, message content |
| Social platform integrations | Connecting your YouTube account to show performance stats (Instagram and TikTok in review, not yet available) | OAuth access tokens, public account/video stats |
A fully named, current list of sub-processors with company names is available on request at the contact below.
6Incident response
If we identify a security incident affecting your data, we will investigate, contain it, and notify affected accounts without undue delay, along with the steps we're taking and what you should do, if anything.
7Responsible disclosure
If you believe you've found a security vulnerability in NimbleAI, please report it to security@nimbleai-edit.com rather than disclosing it publicly. Include enough detail to reproduce the issue. We aim to acknowledge reports within a few business days and will keep you updated as we work through a fix.
Please avoid actions that could degrade the service or access data beyond what's needed to demonstrate the issue — we won't pursue legal action against good-faith, non-destructive research reported to us this way.
8Compliance posture
We design our data handling around standard privacy principles — data minimization, purpose limitation, and deletion on request — consistent with our Privacy Policy. If your organization needs a formal Data Processing Addendum or a specific compliance attestation, reach out and we'll let you know what's currently available.
9Contact
Security reports: security@nimbleai-edit.com. General questions: hello@nimbleai-edit.com.