Security at Versabot
A service of DataStreams Solutions, LLC
Last updated: November 19, 2026
This page describes how we protect the data you and your customers trust us with, and what we do when something goes wrong. Everyone who works on Versabot follows these practices. If you find a security problem, please tell us at contact@datastreamssolutions.com.
Who is responsible
Trevor Martin, founder of DataStreams Solutions, is responsible for information security at Versabot. Security questions and reports go to contact@datastreamssolutions.com.
Encryption
- All traffic to Versabot uses HTTPS (TLS). Plain HTTP requests are redirected to HTTPS.
- Versabot's workspace data, including any bank data received through Plaid, is stored on an encrypted disk volume. Its nightly and pre-release backups are kept on the same encrypted volume and are pruned on a schedule.
- Passwords are stored as salted hashes. API keys and tokens for connected services are kept out of source code.
Access to your data
- Workspaces use roles (owner, admin, member, auditor, client admin and client viewer). Staff on an agency workspace only see the clients they are assigned to.
- Two-step sign-in with an authenticator app or a passkey is available on every account, and it is required before anyone can connect a bank account.
- Production servers are reached only with SSH keys held by the founder. Access is not shared.
- Actions that send messages, publish content, spend money or change connected accounts need approval from a person, and they are logged.
Your consent
We only collect data from your bank, calendar, email, social and payment accounts after you connect them yourself through each provider's own consent screen (for example Plaid Link, Google or Stripe). You can disconnect any of them at any time, and you can ask us to delete your data. See our privacy policy and data deletion pages.
Keeping systems up to date
- Operating system security updates are installed automatically on our servers.
- Every week we run automated vulnerability scans of our servers, the container images we run and the computers we build Versabot on. The results are reviewed and fixes are scheduled by severity.
- Code changes are tested before they are released, and every release keeps a way to roll back.
If something goes wrong
If we learn that customer data may have been exposed, we contain the problem, investigate what happened and tell affected customers without undue delay, with what we know and what we are doing about it. We also notify regulators where the law requires it.
Service providers
We use established providers for parts of the service, including Stripe for payments, Plaid for bank connections and Google and Zoom for calendar and meetings. Each one only receives the data it needs to do its job.
Reporting a vulnerability
Email contact@datastreamssolutions.com with a description and steps to reproduce. We will confirm we received it within three business days and keep you updated. Please don't access other people's data, disrupt the service or share the issue publicly before it's fixed. We won't take legal action against good-faith research that follows these rules.