Privacy policy

Crow stores account identifiers needed for authentication, role-aware access, operator audit events, approval and execution workflow records, journal entries, runtime settings, and market-analysis outputs generated by the product.

Secrets such as bootstrap passwords, API credentials, and provider keys are expected to remain environment-managed rather than embedded inside the UI or exported documentation.

Data is used to authenticate users, render the current workspace, preserve decision history, investigate incidents, and keep the product trustworthy during degraded conditions.

Crow does not present itself as a consumer social network or ad-targeting platform. Operational telemetry exists to support product reliability, security, and accountable workflow follow-through.

Append-heavy tables such as backend audit events, approvals, execution history, and journals are controlled through explicit retention settings. Operators should use the documented runtime maintenance path when pruning is required.

Deletion or export requests should be handled through the documented operational process so the team can confirm scope, environment, and any regulatory or incident-retention exceptions before acting.

Requests involving access, correction, export, deletion, or consent posture should be reviewed by the product and operations owners recorded for the environment. Crow's internal handling note is the source of truth for how to verify the request and where to collect evidence.

Where GDPR, CCPA, or similar requirements apply, Crow should respond through that documented workflow rather than through ad hoc direct database edits.