Skip to content

ADR 0006: Hub as lead and consent backend

  • Status: Accepted
  • Date: 2026-09-11

Context

The shops exist to win Keferboeck Ltd clients: their newsletter signups are Keferboeck leads and must carry provable GDPR consent. Five separate consent stores would fragment evidence and double opt-in behaviour.

Decision

Shops keep no marketing contacts. Signups post to the portal's API (hub.keferboeck.com/api/marketing_contacts) authenticated by a per-store API key (X-Store-Key); the portal owns the contact, the append-only consent ledger, double opt-in and the preference centre. Transactional shop email (orders, shipping) stays in the shop, sent via Mailjet under the shop's sender identity.

Consequences

One consent truth, per-store attribution, and demo shoppers are never emailed marketing by accident. Shops depend on the hub being up for signups, an accepted coupling for a lead-capture feature.