Last Updated: September 30, 2020
We take the security of your data very seriously at Buildster. As transparency is one of the principles on which our company is built, we aim to be as clear and open as we can about the way we handle security.
If you have additional questions regarding security, we are happy to answer them. Please write to email@example.com and we will respond as quickly as we can.
We place strict controls over our employees’ access to the data you and your users make available via the Buildster services, as more specifically defined in your agreement with Buildster covering the use of the Buildster services (“Customer Data“), and are committed to ensuring that Customer Data is not seen by anyone who should not have access to it. The operation of the Buildster services requires that some employees have access to the systems which store and process Customer Data. For example, in order to diagnose a problem you are having with the Buildster services, we may need to access your Customer Data. These employees are prohibited from using these permissions to view Customer Data unless it is necessary to do so.
All of our employees and contract personnel are bound to our policies regarding Customer Data and we treat these issues as matters of the highest importance within our company.
Deletion of Customer Data
Buildster provides the option for Customers to delete Customer Data at any time subject to the other terms and conditions agreed to by the Customer. If we receive instructions from a Customer to delete the Customer Data associated with its account in relation to a project workspace, this may not result in the deletion of such Customer’s Customer Data that is available in another Customer’s or Authorized User’s account in relation to a particular project workspace. Within 72 hours of an approved Customer initiated deletion, Buildster hard deletes all information from currently-running production systems (excluding names, information connected to the accounts of other Customer’s and Authorized User’s and search terms embedded in URLs in web server access logs). Where appropriate, Buildster will de-personalize data of Customers and Authorized User’s where deletion will impact other Customer’s and Authorized User’s project workspace. Buildster services backups are destroyed within 30 days.
Return of Customer Data
Information about the export capabilities of the Buildster services can be found at our FAQ.
Data Encryption In Transit and at Rest
The Buildster services support recommended secure cipher suites and protocols to encrypt all traffic in transit. Passwords and other sensitive data, as determined by Buildster, is encrypted while at rest. Buildster does not store credit card info.
We monitor the changing cryptographic landscape closely and work promptly to upgrade the service to respond to identified weaknesses as they are discovered and implement best practices as they evolve. For encryption in transit, we do this while also balancing the need for compatibility for older clients.
We understand that you rely on the Buildster services to work. We’re committed to making Buildster a highly-available service that you can count on. Our infrastructure runs on systems that are fault tolerant, for failures of individual servers or even entire data centres. Our operations team tests disaster-recovery measures regularly and intends to act quickly resolve unexpected incidents.
Customer Data may be stored at multiple locations in our hosting provider’s data centres to ensure availability. We have established backup and restoration procedures, which allow recovery from a major disaster. Customer Data and our source code are automatically backed up. The Operations team is alerted in case of a failure with this system. Backups are fully tested at least every 180 days to confirm that our processes and tools work as expected.
Firewalls are configured according to industry best practices and unnecessary ports are blocked by configuration with AWS Security Groups.
We perform automated vulnerability scans on our production hosts and remediate any findings that present a risk to our environment. We enforce screens lockouts and endorse the usage of full disk encryption for company laptops, where applicable.
Buildster maintains an extensive, centralized logging environment in its production environment which contains information pertaining to security, monitoring, availability, access, and other metrics about the Buildster services. These logs are analysed for security events via automated monitoring software, overseen by the security team.
Incident Management & Response
In the event of a security breach, Buildster will promptly notify you of any unauthorized access to your Customer Data.
Product Security Practices
New features, functionality, and design changes go through a security review process facilitated by the security team. In addition, our code is audited with automated static analysis software, tested, and manually peer-reviewed prior to being deployed to production. The security team works closely with development teams to resolve any additional security concerns that may arise during development.
If you believe you have found a security vulnerability on Buildster, please let us know right away. We will investigate all reports and do our best to quickly fix valid issues. You can submit your report on firstname.lastname@example.org and our security team will respond as soon as possible.