Our commitment
Your audience, your events, and your content are yours. Hober's job is to be useful enough that you stay — never to make leaving expensive. This page is the written form of that commitment: what you can take with you, how, and what happens in the worst case.
What you can export yourself, today
Everything below is retrievable over Hober's documented, authenticated REST APIs — the same APIs the product itself runs on. Responses are JSON, the open format every migration tool and warehouse ingests natively.
| Data | How |
|---|---|
| Subscribers, attributes & external IDs | Subscribers API (paged listing) |
| Lists & list membership | Lists API |
| Behavioral segments (definitions) | Segments API |
| Raw behavioral event history | Events export API (server key; time-windowed, cursor-paged) |
| Message templates | Templates API |
| Journey definitions | Journeys API |
| Campaigns, schedules & reports | Campaigns and reporting APIs |
| Delivery & engagement analytics | Insights and deliverability APIs |
| Suppression list & consent state | Consent APIs |
| A single subscriber's complete records | Self-service data-request portal (access & erasure) |
Server-key (hober_srv_) authentication covers programmatic access; the
dashboard covers ad-hoc needs. Nothing requires contacting support, and
nothing about your plan or standing changes what you can export.
Formats
- JSON over REST for everything in the table above.
- Message templates export with their content intact (including Liquid personalization tags), so they can be reviewed or transformed for another system.
- We do not export in proprietary or encrypted formats.
If you close your account
Tell us and we delete your tenant's data: subscribers, events, content, and credentials. Consent and suppression records are erased or anonymized consistent with our legal retention obligations (an opt-out we are legally required to honor may be retained in suppressed-hash form). Erasure is irreversible and audited. You can export everything first — we will not rush you.
If Hober shuts down
The bus-factor question deserves a written answer, not a shrug:
- Notice. At least 90 days' written notice to every account owner before the service stops accepting sends.
- Export window. All export APIs and the dashboard remain available, read-only at minimum, for the full notice period.
- Full archive on request. During the notice period we will produce, on request and at no charge, a complete archive of your tenant's data — including raw behavioral event history — in JSON, delivered via a secure signed link.
- Deletion. After the notice period, remaining tenant data is deleted; sub-processor copies are purged per the schedules in our sub-processor list.
Known gaps we are closing
None at present. The last named gap — a self-serve bulk export for raw
behavioral event history — shipped as GET /v1/events/export (server-key
authenticated, time-windowed, cursor-paged JSON) and appears in the table
above. If a future gap opens between this page and reality, it gets named
here first.
Questions
Write to hello@hober.io. Design partners receive this policy countersigned as part of their agreement.