Privacy Policy

How Droplet handles account data, conversations, stored assets, billing records, and provider integrations.

This policy is provided for informational purposes. Legal review recommended before production publication.

What Droplet collects

Droplet collects account information needed to operate the service, including identifiers supplied through Clerk, profile details you provide, and billing records associated with plan purchases.

When you use the product, Droplet also processes conversation content, uploaded files, generated media references, and service metadata such as timestamps, plan state, and usage counters required to enforce limits and support the product.

How that information is used

Droplet uses collected information to authenticate users, deliver chat and media features, maintain conversation history, enforce plan entitlements, process billing, and investigate support or security issues.

Usage metadata may also be processed for reliability, abuse prevention, cost control, operational analytics, and product improvement. Droplet should not use personal data for unrelated marketing or resale without explicit approval and notice.

Third-party service providers

Droplet relies on third-party processors to deliver core service functions. These include OpenAI for model responses, Clerk for authentication and session management, Stripe for payments, and AWS S3 for file storage.

Those providers may process only the information necessary for their role in delivering the service. Droplet operators should maintain written agreements, access controls, and retention policies appropriate to each provider relationship.

Storage, retention, and security

Conversation records, uploaded assets, and billing data are retained for as long as needed to operate the service, satisfy support obligations, enforce limits, and meet legal or accounting requirements. Retention periods should be finalized through legal and operational review before production publication.

Droplet is designed to apply authentication, ownership checks, provider signature verification, upload validation, and other security controls at service boundaries. No system can guarantee absolute security, so the operator should continue to harden infrastructure and monitor for abuse.

Cookies, local storage, and similar technologies

Droplet uses essential authentication technologies through Clerk and stores interface preferences such as theme and sidebar state in browser storage. More detail appears in the dedicated Cookie Policy.

For the current public experience, the documented browser storage keys include droplet-theme-mode and droplet-sidebar-collapsed.

User rights and contact

Users should have a way to request access, correction, deletion, or export of data subject to legal, billing, fraud-prevention, and security constraints. Exact response timelines and jurisdiction-specific rights should be finalized before production use.

For privacy inquiries, support requests, or escalation related to account data, contact `office@jordachewd.com` unless and until Droplet publishes a different official privacy contact.

Related policy pages

Review the dedicated Cookie Policy for browser storage details and the Terms & Conditions page for account, billing, and service-use rules.