Privacy Policy

Version 2.4 · Effective 10 Nov 2026 · Last updated 10 Nov 2026

About this policy. This document is written in two voices. The italic summary at the top of each section says what the clause actually means in plain language. The clause itself, in plain prose underneath, is the binding text. If anything in the summary conflicts with the clause, the clause governs.

This policy explains what data InnerVisions collects from you, why, what we do with it, who we share it with, where it lives, and what control you have. It is written by Metaxu Pty Ltd (ABN 67 698 120 400) trading as InnerVisions App ("InnerVisions", "we", "us", "our").


The four commitments

Before the detail, here is what InnerVisions promises about your data. These are not aspirations. They are reflected in the architecture and in the rest of this policy.

1. We do not sell your data. Not to advertisers. Not to data brokers. Not to anyone.

2. We do not train AI models on your data. Not our own. Not third parties'. Your entries are processed to provide features you've asked for, and that is all.

3. What you write and say is encrypted with AES-256-GCM at rest. The encryption key is stored as a server-side secret in our edge function environment. It is never sent to your device or to any third party. The full text of your entries is not readable in plaintext from our database. Some things are stored without that encryption, behind access controls: the AI's short title, summary and notes on each entry (which can include your own words), and its readings and reviews. Section 3 has the list. Decryption happens only inside our own server code, and only to deliver features you have requested.

4. You can see, export, and delete your content. Your profile is visible to you. Your content is exportable. Deletion is real and we cannot reverse it. Section 10 lists the little we keep afterwards, and why.

The rest of this document is how those commitments are kept.


1. What we collect

Two categories: what you give us, and what we observe so the product works. We keep both as small as we can.

Information you provide directly:

Information we collect automatically:

What we do not collect:


1A. Waitlist

In plain terms: if you hold a place, we keep your email to write to you once, when there is room. Nothing else. Ask and we delete it.

Waitlist. When you hold a place on innervisions.app we store your email address, the date, the page you asked from and, if you followed a link from one of our social media profiles, which one, in our database (Supabase, Sydney). We send one confirmation email at the time, and one further email if and when we can offer you access. Both are sent through Resend. We do not add you to marketing communications, and we do not share the list. We keep waitlist entries until you are given access or for 12 months, whichever is sooner, unless you ask us to delete it earlier at privacy@innervisions.app. Where the GDPR or UK GDPR applies, our basis for this processing is your request (steps taken at your request prior to entering into a contract) and our legitimate interest in running a limited-access launch.


2. Why we use your data

To run the service, keep it secure, and improve it. Nothing else.

We use your data only for these purposes:

We do not use your data for advertising, profiling for sale, behavioural targeting, or any purpose outside running the service for you.


3. How your data is protected

Real encryption, real access controls, real key isolation. The technical details matter, so we're sharing them.

Encryption at rest. Your private content is encrypted using AES-256-GCM (authenticated encryption with a 32-byte key). The fields currently encrypted include: journal entries, sparks, notes, chat messages with Discuss, starred insights, client notes (in any future Practitioner feature), Guide artifacts, seed profile input, your profile (what InnerVisions has learned about you – themes, symbols, tone, the people you mention, your corrections), and session data.

What is not encrypted this way. The AI's structured notes on each entry – its short title, one-line summary, observations, themes and symbols, which can include your own words – MeaningMaker readings and Pattern Reviews are stored in our database without this field-level encryption. They are kept this way so that search and the lists in your journal work. They are protected by the access controls below, and they are deleted with everything else when you delete your account.

Key isolation. The encryption key is stored only as a server-side secret within our Supabase edge function environment. It is never transmitted to your device, included in API responses, or shared with any third-party service including OpenAI.

Server-side decryption. Decryption happens only inside our edge functions and only to deliver a specific feature you have requested. Ciphertext and encryption metadata are stripped from API responses before they reach your device.

Key versioning. Encrypted rows are tagged with a key version identifier (encryption_key_id) so we can rotate keys in the future. Our current production key is AES-256-GCM, rotated from a prior AES-192 key in April 2026.

Encryption in transit. All connections between your device and our infrastructure are encrypted using HTTPS/TLS. Both Supabase and Vercel enforce TLS at the network layer.

Access controls. Access to production systems is limited to authorised personnel and gated by per-user authentication. No person monitors your journal. Our admin tools cannot open anyone's entries, profile or readings: an admin sign-in sees account details and totals, never what you wrote or what InnerVisions wrote about it. Reading content would mean running code with our system keys, which we do only to help you at your request or to meet a legal obligation, and we keep a written record of when and why.

