Privacy Policy

Policy version 18-2026-09-29-r5. Seller: the sole trader operating under the registered business name JPO GLOBAL. Business contact: https://jpowealth.com.au/support. ABN: 99449627727.

Contact us through JPO Support. This product name is proposed; no trade mark registration or financial services licence is claimed.

The plain-English version

We use your email and account identity to keep your records separate and help you sign in. We store the figures, tasks and messages you choose to save. We do not sell personal information, connect to your bank or send balances to advertising analytics. No end-to-end encryption or complete anonymity is claimed.

Why we use your information

We use account details to verify sign-in and prevent unauthorised access; saved entries to provide your plans and tasks; purchase records to unlock access and handle refunds; and support messages to answer your requests. Providing finance details is your choice. Without a verified email we cannot provide a personal cloud account. Enter your JPO password only in the sign-in or password setup form. Do not add passwords, full card numbers, tax file numbers or other people’s information without permission to financial records or support messages.

Information collected

Account information includes your verified email, provider identifier, session records, activation date, trial status and purchase entitlement. Saved content includes money figures, plan history, scenarios, task titles and notes, preferences, any entered planning conversations and accepted document summaries. Support stores the messages you choose to send; it does not automatically attach your finances.

Where information is held

The current site is served through OpenAI Sites with a Cloudflare Workers application and D1 database. Email and password sign-in uses Supabase Auth, with the project configured in Sydney, Australia. Passwords are securely transmitted to Supabase Auth and stored there as password hashes. We do not save readable passwords in your JPO account database, financial records or browser storage. Password setup and recovery require a fresh email verification code. Resend delivers these and optional sign-in codes from accounts@auth.jpowealth.com.au. Square provides website checkout. Apple processes purchases made through the App Store in the iPhone and Mac apps. We verify Apple signed transactions to link purchased access to your JPO account.

Your data is not restricted to Australia. The configured sign-in project is in Australia and sign-in emails are sent from Japan. Resend states that message content and delivery logs are stored in the United States and normally retained for 30 days. Supabase identifies the United States and Singapore among its processing locations. Hosting and payment providers also use international infrastructure and support personnel.

Cloudflare may place its database in North America, Europe, Asia-Pacific or Oceania, and requests can be handled through its global network. The managed host does not expose this site’s precise database country to us, so we cannot give a complete country list or promise Australian-only storage. See Cloudflare’s location information, Supabase’s privacy policy, Resend’s data handling information and Square’s privacy policy. These providers may have administrative access needed to operate and secure their services.

Original uploaded files are stored in account-specific browser storage on the device where uploaded. They do not sync. Accepted figures and extracted planning summaries may sync with your plan. Voice input can use your browser or device’s speech service; do not use it if you do not want that service to receive speech. The older device-only app uses local storage separately.

Security and sessions

Traffic uses HTTPS. Server permissions separate customer accounts and restrict support access. Email verification codes are checked by the authentication provider. JPO sessions use secure, HttpOnly cookies; only a hash of the session token is stored in the application database. These controls reduce risk but cannot guarantee that incidents never happen. Shared or compromised devices can expose locally stored documents and exported files.

Payments and support

Square receives payment and billing information directly. We retain account-linked payment references, amount, status, receipt link and purchase consent version/time. Full card details are not stored in this app. Square may ask for a postal address under delivery or shipping labels to check Australian purchase eligibility. Nothing is posted. Those details may also be visible to the seller in Square’s dashboard. Support threads are visible to you and the authorised support operator. Replies stay in the website; email reply notifications are not currently sent.

Optional website analytics

Website visit measurement starts only after you choose Allow analytics. It records a random browser identifier in a first-party cookie for up to 90 days, a session identifier in session storage, the time, a fixed page or button-action category, approximate country supplied by our host, broad device type and referring website hostname. Query strings, form contents, names, emails, ages, precise locations, raw IP addresses, financial records, task text and support content are not saved in analytics. These pseudonymous visit records are not linked to customer accounts. They help us understand interest in the website; they are not advertising profiles or recordings of your screen.

Only the authorised owner can view the report. Owner and known test accounts are checked solely to exclude their visits; their account identities are not stored in analytics. Native iPhone and Mac app traffic is excluded. Global Privacy Control and Do Not Track are honoured. You can decline without affecting the product, or change your choice below. Withdrawing consent deletes analytics records associated with the current browser cookie and clears it; if the cookie was already removed, we cannot identify those old records. Clearing cookies or using another device can make the same person appear as another browser.

Reports cover the latest 90 days. Older visit records are deleted when the next measurement arrives or the owner opens the report; if the site is inactive they may remain stored until then. The consent preference and owner-exclusion preference stay on the device until changed or cleared. Countries can be inaccurate, particularly with VPNs, and visitor counts do not establish someone’s identity. Earlier daily product counts contain no browser identifier and include testing.

Change website analytics preference

Abuse prevention

Short-lived hashes are used to rate-limit sign-in, message and analytics requests. Hosting and payment providers may keep their own security logs under their policies.

Retention, exports and deletion

Active account content is kept until you delete it or ask for deletion through support. My account offers a cloud export and deletion control. After a fresh email confirmation code, deletion removes the Supabase sign-in identity, active money records, tasks and support conversations and revokes JPO sessions. In the installed iPhone and Mac apps, confirmed deletion also removes the saved offline plan on that installation. Device-only copies on other installations are not removed remotely while offline; remove those copies on each device separately. Exported copies and original device documents remain under your control; remove those on the relevant device separately.

A minimal identity and deletion marker remains to prevent accidental reactivation. Transaction evidence is normally kept for at least five years after the later of preparation or completion of the relevant transaction, and longer where a dispute or legal obligation requires it. A minimal purchase entitlement stays while needed to honour ongoing access. We review retained records and remove information no longer needed; this is not an automatic five-year deletion promise. Provider-held billing, delivery and recovery records remain subject to the provider’s retention obligations. The Version 18 upgrade also creates restricted rollback copies in the same database. Account deletion removes the money, task, support and old account snapshot copies there. The current minimal deletion marker and required payment history can remain. Deleted information can remain in provider recovery backups. Cloudflare publishes a D1 recovery window of 7 or 30 days depending on plan; this does not establish the expiry of every copy held by the managed host. We do not promise immediate removal from all provider systems. Restored data must have deletion requests reapplied before being put back into service.

Expired sign-in sessions, account-linking tokens and rate-limit records are cleaned during subsequent account activity. Expired tokens cannot be used even before cleanup runs. Legacy sign-in identities require a support request. If deletion cannot be completed, contact support; a success message is shown only after identity removal and cloud cleanup complete.

Cookies and device storage

Essential cookies keep you signed in. Browser storage holds device preferences and any original documents you add. Clearing browser storage can remove those device-only documents; export them first. We do not use advertising pixels to send your financial entries to advertisers.

Your questions and rights

Use JPO Support to request access, correction, provider-account removal or to raise a privacy concern. Describe the information or issue involved and what you would like corrected or resolved. Recovery and disclosure require identity checks. If you cannot access your original email, use another email you control to open a support request; this does not automatically grant access to the old account. Return to the support conversation for our reply. If we cannot resolve a privacy complaint, you can contact the Office of the Australian Information Commissioner, which can explain whether it can handle your complaint. We will publish material changes and notify affected customers where appropriate.