Security summary
What we can reach, what we store, how long, and how to delete it. The Privacy Policy is the binding text.
Scopes: what we can reach
- We request no YouTube OAuth scopes. We cannot see your YouTube account, your analytics or anything private.
- Sign in with Google uses only
openid email profile, to confirm your email address. - The Chrome extension reads the public YouTube page you are looking at, in your own browser.
Storage: how it is held
- Passwords are stored as scrypt hashes, never as text.
- Sessions are random ids held on our server, so signing out ends them at once. You can see and end your sessions in Account.
- API keys are stored as hashes. A key is shown once, and can be set to expire.
- Two-factor secrets and webhook signing secrets are encrypted at rest. Recovery codes are stored as keyed hashes.
- Traffic uses HTTPS.
- Webhooks we send are signed, so your tools can check they came from us. See Automate.
Two-factor sign-in
Optional on every plan. Turn it on in Account with any authenticator app. You get 10 one-time recovery codes.
AI tools
Text you send to the built-in AI goes to our AI provider to get an answer. With your own key, it goes straight from your browser to your provider, and TubeMind never sees the key or the text. We make no statement here about how providers use text for training, because we have not confirmed each provider's terms.
Retention: how long we keep it
- Account data: until you delete your account.
- Activity records: raw records 90 days, aggregates with no user id 24 months.
- Backups: up to 30 days, then overwritten.
- Public YouTube statistics: up to 30 days, then refreshed or deleted.
The full list is in the Privacy Policy.
Deletion: how to remove it
- Delete your account from Account. Saved lists, trackers and keys go at once.
- Download a copy first as JSON or CSV from the same page.
- A channel owner can ask for removal from the index on the removal form.
Report a problem
Email [email protected]. We answer every message within 2 business days.