How Ozdust handles personal, financial, and tracking data.
What we collect
Ozdust stores account identifiers, workspace metadata, company profile details, uploaded files, financial inputs, analysis results, chat history, and attribution data such as UTM parameters when present.
Why we collect it
We use this data to authenticate users, persist workspaces across devices, run deterministic finance models, provide AI-assisted explanations, secure member access, and measure product and campaign performance when consent allows it.
Storage and subprocessors
Primary application data is stored in Supabase. Hosting and deployment run on Vercel. Analytics and product instrumentation may use PostHog Cloud and Vercel Analytics. Marketing attribution may use Meta, Google Ads, and LinkedIn Insight when marketing consent is granted. AI workloads may call configured providers such as OpenAI, Anthropic, Gemini, or compatible APIs.
Retention and security
Workspace data remains private to authorized members. External financial tokens are encrypted before persistence. Files are stored in private buckets and accessed through short-lived signed URLs. Operational retention follows product usage and legal requirements, and users can request deletion through support workflows.
Cookie categories
Essential cookies support auth and security. Analytics cookies support product insight and replay-style measurement. Marketing cookies support ad attribution and conversion tracking. Only essential cookies load by default; analytics and marketing require explicit consent.
Your controls
You can change cookie preferences from the consent banner when first visiting and by clearing site cookies later. Workspace owners and admins control member access. Contact Ozdust support for privacy or deletion requests tied to your account data.