Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Block quote

Ordered list

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text





Updated on January 23, 2024. All policies.
Security is our highest priority. In the spirit of openness and transparency, here are some of the security measures we take to protect and defend the Bucket platform.

We protect your data #

All data is written to multiple disks instantly, backed up daily, and stored in multiple locations.

We don’t collect any PII on default #

When Bucket.js is installed in your app, the only information that’s required to be sent to Bucket is the current user’s company identifier.

On default, we don't send any user information (PII) to Bucket.

You can track user information, such as user name or user email, but it's not required, and therefore not enabled on default.

If you would like to track individual users without sending any PII to Bucket, we recommend hashing user name and/or email before sending it to Bucket.

Bucket does not collect any meta data, such as browser information or page views. You can track meta data, but you'll have to do so manually as custom attributes.

Your users’ data never leaves our servers #

We distinguish between data about you, our customer, and your users. Your information is shared with Stripe and Intercom for billing and support, but, any data about your users is never shared with any external providers, and never leaves our servers.

Encrypting data in transit #

Any data in transit between your application and Bucket is encrypted using HTTPS. We use Strict Transport Security Header (HSTS) to ensure that all requests are done via HTTPS, even if a link to Bucket is specified as HTTP. Additionally, we use HSTS preload, guaranteeing that requests are never – not even the very first – made over a non-encrypted connection. Cookies are also set with a secure flag.

Encrypting data at rest #

All data is encrypted at rest.

Hosting and backups #

Bucket is using the following infrastructure for queing and hosting data:
All data is hosted in the EU West region. All of our hosting providers are SOC2 Type 2 certified and all hosting providers perform daily backups.

Concurrency and rate limiting #

We employ several layers to protect against abuse and DoS attacks, including Heroku's DDoS Mitigation. Our servers gracefully queue requests when under high load, using Confluent Kafka, and handles them at a safe pace.

Organizational practices #

  • We operate under the principle of least privilege: Employees are assigned the lowest level of access that allows them to do their work.
  • Two-factor authentication is enforced in all sensitive systems.
  • All employees are required to use our team password manager, 1Password, to generate and store strong passwords that are never reused.
  • All employees are required to encrypt local hard drives and enable screen locking for device security.
  • All access to application admin functionalities is restricted to a small subset of Bucket staff.
  • We never store customer data on personal devices (like laptops).

Development practices #

  • All code changes are thoroughly tested through our Continuous Integration software.
  • All code changes are reviewed by team members.
  • All code changes is tested in a staging environment before deploying to production.
  • We use automatic security vulnerability detection tools to alert us when our dependencies have known security issues. We are aggressive about applying patches and deploying quickly.
  • We use services, like Datadog, to automatically monitor uptime and site availability. Key employees receive automatic email and SMS notifications in the case of downtime or emergencies.
  • Logs are permanently deleted after 15 days.

Penetration testing #

On top of our development-related continuous testing, we also conduct periodic third-party manual penetration testing of both our application and infrastructure. Customers can request a copy of our latest report at hello@bucket.co.

Regularly-updated infrastructure #

Our software infrastructure is updated regularly with the latest security patches. Our products run on a dedicated network which is locked down with firewalls and carefully monitored. While perfect security is a moving target, we work with security researchers to keep up with the state-of-the-art in web security.

We protect your billing information #

All credit card transactions are processed via Stripe using secure encryption — the same level of encryption used by leading banks. Card information is transmitted, stored, and processed securely on a PCI-Compliant network.

Have a concern? #

Have you noticed abuse, misuse, an exploit, or experienced an incident with your account? Please contact us at hello@bucket.co

Keeping customer data safe and secure is a huge responsibility and a top priority. We work hard to protect our customers from the latest threats. Your input and feedback on our security is always appreciated.

This policy have been adapted from the Basecamp open-source policies.