We may process account details, workspace details, usage events, audit data, outreach content and support-related communication needed to operate the platform.

This can include names, email addresses, organization information, website URLs, audit results, CRM records and operational metadata.

We use data to authenticate users, run audits, manage permissions, support shared delivery workflows, enforce quotas and improve product reliability.

We may also use aggregated product telemetry to monitor platform health, abuse, usage patterns and service quality.

We do not position OBRIYM as a data brokerage product. Data sharing should be limited to infrastructure, analytics, email and support providers needed to run the service.

If external tools are used for search, email or infrastructure, they should be covered by separate vendor agreements and privacy terms.

Retention behavior may vary by plan, governance rules and support workflows. Platform operators may also enforce visibility windows and operational limits at the workspace level.

Users should be able to request updates or deletion according to the final production privacy process you define.