Privacy Policy

[COMPLETE BEFORE LAUNCH: identify the responsible legal entity, its address, the services and users covered, and the approved privacy contact.]

Confirm and describe the categories actually collected: account and workspace details, invited-member details, billing references, uploaded content, screen and device identifiers, operational logs, support communications, and product analytics or cookies.

For each category, document whether it comes from the user, their organization, a connected service, or automatic service operation.

Describe uses such as providing and securing the service, processing requested transactions, delivering support, communicating service changes, preventing abuse, and improving reliability.

[LEGAL REVIEW REQUIRED: state the valid legal basis for each purpose in every region where the service is offered.]

[COMPLETE BEFORE LAUNCH: list verified hosting, database, authentication, email, storage, billing, monitoring, and analytics sub-processors; the data each receives; its purpose; and relevant processing locations.]

Explain disclosures to workspace administrators, service providers, authorities when legally required, and parties to an approved corporate transaction.

[LEGAL REVIEW REQUIRED: identify actual transfer routes and the approved transfer safeguards. Do not publish this section until hosting and sub-processor locations are verified.]

[COMPLETE BEFORE LAUNCH: provide verified retention periods or criteria for accounts, workspace content, backups, security logs, billing records, support records, and analytics data.]

Describe approved administrative, technical, and organizational safeguards at an appropriate level without promising controls or certifications that have not been independently verified.

Explain how a person may request access, correction, portability where applicable, restriction, objection, consent withdrawal, or deletion. Clarify when a workspace administrator must handle a request and how identity will be verified.

Start a request through the contact page. [LEGAL REVIEW REQUIRED: add statutory timelines, exceptions, appeal rights, and regulator details for supported jurisdictions.]

[COMPLETE BEFORE LAUNCH: inventory cookies, local storage, analytics, and similar technologies; classify each one; document duration; and add any required consent or opt-out controls.]

[LEGAL REVIEW REQUIRED: define the service’s age policy and any regional child-privacy rules.]

Describe how material policy changes will be communicated and add the approved privacy and data-protection contact details.