What this means in practice. The full text of your entries is not readable in our database without explicit decryption. To read it, an authorised person on our team would need to run code that decrypts it using the production key. The system is built this way deliberately.

A note on what this is and isn't. This is not zero-knowledge or end-to-end encryption. We hold the production encryption key on the server, which means we have the technical capability to decrypt your content. The protection here is enforced by architecture and process – by the fact that decryption requires authorised code execution, and that we have built the system to prevent casual or unauthorised access – not by mathematical impossibility. We are being transparent about this because the difference matters. Products that genuinely cannot read your content (Signal-style messaging, some password managers) operate on different architecture. InnerVisions does not.


4. AI processing

Your content is sent to OpenAI to run AI features. OpenAI does not train on it, and keeps it only as its API policies allow, including for abuse monitoring. We do not train on your data either.

What goes to OpenAI. When you trigger an AI feature – voice transcription, MeaningMaker, Pattern Review, Discuss, Guide artifact generation, or any future AI feature – the relevant decrypted content is sent over an encrypted connection to OpenAI's API for processing. The response is then stored against your account (Section 3 says which parts are encrypted). Saving an entry also sends its text to OpenAI, so the AI can organise it (its title, summary, symbols and reflection). As part of that step, the AI is also asked whether the entry shows signs of serious distress, so we can show you a link to support. The answer is not stored and no one at InnerVisions sees it.

OpenAI's data practices. OpenAI's API is configured not to train on the data we send, and is subject to OpenAI's published Enterprise Privacy commitments and API data usage and retention policies (including any abuse-monitoring exceptions documented in those policies). At the time of writing, that means OpenAI may keep the text we send for readings and replies, and its responses, for up to 30 days for abuse monitoring. Its published policy lists no such retention for audio sent for transcription. We rely on these commitments and policies as part of our processing arrangement with OpenAI. OpenAI's policies may evolve; we will update this section if material changes affect how your data is handled.

We do not train models on your data. We do not train our own models on your content. We do not provide your content to any third party for the purpose of training their models.

AI model evolution. The AI models we use evolve over time. We may switch to or add additional AI providers in the future. If we do so in a way that materially changes how your data is processed, we will update this policy and notify you.

Limits. AI processing has technical limits, can be wrong or inappropriate, and is not a substitute for professional advice (see ToS Section 5).


5. Automated decision-making and profiling

InnerVisions builds a structured "profile" of you over time – themes, symbols, communication style, life context. You can see it all, edit it, and turn it off.

