Privacy notice
This draft explains the information Genesis Code Doctor AI expects to handle, why it is needed, and the choices customers and community members should have.
This is a pre-launch product draft, not the final privacy notice. It has no effective date yet. Data practices, service providers, retention periods, regional rights, and contact details must be verified before publication or payment activation.
What this notice is intended to cover.
This draft covers the public website, account and community features, diagnostics, comparison reports, purchases, subscriptions, refund requests, support, and authorized connections offered under the Genesis Code Doctor AI name. A final notice will identify the responsible legal entity and any region-specific supplements.
Information the service may receive.
| Category | Examples | Typical source |
|---|---|---|
| Account and profile | Name, username, email, authentication status, organization, preferences, and role. | You, your organization, or an authorized sign-in provider. |
| Diagnostic input | URLs, comparison selections, public-page evidence, findings, scores, and scan history. | You and publicly accessible website responses. |
| Authorized workspace data | Files, configuration, test results, instructions, and connection metadata you deliberately provide. | You or an integration you authorize. |
| Community content | Questions, answers, comments, votes, reports, saved items, and public profile details. | You and other community members. |
| Commerce and support | Plan, order, invoice references, payment status, refund requests, and support messages. | You and service providers. Full card details should remain with the payment processor. |
| Technical activity | Device, browser, approximate network information, security events, logs, and cookie choices. | Your browser, device, and the service. |
Why information may be used.
- Provide accounts, diagnostics, comparisons, reports, repairs, billing, community, and support.
- Secure the service, prevent abuse, enforce access controls, and investigate incidents.
- Measure reliability and improve features using appropriately limited data.
- Send requested transactional messages and, only where allowed, optional communications.
- Meet legal obligations and protect users, the service, and the public.
A public URL permits analysis only of information available through permitted public requests. It does not authorize Genesis to access private analytics, source repositories, customer records, messages, credentials, or other restricted systems.
When information may leave Genesis.
Information may be provided to infrastructure, authentication, payment, email, analytics, security, and support providers only as needed for their contracted function; to an organization that administers your workspace; or when required for safety, legal process, or a business transaction. The final notice must name or categorize verified providers and explain international transfers where applicable.
Public forum posts, usernames, profile details, votes, and accepted-answer status are intended to be visible to others. Private diagnostics, uploaded code, billing records, refund details, moderation evidence, and account-security information are not intended for public display.
Retention, choices, and rights.
Retention periods have not been finalized. The production notice must document retention by data type, deletion and export procedures, legal holds, backup handling, and any anonymized aggregate records retained for security or product integrity.
- Account settings should provide profile and communication controls.
- The cookie page should explain available browser and consent choices.
- Regional law may provide access, correction, deletion, portability, restriction, objection, or appeal rights.
- Requests should be submitted through the verified Support Center; identity may need to be confirmed before private data is disclosed or changed.
Security is a process, not a promise.
Genesis is being designed around least-privilege access, private-by-default workspaces, signed service events, audit records, and restricted execution of customer code. No online service can promise absolute security. Final claims must reflect controls that have actually been implemented and tested.
The final notice will be versioned.
Before launch, this page must include the legal entity, contact channel, effective date, change-notice process, applicable regional disclosures, children’s-data position, verified provider details, and approved retention schedule. Material future changes should be communicated through an appropriate account or website notice.