Legal acceptance records help Cendaro show which user acknowledged the current Terms of Service and Privacy Policy version, language, workspace, and timestamp.
What is recorded
When a legal acceptance is captured, Cendaro stores an acceptance record for the relevant document, version, language, user, workspace when available, and acceptance time.
- Terms of Service document type: terms_of_service.
- Privacy Policy document type: privacy_policy.
- Current launch document versions use 2026-05-25.
- Language is recorded as en or fr depending on the acceptance context.
Where acceptance appears
- Signup and account creation flows can include the legal acceptance checkbox.
- Invite acceptance can require the invited user to agree to the Terms of Service and acknowledge the Privacy Policy before joining a workspace.
- Workspace creation or onboarding may also record acceptance when the flow asks for it.
What the checkbox means
The standard checkbox says: I agree to Cendaro's Terms of Service and acknowledge the Privacy Policy.
- Terms of Service links to /terms.
- Privacy Policy links to /privacy.
- The checkbox should not be pre-checked.
Existing users are not blocked
Cendaro should not block normal login only because an existing user does not yet have a historical legal acceptance record. Acceptance is captured at signup, invitation, onboarding, or another explicit acceptance step instead.
Why acceptance records matter
- They help owners and Cendaro operators understand which legal document version was acknowledged.
- They support launch readiness and compliance review without exposing passwords or customer-entered data.
- They make bilingual acceptance clearer by recording the language used at the time.
What acceptance does not do
- It does not replace customer communication consent.
- It does not create permission to send marketing messages.
- It does not change workspace roles, billing access, or team permissions.
Was this article helpful?
Your answer helps Cendaro improve launch documentation.