Privacy notice,
written from the architecture.
This page describes privacy boundaries for Omseek Cloud / Studio from the platform privacy and consent architecture. It is not a fabricated certification page and does not invent a registered address or company number.
Scope
This notice covers Omseek software services (Cloud and Studio) and this website. Contractual data-processing terms in your order or signed commercial documents control where they apply; this page describes privacy capabilities the product actually supports.
Tenant isolation
The platform isolates data by tenant. Resource ownership is resolved and authorised server-side; cross-tenant access is denied by default. A partner relationship does not grant ownership of customer data.
Consent and purpose
Consent records may include tenant/site, subject where applicable, purpose, category, policy version, source, timestamp, status and evidence. Purposes may include necessary operation, analytics, personalisation, marketing, AI conversation retention and advertising/attribution; exact policies vary by market. Downstream use must not exceed the consent and policy under which data was collected.
Visitor identity and journeys
Identity stitching may use only disclosed, consent-compatible signals. Cross-channel journey association must retain provenance and confidence and must not imply identity certainty where only probabilistic association exists.
Data-subject requests (DSAR)
The architecture supports configurable retention, export, deletion/anonymisation, consent withdrawal and audit. Export, delete and anonymise run through platform privacy capabilities; active legal holds may skip deletion with a recorded reason. Progress and scope follow system evidence, not verbal assurances.
Residency and Studio
Studio keeps customer business content and raw evidence local by default. Cloud-assisted processing or benchmark contribution requires explicit configuration or authorisation. Cloud is multi-tenant hosted service; residency regions follow contract and deployment configuration. This page does not claim regional guarantees that are not in place.
Security measures (summary)
Encryption in transit and at rest, strong authentication and session lifecycle, tenant-aware authorisation, secrets and references, rate and abuse controls, auditable security events and protected backups are described in the security baseline as engineering controls. This page does not claim SOC 2, ISO or other certifications that are not published here.
Contact
For privacy questions and data-subject requests, use the contact page. Formal legal delivery is described under Legal notice on About Omseek.