How Maqetin guards the data you send it.
You hand us the record of what your customers do. This page covers who can see it and what happens when someone asks for it back.
Consent is checked before every send.
Every profile keeps a marketing-email flag. Your app sets it when it identifies the person, and an unsubscribe, a complaint or a hard bounce turns it off. Marketing is never sent to a profile marked no.
- Marketing and transactional are separate. A code or a receipt still reaches a profile marked no for offers. An address that unsubscribed, complained or hard-bounced gets no mail at all.
- One-click unsubscribe on every marketing email, honoured across your workspace.
- Email, marketing
- Yes
- Transactional
- Always sentcodes, receipts, alerts
Rights requests in one action.
When a customer asks for their data or asks to be forgotten, run the request from the dashboard or the API.
- Export
- One person's profile, events and messages, as JSON
- Delete
- Profile, events and message records removed, and their journeys ended
- Backups
- Deleted data ages out of backups within 35 days
This removes her profile, 388 events and 9 message records from every store, and ends her 2 journey enrollments. Copies in backups age out within 35 days.
Workspaces are kept apart, and staff access is logged.
Every query is scoped to one workspace, and a test suite that tries to read across workspaces runs on every release.
- Staff access needs a reason, shows a banner the whole time, and is written to the audit log.
- API keys scoped to what each service needs.
- Secret keys are shown once, at creation, and never again.
| When | Who | What |
|---|---|---|
| 14:10:02 BST | Alex (Maqetin support) | Started viewing the workspace · reason recorded |
| 14:22:40 BST | Alex (Maqetin support) | Stopped viewing the workspace |
How the platform is run.
None of this shows in the dashboard.
Mail servers we operate
Email goes through infrastructure Maqetin runs, signed for your domain.
Backups
Databases are backed up every day.
Secrets kept out of code
Credentials live in a secrets manager and are loaded at start-up, never in code or images.
Questions from your compliance team.
Send them over. We'll answer in writing, and share our data processing agreement.