Protecting customer data is a top priority at Bonusly. We understand you are trusting us with your data and we take the responsibility of securing it extremely seriously.
Bonusly’s architecture is designed to be secure and reliable. We use an n-tier architecture with firewalls between each tier and additionally within certain tiers between services. Services are accessible only by other services that require access. Access keys are rotated regularly and stored separately from our code and data.
Bonusly is built with fault tolerance capability. Each of our services is fully redundant with replication and failover. Services are distributed across multiple AWS availability zones. These zones are hosted in physically separate data centers, protecting services against single data center failures.
Our application is hosted and managed within Amazon Web Services (AWS) secure data centers. These data centers have been accredited under:
We make extensive use of the capabilities and services provided by AWS to increase privacy and control network access throughout our system. Documents that provide more details about AWS security are available at AWS Whitepapers.
Bonusly 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.
The system regularly undergoes third-party security reviews and penetration testing to identify potential vulnerabilities and ensure that they are addressed.
Our servers are protected by firewalls and not directly exposed to the Internet.
Bonusly runs a zero-trust corporate network. There are no corporate resources or additional privileges from being on Bonusly’s corporate network.
Bonusly 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.
We maintain secure encrypted backups of important data for one year. We do not retroactively remove deleted data from backups as we may need to restore it, if removed accidentally. Backup data is fully expunged after one year.
We aggregate logs to secure encrypted storage. All sensitive information (including passwords, API keys, and security questions) is filtered from our server logs. Log data is fully expunged after one year.
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.
Bonusly is enabled for several secure single sign on (SSO) standards, including SAML, OpenID, and OAuth.
We monitor and rate limit authentication attempts on all accounts. Our system automatically blacklists any IP addresses responsible for suspicious authentication activity.
We provide multiple user roles with different permissions levels within the product. Roles vary from account admins to users.
All Bonusly 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. Additionally, we use only strong cipher suites.
Our primary databases, including backups are fully encrypted at rest. In addition, all archives and logs are fully encrypted at rest. We use industry standard encryption algorithms.
Bonusly has developed a comprehensive set of security policies covering a range of topics. These policies are updated frequently and shared with employees.
Bonusly has a defined protocol for responding to security events.
All employees complete security training when they join and are continually refreshed.
All employees have signed confidentiality agreements with Bonusly.
All credit card payments paid to Bonusly 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 email us at firstname.lastname@example.org and we will quickly investigate. We request that you do not publicly disclose any issue you discovered until after we have addressed it.