Data processing

Who is responsible for what

For your own account data (your email, sign-in details and settings), BuzzKit is the controller, as described in our privacy policy.

For data your page collects from your visitors, such as newsletter subscribers, contact messages, brand inquiries, poll votes and questions, you are the controller and BuzzKit is your processor. You decide why the data is collected and what is done with it. We process it only to run the features you switch on and on your instructions in the dashboard, and we don't use it for our own purposes or for ads. Our own analytics (page views and clicks, hashed visitors, no cookies) are controlled by BuzzKit and shown to you as approximate.

What we process for you

• Subscribers: email, optional name, the exact consent wording they saw, its version, the source, and when they confirmed or unsubscribed. No IP address is stored.
• Contact messages and brand inquiries: the sender's name, email, message and form answers.
• Poll votes and questions: anonymous choices and text, with a hashed visitor id to limit repeat votes.
• Approximate analytics: daily-rotating hashed visitor ids, referrer, device type and country. No raw IP address and no cookies.

Duration: until you delete the record or your account, or the retention limits shown in the dashboard apply. Deleting your account removes this data.

Our commitments as processor

• We process this data only on your documented instructions, which are your use of the dashboard and these terms.
• Everyone with access is bound by confidentiality, and access is limited to what the work needs.
• We apply the security measures described below.
• We help you answer requests from your subscribers: export your list and delete or unsubscribe a person from the dashboard.
• We tell you without undue delay, and within 48 hours of becoming aware, of a personal data breach that affects your data.
• You can export everything and delete your account at any time; on deletion we delete your audience data, except what the law requires us to keep.
• We give you the information needed to show we follow these terms, and allow reasonable audits on written request, at your cost.

Security measures

• Encrypted connections; sign-in tokens in HttpOnly cookies; codes and tokens stored hashed.
• Access to each page is limited to its owner and invited team members by role, checked on the server.
• Rate limits and input checks on every public form; bots excluded from analytics.
• The database is backed up regularly, and access to the database and storage is limited to the operator and protected by private credentials. The Redis cache holds only cached public pages and rate-limit counters, and the site works without it.

Sub-processors

We use these providers. We will update this list, and email account owners 30 days before adding or replacing one, so you can object.

• DigitalOcean: hosts our API servers, the Postgres database and the Redis cache, and runs our deployments. Stores and processes all account and audience data described above. Transfers rely on standard contractual clauses in DigitalOcean's data processing agreement.
• Cloudflare (Workers and network): serves the BuzzKit website and passes traffic to our servers. Sees the IP address and request details of everyone who visits, and adds the visitor's country to the request. Transfers rely on standard contractual clauses in Cloudflare's data processing addendum.
• Cloudflare R2: stores images you upload. Receives the image files. Transfers rely on standard contractual clauses in Cloudflare's data processing addendum.
• Resend: sends sign-in codes, subscriber confirmation and notification emails. Receives recipient emails and message content. Transfers rely on standard contractual clauses in Resend's data processing agreement.
• Google (Google Ads, through Google Publisher Tag): shows ads on public pages. Receives a visitor's IP address and, with their permission, ad cookies; we send it no account or audience data. Google acts as its own controller for ads. In some regions nothing loads from Google until the visitor allows it.
• Google Sign-In and Safe Browsing: used when you sign in with Google, and to screen links on publish. Safe Browsing receives link addresses only.

International transfers

Where personal data from the EEA, UK or Switzerland is sent to a provider outside those regions, we rely on [TRANSFER MECHANISM, e.g. standard contractual clauses or an adequacy decision]. A signed copy of these terms is available on request.

Your responsibilities

• Have a lawful basis, and a clear notice to your visitors, for the data you collect.
• Email subscribers only for what they agreed to, and honour unsubscribes.
• Keep your team and sign-in secure, and use the contact form and inquiry fields only for their stated purpose.

Liability

The liability limits and exclusions in the terms also apply to these data processing terms, to the extent the law allows. We are not responsible for a breach caused by your own failure to keep your sign-in or team access secure, or for what you do with data you export.

Contact

BuzzKit. Data protection questions and requests: support@buzzkit.app. General: support@buzzkit.app. See also the terms.