Privacy Policy
Last updated: February 18, 2026
How we process data
Intara is designed so dataset rows stay in your browser for CSV workflows. We process schema metadata, your prompts, generated SQL, and usage events on our servers to operate and improve the service.
Data we collect
- Account information from Clerk (email, name, user identifier).
- Dataset metadata (name, schema, row count, size, source type).
- Conversation and message history (questions, SQL, summaries, feedback).
- Product telemetry (performance, errors, and feature usage).
- Billing metadata from Stripe (customer/subscription identifiers).
Legal basis (GDPR)
We process personal data based on contract performance (providing the service), legitimate interests (security, reliability, analytics), and legal obligations (tax and fraud prevention).
Your rights
Depending on your jurisdiction, you can request access, correction, deletion, portability, restriction, or objection to processing. You can also delete your account in Settings, which removes your application data and account identity from our systems.
CCPA notice
We do not sell personal information as defined by CCPA/CPRA. We also do not share personal information for cross-context behavioral advertising. California residents may still submit access/deletion requests through support.
Do Not Sell or Share My Personal Information: not applicable based on our current data practices.
Subprocessors
- Vercel (hosting)
- Clerk (authentication)
- Anthropic (LLM processing)
- OpenAI (LLM + embeddings)
- Stripe (billing)
- Sentry (error monitoring)
- PostHog (product analytics)
- Upstash Redis (cache and rate limiting)
- Pinecone (semantic cache index)
Retention policy
- Conversation queries: retained until user deletion.
- Cache entries: up to 24 hours for response acceleration.
- Soft-deleted records: up to 30 days before permanent removal.
- Operational logs: up to 90 days for reliability and security.
Contact
For privacy requests, contact support through the product support channel. Include your account email and request type (access, delete, correction, portability, or objection).