Terms, privacy, and processing

DRAFT · NOT AN AGREEMENT OR PRIVACY NOTICE

Who we are

The contracting entity, registered details, governing law, responsible contacts, and controller identity require owner and legal confirmation. This page does not establish them.

What must be defined

Why we process it

Lawful bases, contractual purposes, legal obligations, enquiry handling, security processing, and any model-use restriction require explicit approval in the final notice.

No analytics SDK or advertising tracker is included in this public build. Any future measurement requires a separate privacy and consent decision.

Controller and processor

Controller and processor roles, documented instructions, security measures, deletion, export, and assistance obligations require signed terms. No role or processing promise is created by this page.

Subprocessors

Provider identities, processing locations, transfer mechanisms, contractual safeguards, and change notices require a verified subprocessor register before publication.

Carrier and sales-channel relationships must be classified from the actual integration and contract; this draft does not assign their legal role.

Retention

Retention periods, deletion events, export scope, backup treatment, and post-contract access require an approved schedule. No period or export guarantee is published here.

Your rights

The approved notice will identify applicable rights, the verified request route, identity checks, response handling, and the relevant supervisory authority.

Contact

Use the contact page for a general enquiry. Privacy and security inbox ownership, delivery testing, and response targets must be verified before they are published.

This is a publication-status notice, not legal advice, terms of service, a privacy notice, a data processing addendum, or evidence that any policy is operational.