WORKING DRAFT
Privacy policy
This draft describes the current prototype. It is not a final legal policy and must be reviewed and completed by the operator and qualified counsel before launch.
Information handled
Trevoka uses account email addresses and profile details to provide account access. When you create an agreement, the service stores its title, description, terms, due date, participants’ email addresses, status and response history. Private participant links are stored as digests rather than as reusable raw tokens.
How information is used
Information is used to provide agreement creation, sharing, response tracking, account settings and subscription billing. Payment-card details are handled by Stripe Checkout and are not collected by the agreement forms.
Service providers and storage
The current implementation uses Supabase for authentication and database storage, Stripe for subscription checkout and billing, and Vercel for hosting. The operator should confirm applicable data-processing terms, storage regions, retention periods and any analytics configuration before production.
Links and responses
An agreement owner can create an expiring, recipient-specific link. Anyone with that link can view the agreement and submit one response for its intended recipient. Owners should share links privately and contact participants if a link is shared with the wrong person.
Retention and requests
A production policy should state how long accounts, agreements, audit events and billing records are retained and explain how people can access, correct or delete information. The prototype does not yet include self-service account deletion. Before launch, replace this section with a monitored privacy contact and the operator’s actual retention and rights-request process.
Contact
The operator should provide a verified privacy contact before public release.