Protecting and securing data at BlitzBear is our top priority.
BlitzBear’s architecture is designed to be secure and reliable.
We require the use of a firewall and whitelisted IP addresses, and the use of network load balancers in order to optimize the bandwidth available per each server. We regularly monitor incoming and outgoing data using Network and Graph analytics provided by third-party tools, such as Google Cloud Platform and Digital Ocean. We utilize networking tools such as Cloudflare for firewall and whitelisting utilities that prevent, minimize, and alert of network attacks.
Services are accessible only by other services that require access. Access keys are rotated regularly and stored separately from our code and data.
Our application is hosted and managed within Digital Ocean (DO) secure data centers. These data centers have been accredited under:
We make extensive use of the capabilities and services provided by DO to increase privacy and control network access throughout our system. You may view Digital Ocean Trust Certificates here.
BlitzBear uses security tools to continuously scan for vulnerabilities. Additionally, vulnerabilities in third-party libraries and tools are monitored and software is patched or updated promptly when new issues are reported.
Our servers are protected by firewalls and not directly exposed to the Internet.
BlitzBear runs a zero-trust corporate network. There are no corporate resources or additional privileges from being on BlitzBear’s corporate network.
BlitzBear data stores are accessible only by servers that require access. Access keys are stored separately from our source code repository and only available to the systems that require them. Additionally, production environments are sandboxed from testing environments.
Our servers are located in Frankfurt, Germany, unless our customer agreements specify otherwise. We utilize cloud providers like Google Cloud and Digital Ocean.
For data storage, we retain daily backups. Data is retained from 30-60 days, depending on the subprocessor. We do not retroactively remove deleted data from backups as we may need to restore it, if removed accidentally.
We aggregate logs to secure encrypted storage. All sensitive information (including passwords, API keys, and security questions) is filtered from our server logs.
We only share data with the vendors listed in the subprocessors section on the BlitzBear GDPR Portal.
Our internal GDPR and CCPA Compliance processes cover protocols for data breaches, user policies, and more.
We never store passwords in a form that can be retrieved. Instead, we store an irreversible cryptographic hash using a function specifically designed for this purpose. Authentication sessions are invalidated when users change key information and sessions automatically expire after a period of inactivity.
We monitor and rate limit authentication attempts on all accounts.
We provide multiple user roles with different permissions levels within the product. Roles vary from account owners, to admins, users, and roles that limit visibility of Personally Identifiable Information (PII).
All BlitzBear web traffic is served over HTTPS. We force HTTPS for all web resources, including our REST API, web app and public website. We also use HSTS to ensure that browsers communicate with our services using HTTPS exclusively.
We encrypt all data in transit over the HTTPS network protocol.
Certain sensitive information such as third-party API keys are encrypted at rest via SHA-256.
BlitzBear has developed a comprehensive set of security policies covering a range of topics. These policies are updated frequently and shared with employees.
Topics include, but are not limited to, general internal protocols, password and security/network policies for BlitzBear employees, including handling sensitive customer data.
BlitzBear has a defined protocol for responding to security events.
All employees complete security training when they join and are continually refreshed.
BlitzBear performs background checks on all new employees in accordance with local laws. The background check includes employment verification and criminal checks for all employees.
All employees have signed confidentiality agreement with BlitzBear.
All credit card payments paid to BlitzBear go through our payment processing partner, Stripe. Details about their security posture and PCI compliance can be found at Stripe’s Security page.
If you have any concerns or discover a security issue, please contact us directly. Our Security team will acknowledge receipt of each vulnerability report, conduct a thorough investigation, and then take appropriate action for resolution. We request that you do not publicly disclose any issue you discovered until after we have addressed it.
|Business continuity process
Our internal Business Continuity Process (BCP) outlines protocols in the event of a disruption to normal operations.
|Disaster recovery process
Our internal Disaster Recovery Process (DRP) outlines protocols to restore data in the event of disasters.
|Security questionnaire request policy
Please note, BlitzBear only accomodates security questionnaire requests, modified DPA requests, or any other legal/vendor requirements for customers on custom Enterprise plans. If you have bespoke legal and compliance needs, please get in touch with sales.