Trust

What Beacon does to protect your data and your subscribers, described as it works today. Each point below is something the product does, not a promise about something we hope to do.

Protecting stored data

How secrets and keys are kept at rest.

  • Stored credentials are encrypted

    Credentials the platform has to read back later, such as mail provider keys, SMTP passwords and connected app secrets, are encrypted with AES-256-GCM before they are written to the database. The key is derived from a secret held in the server environment, not in the database.

  • DKIM signing keys are encrypted

    When you add a sending domain, the private DKIM key is generated by the platform and stored encrypted. Only the public half is ever shown or published in DNS.

  • API keys are stored as hashes

    An API key is shown to you once, when it is created. We keep only a one-way hash, so we cannot recover or display it later. If you lose a key, you create a new one.

Accounts and access

How sign-in, sessions and tenant separation work.

  • Repeated failed sign-ins are slowed down

    Failed sign-ins lock the account for progressively longer periods, and sign-in attempts are rate limited per IP address. The thresholds come from a policy an administrator can change.

  • Session cookies are locked down

    Session cookies are HttpOnly, so page scripts cannot read them, use SameSite=Lax, and are marked Secure on production deployments.

  • Every request is checked against your organisation

    Server procedures that touch organisation data first check that the signed-in person is a member of that organisation and has the authority the action needs. The organisation comes from the verified membership, never from a value the browser supplies.

  • Subscriber details can be hidden by role

    Team members without the permission to view personal data receive masked email addresses and names from the server itself. The values are not sent to the browser and hidden there.

  • Connected tools use OAuth with PKCE

    Tools that connect to your account through the OAuth flow must use PKCE with the S256 method. Public clients receive no client secret, and the PKCE check is done in constant time.

Sending and recipients

How the links and headers in your emails behave.

  • One-click unsubscribe on marketing email

    Marketing email carries the List-Unsubscribe and List-Unsubscribe-Post headers (RFC 8058), and the unsubscribe endpoint accepts the one-click POST that mailbox providers send.

  • Suppressed recipients are not emailed

    A recipient on the suppression list, for example after a hard bounce or a complaint, is excluded when a campaign is prepared for sending. The skipped message is recorded so reports still add up.

Privacy controls

What you and your visitors can see and control.

  • Our sub-processors are listed

    The services that may handle customer data on our behalf are listed on a public page, with what each is used for. When we change the list we publish a dated notice on that page and in a feed. We do not email a notice.

Operations

What we tell you about the platform itself.

  • A public status page with honest limits

    The status page shows the web app, database, queue, sending engine and send pipeline, plus incidents we have recorded. The checks run from inside the platform, so they show what the platform can see about itself. They are not an independent monitor.

What this page does not say

  • We do not hold any security or privacy certification, and we do not publish an audit report.
  • We have not published the result of an independent penetration test.
  • We make no uptime guarantee on this page.
  • We make no statement here about where data is stored.

See also the privacy policy, the sub-processors and the live status page.