Privacy Policy
Early-access version. It's still being finalized; when it changes, we'll ask you to accept the new version before you continue. See also our Terms of Service and Service Providers.
Last Updated: October 13, 2026
This Privacy Policy describes how Richard Hieb, an individual operating The Self Mirror ("we," "us," or "our"), processes personal information collected through the website and application currently hosted at theselfmirror.com (the "Service").
1. JURISDICTION: UNITED STATES ONLY
The Service is hosted in the United States and is intended exclusively for residents of the United States. We do not knowingly market to, accept data from, or target individuals located in the European Union, the United Kingdom, Canada, or other international jurisdictions.
2. DATA WE COLLECT
2.1 Account Information: Email address, verification status, and account metadata managed via Firebase Authentication (Google). User passwords go directly to Firebase and are never seen, processed, or stored on our servers. If you sign in with Google, Firebase receives your Google account's email address and basic profile from Google; we don't receive your Google password.
2.2 User-Submitted Person Profiles:
- Identities: Names, birth names (for numerology), and optional pronouns.
- Birth Parameters: Exact date, time, and birthplace (converted to coordinates and time zone offsets).
- Personality Data (Optional): Big Five / IPIP-50 questionnaire answers, scores from external systems (MBTI, Enneagram, DISC, Omnia), and user-written notes.
- Relationship Data: Declared links and labels connecting saved persons.
- Permission Confirmation: When you add someone other than yourself, the date you confirmed you have their permission or are their parent or guardian.
- Questions (Optional): The questions you ask about a section of a profile ("Ask about this") and the answers. They're sent to the AI service as described in section 3, and kept with that section until you delete them or your account.
- Journal (Optional): Your answers to the daily reflection prompt on Today, and an optional mood. Only you can see your journal. It's never sent to the AI service or anyone else, it's encrypted, it's in your data download, and it's deleted with your account or when you delete an entry.
2.3 Technical Telemetry & Logs:
- Keyed Account Numbers: A cryptographically keyed 16-character identifier used in place of your email address in usage and audit tables.
- Application Logs: Application-level log lines are sanitized to prohibit names, birth details, profile text, or IP addresses from entering diagnostic logs.
- Platform Edge Logs: Inbound HTTP requests (including visitor IP addresses and browser user-agent headers) are recorded by Google Cloud Logging at the infrastructure boundary.
- Sign-up Checks: When an account is created, the IP address is used in memory to check the country (an offline DB-IP database; nothing is sent out) and is not stored. A keyed code derived from the network address is counted for 30 days to detect mass sign-ups.
2.4 Invite Requests and Landing Page Totals: If you request an invite, we keep your email address, the plan you're interested in and your optional note until the request is handled, or for at most 180 days. The public pages record daily totals only (for example, views per day), with no cookies and nothing per visitor.
3. THIRD-PARTY SUB-PROCESSORS
To calculate charts and synthesize profiles, specific data fields are transmitted to third-party processors. The current providers, by name, are listed on our Service Providers page, which we update when a provider changes:
| Provider | Function | Data Transmitted | Data Safeguards |
|---|---|---|---|
| Google Cloud Platform | Hosting & Firestore Database | Stored account records, person data | Encrypted at rest and in transit |
| Firebase Auth (Google) | Identity & verification; sends verification and password-reset emails | Email, authentication credentials | Salted/hashed credentials; zero raw password exposure |
| AI text provider (a commercial AI service) | AI profiles, daily reads and answers to questions | Charts, scores, notes and your questions, as described below the table | Commercial paid API; under its commercial terms, inputs are not used to train its models |
| AstrologyAPI.com | Chart calculations | Birth date, time, latitude, longitude, UTC offset | NO personal names or identities transmitted |
| OpenStreetMap Nominatim | Geocoding birthplaces | Typed location string (e.g., "Austin, TX") | Free lookup; no user credentials attached |
| Resend | Invitation, connection, household and account-notice emails, and verification emails we resend | Recipient email address and the message, which can include the sender's email address and a personal note | Standard transit encryption |
Names and the AI service: Profiles, readings and answers to your questions are written by a third-party AI service from your charts, test results and notes, and the questions you ask. We keep the people in them from being named: their names are left out or replaced with stand-in names, including in your notes and questions. Anything else you type in a note or a question, including other people's names, is sent as written. We take care with this but can't guarantee it; a mistake could let a name through. If we ever change how names are handled, we'll tell you and ask you to agree again before it applies.
WE DO NOT SELL, RENT, OR MONETIZE YOUR PERSONAL INFORMATION.
4. DATA ENTERED ABOUT THIRD PARTIES & REMOVAL PROCESS
4.1 Third-Party Data. Users frequently input details about partners, children, and friends. The account holder is legally responsible for having obtained all necessary permissions before entering such data.
4.2 Removal Workflow for Non-Users. By design, person records are indexed under individual user accounts, and our systems do not maintain a global public name index. If you believe your personal details were entered into the Service without your consent, you must submit a removal request containing:
(a) Your identifying details (full name and birth parameters); and
(b) The email address of the account holder you believe submitted your information (accounts can only be looked up by email).
Upon receipt of this identifying context, the Operator will conduct an audited lookup of the specified account and permanently purge the corresponding person record.
4.3 Sharing Between Users. If you share a person or profile with another user, that user can see it. Birth details are included only if you choose to include them. Their access ends when you stop sharing or either of you disconnects, except for copies you approve, which become theirs. If they include a person you shared in a relationship profile, that person's charts and results go to the AI service under the same rules as your own (section 3).
4.4 Children. Account holders must be 18 or older. Adults may add a child they are the parent or guardian of, or have permission to add. We use each person's birth date to tell whether they are under 18. If they are, what the AI writes is written for a parent about their child, there is no Professional version, and romantic links aren't allowed. We don't knowingly collect information directly from anyone under 18.
5. DATA RETENTION SCHEDULE
- Person Records, Charts, & Notes: Retained until deleted by the user or upon complete account termination.
- Journal Entries: Retained until you delete the entry or your account.
- Questions and Answers: Retained until you start the section over (which deletes them) or delete your account.
- Usage Log Records (
usage_events): Stored under a keyed account number; purged after 18 months or upon account deletion. - Audit Logs (
admin_audit): Stored under a keyed account number for 2 years for security accountability. - Error Diagnostics (
error_reports): Purged after 90 days. - Daily Usage Counters: Purged after 90 days.
- Sign-up Abuse Counters (keyed network codes): Purged after 30 days.
- Invite Requests: Deleted when handled, or after 180 days.
- Shared Daily Readings about Other People: Purged after 3 days.
- Daily Spend Totals and Landing Page Totals: Contain no personal data; kept 2 years and 90 days respectively.
- Database Backups: Point-in-time recovery copies expire automatically after 7 days.
- Platform Edge Logs: Retained in Google Cloud Logging in accordance with platform defaults (typically 30 days).
6. SECURITY: BEST EFFORTS DISCLAIMER
We implement technical safeguards including keeping names out of what goes to the AI service (section 3), keyed identifiers in diagnostic databases, and audited administrative controls. The operator, and people the operator authorizes, see account information only through audited admin tools; seeing a person's name or birth details takes a separate, recorded step.
However, we provide this Service on a commercial best efforts basis. No digital transmission or database is completely secure. We do not warrant or guarantee absolute data security against all vulnerabilities or breaches.
7. USER CONTROLS
Account holders have built-in self-service controls:
- Correction: Edit birth data, scores, or notes at any time.
- Portability: Export complete personal data in JSON and CSV formats via "Download all my data."
- Erasure: Delete individual persons, or delete your whole account yourself from the Account menu ("Delete my account").
8. CONTACT INFORMATION
For privacy requests, contact:
The Self Mirror / Richard Hieb
Email: rich.hieb@gmail.com