Acceptable use
Genesis Code Doctor AI should help people examine and improve systems they are authorized to use—not bypass safeguards or harm others.
This pre-launch policy is not final. Enforcement thresholds, appeal procedures, emergency handling, prohibited jurisdictions, age requirements, and legally required exceptions must be approved before publication.
Only inspect or change what you have the right to use.
- Do not connect accounts, submit private code, upload files, or authorize changes without permission.
- Do not evade authentication, paywalls, robots controls, rate limits, network restrictions, or platform terms.
- Do not use public comparison tools to obtain or infer a competitor’s private analytics, messages, credentials, customer records, source code, or proprietary databases.
- Do not impersonate a site owner, customer, expert, moderator, Genesis representative, or another person.
No malicious, disruptive, or unsafe activity.
Users must not use Genesis to develop, distribute, test, or deploy malware; steal credentials or data; exploit systems without authorization; conduct denial-of-service activity; automate abusive traffic; conceal harmful code; evade safety controls; or expose operational exploit details in public community areas.
Potential vulnerabilities, secrets, private records, live exploit details, and sensitive evidence must go through the restricted security or support path—not public posts, profile pages, or shared reports.
Respect privacy, intellectual property, and human safety.
- Do not submit personal, confidential, regulated, or proprietary information unless you are authorized and the selected workflow supports it.
- Do not copy a competitor’s protected text, images, branding, or creative work. Learn from capability gaps and create original material.
- Do not post unlawful, deceptive, hateful, harassing, sexually exploitative, or privacy-invasive content.
- Do not manipulate votes, reviews, reputation, diagnostics, or verification labels.
- Do not generate or distribute fraudulent invoices, phishing pages, counterfeit services, or misleading evidence.
Plans and payment systems cannot be gamed.
Users must not abuse trials, credits, refunds, chargebacks, referral programs, usage limits, organization seats, or service integrations. Scraping, bulk automation, resale, benchmarking, or high-volume use may require an approved plan or written permission. Final limits must be disclosed in the relevant plan or order form.
Keep a qualified human in high-impact decisions.
Diagnostics and generated repairs may be wrong, incomplete, outdated, or incompatible with a private environment. Do not use them as the sole basis for decisions that could materially affect safety, legal rights, employment, housing, credit, health, public infrastructure, or another high-impact domain. Production and destructive changes require review, backup, testing, and explicit authorization.
Protective action should be proportionate and reviewable.
Genesis may limit scans, quarantine content, restrict a connection, preserve evidence, suspend an account, or contact appropriate parties when reasonably necessary to protect the service or others. The final policy must define notice, appeal, evidence retention, repeat violations, urgent threats, and circumstances where notice is legally restricted.
Potential violations can be reported through the Support Center. Community-specific expectations appear in the Community Guidelines.