Privacy Policy
Last updated: 4 November 2026
What this means for you
Some of the information Healogy.ai handles is sensitive — your date, time, and place of birth (used to generate astrology and “cosmic DNA” content), the contents of your AI readings, and, if you choose to connect them, health metrics from wearables and a private “care record” you can share with a practitioner. We treat all of this as special-category / sensitive personal data, we ask for your explicit consent before collecting it, we encrypt the most sensitive parts, and you can export or delete it at any time. We never sell it.
1. Who we are
Healogy.ai (the “Platform”) is operated by Pairox Pty Ltd (ACN 154 477 728), a company incorporated in New South Wales, Australia (“Pairox,” “we,” “us,” or “our”). Pairox is the data controller / data fiduciary for the personal data described in this policy. Our Privacy Officer is reachable at privacy@healogy.ai.
This policy explains what personal data we collect, why, the legal bases we rely on, who we share it with, how long we keep it, and the rights you have. It applies to our website, mobile apps, and related services. It incorporates and is incorporated by our Terms of Service, our Cookie Notice, and our Medical Disclaimer.
2. Categories of personal data we collect
We collect the following categories of personal data. Sensitive / special-category categories are marked, and the legal basis for those is your explicit consent (see Section 4).
| Category | What we actually store | Storage & protection |
|---|---|---|
| Account & contact | Name, email, hashed password, phone number, profile image, language, timezone, and account roles. | Email and phone are stored in cleartext for delivery; your password is hashed; two-factor secrets and backup codes are stored separately and are never included in a data export. |
| Birth / astrology data (sensitive) | Date of birth, time of birth, place of birth (free-text location and geocoded latitude/longitude to seven decimal places), whether a birth time was provided, and timezone. | Stored on your user record; used as input to the astrology and AI-reading pipeline. Erased on account deletion. |
| Health-screening / intake (sensitive) | Your confirmation that you are 18+, your acknowledgement of the Medical Disclaimer, a health-content-consent timestamp, and any intake notes you record in your care record. | Acknowledgements are timestamped; intake notes live in the encrypted care record (below). |
| AI-reading inputs & outputs (may be sensitive) | The free-text question you submit, the reading cards returned, the cultural context selected, the prompt variant, and token counts. | Stored per-user, linked to your account, to render your reading history. Erased on account deletion. |
| Wearable health metrics (sensitive; only if you connect a device) | Steps, sleep duration, resting heart rate, heart-rate variability (HRV), active energy, heart rate, and workout records, with timestamps and source. | The detailed raw provider payload is encrypted at rest(AES-256-GCM); only coarse scalar values are kept in cleartext for trend charts. OAuth tokens for cloud sources are themselves encrypted at rest and are never logged. Every practitioner read of your data is audit-logged. |
| Care record (sensitive; consent-gated) | Longitudinal wellness entries — notes, session summaries, goals, intake — that you can keep private or share with a specific practitioner. | Encrypted at rest (AES-256-GCM); default visibility is private (you only); sharing requires an explicit, revocable consent grant per practitioner; every read is audit-logged. |
| Payment & tax data | Stripe customer / subscription / payment-method identifiers (tokens), wallet balance, transaction records, and — for practitioners — a hashed tax ID (only the last four digits in cleartext). When you pay by card or save a card, we check which country you are paying from, to apply our payment and sanctions rules. We use the country on your billing address or, if you have not given one, the country your network address points to. On our website, our hosting provider Vercel tells us that country; in our phone app, our own server looks it up in a country list from DB-IP that it holds itself, so no other company looks up your address. We keep neither your network address nor that country for this check, except with a request to start Premium straight away or a withdrawal from Premium, where the country decides whether EU, EEA and UK withdrawal rules apply. When you buy something, we also keep the country your network address points to with the record of that purchase (see the usage and analytics row in this table). | We never see or store your full card number — Stripe handles all card data (see Section 5). |
| Practitioner application (only if you apply to offer services) | The answers you type into the application form, and the files you upload with it: any certificates or licences you add and, where we ask for it, a photo or PDF of your government ID. Applications sent before 5 November 2026 also asked for a government ID number; we kept only a coded copy of it, never the number itself. | The files are kept in private storage that has no public web address. Only Healogy.ai staff with an administrator account can open a file, through a link that works for 60 seconds, and a record is kept every time a file is opened. You cannot open a file again from your own account after you upload it. Section 7 says how long we keep them. |
| Communications & device data | Messages between you and practitioners, push-notification device tokens, and the mobile number, text message consent and channel preferences used for text messages and reminders. | Used to deliver the service and the reminders you opt into. |
| Usage & analytics | Product-analytics events and standard request/serving data (e.g. IP address, device and request metadata). When you create an account or buy something, we save the country your internet connection comes from (only the country, never your address or exact location), so we can see which countries our members are in and plan where to support next. For a purchase, we keep it with the record of that purchase. This is part of creating your account or buying, so it does not depend on your cookie or analytics choice. | In your browser, analytics run only if you agree to the “analytics” cookie category. If you agree, our servers also send our analytics provider the AI readings you start, finish and rate, steps toward upgrading, card activity, bookings and their cancellations, and event ticket cancellations, under your account number. With your consent we also save the campaign tags of the first and the most recent link that brought you to our site with your account when you sign up or sign in. To count sign-ups and payments, our servers tell our analytics provider, under your account number, when an account is created (with those campaign tags, if you agreed to them) and when a payment or refund is made (the amount, currency and plan, never campaign tags); we do this on the basis of our legitimate interests, and this count does not depend on your cookie choice. We never send it your email address. Our phone app sends no analytics (see Section 5). See our Cookie Notice. |
3. How and why we use your data (purposes)
- To provide the Service. Create and manage your account, generate AI readings and astrology content from your birth data, facilitate bookings and live video sessions with practitioners, and operate messaging.
- To process payments. Take payments, manage subscriptions and wallet balances, pay practitioners, and handle refunds and disputes.
- To send you communications you ask for. Transactional email, and SMS or WhatsApp reminders where you opt in. If you turn on text messages, we send them through Twilio to the mobile number you give us. We never share or sell your mobile number or your text message opt-in with third parties or affiliates for their marketing. If you reply STOP, we keep that number on a do-not-text list so we never text it again, even after you delete your account.
- To keep the Platform safe. Detect and prevent fraud, abuse, and security incidents.
- To meet legal obligations. Tax, financial-record-keeping, and consumer-protection requirements.
- To improve the Platform. We use analytics in your browser and apps only where you have agreed to them, and our servers count sign-ups, AI readings, upgrade steps, card activity, bookings, event tickets and payments. We do not use your readings, messages, care-record content, session recordings, or wearable data to train AI models (see Section 4).
Support replies and AI
Replies to the support emails and messages you send us may be written by our AI assistant. Every such reply is checked automatically before it is sent, and a reply written by AI says so. Before your message reaches the AI, names, email addresses, phone numbers, links and long runs of digits are masked. Messages about a crisis are never sent to it. The providers involved are listed in Section 5.
When you call or message the practitioner support line, the care desk checks the number against the phone numbers on practitioner accounts to route the request; a match is never treated as proof of who you are, and account matters are answered only by email to the account’s own address.
Automated decisions
Computer programs, including AI, make some decisions about your support conversations: they answer routine support questions, close messages that are obviously spam, and close a conversation that has been answered once 7 days pass without a reply from you. Everything else is passed on for review. You can ask for any decision to be reviewed. To ask, reply to the conversation or email support@healogy.ai.
Rules and an AI check decide practitioner applications. An application that passes every rule is approved, one with a missing detail is asked for more information, and anything the rules cannot confirm is decided by hand. The AI check reads only the text typed into the application form, never ID documents or other files, and it can only send an application to be decided by hand, never approve one. You can ask us to look at any decision again: reply to the decision email or email support@healogy.ai.
Practitioners’ published business contacts
We hold lists of independent practitioners’ business contact details. Before we contact anyone, we check the address or profile on the practitioner’s own page or public listing, and we note that page and the date we checked it. We use these details only to invite the practitioner to join Healogy.ai.
- We write at most twice.
- With no reply, we delete the practitioner’s details within 90 days of the first message.
- A reply of “stop” deletes them. Our mail provider’s recovery copy clears on its own schedule, usually within a few weeks.
- Either way, we keep only a scrambled copy of the email address, so we never write to it again.
- A practitioner who replies and then goes quiet is deleted after 180 days with no activity on their record.
Questions about this go to support@healogy.ai.
4. Legal bases for processing
Where the EU/UK GDPR applies, we rely on the following legal bases:
- Explicit consent (Article 9(2)(a)) for all health and special-category data — your spiritual, religious, and philosophical beliefs (the belief systems and traditions you choose to follow), birth/astrology data, AI-reading inputs, wearable health metrics, care-record entries, and health-screening data. You can withdraw this consent at any time (Section 7).
- Performance of a contract (Article 6(1)(b)) — to provide the account, bookings, and payments you have signed up for.
- Consent (Article 6(1)(a)) — for analytics/marketing cookies and optional communications.
- Legitimate interests (Article 6(1)(f)) — for fraud prevention and platform security, and for counting sign-ups, AI readings, upgrade steps, card activity, bookings, event tickets and payments to understand how the service is used, balanced against your rights.
- Legal obligation (Article 6(1)(c)) — for tax and financial record-keeping.
For users in Australia, we handle personal and sensitive information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (sensitive information is collected only with consent, per APP 3). For users in India, we process personal data on the basis of consent under the Digital Personal Data Protection Act, 2023 (DPDP Act). For users in California, we honor CCPA/CPRA rights; we do not sell your personal data.
No AI training on your personal data. We do not use your readings, messages, care-record content, session recordings, or wearable data to train, fine-tune, or develop AI/ML models without your separate, specific, written consent. We may use aggregated, anonymized data that does not identify you for service improvement.
5. Service providers (sub-processors)
To run Healogy.ai we share the minimum necessary data with the service providers below. Each provider we contract with is bound by a data-processing agreement and may only use the data to provide its service to us. Your browser's push service is not one of them: the company that makes your browser runs it. We never see or store your full card number — card data is entered directly with Stripe.
| Provider | What it does for us | What it receives | Where it handles your data |
|---|---|---|---|
| Vercel | Hosts our website | Your network address, browser and device details, and the pages you ask for. | United States (Virginia). Pages may reach you from the Vercel location nearest you. |
| Railway | Runs the servers behind our phone apps and our background tasks | What our phone apps send us, and the data each background task needs. | United States (Virginia) |
| Neon | Our main database | The account data described in Section 2. | United States (Virginia) |
| Upstash | Short-term storage that limits repeated requests and holds tasks waiting to run | Your account number or network address, and the data a task needs while it waits to run. | United States (Virginia) |
| Stripe (including Stripe Connect) | Payments, payouts, subscriptions and practitioner identity checks | Card and payment details, which you enter directly with Stripe (we never receive your full card number), billing amounts, customer and subscription identifiers, and, for practitioners, payout and tax reporting details. For practitioners who verify their identity with Stripe Identity, Stripe also receives the identity document and the selfie they submit, and their account number with us. | United States |
| Airwallex (Airwallex Pty Ltd) | Sends payouts by bank transfer to practitioners in countries Stripe cannot pay out to | For practitioners paid this way: their name and email address, the bank account details they give us, the payout amount and currency, and their bank's country. | Australia, with hosting in Singapore, Belgium, the Netherlands, Japan, Malaysia and the United States |
| Anthropic (Claude) | AI readings and the AI assistant | The questions you ask in a reading and your chats with our AI guides, assistant, concierge and help chat, with the earlier messages of that chat; the photo you take for a camera reading; the dream journal entries you ask it to interpret; your first name and your birth date, time and place, or a summary of your birth chart, when a reading, a program day or your daily briefing uses them; to make a cosmic DNA, compatibility or roast card, the name and birth date, time and place you type in, including those you type in for the other half of a compatibility card; the beliefs and practices you have told us about; and, for practitioners, the listing text they ask it to help write. Used only to produce the answer. | United States |
| Anthropic (Claude), for customer care | Drafts and checks replies to the support emails and messages you send us, and to what you say or write on the practitioner support line | The text of your support emails and messages. Names, email addresses, phone numbers, links and long runs of digits are masked before it reads them. It does not train on this data. We have asked Anthropic to keep none of this data (zero data retention); until that is granted, Anthropic's standard API retention applies. Messages about a crisis never reach it. On the practitioner support line: the text of what you say on calls and write in messages, to pick or write a reply; words the care desk's crisis keyword check flags are not sent to it. | United States |
| Anthropic (Claude), for the practitioner assistant | Helps a practitioner prepare for and follow up a session (only if enabled) | A client's first name and booking notes, and the practitioner's session notes. | United States |
| Anthropic (Claude), for checking practitioner applications | Checks the text of a practitioner application before a decision | Practitioner application form text: name, bio, specializations, qualifications, certifications, traditions, the declared practitioner type, licence type, issuing body and registration country (never the licence number, ID documents or other uploaded files). Used only to check that an application adds up. | United States |
| Anthropic (Claude), for content moderation | Checks the text members and practitioners post against our community guidelines | The text of reviews and of practitioners' responses to them, community posts, replies and moon circle messages, and the text of a direct message only when it is reported. Never photos or other attachments, and never an unreported direct message. Practitioners' profile, listing and application text is checked by our own rules, not sent to this provider. Used only to decide whether the text follows our community guidelines; it never writes a reply. | United States |
| Supabase | Stores support conversations | Your support conversations with us. The text of each message is encrypted with keys Supabase does not hold. | Australia (Sydney) |
| Fly.io | Runs our customer-care system | Your support emails and messages while our customer-care system handles them. | Australia (Sydney) |
| Pushover | Sends alerts about our customer-care system | Support ticket numbers only, never message content or contact details. | United States |
| PagerDuty | Sends alerts about our customer-care system | Support ticket numbers only, never message content or contact details. | United States |
| Meta (Instagram and Messenger) | Carries the messages you send us on Instagram or Messenger | The messages you send us there, and the account you send them from. | Ireland (EU/UK users) and the United States |
| Resend | Sends our emails | Your email address and the message, such as receipts, reminders, data export links and account notices. | United States (Virginia) |
| Migadu | Hosts our healogy.ai mailboxes | The emails you send to any healogy.ai address. | Switzerland and the European Union |
| Twilio | Text and WhatsApp messages: your daily briefing and booking reminders, only if you turn them on; and calls and WhatsApp messages to the practitioner support line | Your mobile number and the message. On the practitioner support line: your number and your messages and, on calls, your voice, which Twilio and its speech provider, Google, transcribe in real time; calls are not recorded and Twilio keeps no transcript of a call. Twilio keeps its own record of every message to or from the line, WhatsApp messages included, with its text: in view in its console and API for 13 months, and in its backups after that. | United States |
| WhatsApp (Meta) | Delivers WhatsApp messages: your daily briefing and booking, class and event reminders, only if you turn them on (only if enabled) | Your mobile number and the message text: your daily briefing and your booking, class and event reminders. | Ireland (EU/UK users) and the United States |
| WhatsApp (Meta), for the practitioner support line | Delivers WhatsApp messages between practitioners and the practitioner support line | Your WhatsApp number and the text of the messages you send to and receive from the support line. | Ireland (EU/UK users) and the United States |
| PostHog | Product analytics | In your browser, only if you agree to analytics cookies on our website. Then it receives how you use the site and, from our servers, the AI readings you start, finish and rate, steps toward upgrading, card activity, taps on crisis support, the age and medical-advice step before sign-up, bookings and their cancellations, and event ticket cancellations, under your account number (or a random visitor number if you are not signed in). Separately, to count sign-ups and payments, our servers tell it, under your account number, when an account is created on our website or in our phone app and when a payment or refund is made (the amount, currency and plan, never campaign tags); we do this on the basis of our legitimate interests, and this count does not depend on your cookie choice. Never your email address, name or phone number. Our phone app itself sends it nothing. | Germany (Frankfurt), in the European Union |
| Sentry | Error reports from our website and phone apps so we can fix faults | Details of the fault, the page or screen it happened on, your browser or device, your network address and your account number. On our website, a recording of the page in the moments before the error, with all text masked and images and media blocked. | United States |
| Cloudflare R2 | Stores files and data exports | Files you upload, the files you add to a practitioner application, and your data export, which sits behind a link that expires. | United States |
| LiveKit | Live video for practitioner sessions | The live sound and picture of your session, and connection details. | United States |
| Google Maps Platform | Birth place search | What you type in the birth place search, the place you pick and its map preview, and your network address. Sent only when you use the search. | United States and other countries where Google has data centres |
| Google Fonts | Fonts and icons on our website | Your network address and browser details, each time a page of our website loads. | United States and other countries where Google has data centres |
| Google and Apple (sign-in) | Sign in with Google or Sign in with Apple, only if you choose it | That you are signing in to Healogy.ai, and your network address. They send us your name and email address. | United States |
| Expo | Sends notifications to our phone apps and delivers app updates | Your phone's notification token and the notification text. Each time our phone app opens it checks Expo for an update, which sends your network address and device and app details. | United States |
| Apple and Google | Deliver notifications to your iPhone or Android phone | Your phone's notification token and the notification text. | United States |
| RevenueCat | Manages purchases made in our phone apps | Your account number and the purchases you make through the App Store or Google Play. | United States |
| Your browser's push service | Delivers website notifications, only if you allow them. The company that makes your browser runs it; it is not a company we contract with. | The notification we send you (its title, text and link), encrypted so that only your browser can read it, and an anonymous push address your browser creates. | Set by the company that makes your browser |
| Oura, Apple Health, Google Fit (only if you connect them) | Wearable data sources | We receive health metrics from these services under the access you grant. We do not send your data to them. | Not applicable: we only receive data from them |
| Axiom | Stores our server logs (only if enabled) | Records of requests to our servers, which can include your account number and network address. | United States |
| Vercel Web Analytics | Counts page visits (only if enabled) | Pages visited and browser details, without cookies. | United States |
| OpenAI | Turns the words you search for into search data, and is our backup AI provider when Claude is unavailable (only if enabled) | The words you search for when you look for an AI guide, and the messages of your chats with our AI guides, to make them searchable; and, if we switch it on as a backup, the same text and context we would send to Anthropic. | United States |
| Cloudflare Turnstile | Tells people from automated abuse on card generation (only if enabled) | Your network address and browser signals. | United States |
| hCaptcha | Tells people from automated abuse on card generation (only if enabled) | Your network address and browser signals. | United States |
| Google reCAPTCHA | Tells people from automated abuse on card generation (only if enabled) | Your network address and browser signals. | United States and other countries where Google has data centres |
| Meilisearch | Search (only if enabled) | The words you search for. | France |
| Google Calendar | Adds your bookings to your calendar, only if you connect it (only if enabled) | Booking times and titles. | United States and other countries where Google has data centres |
| Microsoft Outlook Calendar | Adds your bookings to your calendar, only if you connect it (only if enabled) | Booking times and titles. | United States |
| QuickBooks and Xero (practitioners only, if they connect them) | Accounting export (only if enabled) | A practitioner's earnings and fee records. | United States (QuickBooks) and New Zealand (Xero) |
Some companies handle your data under their own privacy policies, not ours: Google or Apple when you sign in with them, the App Store or Google Play when you buy in our phone apps, and Meta for the messages you send us on Instagram or Messenger and the messages we send you on WhatsApp.
6. How we protect and limit use of sensitive data
- Encryption at rest. Care-record entries and the rich wearable payloads are encrypted with AES-256-GCM. Wearable OAuth tokens are encrypted at rest and are never written to logs.
- Consent-gated sharing. Your care record is private by default. A practitioner can only see an entry if you grant a specific, revocable consent.
- Audit logging. Every practitioner-side read of your care record or wearable data is recorded so you can see who accessed what, and when.
- Purpose limitation. Practitioners may use information you share only to deliver your sessions — never for marketing, for other clients, or to train AI models.
7. How long we keep your data (retention)
We keep personal data only as long as needed for the purpose you provided it, then delete or anonymize it — except where the law requires us to keep specific records for a fixed period. The detailed windows are set out in our Terms of Service §10; in summary:
- Tax and financial records — 5 years (Australian tax law).
- Billing and transaction records — 3 years (chargeback/dispute window).
- Security event logs (sign-in, sign-up and password-reset attempts and administrator data exports, with the IP address and device string of each) — 12 months, then automatically deleted.
- Security incident records (when our systems detect an attack: the rule that fired, attempt counts and the source network shortened to its first three IPv4 blocks or the first 48 bits of an IPv6 address) — kept in our tamper-evident audit trail, which cannot be edited or deleted.
- Fraud and abuse records — 12 months.
- Grievance and dispute correspondence — 3 years.
- Session recordings — we do not record live sessions or classes. Audio and video are streamed in real time through our live-video provider and are not saved. A practitioner may record a session themselves only with your explicit consent; if they deliver that recording to you through Healogy.ai’s post-session delivery, it is stored with that session’s post-session files. If we ever offer recording, it will be off unless both you and the practitioner agree to it at the time, and we will update this policy, including how long recordings are kept, before any session is recorded.
- Post-session notes and files (what a practitioner delivers to you after a session) — kept while your account is active so you can go back to them; deleted when you delete your account, the files within 2 days. If the practitioner deletes their account, what they delivered to you stays available to you. A file uploaded but never attached to a delivery is deleted within 2 days.
- Practitioner application documents (your government ID and any certificates or licences you upload) — kept while your application or your practitioner account exists. If your application is declined we still keep them; we do not yet delete them on a set date after a decision. When your account is deleted (Section 8), we remove the documents from your application and delete the stored files within 9 days. A file that is uploaded but not attached to any application is deleted within 9 days. When your account is deleted we also delete the answers you typed into the form, the coded copy of your government ID number, if you gave one, and the reviewer’s notes kept with your application and documents. We keep a record that an application was made, its decision and its dates. Our staff activity log, which cannot be edited, keeps each review decision with the reviewer’s note. If you were approved as a practitioner, your practitioner profile and earnings records are not yet removed automatically when your account is deleted; email privacy@healogy.ai and we will finish it.
- Camera scans (palm, face and the other photo readings) — the photo is sent to our AI provider (Anthropic, see Section 5) to produce the reading and is never saved on our servers. The reading it produces (the analysis and its clarity score) is kept for 90 days, then automatically deleted. If a reading is flagged by our safety checks or reported to us, an excerpt of it is kept with that safety review. A minimal record that a scan happened (its type and date) is kept while your account is active and deleted with it.
- Gift recipient details (the name, email address and message entered for a gift) — if a gift checkout is never paid for, deleted 30 days after it began; on a paid gift, deleted 30 days after the gift expires; and removed straight away if the person who redeemed the gift deletes their account. The payment record itself is kept as described above.
- Account/profile data, AI-reading history, birth/astrology data, care-record entries, and wearable samples — kept while your account is active; deleted or anonymized on account deletion, subject only to the legal-hold carve-outs above.
8. Your data protection rights
Depending on where you live, you have some or all of the following rights over your personal data. We honor these for users in the EU/EEA and UK (GDPR / UK GDPR), India (DPDP Act, 2023), Australia (Privacy Act 1988 / Australian Privacy Principles), and California (CCPA/CPRA), and we extend them to all users as a matter of policy.
- Access. You can ask for a copy of the personal data we hold about you.
- Portability. You have the right to receive the personal data you provided to us in a structured, commonly-used, machine-readable format (we provide JSON), and to reuse it elsewhere. Where you ask and it is technically feasible, we will help you move it to another service. This applies to data you provided that we process on the basis of consent or contract.
- Correction. You can ask us to correct inaccurate or incomplete data, including from within your account settings.
- Erasure (“right to be forgotten”). You can delete your account and ask us to erase your personal data. A 30-day grace period applies, during which you can cancel by signing in; after that, your data is permanently erased except for the limited records the law requires us to keep and the items Section 7 says are kept.
- Restriction & objection. You can ask us to restrict, or object to, certain processing.
- Withdraw consent. Where we rely on your consent (including for health, wearable, and astrology/birth data), you can withdraw it at any time — for example, by disconnecting a wearable, revoking a care-record share, or deleting the data. Withdrawal does not affect processing that already happened.
- Do Not Sell or Share (California). We do not sell your personal data. You can exercise the “Do Not Sell or Share My Personal Information” control from the cookie preference centre in our footer.
- Complain. You can complain to us (privacy@healogy.ai, attn. Privacy Officer) or to your local data protection authority — for example, the Office of the Australian Information Commissioner (OAIC), your EU/EEA supervisory authority, the UK ICO, or the Data Protection Board of India.
How to exercise your rights. Signed-in users: Settings → Privacy. Anyone: email privacy@healogy.ai or use the controls on our Your privacy rights page. We respond to verified requests within 30 days. We may ask you to confirm your identity before acting on a sensitive request.
9. Getting a copy of your data (right of access and data portability)
You can ask us for a copy of the personal data we hold about you at any time. If you have an account, go to Settings → Privacy → Request my data; if you don’t, contact us at privacy@healogy.ai.
Format. We provide your data in a machine-readable format: a ZIP archive containing a structured JSON file (export.json) with your data, plus a plain-language PDF summary (summary.pdf). The JSON format means you can read, search, or import your data into another service.
What’s included. Your export contains your profile (with security secrets such as passwords removed); your messages (sent and received); your readings, signature and cosmic-DNA profiles, generated cards, daily briefings, angel-number, crystal, manifestation and dream-journal entries, and yearly summaries; your AI assistant sessions, conversations and feedback; transaction and billing records; gifts you sent and gifts you redeemed; post-session notes and files delivered to you (and, if you are a practitioner, those you delivered); your notifications, favourites, camera-scan records and feature-test assignments; your connected accounts, calendars, wearable connections and push-notification devices (without their access tokens); your care-record consents and the log of who viewed your wearable data; — decrypted for your own access — your care-record entries and wearable health samples; and the security events on your account (sign-in, sign-up and password-reset attempts, and administrator exports you ran) — the event, its time and its reason; the IP address and device of each attempt are withheld because the attempt may have been made by someone else. Because some categories can be very large, generous per-category limits apply; if your export reaches a limit, the included summary tells you so and how to request the remainder.
Practitioner application. If you applied to offer services, your export includes your application: the answers you typed, its status and dates, the reviewer’s notes, and a list of the documents you uploaded with the result of each check.
What is not included. The export lists the documents you uploaded with a practitioner application but does not contain the files. To get a copy of a file, email privacy@healogy.ai.
Timeframe. We respond to verified requests within 30 days (consistent with GDPR Articles 15 and 20, the DPDP Act, and equivalent laws), and may extend this where the law permits for complex requests, telling you why. Your download link is available for 7 days, after which you can request a fresh one.
Sensitive data. Your care record and wearable readings are health data. We decrypt them in your export only for you; the export is delivered over a secure, time-limited link.
10. Where your data is handled
Pairox Pty Ltd is an Australian company. Our main database and the servers behind our website and phone apps are in the United States (Virginia), so most of the personal data we hold is stored and processed there. Our customer-care system and the support conversations it keeps are in Australia (Sydney). The table in Section 5 shows where each provider handles your data. Where we transfer personal data internationally, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses (2021/914) or equivalent mechanisms.
Your personal data is likely to be sent outside Australia. The providers in Section 5 handle it in these other countries and regions: United States, Ireland, Switzerland, European Union, New Zealand, France, Singapore, Belgium, Netherlands, Japan, Malaysia.
Some providers also handle it in places that depend on where you are or what you use: Google's data centres in other countries, the Vercel location nearest you and your browser maker's push service.
11. Children
Healogy.ai is for adults. You must be 18 or older to use the Platform. We do not knowingly collect personal data from anyone under 18; if we learn that we have, we delete it.
12. Changes to this policy
We may update this policy from time to time. We will post the updated version here with a new “Last updated” date and, for material changes, notify you by email or in-app notice.
13. Contact
Privacy and data matters: privacy@healogy.ai (Privacy Officer). General support: support@healogy.ai. You can also use our contact page or the Your privacy rights self-service controls.