contact
policy_unavailable
No approved legal policy configuration is active for this deployment. Until one is active, no approved operator contact is shown here — only the operational channel below and the in-app destinations.
sonder is an independent project. While the approved contact configuration is unavailable, the operational channel is jb@baek.io.
Email is a separate channel: it opens your own mail program and keeps its thread outside the app, so a case reference from one of the surfaces below is the quickest way to follow up.
working destinations
These are the app's own case surfaces, and each one keeps what you submit with a persistent case reference, status and history — signed in, they are the record of what was asked and what happened.
- Support cases — product, purchase and access questions; no workspace needed, so buyers can use it too.
- Account, rights requests and closure — verified access, export, correction, erasure and restriction requests, plus email changes and closure review; no workspace needed.
- Restriction notices and appeals — a workspace's restriction case reference and its staged-restoration state, for that workspace's members; its owner or an admin can appeal.
Many questions are answered by the surface that owns them. Each of these shows its own current state rather than a case history:
- Your library — purchases, memberships, courses and bookings with their own next actions; open an order there and choose “Get support” to link a case to it.
- Team — members, roles, invitations with their delivery and acceptance state, and ownership transfer.
- Domain — your platform address and any custom host's ownership, routing and TLS state.
- Exports and Imports — portable packages with their manifest, omissions and request history; see the FAQ on leaving sonder for what a package does and does not carry.
- Service status — notices an operator has reviewed and published. It makes no uptime or response-time promise, and says so when it cannot load.
what to include
A useful note includes the email on the account, the creator page or offer, an order or booking reference if you have one, and a clear description of what you need. Screenshots or links can help. Never include a password or full payment-card number.
policy questions
You can read the terms, privacy policy, and refund policy before writing. Each shows its approved version, effective date and approval reference — the terms and refund pages list every retained approved version at its own permanent address — or an explicit policy_unavailable state, never a substitute text.
terms · privacy · refund policy · faq · service status