OptiLife AI Privacy

Information We May Collect

• Name, email, phone, free launch code, referral code, and profile preferences.
• Goals, tasks, workflows, business or family organization notes, and user-submitted instructions.
• Technical information needed for security, abuse prevention, and audit logs.

Information We Do Not Want

• Passwords, MFA codes, recovery keys, raw session cookies, full card numbers, full bank numbers, or Social Security numbers.
• Private third-party information unless the user has permission to share it.

How Information Is Used

• Create and improve the user's OptiLife AI account/profile.
• Send signup, profile, billing, and service updates after consent.
• Improve generalized playbooks using anonymized patterns, not private client facts.

Consent And Control

Users should choose what to share. Public research, outreach, payment, account access, and sensitive automations should require clear consent and approval. Private profiles should stay private unless the owner explicitly opts into public visibility.

Security

OptiLife AI should use data minimization, access controls, audit logs, private workspaces, HTTPS, secure payment providers, backup/rollback planning, and a draft incident-response process before paid launch.

Incident Response And Recovery

If a security, privacy, or public-copy issue is detected, OptiLife AI should pause risky actions, document scope, verify rollback, and keep any external notice draft internal until Eric approves a real-world send.

Public Profile Visibility

Public profile pages should be optional. Helpful public pages can exist, while private profile details remain private until the owner approves public copy and visibility.