PRIVACY & DATA HANDLING

Clear about
what happens here.

Website privacy notice · Updated September 12, 2026

This website

This is a static product information website. It does not create accounts, accept resumes, or submit early-access registrations. The preview form is disabled. This website’s code does not use analytics, advertising trackers, cookies, or browser storage. Fonts and artwork are served with the site.

Website hosting

GitHub Pages hosts the site. Requests necessarily share technical information such as your IP address and browser request details with the hosting service. Cloudflare provides the domain’s DNS. Their processing is governed by their own policies: GitHub privacy statement and Cloudflare privacy policy.

Contact information

If you choose to email RoleDaemon, your address, message, and any attachments are shared with the email services used to deliver that message. Do not send resumes, credentials, or sensitive employment information. The website itself does not store your message.

Request data deletion

There are no website accounts or stored signup records to delete. For information you have sent by email, contact RoleDaemon with the subject “Data deletion request” and identify the message or information concerned. Do not include identity documents. Product account deletion is not available through this site.

Request a copy of your information

For information you have sent by email, contact RoleDaemon with the subject “Data access request.” Product data export is not available through this site; the supported workflow must be documented before public beta.

Third-party AI and data services

This marketing website sends no form content to an AI provider. The application’s providers, information shared with them, retention rules, and available controls have not been documented here yet. These details must be published before public beta. Do not infer local-only processing or encryption guarantees from the previews.

Security contact

Use the project contact with the subject “Security report.” Send a concise description first; do not include passwords, tokens, or personal data.

Before public beta

The product privacy policy will need to identify the operator, purposes of processing, data categories, service providers, retention periods, relevant rights, and supported deletion and export workflows before personal data is collected through the product.