Privacy
Policy.
Your privacy is central to Claron. This Privacy Policy details how we collect, process, and secure your account and visual bug tracking data.
1.1 Information You Provide Directly
- Account Registration: Full name, email address, password, profile info, organization/workspace details, phone number (optional), and payment tokens (processed securely via Razorpay).
- Integration Credentials: OAuth tokens (GitHub, Google, etc.), API keys for third-party services (Linear, Jira, Trello, Slack, etc.), and connection settings.
- Project and Source Code Data: GitHub repository URLs, branches, build configurations, cached artifacts, and environment variables (encrypted at rest using AES-256).
- Annotation and Feedback Data: Text comments, bug descriptions, screenshots, computed CSS styles, DOM selectors, and collaborative metadata.
1.2 Information Processed by Our Service
- Source Code Processing: We clone connected repositories into isolated temporary build sandboxes to extract source maps and resolve paths. Source code is never used to train AI models.
- Build Environment Data: Build logs, compilation output, and framework caching data (.next/cache, .vite/cache, etc.).
- Annotation Metadata: Viewport dimensions, console/warning logs, network header request details (sanitized), and JavaScript stack traces.
- Session and Event Data: Mouse clicks, scroll positions, and real-time cursor events recorded in review sessions.
1.3 Automatically Collected Information
- Usage Analytics: Dashboard views, feature interactions, and build trigger frequency.
- Device and System Info: IP address, geolocation (city/country level), user agent, and browser version.
- Cookies: Session cookies for authentication and CSRF protection, and preference settings.
2.1 Service Delivery & AI Automation
We use your information strictly to provide, maintain, improve, and secure the Claron Service. Specifically:
- To clone, build, and host frontend previews for review.
- To compile annotations, comments, and bug tickets.
- To execute AI-powered code analysis through contracted AI services under zero-retention Enterprise API agreements — your code is never used for training models.
- To synchronize annotations with your third-party integrations (Linear, Jira, Slack, etc.).
2.2 Communications & Analytics
- Delivering system notices, billing alerts, and customer support.
- Analyzing usage patterns to identify infrastructure bugs or performance bottlenecks.
- Enforcing our Terms of Service and preventing platform abuse.
Under GDPR, CCPA, and applicable laws, we process data based on the following grounds:
- Contract Performance: Account creation, repository cloning, build serving, and subscription processing.
- Legitimate Interests: Improving service performance, monitoring access logs, and verifying account security.
- Consent: Opt-in preferences, third-party OAuth credentials, and marketing communications.
4.1 Ephemeral Storage (Temporary Data)
- Cloned Repositories: All cloned files, docker containers, and in-memory environment variables are wiped clean 30 minutes after a session goes idle.
- Framework Caches: Framework caches are evicted if a project remains inactive for 60 days.
- Screenshots: Visual bug screenshots and comparisons are automatically deleted after 30 days.
4.2 Persistent Database Storage
User credentials, organization config, integration tokens, and annotations are stored indefinitely until you request deletion, revoke the integration, or cancel your account. Deleted account data is purged within 30 days.
5.1 Subprocessors & Infrastructure
We share operational data with trusted infrastructure providers:
- Infrastructure: AWS (hosting, DB), Vercel (CDN), Cloudflare (security), DigitalOcean (Redis).
- Operations: Postmark (emails), Razorpay (payments), Sentry (errors).
- AI service providers: Contracted providers operating under zero-retention API agreements.
5.2 Integration Partners & Compliance
When syncing annotations with Linear, Jira, or Slack, we share only scope-specific issue data, not source code. We may disclose data when legally subpoenaed by law enforcement or regulatory authorities.
Our primary servers are hosted in the United States (AWS us-east-1). Edge caches reside on Cloudflare's global network. For EU-to-US data flows, we execute Standard Contractual Clauses (SCCs) to safeguard your data rights. By using Claron, you consent to these cross-border transfers.
You have the following control rights over your personal data:
- Access & Portability: Request a copy of your personal details by contacting privacy@claron.dev.
- Correction: Modify profile and workspace details inside settings.
- Deletion: Cancel and delete your account directly via settings. Residual backup logs are permanently deleted within 90 days.
- Opt-Out: Unsubscribe from marketing newsletters via the opt-out footer.
8.1 Technical Security
- HTTPS/TLS 1.3 encryption for all traffic in transit.
- AES-256 encryption at rest for environment variables and API keys.
- Database encryption at rest via AWS RDS storage layers.
- Containerized builds and strict path traversal validation blocks.
8.2 Password & Auth Security
Passwords are hashed via Bcrypt (salt rounds ≥ 10). Session tokens expire in 24 hours. Employee access to production infrastructure is managed via multi-factor authentication (MFA) and VPN tunnels.
Claron does not knowingly collect or target information from children under 13. If you believe a child has provided us with personal information, please alert us immediately at privacy@claron.dev so we can delete it.
Our platform includes integrations and links to external services (GitHub, Slack, Jira, etc.). This Privacy Policy does not cover third-party data processing. We encourage you to review their respective privacy policies.
We may update this policy occasionally. Material updates that impact your rights will be communicated to your registered email or via in-app dashboard alerts 30 days prior to taking effect.
General Inquiries
If you have questions regarding privacy, contact us at:
- Email: privacy@claron.dev
- Mailing Address: The creators and operators of Claron, Privacy Team, Vadodara, Gujarat, India
- DPO Contact: dpo@claron.dev