Privacy policy
This policy explains the data needed to authenticate users, deploy projects and operate the service. ClaudeToHost does not sell personal data.
Account data
The authentication service stores your email address, password hash, verification state and security metadata needed to protect the account. OAuth providers may return an identifier, email address and profile name.
Deployment data
ClaudeToHost stores uploaded archives, generated releases, deployment metadata and logs so sites survive restarts and can be managed or rolled back. Do not include secrets in an archive. Detected secret locations may be reported without retaining the matched value in the diagnostic.
Public artifacts
A deployed static site is public by design. Its bundle is served through an unguessable internal artifact URL used by the hosting platform. Treat every deployed file as publicly accessible.
Technical data
Request identifiers, timestamps, IP-derived abuse controls, response status and operational metrics are processed for security, quotas, troubleshooting and service reliability. Anonymous deployment reservations are rate-limited and expire.
Retention and deletion
Deleting a site removes its hosting resources and active bundles. Old release records and unreferenced build artifacts are retained for a bounded operational rollback window, currently up to 30 days, then collected automatically. Security and infrastructure logs may be kept longer when required to investigate abuse or an incident.
Your rights
You may request access, correction, export or deletion of personal data, and object to processing where applicable. Contact support@claudetohost.com. You may also contact the CNIL.