Privacy Policy
Last updated: August 2026 · Applies to all DruxAI products
1. Who we are
DruxAI ("DRUX", "we", "us") operates the drux.space platform and all associated products: Chat by Drux, Village, Communiti, Vizible, DruxDocs, RoundTable, and Chorus. This policy explains what data we collect, how we use it, and your rights.
2. What we collect — all products
When you create an account, we collect your email address and name via Clerk, our authentication provider. We collect usage data (feature interactions, error logs) for product improvement. We use Vercel Analytics for anonymous, aggregate traffic statistics — no personal identifiers are tracked in analytics.
3. Chat by Drux
When you run a search, we store your query text and the AI responses linked to your account to display your search history. Search history is visible only to you. Your queries are transmitted to third-party AI model providers (via OpenRouter) solely to generate responses.
4. Village — conversation data
Village stores: your village configuration (villager names, archetypes, custom roles, avatar settings); the contextual profile you provide (age range, gender, country, city — all optional); and your full conversation history per villager. Conversation data is stored in our Supabase database, associated with your user ID, and is never shared with or sold to third parties. Villager conversations are transmitted to third-party AI model providers to generate responses — only the message content is transmitted, not your profile data. You can request deletion of all Village data by contacting support@drux.space.
5. Communiti — persona and survey data
Communiti stores: persona configurations you create or import; population definitions; survey prompts and AI-generated synthetic responses. All persona response data is synthetic — it is generated by AI models and does not correspond to real individuals. If you upload or describe real research context in survey prompts, treat that content as you would any data submitted to an AI system. We do not use your research prompts to train our own models.
6. Vizible — tracking data
Vizible stores: brand or topic groups you create; prompts used for visibility runs; run results and AI response samples. Run results include sampled AI model outputs. This data is linked to your account and visible only to you and, where applicable, your organisation.
7. Vizible Ads — Google Ads & Google Analytics (GA4) connections
If you connect your own Google Ads account and/or Google Analytics (GA4) property to Vizible Ads, here is exactly what we access, how we use it, and how it's protected: Data accessed: with your explicit OAuth consent, we access your Google Ads account list, campaign data (names, budgets, status, performance), and — separately — your GA4 property list and site traffic/attribution data (sessions, referral source, conversions). We only request the minimum scopes needed for these features (Google Ads: 'adwords'; Google Analytics: 'analytics.readonly' — read-only, we never modify your Analytics data). How it's used: this data is shown back to you in your Vizible dashboard, and — for Google Ads only — is used by an AI marketing agent to draft campaign suggestions (headlines, budget, targeting) that YOU review and must explicitly approve before anything is created in your real Google Ads account. Nothing is created, changed, or launched in your Google account without that explicit approval step. Who it's shared with: this data is transmitted to third-party AI model providers (via OpenRouter, e.g. Anthropic, OpenAI) solely to generate the campaign drafts and analysis described above. It is not sold, rented, or shared with data brokers, advertisers, or any party for advertising/marketing purposes of our own. It is not used to train any AI/ML model — ours or any third party's. How it's protected: OAuth access/refresh tokens are encrypted at rest (AES-256-GCM) and are never exposed to your browser or any other user. Every request is scoped server-side to your own account only. Retention & deletion: you can disconnect your Google Ads or GA4 connection at any time from Vizible Settings, which immediately revokes and deletes the stored token. Historical campaign/attribution data already shown in your dashboard is retained until you delete the subject or close your account, per the retention terms in section 12.
8. DruxDocs — document data
DruxDocs stores: documents you create or upload for processing; job configurations and pipeline outputs. Uploaded files are processed by AI models to generate outputs. Processed outputs are stored linked to your account. We do not use your documents to train models. You can delete jobs and associated files from within the product.
9. RoundTable — question and answer data
RoundTable stores: questions you submit; answers you write; voting and reaction activity. Questions and answers you post are visible to other users of the platform. AI-generated answers are produced by third-party models and attributed clearly. Do not include sensitive personal information in publicly-posted questions.
10. Teecha — YouTube API Services
Teecha uses YouTube API Services to search for and display educational video content. By using Teecha, you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms). Data collected: Teecha uses the YouTube Data API to search for videos and retrieve video metadata (titles, thumbnails, durations, view counts). We do not access your YouTube account, watch history, or any personal YouTube data. No YouTube user data is collected, stored, or shared. How YouTube data is used: video metadata retrieved from the YouTube API is used solely to curate learning paths and display video information within the Teecha product. Videos are embedded using YouTube's official embedded player — we do not download, re-host, or modify any YouTube content. Data storage and deletion: YouTube video metadata (titles, IDs, thumbnails) is stored as part of your curated learning paths. You can delete any learning path from your library at any time, which removes all associated YouTube metadata. Deleting your account removes all stored data within 30 days. Revoking access: since Teecha does not access your personal YouTube/Google account, there is no OAuth token to revoke. However, you can review and manage apps connected to your Google Account at https://myaccount.google.com/permissions. Google Privacy Policy: our use of YouTube API Services is also subject to the Google Privacy Policy (https://policies.google.com/privacy).
11. Third-party services
We use: Clerk for authentication (see clerk.com/privacy); Stripe for payment processing (see stripe.com/privacy); Supabase for database hosting; Vercel for infrastructure; OpenRouter as an AI model gateway; and YouTube API Services for video search and metadata. Your queries and content are routed through OpenRouter to model providers per their respective terms. We do not control and are not responsible for third-party data practices.
12. How we use your data
We use your data to: deliver and operate our products; display your history and configurations; send transactional emails (billing receipts, critical security notices); improve our products in aggregate and anonymised form. We do not sell your personal data. We do not use your content to train AI models.
13. Data retention
Account data is retained while your account is active. Search history, Village conversations, Vizible runs, and DruxDocs jobs are retained until you delete them or close your account. Deleting your account removes all personally-identifiable data within 30 days. Some anonymised aggregate data may be retained for analytics purposes.
14. Cookies
We use essential session cookies via Clerk for authentication. We do not use advertising cookies, tracking cookies, or third-party analytics cookies that identify you personally.
15. Your rights
Depending on your jurisdiction, you may have the right to access, correct, or delete your personal data; withdraw consent; or lodge a complaint with a supervisory authority. To exercise these rights, email support@drux.space. We will respond within 30 days.
16. Children
Our products are not directed at children under 18. We do not knowingly collect data from anyone under 18. If you believe a child has provided us data, contact support@drux.space and we will delete it promptly.
17. Changes to this policy
We may update this policy at any time. Material changes will be notified by email or prominent in-app notice. The current version is always available at drux.space/privacy.
18. Contact
For privacy questions or data requests, email support@drux.space.