LEGAL CENTER

Privacy Legal Documents Hub

Use this legal hub to access full privacy-related policies and agreements for Zmirf services.

Last updated: March 18, 2026

Privacy Policy

  • We process account, billing, technical, and support data to deliver and secure services.
  • Legal bases include contract, legitimate interests, legal obligations, and consent where required.
  • Data subject rights include access, correction, deletion, restriction, objection, and portability where applicable.
  • Cross-border processing uses contractual safeguards where required by law.
Read more (full Privacy Policy)

Cookie Policy

  • Essential cookies support authentication, security, and platform continuity.
  • Non-essential cookies are used only where consent or lawful basis exists.
  • Users can manage cookies from browser controls and supported preference tools.
  • Disabling essential cookies may reduce functionality in authenticated areas.
Read more (full Cookie Policy)

Privacy Notice for Suppliers

  • Supplier representative data is processed for onboarding, contracting, payment, and compliance.
  • Processing includes identity, business contact, and due diligence records.
  • Retention follows legal, accounting, and audit obligations.
  • Supplier representatives may exercise privacy rights subject to lawful verification.
Read more (full Supplier Privacy Notice)

Data Processing Agreement

  • Customer acts as controller and Zmirf acts as processor for covered processing activities.
  • Processing occurs only under documented instructions and legal obligations.
  • Subprocessors are engaged under contract and data transfer safeguards.
  • Deletion/return commitments apply at service end, subject to retention requirements.
Read more (full Data Processing Agreement)

How to navigate privacy documents by use case

Different privacy documents serve different operational purposes. The main Privacy Policy explains platform-wide data handling, the Cookie Policy covers tracking and session behavior, the Supplier Notice addresses procurement relationships, and the DPA defines controller-processor obligations for customer workloads.

Teams responsible for product, legal, and operations should review the relevant document before launch or integration changes. This helps align account workflows, support procedures, and third-party services with documented privacy commitments and compliance expectations.

  • Use the Privacy Policy for customer-facing disclosures.
  • Use the DPA for controller and processor responsibilities.
  • Use supplier notice terms for procurement data handling.
  • Use cookie terms for consent and session behavior guidance.