Privacy policy
How Clerisi handles account, event, billing, submission, analytics, archive, and access-related personal data.
1. Overview
This page describes Clerisi’s intended data-handling practices. The published legal policy should be reviewed and maintained by qualified legal counsel.
Design intent: Clerisi should collect the data required to run events, accounts, access, payments, resources, archive features, feedback, and editorial operations — not unnecessary surveillance data.
2. Information Clerisi may collect
- Account information such as name, email, credentials, role, and preferences.
- Event information such as registrations, access status, attendance records, questions, votes, or participation data where enabled.
- Billing and entitlement data such as plan, purchase, invoice, subscription, and access records.
- Saved-item and usage data such as saved articles, resources, clips, topics, and archive interactions.
- Submitted content such as ideas, claims, applications, inquiries, feedback, and messages.
- Technical data such as device, browser, log, cookie, and security information.
3. How information may be used
Access
To provide accounts, registrations, replays, resources, archive entries, and paid entitlements.
Operations
To run events, send reminders, manage payments, support users, and maintain security.
Editorial
To process submissions, moderate participation, prepare approved editorial records, and connect published outputs to the archive.
Improvement
To understand which formats, topics, and resources are useful and where the product needs improvement.
5. Public event record
Clerisi sessions may produce public or protected records such as recordings, transcripts, articles, clips, resources, claim pages, or archive entries. Speakers and participants should be informed when contributions may become part of a published or member-accessible record.
6. User rights
Users should be able to request access, correction, deletion, export, or restriction of their personal data where applicable law grants those rights.
7. Security and retention
Clerisi should use role-based access, protected delivery for gated files, administrative safeguards, and retention rules appropriate to the sensitivity of the data.
8. Contact
Privacy inquiries should be directed through the Clerisi contact page until a dedicated privacy contact address is configured.