Privacy Policy

Last updated: June 21, 2026

This policy explains what enspire collects, how we use it, and who we share it with.

What we collect

• Account — when you sign in with GitHub we receive your GitHub username and email and a session identifier.
• Repository data — for repositories you connect, we read commit messages, commit metadata, and changed-file names to generate drafts. We do not need or store your source code.
• Channel credentials — if you connect a channel (e.g. dev.to), we store the API key encrypted (AES-256-GCM) and use it only to publish on your behalf when you approve a post.
• Generated content — the narratives and drafts created from your activity.
• Payment — handled by Stripe. We do not store your card details; we keep a customer/subscription identifier and plan status.

How we use it

To operate the Service: generate drafts, let you review and publish them, manage your subscription, and secure and improve the product.

Subprocessors

We rely on these providers to run the Service:

• Supabase — database & authentication
• Vercel — hosting
• Anthropic (Claude) — generating drafts from your commit data
• Stripe — payments
• GitHub — sign-in and repository access
• dev.to, X, LinkedIn — only when you choose to publish to them

Sharing

We don’t sell your data. We share data with the subprocessors above only as needed to run the Service, or where required by law.

Retention & deletion

We keep your data while your account is active. You can delete your account, which removes your projects, generated content, and stored channel credentials. Some records (e.g. billing) may be retained as required by law. Requests: support@enspire.co.

Security

Channel credentials are encrypted at rest, and access to your data is restricted to your account via row-level security. No system is perfectly secure, but we take reasonable measures to protect your data.

Your rights

You can access, correct, export, or delete your data — email support@enspire.coand we’ll help.

Contact

support@enspire.co