← Back to Clint

Privacy Policy

Last updated: May 12, 2026

1. Introduction

Clint AI (“we”, “us”, “our”) operates the Clint platform (“the Service”). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service. By using Clint, you consent to the data practices described in this policy.

2. Information We Collect

2.1 Information You Provide

  • Prompts and descriptions: The text you type to describe applications you want to build.
  • Account information: Email address and authentication credentials if you create an account.
  • API keys and credentials: Third-party API keys (Stripe, OAuth provider credentials, OpenAI) you enter in Settings to enable features in your generated applications.
  • Chat messages: Messages you send through the post-build chat interface to modify your applications.
  • Settings and preferences: Configuration choices you make within the platform.

2.2 Information Generated by the Service

  • Generated code: Source code files created by AI models based on your prompts.
  • Database schemas and data: PostgreSQL databases provisioned for your applications, including table structures and any data entered by users of your applications.
  • Test results: Automated browser test outcomes, screenshots, and error logs.
  • Deployment metadata: URLs, deployment IDs, and build logs from Vercel deployments.
  • Version snapshots: Copies of your application files saved before each modification.

2.3 Information Collected Automatically

  • Usage data: Token consumption, build counts, and feature usage for billing and analytics.
  • Log data: Server logs including IP addresses, browser type, and timestamps.
  • Error data: Application errors and crash reports to improve the Service.

3. How We Use Your Information

  • Provide the Service: Generate applications, provision databases, run tests, deploy to hosting infrastructure, and process chat commands.
  • AI processing: Your prompts and chat messages are sent to AI model providers (Anthropic, OpenAI) for code generation and natural language processing. These providers process your input according to their own privacy policies.
  • Improve the Service: Analyze usage patterns, error rates, and test results to improve code generation quality and system reliability.
  • Security: Detect and prevent fraud, abuse, and unauthorized access.
  • Communication: Send service-related notifications, updates, and support responses.

4. Data Storage & Security

4.1 Where Data Is Stored

  • Application files: Stored on the local filesystem of the Clint instance and deployed to Vercel's global CDN.
  • Database data: Stored in Neon PostgreSQL instances hosted in AWS data centers. Each application receives its own isolated database schema.
  • API keys: Stored in a local settings file on the Clint instance. Keys are injected as environment variables during deployment and are not included in client-side code.
  • Chat history: Stored as JSON files alongside project files on the local filesystem.

4.2 Security Measures

  • API keys are stored server-side and never exposed to the browser in generated applications.
  • OpenAI API calls are proxied through serverless functions to keep keys secure.
  • Database connections use SSL/TLS encryption.
  • User passwords in generated applications are hashed using PBKDF2 with random salts.
  • OAuth tokens are stored in the database, not in client-side storage.
  • Each application's database schema is isolated from other applications.

5. Third-Party Data Sharing

We share data with third-party services only as necessary to provide the Service:

  • Anthropic (Claude): Your prompts, chat messages, and generated code are sent to Anthropic's API for AI processing. Anthropic's data retention and privacy policies apply. Anthropic Privacy Policy
  • OpenAI: If your generated application uses AI features, end-user interactions are sent to OpenAI's API through a server-side proxy. OpenAI Privacy Policy
  • Vercel: Generated application files and environment variables are deployed to Vercel's infrastructure. Vercel Privacy Policy
  • Neon: Database schemas and application data are stored in Neon PostgreSQL. Neon Privacy Policy
  • Stripe: If payment features are enabled, payment processing is handled by Stripe. Clint does not store credit card numbers. Stripe Privacy Policy
  • OAuth providers: When you connect third-party accounts (Google, Spotify, Strava, etc.), authentication tokens are exchanged with those providers according to their policies.

We do not sell your personal information to third parties. We do not use your data for advertising purposes.

6. Data Retention

  • Generated applications: Retained until you delete them. Version snapshots are retained up to 20 versions per project.
  • Database data: Retained as long as the application exists. Deleted when you delete the project.
  • Chat history: Retained per project, up to 200 messages. Cleared when you start a new chat session.
  • Build logs: Retained temporarily during the build process and discarded after completion.
  • API keys: Retained in settings until you remove them or delete your account.

7. Your Rights

Depending on your jurisdiction, you may have the following rights:

  • Access: Request a copy of the personal data we hold about you.
  • Correction: Request correction of inaccurate personal data.
  • Deletion: Request deletion of your personal data and generated applications.
  • Portability: Request your data in a structured, machine-readable format.
  • Objection: Object to processing of your personal data for certain purposes.
  • Restriction: Request restriction of processing of your personal data.

To exercise these rights, contact us at privacy@clint.build.

8. Data of Your Application Users

When you deploy applications built with Clint, those applications may collect data from their own end users (e.g., account signups, form submissions, user-generated content). You are the data controller for this data. You are responsible for:

  • Providing your own privacy policy to your application's users
  • Obtaining appropriate consent for data collection
  • Complying with applicable data protection laws (GDPR, CCPA, etc.)
  • Responding to data subject requests from your users

Clint acts as a data processor for this data, storing it in PostgreSQL databases on your behalf. We do not access, use, or share your application users' data except as necessary to provide database hosting services.

9. Children's Privacy

The Service is not intended for use by individuals under the age of 13. We do not knowingly collect personal information from children under 13. If you become aware that a child has provided us with personal information, please contact us and we will take steps to delete such information.

10. International Data Transfers

Your data may be transferred to and processed in countries other than your country of residence. These countries may have different data protection laws. By using the Service, you consent to the transfer of your data to these countries. We take appropriate safeguards to ensure your data remains protected in accordance with this Privacy Policy.

11. Cookies & Tracking

The Clint platform uses minimal cookies and local storage:

  • Authentication tokens: Stored in localStorage to maintain user sessions in generated applications.
  • UI preferences: Theme and layout preferences stored in localStorage.

We do not use third-party tracking cookies, advertising cookies, or analytics services that track individual users across websites.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by posting the new policy on this page and updating the “Last updated” date. Your continued use of the Service after changes constitutes acceptance of the updated policy.

13. Contact Us

For questions or concerns about this Privacy Policy or our data practices, contact us at: