Privacy Policy
INSARC (“we”) respects your privacy. We do not sell your personal information. This policy describes what we collect, why, and your choices.
1. What we collect
- Account data: email and identifiers from our authentication provider (e.g. Clerk) to sign you in.
- Content you submit: ideas, answers, and text you enter so we can generate architecture blueprints and prompts.
- Technical data: basic usage and error metadata to run and improve the service (e.g. hosting and analytics).
2. How we use data
- To provide INSARC (generation, history, credits, and support).
- To secure the service and prevent abuse.
- To meet legal obligations.
3. AI & model providers
To generate outputs, your content is sent encrypted in transit to AI and search providers we configure (e.g. language models and web search). Whether your inputs may be used for provider model training depends on each provider’s policies and your relationship with them; INSARC configures API usage for the service but cannot override third-party legal terms you accept when using those providers.
4. Where data is stored
Data may be processed on infrastructure we control (e.g. Vercel, Supabase) and by subprocessors necessary to run the product, including Clerk (authentication), Supabase (database), Creem (payments and subscription billing where enabled), AI providers (e.g. language models), and web search APIs used for research features. Payment card data is handled by Creem rather than stored by INSARC.
We use industry-standard safeguards; no system is 100% secure.
5. Retention
We retain data as long as your account is active and as needed for legal or operational purposes. You may request deletion where applicable; some records may be kept where the law requires.
6. Your choices
You may request access, correction, or deletion of your personal data where applicable by contacting support@insarc.dev.
7. Updates
We may update this policy. Continued use after changes means you accept the updated policy.
8. Contact
Privacy questions: support@insarc.dev