Terms and support
Links to the legal documents, how the write path behaves when a write cannot land, what retention and webhook delivery do, and how to reach support and sales.
Your agreement governs. This page points to the legal documents and says how the service behaves where your integration meets it.
Legal documents
| Document | URL |
|---|---|
| Terms of Service | https://pacspace.io/terms |
| Privacy Policy | https://pacspace.io/privacy |
Availability
The write path fails safe. A write that PacSpace cannot commit as sent is refused with a code and a sentence, or reported as failed at your webhook and in the history; nothing weaker is written in its place. Recording need not sit in your agent's way: the agent does its work, records afterward, and a write that did not land is sent again with the same idempotency key. See Safety and idempotency.
PacSpace publishes no uptime commitment on this site. Any service commitment is the one your agreement sets.
Data retention
Nothing in a record is removed by a retention setting: every entry as you wrote it, every seal, and when each was committed are kept. A retention window, off by default, removes the payloads of finished webhook deliveries once they are that old. See Data retention.
Webhook delivery
A delivery that does not get a 2xx within ten seconds is tried again on a growing schedule until 72 hours have passed. After that it is marked failed, and you can retry it from the dashboard. See Webhooks.
Support and sales
| Channel | Details |
|---|---|
| Support | support@pacspace.io |
| Sales, including Enterprise plans | sales@pacspace.io |
| Dashboard | app.pacspace.io |