We take the security of your data seriously. Browse AI engineering team has years of experience developing web-based software for Canadian banks. We've leveraged bank-level encryption and access management to ensure data privacy and security.
Below are some highlights:
- We use Auth0 to authenticate users and store their Browse AI account credentials. We don't store any Browse AI account credentials on our infrastructure.
- We use AWS US datacenters for our services and databases.
- We use TLS 1.2 wherever possible (both via Browse AI and external API services). You can find more details here.
- Any passwords entered during recordings are encrypted with AES-256 and stored in a database. Of course, Browse AI has the decryption keys on hand so it can use the credentials when running tasks but they are stored and maintained separately and behind multiple layers of protection. The keys are technically only accessible to the CTO and the DevOps lead, who have never tried to access the keys so far.
- Encrypted task variables are only decrypted on the server when running a task. You and your team members who have access to the task can never access the decrypted input on the dashboard or through the API.
- Datadog is used for monitoring the application and storing its logs for up to 30 days for troubleshooting purposes. We make sure no sensitive information, such as encrypted inputs, are ever logged.
- Browse AI support team have access to your tasks in case you ask them for help. We monitor our staff's activities to make sure they only access a task when the task owner has authorized them to do so. In the future, we plan to create an "temporary access key" system so you can grant temporary access to a single task when you need support.
- The support team can never access your encrypted inputs, such as recorded passwords.
If you have any questions on how Browse AI stores or handles your information, please contact us.