Last reviewed: To be confirmed · Controller / operator: To be confirmed before launch
1. Privacy at a glance
Accrod is intended to help customers organize lease-related records and workflows. Before this notice is published, the operator must document the actual information collected, why each category is needed, which service providers process it, where it is stored and how customers can exercise their rights.
2. Information collected
Complete this section with verified details for account and profile information, workspace and lease data, uploaded documents, support communications, billing metadata, device/log information and optional analytics. Do not say that a category is not collected until code, hosting and vendors have been reviewed.
3. Purposes and legal bases
Map each purpose—account delivery, storing customer content, sending requested reminders, support, billing, abuse prevention and product analytics—to the applicable lawful basis for each region. Separate necessary service messages from optional marketing communications.
4. Lease documents and customer content
Lease records can contain confidential or personal information. Explain who can access customer content, how support access is controlled, whether content is used for model training or automated analysis, and how permissions work. Do not imply encryption or isolation controls until verified.
5. Service providers and transfers
List actual hosting, storage, email, payment, analytics and support providers. State processing locations, international transfer mechanisms and relevant contractual safeguards where applicable. Do not include providers that are only being considered.
6. Retention, export and deletion
Document retention periods or the criteria used to determine them, backups, deletion delays, billing/legal retention and customer data export paths. Account deletion should state what is deleted, what is retained and why.
7. Privacy rights and choices
Describe applicable rights by region, how to request access/correction/export/deletion, how identity is verified and where complaints can be directed. Include a verified privacy contact and response process.
8. Cookies and analytics
Inventory actual cookies, local storage, analytics, session technologies and third-party embeds. Explain consent choices where required. Avoid calling all browser storage “essential” without review.
9. Children, changes and contact
State the intended audience, minimum age if applicable, how material notice updates are communicated, the effective date and the legal entity/contact. Verify all statements before publishing.
The final notice must match the data flows, access model, retention behaviour, hosting configuration and providers actually in production.
