Privacy Policy — DRAFT, not operative

Status: placeholder pending counsel. Last updated: October 30, 2026.

This page is a draft placeholder, not an operative privacy policy. It does not create rights or obligations and must not be relied on in a customer contract. The final policy is being prepared by Diar legal and must be approved by counsel before publication.

1. Deployment models

DiarERP is offered two ways, and the privacy terms differ between them:

Managed cloud workspace at app.diarcrm.com, operated by Diar under a managed service agreement.
Self-hosted deployment for licensed customers, as a desktop application, a Python package or a Docker Compose stack on infrastructure the customer controls.

The final privacy policy must state separately, for each model, who is the controller and who is the processor, which personal data is processed, the purposes and lawful bases, retention, international transfers, subprocessors, data-subject rights, security measures and breach handling.

2. What this placeholder does not state

Those facts are not derivable from the product documentation and are not stated here. In particular, this draft does not assert:

that all data always remains on one machine or in one country;
a specific database engine, storage location or subprocessor list;
a specific AI provider or AI data-flow model;
that telemetry, analytics, cookies or similar technologies are absent;
the existence, terms or data handling of any evaluation or demo environment;
retention periods, data-residency commitments, transfer mechanisms or breach-notification windows.

Those are unresolved legal and commercial decisions. They must be supplied by Diar legal and counsel, not inferred from this page or from the code.

3. Contact and current documents

For the current executed privacy policy, data-processing agreement or a data-handling question, contact Diar through diarcrm.com/contact or info@diarcrm.com and ask for the legal team.

See also the repository legal status note at docs/legal/README.md.