Privacy Policy

1. Introduction

Welcome to JungOcean (jungocean.com). We value your privacy. This policy outlines how we handle data collected at every step of using our Jungian Typology & Big Five assessment: the free test, your results, an optional emailed copy, the paid Deep Dive and AI Blueprint reports, the Alchemical Sandbox chat, and the update email you can opt into.

As of 6 September 2026, JungOcean is not available to visitors in the European Economic Area: we're a small Australian business and can't yet meet the EU's requirements for handling data from there, so we've switched the site off for EEA visitors rather than get it wrong. The UK and Switzerland are unaffected.

2. What We Collect, Step by Step

• Free assessment: your answers are scored in your browser to compute your Big Five (OCEAN) traits and Jungian type. Nothing about your answers is sent to our servers just to see your free results.Legal Basis: Contractual Necessity (Art. 6(1)(b) GDPR) to calculate and render your profile.
• Your results (paid purchases): if you buy a report, we store your scores and Jungian type in our database so you can come back and restore them without redoing the test. See Section 6 for how long. Your free assessment results are never stored on our server this way: they stay saved directly in the browser you took the assessment in. If you retake the test, your earlier results (up to 10) also stay in your browser so you can compare them. You can clear them from your results page or with Privacy Choices.Legal Basis: Contractual Necessity (Art. 6(1)(b) GDPR).
• Optional emailed copy of your free results: on the free results screen, you can enter your email to get a one-time email with a summary of your Jungian type (its name, description and cognitive stack) and the free 4-Step Shadow Integration Starter Guide. It doesn't include a link back to your results or your Big Five scores, and we don't cache your scores on our server for this; your free results stay in your browser. We can't check that an address belongs to the person typing it, so the email says it was requested for that address and that you can ignore it if it wasn't you. After a send, your browser keeps one small timestamp (no address) in its localStorage for 24 hours so the form doesn't offer a second send straight away; “Use a different address” on the card, “Reset all” in Privacy Choices, or clearing your browser data removes it. To limit abuse we count sends per address for 24 hours under a keyed hash (never the address itself, and never an IP address or device detail), plus one overall hourly count. If you also tick the separate newsletter checkbox there, we create a subscriber record with your email and Jungian type (never your OCEAN scores) so we can send you occasional update emails, kept for 90 days after the last email we send you, and deleted right away if you unsubscribe. Leaving that box unchecked means we don't create this record at all. If your address was already unsubscribed, ticking the box does not subscribe it again.Legal Basis: Legitimate Interest (Art. 6(1)(f) GDPR) for sending the one-time email and for the abuse counters; Explicit Consent (Art. 6(1)(a) GDPR) for update emails and the subscriber record that supports them.
• Email addresses: when you provide your email to receive a copy of your free results or to unlock a paid report, we collect your email address. This is used to email your report and, only if you explicitly opt in, to send occasional update emails.Legal Basis: Performance of Contract for results delivery; Explicit Consent (Art. 6(1)(a) GDPR) for update emails.
• Paid Deep Dive report: payments are processed directly and securely by Stripe. We do not store or have access to your credit card details. Since 6 September 2026, purchases store your scores and type only in our own database (see Section 4); Stripe holds the payment record and a checkout reference. Purchases made before that date are moved to our database and cleared from Stripe the first time they're opened, or by our one-off migration.Legal Basis: Contractual Necessity (Art. 6(1)(b) GDPR).
• AI Blueprint report: if you buy this add-on, your OCEAN scores and Jungian type are sent to the Google Gemini API to generate the report text. Your name or email are never included in that request.Legal Basis: Contractual Necessity (Art. 6(1)(b) GDPR).
• Alchemical Sandbox chat: included with every paid report, whether or not you also buy the AI Blueprint add-on. If you use it, the messages you send, plus your OCEAN scores and Jungian type, are sent to the Gemini API to generate a reply, the same way the AI Blueprint report itself is generated.Legal Basis: Contractual Necessity (Art. 6(1)(b) GDPR).
• Sending your results to Google's Gemini: before you pay for the Deep Dive report, the AI Blueprint add-on, or the Alchemical Sandbox, we ask you to tick a separate box, unticked by default, agreeing to send your Big Five scores, personality type and onboarding answers to Google's Gemini. Stripe only handles the payment and never receives this data. We keep your results in our own database for 12 months to deliver what you bought. Some privacy laws may treat this data as sensitive, so we ask for your explicit consent on that box; ticking it does not by itself decide whether the data is sensitive. You can withdraw this consent at any time on our Your data page, or by emailing support@jungocean.com. Once we've processed your request, we stop sending your data to Gemini (no new report sections or sandbox chat replies) and delete your stored results. We can't undo a report that was already generated.Legal Basis: Contractual Necessity (Art. 6(1)(b) GDPR) to deliver the purchase you asked for; Explicit Consent (Art. 9(2)(a) GDPR), kept on top of that in case this data is later found to be sensitive (such as under a consumer-health-data law like Washington's).
• AI-assistant access (included with every paid report): every paid report includes AI-assistant access, which starts when the assistant panel launches. It isn't live yet, and we'll tell you when it is. From then on, an assistant you choose, such as Claude Code or Cursor, can read a profile card and growth plans built from your stored results, for 100 successful calls per purchase and up to 365 days. You create the access token yourself on your results page. We show it to you once and store only a keyed hash of it (an HMAC, so the token itself can't be read back from our database), tied to your purchase. The token record holds no scores and no answers. The profile card and plans are written in bands such as high or low, not exact numbers, and your AI Blueprint report is readable too if you bought it. Once your assistant has that text, it sits with whoever runs the assistant, under their terms. Like the rest of the site, this isn't available from the European Economic Area.Legal Basis: Contractual Necessity (Art. 6(1)(b) GDPR), because it is part of what the report price covers.
• AI-assistant usage records: to keep to the limit of 100 successful calls and to stop abuse, we keep a call counter, short-lived throttle counters (one for a minute, one for an hour) and a marker of when access was last used, rounded to the hour, all tied to your purchase. A separate limiter keeps a keyed hash of your connecting IP address for 60 seconds and for 1 hour (never the address itself), and a per-purchase counter of how often access is created, replaced or ended for 1 hour. None of them holds scores or answers. Each call also adds to a usage count (which tool, whether it worked, which kind of client), and that count carries no purchase identifier at all. When access is created, replaced or ended, we log a lifecycle event with only a keyed hash of the purchase, the way we already do for purchase events. The usage count and these lifecycle events go to PostHog, our US analytics provider. They follow PostHog's own retention, and “Withdraw consent and delete my results” doesn't remove them. None of these records holds an email address, a name, a score or an answer.Legal Basis: Legitimate Interest (Art. 6(1)(f) GDPR) to enforce the call limit and keep the service safe from abuse.
• Update emails (drip): if you opt in, we store your email address and send a short series of follow-up emails. You can unsubscribe from any of them at any time.Legal Basis: Explicit Consent (Art. 6(1)(a) GDPR).
• Device and Usage Data, four independent categories: Our cookie banner lets you choose four things separately, not just accept-or-decline. Necessary is always on: it remembers your choice, whether we sell the paid report where you are (the paid-availability cookie named in Section 3) and, if you buy or restore a purchase, the four purchase and restore cookies named in Section 3. Basic counting is on by default for an undecided visitor: a random ID stored only in your browser's sessionStorage, gone the moment you close the tab, counting which steps of a visit happen with no cookie at all. We also note the general kind of site you arrived from, such as a search engine, a social network, or an AI assistant, but never the exact page or address you came from. Analytics across visits is off by default: turning it on upgrades that same ID to a persistent cookie so we can tell a return visit from a new one. Session replay is off by default: turning it on records how you move through the pages so we can fix confusing screens, with everything you type, your answers, and your results masked in your browser before anything leaves it. See “Your Choices” below for the full breakdown and how to change any of this at any time.Legal Basis: Legitimate Interest / the first-party audience-measurement exemption (Art. 6(1)(f) GDPR) for basic counting, with an opt-out available any time via “Reject all” or the Basic counting switch; Explicit Consent (Art. 6(1)(a) GDPR) for analytics across visits and session replay. Server-side crash diagnostics run separately under Legitimate Interest.
• Purchase Recovery Records: If you request purchase recovery, we look up your transactions in Stripe and send a temporary recovery token containing your Stripe session identifier via Resend.Legal Basis: Contractual Necessity (Art. 6(1)(b) GDPR) to restore your purchased access.
• Your data page: when you ask for a link to unsubscribe, withdraw consent or delete your results, we check your email against our Stripe payment records and our subscriber list, and send a one-time link only if we find a match. The link works for 15 minutes. To stop abuse we keep a counter for up to an hour under a keyed hash of your email, never the address itself, and a marker that a link has been used for 20 minutes. Our code never stores or logs your IP address.Legal Basis: Legal Obligation and Legitimate Interest (Art. 6(1)(c) and 6(1)(f) GDPR) to act on your requests and keep the service safe from abuse.

3. Cookies & Advertising

Before you make a choice on the cookie banner, the only cookies we set are one small cookie called paid-availability, plus up to four purchase and restore cookies named below (jo_purchase_nonce, jo_assistant_session, deep_dive_session and restored_results), which exist only if you buy or restore a purchase. paid-availability is strictly necessary for the site to work: it holds just a 1 or a 0, which says whether we sell the paid report where you are, so the buy buttons show or hide on the first screen. It holds no country code and no ID, it expires after 1 day, and it doesn't depend on your cookie choice. The session ID described in Section 2 lives only in sessionStorage, tied to that one browser tab, and is gone as soon as you close it. Turning on “Analytics across visits” is what sets a real, persistent cookie (via PostHog) so return visits are recognized. Rejecting everything sets one small cookie called cookie-consent that records that choice for 12 months, and nothing else. PostHog also keeps its own small record of your accept/decline/opt-in choice in your browser's localStorage, separate from the cookie above; the Privacy choices control below can clear both together.

If you buy a report, or restore a purchase with the link we email you, we set up to four more cookies. All of them are strictly necessary for the purchase and restore flows, so they don't depend on your cookie choice. jo_purchase_nonce is a random value set when checkout starts and kept for 2 hours, so we can confirm your purchase comes back to the same browser that started it; we keep a one-way hash of it with the checkout record at Stripe. jo_assistant_session is signed so it can't be forged. We set it after your purchase, or after you use the restore link we email you, and it lasts as long as your AI-assistant access, up to 365 days. It holds your checkout reference and an expiry date, and it lets your results page manage that access. deep_dive_session is set when your payment is confirmed, or when you use the restore link. It lasts 30 days and holds only your checkout reference, so the site can recognize your purchase when you come back. Page scripts can't read it, your browser only sends it to our own site, and we remove it when you finish the full assessment. restored_results is set only by the restore link and lasts 5 minutes. It carries your results to your screen so you don't have to retake the test, and the page deletes it as soon as it has loaded them. Unlike the others, it does hold your scores and type profile, along with your checkout reference and whether the AI Blueprint add-on is included. For those few minutes it exists only in your own browser and on our servers, and we never pass it to anyone else. The other three cookies hold no scores, answers, email address or token.

JungOcean is currently 100% ad-free. We do not display advertisements, and no advertising cookies or device identifiers are set on this site.

If we introduce advertising in the future, it will be consent-gated: ad cookies and personalization will only load after you explicitly opt in through our cookie banner, and this policy will be updated first to disclose the vendors involved and how to opt out.

If you wish to change your cookie choices or withdraw consent for analytics on this site, you can reopen your choices at any time. The same Privacy choices control also appears at the bottom of every page:Privacy choices

3a. Your Choices

The cookie banner (and the Privacy choices control above) lets you turn four things on or off separately:

• Necessary: always on, can't be switched off. Remembers this choice, whether we sell the paid report where you are (the paid-availability cookie, just a 1 or a 0) and, if you buy or restore a purchase, the four purchase and restore cookies described in Section 3 (jo_purchase_nonce, jo_assistant_session, deep_dive_session and restored_results). Nothing else.
• Basic counting: on by default. A random ID kept in this tab only, gone when you close it. Counts which steps of the visit happen. No cookie.
• Analytics across visits: off by default. The same ID kept between visits (browser storage and a cookie), so we can tell a return visit from a new one.
• Session replay: off by default. A recording of how you move through the pages, so we can fix confusing screens. What you type, your answers, and your results are masked before it ever leaves your browser.

You can change any of these at any time from the cookie banner or the Privacy choices control above. There's no need to wait for a reset. A full reset clears everything and puts you back to the not-yet-decided state.

Each time you make or change a choice here, we also keep a small record of it on our own server for up to two years (the choice itself and a random receipt ID you can quote back to us, never your IP address or any other identifying detail), so we can show proof of what was actually agreed to if that's ever in question.

4. Third-Party Services We Use

We share data with or utilize the following third-party processors to run the site:

• Stripe: Payment transaction gateway. No financial details touch our servers. Since 6 September 2026, purchases store your OCEAN scores and Jungian type only in our own database (Upstash, below); Stripe holds the payment record and a checkout reference. Purchases made before that date are moved to our database and cleared from Stripe the first time they're opened, or by our one-off migration.
• Resend: Transactional and marketing email provider. We share your email address and results report with Resend to deliver your analysis documents, and your email address and Jungian type summary to send the free profile email. If you tick the newsletter checkbox, Resend also holds your address as a marketing contact.
• Google Gemini API (paid tier): For generating the Jungian Analytical AI Blueprint report and the Alchemical Sandbox chat. We send assessment scores (OCEAN metrics and Jungian cognitive type profile), and your sandbox messages if you use it, to Gemini to generate text. No personally identifiable details (like your name or email) are sent to the AI API. This processing may happen on Google's infrastructure anywhere in the world, including the US. Google keeps this data for up to 55 days for abuse monitoring (during which authorised Google personnel may review it) before deleting it.
• PostHog (US-hosted): For analytics, server-side crash diagnostics, and, only if you turn it on, session replay. Before you make a choice, PostHog only sees the session-scoped ID and event set described in Section 2: no cookie, no cross-visit tracking. Turning on “Analytics across visits” sets a persistent cookie; turning on “Session replay” starts a masked recording of that session only. We've configured PostHog to discard your IP address and delete precise location data before it's stored. Separately, our production server also reports its own crashes to PostHog using an anonymous, fixed identifier, never a visitor identity. We don't use it for advertising or cross-site tracking. If you're visiting from the European Economic Area, the UK, or Switzerland, our cookie banner tells you plainly that our servers and analytics are US-hosted before you decide.
• Vercel (US-hosted): Hosts the site and runs the server that terminates analytics requests before they reach PostHog.
• Upstash (US-hosted): our database and cache, in N. Virginia (us-east-1). It stores your assessment results, generated AI report text, and (if you sign up for update emails) your subscriber record. Each of these expires automatically (see Section 6, Data Retention) rather than being kept indefinitely. It also holds the records behind AI-assistant access: the token record (found by its keyed hash, never by the token), the call counter, the throttle counters and the last-used marker. None of them holds scores or answers. We use it so you can come back and restore your results without starting over.

Where a provider above is based in the US, we rely on their own current certification under the EU-US Data Privacy Framework (and its UK Extension, where applicable) as the legal basis for sending data there, backed by standard contractual clauses where a provider isn't DPF-certified.

5. Do Not Track

We don't currently change what we track based on your browser's Do Not Track signal. Your choice in the cookie banner is what actually controls measurement on this site.

6. Data Retention & User Rights

How long we keep things depends on what it is:

• If you bought a report, we keep your OCEAN scores and Jungian type in our own database for 12 months so you can restore them, and delete them sooner on request. Since 6 September 2026, purchases store your scores and type only in our own database; Stripe holds the payment record and a checkout reference. Purchases made before that date are moved to our database and cleared from Stripe the first time they're opened, or by our one-off migration.
• Your generated AI Blueprint report text is kept for 30 days, whether or not you bought it. Reopening it after that regenerates a fresh version rather than restoring the old one.
• Your AI-assistant access, and the records behind it (the token record, call counter, throttle counters and last-used marker), last as long as your stored results, up to 365 days from your purchase. If you use “Withdraw consent and delete my results” on our Your data page, those records are deleted and your access ends at once.
• A full refund of the report, or a payment dispute, ends AI-assistant access for that purchase, and it doesn't come back on its own. A refund of the AI Blueprint add-on alone doesn't.
• If you request the optional emailed copy of your free results without buying a report, we don't cache your scores on our server at all. We only send the one-time email described in Section 2; your free results stay in your browser. The per-address send counter behind it expires after 24 hours and the overall counter after one hour. If you also tick the newsletter checkbox there, see the next bullet for how long we keep the subscriber record it creates (it includes your Jungian type, never your scores).
• If you sign up for update emails, we keep your subscriber record for 90 days after your last activity, and delete it right away if you unsubscribe.
• Once you unsubscribe or ask us not to email you again, we keep a record of that choice indefinitely: the whole point of keeping it is to make sure we honour it.
• Stripe's own record of your payment follows Stripe's own independent retention obligations, not ours.

If you are a resident of the European Union (GDPR), United Kingdom, or California (CCPA), you have the right to request access to, rectification of, restriction of, or deletion of your personal data, to object to marketing at any time, and to withdraw any consent you've given.

You can unsubscribe, withdraw your consent, or have your stored results deleted yourself on our Your data page: enter your email and we'll send you a link that works for 15 minutes. Deleting your results doesn't remove Stripe's record of your payment, because tax rules require it to be kept. If you'd rather ask a person, email support@jungocean.com.

You also have the right to lodge a complaint with your local Data Protection Authority (DPA) if you believe our data processing practices violate applicable law.

If you have a complaint about how we handle your data, email support@jungocean.com. We read and personally respond to every message sent there.

We never sell your personal data, your scores, or your type to anyone, for any price.

If we make a material change to this policy, we'll post the updated version here with a new effective date. This page is always the current version.

A note on our own numbers: when we talk about “visitors” measured before you accept the cookie banner, that count reflects browser sessions, not distinct people. Opening a new tab, or coming back tomorrow, looks like a new visitor to us, even if it's you again. Once you accept and get a persistent ID, we can tell returning visits apart properly.