Where Your Data Lives

This page lists, region by region, where data handled by Buzzz is processed and stored. It supports our POPIA Notice (cross-border transfers) and our Data Processing Agreement (sub-processors).

1. Outbound email

Sent through Amazon SES in AWS region eu-north-1 (Stockholm, Sweden). Message content, recipient addresses, and delivery events pass through this region.

2. Inbound email

For customers who enable inbound receiving on a verified domain, Amazon SES accepts the mail and the raw message is stored in Amazon S3, both in AWS region eu-west-1 (Ireland). Attachments extracted from inbound mail are re-stored in our own object store (see the next section).

3. Uploaded images and stored attachments

Dashboard image uploads (template assets) and attachments extracted from inbound email are written to our own S3-compatible object store (MinIO), configured independently of the AWS regions above. This store is not a third-party sub-processor: it runs on the same Beesworx-operated infrastructure as the application.

4. Primary database and job queue

Customer, contact, campaign, and message-record data is held in a PostgreSQL database; background jobs (sending, sweeps) run through Redis, both on the same Beesworx-operated infrastructure as the application. Our deployment guide's reference environment is Hetzner Cloud in the European Union (Nuremberg, Germany); the exact host for a given deployment is set by that deployment's own configuration. Database backups run daily and are retained for 30 days on the same infrastructure.

5. SMS

Sent through BulkSMS.com and/or Twilio, depending on the customer's configuration. Message body and recipient number pass through whichever provider handles the send, and through that provider's own delivery-receipt and (for STOP/START/HELP) inbound webhook. BulkSMS is used through a South African account; Twilio is a US-headquartered global provider whose Messaging API routes a send through the region nearest its destination.

6. Error tracking

Sentry receives application errors. Request headers carrying credentials are stripped before an event leaves our servers. Browser session replay masks input field contents but not all visible page text, so a captured error session could include contact or message content that was on screen. Our configuration uses Sentry's default hosted region (United States).

7. Analytics

PostHog receives product-usage events from both the server (signup, sends, upgrades) and the browser (pageviews on the dashboard and marketing site), identified by user id, email, and name. Session recording of dashboard use is available in our configuration but off by default. Our configuration uses PostHog's US cloud host, the default when no other host is set.

8. AI features

The subject-line, rewrite, and composer assist features send only the customer's own message copy to Anthropic (never contact data or credentials), and only when the customer actively uses the feature. Our configuration sends this to Anthropic's own API by default; it can instead be routed through an internal gateway Beesworx operates on the same infrastructure as the application.

9. Billing

Plan, entitlement, and allowance data is processed through RevEx (revex.co.za), also a Beesworx product operated on the same infrastructure as Buzzz. RevEx's own payment processor is not part of this codebase; contact us for details.

10. Operational logs and traces

Our configuration supports sending application traces and metrics to an external collector for diagnosing performance issues; these can carry user identifiers. No external destination is configured by default, and none is part of our current production setup.

11. Providers you connect yourself

If you configure your own email provider (SendGrid, Brevo, Resend, MailerSend, Gmail, or a custom SMTP server), your message is sent through that provider under your own account and credentials. Its processing region is set by your agreement with that provider, not by us.