What the profile is. As you use InnerVisions, the service builds a structured representation of you across time: recurring themes, symbols that reappear, your communication style, life context, and other patterns. This profile is used to give features continuity (so Pattern Reviews feel personal, Discuss remembers what came before, the Guide can speak to what's actually been arising for you).

On-by-default consent. When you complete the Seed Profile step in onboarding, profile memory is enabled by default. We have made this choice because continuity is core to the service. You retain full control:

When profile memory is disabled, no new profile updates occur and no profile context is injected into AI features.

Questions and objections. Wherever you live, you can ask us how a profile-driven feature produced a result, ask for a person to look at a specific output that troubles you (they will read only what you send or point them to), and object to your data being used for profiling. Contact privacy@innervisions.app (see Section 19).

What the profile is not. Your profile is not a clinical diagnosis, a personality assessment, a behavioural score, or a categorisation of you against other users. It is a personal index of what has appeared in your own material.


6. Analytics

We count which features get used so we can fix bugs and improve the product. We don't record your screen or your sessions.

Analytics. We use PostHog for product analytics. PostHog records pseudonymised events about how you use features (linked to your account ID, never your name or email) – for example, "user created an entry", "user viewed Pattern Review" – to help us understand usage patterns, find bugs, and prioritise improvements.

No session recording. We don't use session replay. Nothing records your screen, your typing, or what you read in the app.

No content in analytics. Analytics events describe actions, never content: no journal, chat, Guide, or profile text is ever included in an event.

Your control. You can opt out of analytics at any time by contacting privacy@innervisions.app.

Data residency. PostHog stores analytics data on its own infrastructure in the United States, separate from your encrypted journal content.

Our public website. On innervisions.app itself (the pages you see before signing in) we collect page views and a small number of anonymous interaction events (for example that a section was read or the waitlist form was opened) – no session recording, no surveys, no identification of who you are – and it runs without setting cookies. The analytics described above apply only inside the app, after sign-in.


7. Subprocessors

The third-party services we rely on to run InnerVisions. Each one is bound by a data processing agreement with us.

InnerVisions uses the following subprocessors. Each holds only the data needed for its function, and is contractually required to handle that data in line with applicable privacy law.

Subprocessor Purpose Data handled Location
Supabase Database, authentication, edge function runtime, file storage All account, content (encrypted), and metadata Sydney, Australia
OpenAI AI processing for transcription and content generation Decrypted entry content during feature requests (not used for training; kept only as OpenAI's API policies allow, including for abuse monitoring) United States
Vercel Application hosting, edge delivery Application code, request routing, no persistent content storage Global edge network
Stripe Subscription billing and payment processing Email, customer ID, payment method (held by Stripe, not us), subscription state United States / Ireland
PostHog Product analytics in the app; anonymous page-view and interaction events on the public website Pseudonymised event data in the app; anonymous events on the public website United States
Sentry Error monitoring in the app Technical error reports (error messages, page paths, browser details), your account ID. Configured to exclude journal content, request bodies and your email EU or US (depending on configuration)
Resend Authentication, waitlist and transactional email Email address, message content limited to auth and service notifications United States
Google Fonts Font files for the app's interface (inside the app only – our public website hosts its own fonts) IP address and browser details when the font files load; no account or content data Global (Google)
Fontshare (Indian Type Foundry) Font files for the app's interface (inside the app only) IP address and browser details when the font files load; no account or content data Global content delivery network
Cloudflare (Turnstile) The check on the sign-in page that keeps automated sign-ups out IP address and browser details when you sign in; no account or content data Global content delivery network

We will update this list when subprocessors change. If we add a new subprocessor that handles content data, we will notify you by email at least 14 days before the change takes effect.


8. Cross-border data transfers

Your encrypted journal lives in Sydney. Some processing happens elsewhere – OpenAI and Stripe in particular. We've structured this in line with privacy law.

Your encrypted journal content is stored in Australia (Supabase, Sydney region). However, some processing occurs in other countries:

Under Australian Privacy Principle 8, we take reasonable steps to ensure overseas recipients of your personal information handle it in line with the Australian Privacy Principles, through our data processing agreements with each subprocessor.

For EU/UK users, transfers of personal data outside the EEA or UK rely on Standard Contractual Clauses (or equivalent UK provisions) where the destination country is not deemed adequate.


9. Your rights

Access, correction, deletion, export, objection, withdrawal of consent. These are real rights and we will honour them.

Subject to applicable law, you have the right to:

To exercise any of these, email privacy@innervisions.app. We aim to respond within 30 days, or sooner where the law that applies to you requires it.

A note on data export. Once you export your content, it leaves InnerVisions' encrypted environment and becomes your responsibility to store and protect. Export formats may evolve over time; past exports remain valid but we do not guarantee that future versions of InnerVisions will import older export formats. You are responsible for maintaining your own backups after export.


10. Data retention and deletion

We keep your data while your account is open. When you delete your account, we delete your content – and we never bring a deleted account back.

Active accounts. We retain your data for as long as your account is active.

Account closure. When you close your account or request deletion:

Deletion is permanent. We don't restore deleted content. Export anything you want to keep before deleting.

When we may hold something back. If you have raised a complaint or legal claim with us, if we are investigating a security incident, or if a law requires it, we may keep the specific information needed for that purpose for a limited time, with restricted access, and then delete it. Where the law allows, we will tell you if this affects a deletion request.

Inactive accounts. We may delete or anonymise data from accounts that have been inactive for a long period (currently set at 3 years). We will email you before doing this, where we have a working email address.


11. Government requests and legal process

If we get a subpoena, court order, or other binding legal demand, we comply with the minimum necessary. We push back on overbroad requests.

If we receive a subpoena, court order, search warrant, or other valid legal process from a competent authority, we will comply as required by law. Our approach:

About encrypted content. Your content is encrypted at rest, but because we hold the key, content we are legally compelled to disclose can be provided in readable form. We review every demand, push back on overbroad ones, and disclose only what the demand requires.

We may publish an aggregated transparency report from time to time describing the number and types of legal requests received.


12. Data breach notification

If something goes wrong, we'll tell you. Fast. Within the timeframes the law requires.

If we become aware of a data breach that is likely to result in serious harm or a risk to your rights:


13. Marketing communications

We send service emails because we have to. We send marketing only if you separately ask us to.

Essential service emails (authentication links, billing notifications, security alerts, material policy changes) are part of the service. You cannot opt out of these without closing your account.

Marketing communications (product updates, feature announcements, content, newsletters) are separate. We send these only if you have separately opted in, and you can unsubscribe at any time from a link in any email or from your account settings.

Emails during your trial. While you are on a free trial we send a small number of emails about using InnerVisions and about your trial ending. Each one says how to stop them.

We do not share your email address with third-party marketers.


14. Cookies and similar technologies

We use the minimum cookies needed to make the service work, plus analytics that you can opt out of.

We use cookies and similar technologies for:

We do not use advertising cookies, third-party tracking pixels, or behavioural retargeting cookies.

Our public website (innervisions.app, before you sign in) is cookieless: its analytics set no cookies or similar technologies on your device. The cookies and storage above exist only inside the app (my.innervisions.app), from the sign-in page onward.

We do not show a cookie banner: we set no advertising or cross-site tracking cookies.


15. Children

InnerVisions is for adults. We do not knowingly accept users under 18.

InnerVisions is not intended for, and is not directed at, anyone under the age of 18. We do not knowingly collect data from minors. If we learn that an account is held by a person under 18 – for example because they, a parent or a guardian tell us – we will close it and delete the associated data.

If what you write says you are under 18, the AI features show one short line pointing to people who can help (our support page, which lists Kids Helpline) instead of a reading, review or reply. An entry you save stays as you wrote it, without a reading. The answer to that check is not stored, logged or shown to anyone at InnerVisions.

If you are a parent or guardian and believe your child has provided us with personal information, please contact us at privacy@innervisions.app.


16. Death or incapacity of an account holder

We don't transfer journal access to anyone after death. Journals are private during life and private after.

InnerVisions journals are deeply personal. We do not hand access to a deceased user's account to family, executors, attorneys or anyone else, whatever a will or power of attorney says. We comply with a court order or other valid legal process (see Section 11), and only as far as it requires.

On verified notice of an account holder's death (typically via a death certificate or equivalent), we will close the account and delete the associated data within 30 days, unless a law or legal process requires us to keep it for longer (see Sections 10 and 11).

We may, in future, offer a legacy contact setting that allows account holders to choose what happens to their account at end of life. Until that feature exists, the default is deletion.


17. Stellar and related products

InnerVisions and Stellar are separate. No data flows between them.

Some users may know that the founders of InnerVisions also operate Stellar, a separate wellness ecosystem, and that our website describes InnerVisions as "a Stellar product". The two are run as separate products with separate accounts. No data flows between InnerVisions and Stellar. Your InnerVisions data is not used to deliver Stellar services, and vice versa. If we ever introduce any integration between the two, it will be opt-in and disclosed at the point of consent.


18. Where you live

We run InnerVisions from Australia, under Australian privacy law. Wherever you are, you have the same core rights.

Australia. This policy is designed to comply with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. You can complain to us at privacy@innervisions.app, or, if unresolved, to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

New Zealand. You can complain to us at privacy@innervisions.app, or, if unresolved, to the Office of the Privacy Commissioner at privacy.org.nz.

United States. We do not sell personal information, and we do not share it for advertising. If you live in Washington State or Nevada, our Consumer Health Data Privacy Policy applies to any health information in your journal.

Everywhere else. You are welcome to use InnerVisions from anywhere. We have built it around Australian privacy law, and not yet around each other country's. The rights in Section 9 apply to you wherever you live, and you can use them in the app or by writing to privacy@innervisions.app. If your local law gives you more, tell us which law and what you need, and we will respond under it. You can also complain to your local privacy regulator.

Sensitive information, everywhere. A journal can reveal sensitive information – health, sexuality, religious or philosophical beliefs. We process it only with your explicit consent: a separate tick before you begin, recorded with its date and a fingerprint of the exact wording. You can withdraw that consent at any time in Settings, by pausing "InnerVisions reading your entries". While it is paused, no AI feature runs and new entries cannot be saved; what is already in your journal stays visible to you, and you can still export or delete it.


19. Contact

For privacy questions, requests, or complaints:

Privacy email: privacy@innervisions.app
General email: hello@innervisions.app
Postal: 5b Beaconsfield Street, Newport NSW 2106, Australia
Legal entity: Metaxu Pty Ltd (ABN 67 698 120 400) trading as InnerVisions App

We aim to respond to privacy requests within 30 days.


20. Changes to this policy

Material changes get 30 days' email notice. Minor edits don't.

We may update this policy from time to time. For material changes (changes to subprocessors, data uses, retention, your rights, or how we handle AI processing), we will notify registered users by email at least 30 days before the change takes effect. Notice of a change is not consent: where a change needs your consent, we ask for it before the change applies to you.

For non-material changes (clarifications, typo fixes, restructuring), we may update the policy without prior notice. The "Last updated" date at the top of this page always reflects the current version.