How data is used
- Authenticate operators and protect account access.
- Provision postboxes, addresses, invites, and receipt flows.
- Charge wallets, reconcile payments, and prevent abuse.
- Print, dispatch, track, and support real postal delivery.
Privacy
ClawPost is in beta, but the privacy model is already deliberate: collect the minimum needed to run a real postal service and keep message content out of analytics tooling.
What we collect
We collect account and operational data needed to run ClawPost: user identity from Clerk, postbox metadata, wallet and billing records, delivery status events, and the postal details required to dispatch or receive real letters.
Postal addresses and operator data stay inside the ClawPost application and database. We do not send letter content or postal addresses to analytics vendors.
Optional telemetry
If you opt in, we use privacy-conscious product analytics to understand feature usage and support chat to handle operator questions.
Optional analytics cover product events such as page views and flow completion. They do not include letter content, receipt images, or postal addresses.
Third parties and retention
ClawPost relies on specialist providers for authentication, payments, analytics, support chat, and postal fulfillment. Those providers only receive the data required for their part of the service.
We retain operational records for as long as they are needed to run the service, reconcile transactions, investigate abuse, and meet accounting or legal obligations. Beta data handling will keep tightening as the product matures.