Client authority
The client remains the system of record for identity, consent, bookings, payments, safety, and final user-facing records.
SmoozenExplore
Smoozen privacy overview
Data boundaries are explicit.
This Preview overview explains the intended product boundary. It is not a final privacy notice, data-processing agreement, or legal advice.
Privacy by boundary
Only the approved context should cross the line.
Privacy is expressed as a set of visible decisions about purpose, scope, authority, retention, and evidence.
Minimisation
Smoozen should receive only approved fields required for the enabled capability. Passwords, payment details, identity documents, private messages, safety notes, and unrestricted records are excluded by default.
Advisory processing
Recommendations may be incomplete or wrong. Human review and deterministic client controls are required before publication or consequential action.
Tenant separation
A client context is established by authenticated deterministic controls. Cross-client visibility is not a default product feature.
Retention and deletion
Retention, export, deletion, model-provider use, and network removal must be specified in the approved client launch profile and data schedule.
Evidence and provenance
Public or operational metrics need a source, threshold, anonymisation review, and named approval before they are presented as evidence.
Before real-data launch
Make the privacy decisions reviewable.
Each client profile should name an owner and leave an evidence trail before production enablement.
Data schedule
Name the fields, purpose, source, retention period, and approved recipients for each enabled capability.
Consent and notice
Confirm the client-owned notice, consent flow, human-review path, and escalation owner before real data is enabled.
Deletion and incidents
Document deletion requests, exports, connector removal, incident contacts, and rollback or containment steps.