How the checklists are built
See how this hub builds source-first AI companion checklists, handles changing policies, separates observations from claims, and records uncertainty.
Every checklist starts with a decision a reader can control: what to disclose, whether to upload, whether to pay, where renewal is managed, how to leave, or which unanswered question requires support. We then identify the current first-party sources that could answer it. These may include the detailed privacy notice, terms, checkout confirmation, account billing screen, permission dialog, help article, request form, or a written support answer reached from an official page.
Evidence is dated and scoped. A screenshot records what one screen showed at one time; it does not prove future behavior. A policy sentence describes the provider's published position; it does not by itself prove how every system works. A support reply may answer one account or region. The guides therefore tell readers to preserve exact wording, note conflicts, and avoid extending a narrow observation into a broad promise.
We prefer specific questions over scores. For example: what total is due now, who controls renewal, which action uses credits, what data category is covered, what a removal control claims to change, and what confirmation remains afterward. Unknown answers stay unknown. Vague reassuring language does not receive an invented interpretation.
Public pages are checked for a single main heading, descriptive titles, self-referencing canonical addresses, structured page information, working internal links, readable tables, clear update dates, prohibited unsupported claims, and minimum visible depth. The full canonical page list must match the sitemap, while retired overlapping addresses point permanently to the closest safety checklist.
Use the checklists
The following pages turn this site's scope into concrete actions. Choose the page closest to your next account, payment, upload, conversation, or request decision. Verify every answer against the provider's current official source.
- Private AI Companion Account Setup Checklist — Use this first when you want to reduce avoidable links between a companion account and the email addresses, profile names, photos, or notification channels you use elsewhere.
- AI Companion Payment and Renewal Checklist — Open this before entering payment details. It turns a vague monthly-cost question into a record of the exact checkout, renewal, credit, receipt, and cancellation information visible now.
- AI Companion Cancellation Path Checklist — Use this checklist to trace who controls the subscription, when cancellation takes effect, what happens to remaining access or credits, and what confirmation you should keep.
- AI Companion Credit and Usage Limit Checklist — Use this worksheet when words such as credits, tokens, points, generations, messages, or premium actions appear. Record what each unit buys instead of comparing balances by size alone.
- AI Companion Conversation History Privacy Checklist — Use this before writing details you would not want exposed through a title, preview, account screen, shared session, or future export. The safest sensitive detail is the one you never enter.
- AI Companion Data Export and Deletion Questions — Use this page as a request-preparation worksheet. Start with the current policy and interface, identify every data area you care about, and keep the final request narrow enough that the provider can answer each part clearly.
Questions and corrections
If public guidance conflicts with a provider's current detailed source, treat the current source as the item to investigate and preserve both dates. Do not send this site passwords, recovery codes, full payment credentials, private conversations, identity documents, or personal media. Use the provider's verified official route for account-specific matters.