Triple Moon Goddess · triplemoongoddess.com · Lisa@TripleMoonGoddess.com
Privacy Policy v2026-10k · Effective October 21, 2026 · Version history
Triple Moon Goddess is built so your identity and your data are kept apart. No single record holds both.
Your email and birth data are encrypted at rest (Google Cloud KMS) and in transit (HTTPS). We never sell your data.
Your birth data never leaves its encrypted vault to be shown in the apps — not to other users, and not to practitioners. The calculations that use it run on our secure servers, not in your browser. The one exception: Lisa, the site owner, can view your birth data through an internal admin tool solely to correct a data-entry error, such as a mistyped birth date. You remain the owner of your data.
Your birth data is never used for research. The research signals we keep — anonymous counts of how strongly each chart placement resonated — contain no name, no email, no birth data and no access code.
You can delete your data at any time. After you delete, the only things kept are the anonymous research counts above and payment records reduced to amounts and status, so nothing links back to you. Deleting also removes you from the services that hold your email: your MailerLite subscriber record, your booking events on our calendar, and your Stripe customer record (Section XII). Deleted files clear from storage within 14 days, and backups age out within 98 days (Section VIII).
These rules are enforced automatically in our software: an internal privacy check blocks any change that would store a client's name, search an email in plain text, or move birth data outside its vault.
Triple Moon Goddess is a wellness journaling and medical astrology application operated by Lisa Hagan ("we", "us", "our"). For all data protection enquiries, please contact:
Triple Moon Goddess
Lisa Hagan
3654 Thornton Ave, Unit #748
Fremont, CA 94536
United States
Email: Lisa@TripleMoonGoddess.com
Website: triplemoongoddess.com
This policy applies to all users of the Triple Moon Goddess ecosystem: the natal chart generator, the Health Journal (PWA), the Health Blueprint app, the Tea Moon app, and the phone widget application, together with the paid practitioner applications (Integrative Practitioner, Soul Pattern, Constitutional Health, and Relationship Advice), clients who share their records with a practitioner, and any associated email communications.
Triple Moon Goddess offers its services in the United States. Our own databases, file storage, backups, encryption keys and servers, including the service that calculates charts, are in the United States. The processors in Section V store the data they receive under their own terms: Anthropic stores data in the United States and may route requests through other countries; Stripe may transfer data to other countries, including the United States and India; MailerLite stores newsletter data in the European Union; Google Workspace, which carries our business email and calendar, may store data in any country where Google or its subprocessors have facilities; and Google reCAPTCHA Enterprise, which checks that requests come from our own app pages, is a Google Cloud service that may process data in any country where Google or its subprocessors have facilities. We do not market to or target people outside the United States. If you use our services from elsewhere, the rights in Section XII still apply to you. Consumer health data is also covered by our separate Consumer Health Data Privacy Policy.
Collected only if you voluntarily provide it:
| Data | Purpose |
|---|---|
| Email address | Account lookup, sign-in links, chart delivery, receipts, booking invitations, reminders, and the newsletter |
| Birth date, time & location | Natal chart generation |
If you use the contact form on this website, we collect the email address and message you submit, solely so that Lisa can read and reply to your enquiry. The form asks for no name. Our own server emails your message to Lisa; that email is deleted from our mailbox after 30 days, nothing else is stored, and no third-party form service is involved. If Lisa replies, that conversation is kept as normal correspondence. This is separate from the apps: nothing from the contact form is added to your app records. Please avoid including health details or other sensitive information in a contact-form message — if you need to share something sensitive, email Lisa@TripleMoonGoddess.com directly instead.
Recording a reading is optional. When you enter your birth details you can tick a box consenting to your reading being audio/video recorded; you can also give or decline consent verbally, which Lisa records on your behalf. A recording is only ever made during a live session with Lisa, and you can decline or withdraw consent at any time. Your consent answer is stored against the one-way lookup code for your email, not against your name.
Recordings are kept locally on Lisa’s own computer and are deleted within one month of the session. If we send you a copy of your recording or transcript, it is sent to your email address.
This is health data, and consumer health data under Washington's My Health My Data Act and similar state laws (see our Consumer Health Data Privacy Policy). It includes daily body scores (mood, energy, optimism, physical/mental stamina), sleep data, symptoms, medication and supplement logs, food and beverage log, tongue observations (Traditional Chinese Medicine), personal notes and reflections, and astrology transit journal responses.
Firebase Authentication UID (anonymous for the free apps; an email sign-in account for clients who share their records with a practitioner), FCM push notification tokens, app preferences (tab config, reminder times, food plan, house system), timezone, and rate-limit counters keyed by anonymous UID.
When an app page opens, Google reCAPTCHA Enterprise runs in the background as part of Firebase App Check (Section V). It reads information about your browser and device and how the page is being used, such as your IP address, browser and screen details, and the timing of mouse, touch and keyboard activity, so Google can judge whether a person or an automated script is using the page. It does not receive your name, email, access code, birth data, or any health or journal data.
We do not collect precise device geo-location (GPS). The only location data we process is the birth location you enter for natal chart calculation — it is supplied by you, not derived from your device's location services. To turn the place you type into coordinates, the place name is sent to the OpenStreetMap Nominatim service through our server.
We use Firebase (Google) infrastructure. Firebase collects basic performance and crash data per its own terms. We do not use Google Analytics, Firebase Analytics, Facebook Pixel, any advertising trackers, session replay tools, or heatmap software. We record which of our apps were used on which day, keyed by the sign-in ID; that record is deleted when you delete your data.
To provide the apps you use: sign-in, your chart and journal, push notifications, email reminders, and rate limiting.
Only with your consent, given in the app before any health data is entered: storing and showing your journal entries, producing the PDF exports you ask for, and sharing with a practitioner you choose. You may withdraw consent at any time (Section XII).
Only with your consent. AI features are entirely optional. In the free apps, each chart receives 5 complimentary AI uses, counted on our server; after that, AI is only available if you choose to add your own Anthropic API key. Practitioner AI runs only on the practitioner's own Anthropic API key: the request goes directly from the practitioner's browser to Anthropic under the practitioner's own Anthropic account, outside Triple Moon Goddess's systems and agreements. An API key you add is stored encrypted on your device only. With no free uses left and no key, no data is ever sent to Anthropic.
When any AI feature is used, only the data relevant to that interaction is sent to Anthropic's API. No name, email, or access code is ever included. Anthropic does not use this data to train models. There are seven AI touchpoints across the apps, each with a just-in-time privacy notice shown before data is sent:
| Location | Trigger | Data sent to Anthropic | Notice type |
|---|---|---|---|
Journal — AI Dialog (SummaryTab.tsx) | First message send per session (including starter chips) | Message text plus today’s journal context: health scores, symptoms, notes, astrology data | Modal on first send; sessionStorage key tmg_ai_dialog_noticed suppresses on subsequent messages |
Practitioner — AI Summary (JournalTab.tsx) | Tab load when AI summaries are present | Client session data: chart placements, pattern scores, comparison signals, intake answers, journal entries, practitioner notes, astrological context. No client name, email, or birth date, time or place. | Inline notice card above entry list; summaries hidden until acknowledged. SessionStorage key tmg_practitioner_summary_noticed. |
Practitioner — AI Dialog (AITab.tsx) | First message send per session (Send button or Enter key) | Message text plus session context: chart placements, pattern scores, comparison signals, intake answers, journal entries, practitioner notes, astrological outputs, and any file or image the practitioner attaches to the message. No client name, email, or birth date, time or place — but anything the practitioner types or attaches is sent. | Modal on first send; sessionStorage key tmg_practitioner_dialog_noticed suppresses on subsequent messages |
Journal — Tongue Analysis (TongueTab.tsx) | Each tongue photo you submit for analysis (top, then underside) | The photo itself; for the underside photo, also the AI findings from your top photo. Photos are not stored by TMG. No name, email, access code, or birth data. | Modal before the first photo is sent each session; sessionStorage key tmg_tongue_ai_noticed suppresses on subsequent photos |
Practitioner — Soul Pattern AI (SoulAIPanel.tsx) | Each message the practitioner sends | Message text plus chart and lived pattern scores, divergences, trigger notes and natal positions. No client name, email, or birth data. | Modal on first send; sessionStorage key tmg_soul_dialog_noticed suppresses on subsequent messages |
Practitioner — Synastry AI (SynastryAIPanel.tsx) | Each message the practitioner sends | Message text plus the synastry report: sign and house placements and aspect readings for “Partner A” and “Partner B”. No names, email, or birth data. | Modal on first send; sessionStorage key tmg_synastry_dialog_noticed suppresses on subsequent messages |
| Practitioner — Remedy AI (Integrated app, Recommendations tab) | Automatically when the practitioner opens the Recommendations tab, and again if the client’s constitution changes | The same session context as the Practitioner AI Dialog, plus the food and herb results from the remedy engine. No client name, email, or birth data. | Notice card on the Recommendations tab; nothing is sent until the practitioner presses “Generate AI summary”. sessionStorage key tmg_remedy_summary_noticed lets later summaries in the same session generate without the card |
Provides database, authentication, hosting, and cloud functions. Stores all Firestore data, files, and push tokens in Google data centres in the United States.
firebase.google.com/support/privacyProvides the Claude AI API for optional AI summaries and AI dialog features. Data sent varies by touchpoint — see Section IV for the full breakdown. No name, email, or access code is ever included. Anthropic does not use this data to train models. Free-app AI uses run through our server. Practitioner AI runs on the practitioner's own Anthropic account, directly from their browser; that relationship is between the practitioner and Anthropic.
anthropic.com/privacyHosts our Swiss Ephemeris calculation API for astrological positions. Data sent: birth date, time, and location — not linked to your identity. Migrated from Railway to Google Cloud Run in May 2026.
cloud.google.com/terms/cloud-privacy-noticeTurns the birthplace you type into map coordinates. Our server sends only the place name — no date, time, email, or access code — and nothing is stored by TMG from the lookup.
osmfoundation.org/wiki/Privacy_PolicyRuns sign-in. Clients who share their records with a practitioner sign in with a single-use link sent to their email. Practitioners and the administrator also complete two-step sign-in with an authenticator app. Password sign-in is turned off. Signed-in sessions end after 30 minutes without activity.
policies.google.com/privacyLets our servers tell requests from our own app pages apart from automated scripts. It runs in the background on every app page; there is no puzzle to solve. Google receives the browser, device and page-use information described in Section III and returns a short-lived token, which the page sends with its requests to our servers. No name, email, access code, birth data, health or journal data is sent to it. Requests without a valid token are counted and, for now, still answered; we will start refusing them once the counts show that real visitors always pass. App pages show Google's notice: "This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply."
policies.google.com/privacyPractitioner, partner, and administrator accounts sign in with Google. We receive only your email address and your Google account identifier. We do not request or receive your Gmail messages, Google Drive files, Google Contacts, or your own personal calendar. We do not store your Google display name or profile photo. Your email address is stored as a keyed one-way fingerprint, with the address itself held in a separate encrypted vault. Individual seekers do not use Google Sign-In — the free chart, journal, widget, Tea Moon, and intake apps use anonymous authentication with no Google account involved. See Section VI for full detail.
policies.google.com/privacyUsed to schedule sessions. Access is authorised once by Lisa Hagan for her own Triple Moon Goddess business calendar — no client or practitioner is ever asked to connect their own Google account for scheduling. When you book a session we check availability on that calendar and create the appointment. Your email address is sent to Google Calendar as the event attendee and appears in the event description, together with the order reference and product, so that you receive the invitation and the video-conference link. Event guests cannot see other guests, invite others, or modify the event. When you delete your data, your booking events are deleted from the calendar, past and future. No health data, journal content, or birth data is ever sent to Google Calendar. See Section VI for full detail.
policies.google.com/privacyEmails that carry your data — charts, readings, sign-in and return links, booking confirmations, and PDF attachments — are sent through the Gmail API from a dedicated address, notifications@triplemoongoddess.com, by our own server functions with permission to send only; no mail password is used. Our copies of those emails are deleted automatically after 30 days. We use the Gmail API only on our own business mailbox: to send those emails, to notice emails that bounced (read-only), and to delete our own 30-day-old copies. Replies you send to Lisa are kept as normal correspondence. PDFs are generated either in your own browser or by our secure server functions, and are delivered as email attachments; download pages use links that expire after 15 minutes. We do not use Google Drive.
Processes payments for readings, sessions, and practitioner subscriptions. Card details are entered on Stripe and never reach TMG. Stripe receives your email address (for your receipt) and the order details: the product purchased, an internal order reference, any referral code or credit applied, and — for a reading — how you heard about us, whether you opted in to the newsletter, and the call time you chose. The question you submit with a reading is never sent to Stripe. For refunds and cancellations it also receives the reason. When you delete your data, your Stripe customer record is deleted; the payment records Stripe must keep by law stay with Stripe. For practitioner subscriptions it receives the plan and an internal account reference, and influencer commission payouts are made through Stripe Connect. Your access code, journal data, and birth data are never sent to Stripe. stripe.com/privacy
Sends our newsletter. When you opt in, your email address is added to our newsletter list, together with how you heard about us if you tell us. When we email you your chart, your email address is also added to our subscriber list in MailerLite. Every chart email includes an "Unsubscribe from the newsletter" link (and your mail app's one-click unsubscribe), which removes you; once you unsubscribe, a later chart email does not add you back. When you delete your data, your subscriber record is deleted from MailerLite. For newsletter subscribers, MailerLite also receives a short personal transit note written from your chart, so each newsletter can include it. No health or journal data, no birth date, time or place, and no access code is shared. You can unsubscribe from any newsletter email. mailerlite.com/legal/privacy-policy
This section describes in full how Triple Moon Goddess accesses, uses, stores, and shares data obtained through Google APIs ("Google user data"). It is provided in addition to the general disclosures elsewhere in this policy.
| Google permission | Who grants it | What we receive | Why |
|---|---|---|---|
openid, email, profile — Google Sign-In | Practitioners, partners, program members, and administrators signing in to the paid practitioner and partner applications | Your email address and your Google account identifier | To create and authenticate your practitioner account and match it to your subscription |
https://www.googleapis.com/auth/calendar | Lisa Hagan only, once, for her own Triple Moon Goddess business calendar | Read and write access to that one business calendar | To check appointment availability and create session bookings with a video-conference link |
We request no other Google permissions from you. (Our own business mailbox is reached through Google Workspace by our own service accounts, as described under Email delivery in Section V; that is not your Google user data.) We do not request or receive access to your Gmail, your Google Drive, your Google Contacts, your Google Photos, or your own personal Google Calendar. Individual seekers — users of the free chart, journal, widget, Tea Moon, and intake apps — are never asked to sign in with Google at all; those apps use anonymous authentication.
Google user data is retained only for as long as your practitioner account is active. When your account is cancelled or deleted, the associated email hash and encrypted email record are deleted and the Google account identifier ceases to be used. To request deletion of any Google user data we hold about you, email Lisa@TripleMoonGoddess.com. You may revoke Triple Moon Goddess's access to your Google Account at any time at myaccount.google.com/permissions. The Google Calendar authorisation is held by Lisa Hagan and may be revoked by her the same way; revoking it immediately ends all Triple Moon Goddess calendar access.
If we change the way this application uses Google user data, we will update this section, update the effective date at the top of this policy, and notify affected users by email before the change takes effect.
Our databases, file storage, backups, encryption keys, and servers are all in the United States. If you use TMG from outside the United States, your data is stored in the United States. Third-party processors (Section V) may also process data in other countries under their own terms; Section II lists where each one stores it.
| Data Type | Retention Period |
|---|---|
| Journal entries & health data | Until you delete them (Section XII) |
| Email (identity vault) | Until deletion request or chart deletion |
| Notification log | Auto-deleted after 3 days |
| AI rate limit counters | Deleted automatically when their time window ends; older daily AI summary counters are deleted 30 days after their day |
| Record of which app a session opened, by day | Deleted automatically 1 year after the visit |
| Anonymous sign-in sessions on your device | Deleted automatically after 1 year without use; your charts stay until you delete them |
| Sign-in links | Single use; expire after 15 minutes and are then deleted automatically |
| Return links in our emails | Expire 72 hours after the most recent email that carried them, then deleted automatically |
| Practitioner invitations | Expire after 7 days, then deleted automatically |
| Our copies of emails carrying your data | Deleted from our mailbox after 30 days |
| Video readings and previews | Deleted from storage about 7 days after they are made; the recovery copies are removed automatically within 14 more days |
| Reading PDFs | Until you delete your data. A deleted PDF’s recovery copies are removed automatically within 14 days. |
| Data-access audit logs (which records were read, and by which signed-in account; when a record is looked up by email address, which happens when Lisa corrects a client's email and when you delete your data, and when you ask for a sign-in link, the entry also holds that address) | 6 years, then deleted |
| Application logs (no email addresses, access codes, or AI text since October 8, 2026; some entries from September 20 to October 8, 2026 hold an email address from a newsletter sign-up, are past their 30 days, and are waiting to be removed by Google) | 30 days |
| Practitioner records about a client | Until the practitioner deletes them, or their subscription is cancelled |
| FCM push tokens | Until push disabled or token becomes invalid |
| Database backups | Daily and weekly encrypted backups are kept for 98 days, with 7-day point-in-time recovery; a separate, isolated backup copy is kept for 31 days and is locked so it cannot be deleted early, and its recovery copy is removed automatically within about 9 more days. Backups hold no names, and email and birth data inside them stay encrypted. When you ask us to delete your data, it is removed from the live system immediately and ages out of the backups within these periods. |
| Website contact form messages | Not stored by our server; the email it sends to Lisa is deleted after 30 days (any reply conversation is kept as normal correspondence) |
| Session recordings | Kept locally on Lisa’s computer; deleted within one month of the session |
Your most sensitive data — your email, your birth data, and, for practitioner accounts, practitioner notes and psychological readings — is encrypted at rest with a dedicated Google Cloud Key Management Service (KMS) key. The key lives server-side only. Encryption and decryption happen inside our Cloud Functions; the key is never sent to, or held by, any browser.
Your email and your birth data are each stored once, in their own access-controlled vault. Email is encrypted in one vault and located only through a keyed one-way fingerprint (HMAC-SHA256 with a secret key held in Google Secret Manager) — it is never stored or searched as plain text in our database. Birth data is encrypted in a separate vault, keyed only by your anonymous access code. Neither vault is readable by the apps or by other users; only our server functions can decrypt, and only for a permitted purpose such as sending your chart by email.
Practitioner records about a client — notes and psychological readings — are encrypted with the same managed key on the server at the moment they are saved, and the plaintext is removed. Even if the database were fully compromised, these records would be unreadable, because the key is not in the database and never leaves the server. A practitioner can decrypt only the records of clients who accepted that practitioner's invitation: every decryption is checked on the server against the practitioner's signed-in account and the client's consent (or is made by the administrator).
The following data is protected by Firebase Security Rules rather than field-level encryption: natal chart outputs, client intake answers, intake match results, journal entries, and Soul module session data.
All data transmitted over HTTPS (TLS 1.2+). Data is encrypted at rest by default (Firebase/Firestore), with the sensitive fields above additionally encrypted under our own Cloud KMS key. Your birth data is write-only from the browser — it can be sent in to be stored, but no app or user can read raw birth data back; all chart, transit, and reading calculations run on our secure servers. API keys are stored in Google Cloud Secret Manager — never in code. Firebase Security Rules restrict database access to each authenticated user's own data, and a practitioner's access to a client's records to clients who gave consent. Practitioners and the administrator must use two-step sign-in and must have signed in within the last hour; signed-in sessions end after 30 minutes without activity. The admin portal is restricted to a single authorised account, and admin access to raw birth data (used only to correct a data-entry error) is audit-logged. Identity data and health data are held in separate collections — no single record contains both.
If a personal data breach occurs, we will act without undue delay to investigate and contain it. Where your personal information is affected, we will notify you, and any regulator, as required by applicable state breach-notification laws, including California Civil Code § 1798.82, without unreasonable delay. Because your identity data and your health data are held in physically separate Firestore collections, a breach affecting one does not necessarily expose the other.
We do not use advertising cookies or tracking pixels. We use browser local storage and sessionStorage only for strictly necessary app functions:
| Key / Purpose | Storage type | Who it applies to |
|---|---|---|
| Access code (session continuity) | localStorage | All users |
| Consent decision and timestamp | localStorage | All users |
| Firebase authentication session cache | localStorage | All users |
_grecaptcha — set by Google reCAPTCHA for its check that a person is using the page (Section V). | localStorage | All app users |
firebase-app-check-database — the App Check token that shows our servers a request came from our own page. It expires within an hour. | IndexedDB | All app users |
| Widget email preference (phone widget only) | localStorage | Widget users |
tmg_minor_chart — natal chart data for the under-18 chart experience. Device-local only; nothing is stored on any TMG server. | localStorage | Users under 18 only |
tmg_anthropic_key_enc and the tmg-ai-key database — your own Anthropic API key, if you add one, encrypted with a key that never leaves this device. | localStorage and IndexedDB | Users who add their own AI key |
tmg_ai_dialog_noticed — records that the Journal AI Dialog privacy notice has been shown this session. | sessionStorage | Journal users who use AI Dialog |
tmg_practitioner_summary_noticed — records that the Practitioner AI Summary privacy notice has been acknowledged this session. | sessionStorage | Practitioners with AI summaries enabled |
tmg_practitioner_dialog_noticed — records that the Practitioner AI Dialog privacy notice has been shown this session. | sessionStorage | Practitioners who use AI Dialog |
tmg_tongue_ai_noticed — records that the Tongue Analysis privacy notice has been accepted this session. | sessionStorage | Journal users who use Tongue Analysis |
tmg_soul_dialog_noticed — records that the Soul Pattern AI privacy notice has been accepted this session. | sessionStorage | Practitioners who use Soul Pattern AI |
tmg_synastry_dialog_noticed — records that the Synastry AI privacy notice has been accepted this session. | sessionStorage | Practitioners who use Synastry AI |
tmg_remedy_summary_noticed — records that the Remedy AI privacy notice has been accepted this session. | sessionStorage | Practitioners who use Remedy AI |
No third-party tracking cookies are used. Google reCAPTCHA may also set its own security cookie on google.com, under Google's Privacy Policy. Apart from the reCAPTCHA and App Check entries, which are used for Google's check, none of the above keys are shared with any third party. SessionStorage keys expire automatically when the browser tab closes.
The full TMG platform — Health Journal, Tea Moon, Health Blueprint, and practitioner apps — is intended for adults aged 18 and over. Readings are for adults only. We do not knowingly store personal data from children under 13. If you believe a child under 13 has submitted data to us, please contact Lisa@TripleMoonGoddess.com and we will delete it immediately.
The main natal chart app offers a limited, age-appropriate experience for anyone whose birth date shows they are under 18, with parental or guardian consent confirmed before any chart is generated. This experience is designed with privacy as the default: no account is created, no email is collected, and nothing is stored on any server. The natal chart is calculated using our Swiss Ephemeris service (birth date, time, and coordinates are transmitted for computation only and not stored by TMG; the birthplace name is turned into coordinates by OpenStreetMap Nominatim) and stored locally on the user's device under the key tmg_minor_chart (see Section X). Our server refuses to store the birth data of anyone under 18, except when Lisa records a chart herself, in person, after a parent or guardian has given consent. The chart can be cleared at any time by tapping "New Chart." Secondary apps — Health Journal, Tea Moon, Health Blueprint, and the practitioner apps — are not available to users under 18.
Parental or guardian consent is confirmed within the app before chart generation for any user whose birth date indicates they are under 18. By providing consent, the parent or guardian confirms they have reviewed and agreed to this privacy policy on behalf of the minor.
These rights apply to everyone who uses our services, wherever you live:
California residents (CCPA / CPRA) have the rights above: to know, delete and correct, to opt out of sale (we do not sell data) and to non-discrimination. Categories collected: identifiers, health information, internet/electronic activity (which of our apps you used, and when). Sold or shared for advertising: No. Residents of other states with privacy laws have the same rights. Washington, Nevada and Connecticut residents: see also our Consumer Health Data Privacy Policy.
The Integrative Practitioner, Soul Pattern, Constitutional Health, and Relationship Advice apps are separate paid-tier applications. A practitioner works only with clients who chose to share their records.
A practitioner invites a client by entering the client's email address. If that email already has a chart with us, the client receives an invitation that works once and expires after 7 days. The client signs in with a single-use link sent to that email and chooses to share their records. Only then can the practitioner see anything. The invitation and the consent are recorded with the client's email encrypted under our managed Cloud KMS key. Lisa, as administrator, may also add a client she reads for directly.
Once a client has shared their records, the practitioner sees the client's email address, the chart-derived outputs (sign placements, house positions, constitutional profile, pattern group scores, and comparison signals), relationship charts with another client who has also shared their records, intake answers, and Soul questionnaires. The practitioner sees the client's journal only while the client's "I'm working with a practitioner" setting is on. Practitioners never see the underlying birth date, time, and place, and they do not enter birth data.
Practitioners may write notes, psychological readings, results, and follow-ups about a client who has shared their records. Notes and readings are encrypted with our managed Cloud KMS key on the server at the moment they are saved. A practitioner can delete their own records about a client at any time; they are also deleted automatically when the practitioner's paid subscription is cancelled. The client's own data stays with the client.
Practitioner AI runs only on the practitioner's own Anthropic API key, directly from the practitioner's browser to Anthropic. It receives the client's chart placements, scores, intake answers, journal entries and the practitioner's notes, labelled only "CLIENT" — never the client's name, email, or birth date, time or place. See Section IV.
Soul module session records are kept under the client's anonymous access code, never under a name or email, and are deleted when the client deletes their data or the practitioner deletes their records. No name, email, birth date, birth time, or birth location would be included in any published or shared research output.
We will update this policy when our data practices change. Material changes will be communicated via an updated notice on the consent screen within the app and an updated effective date at the top of this document. Continued use of the app after a material change constitutes acceptance. Where legally required, we will re-obtain explicit consent.
For any privacy-related question, data request, or complaint:
Triple Moon Goddess
Lisa Hagan
3654 Thornton Ave, Unit #748
Fremont, CA 94536
United States
Email: Lisa@TripleMoonGoddess.com
If you are not satisfied after an appeal (Section XII), you can contact your state attorney general or, in California, the California Privacy Protection Agency (CPPA).