OzVisa · Legal
Privacy Policy

OzVisa Privacy Policy

Effective 14 May 2026 · Last reviewed 14 May 2026

1. Introduction

OzVisa ("the App", "we", "us") is an independent iOS application that helps Australian skilled-migration applicants and planners track their visa journey. This Privacy Policy explains what limited information OzVisa collects, how it is used, and which third-party services participate in those flows.

OzVisa is developed and published by RanKKI Studio. We are a small independent developer; we do not operate as a registered migration agent and we have no affiliation with the Australian Department of Home Affairs ("DHA") or any state nomination program.

2. The Short Version

3. What We Collect

3.1 Anonymous Identifier

On first launch the App calls Supabase Auth's anonymous sign-in, which returns a randomly generated UUID. This UUID is the only identifier we use for backend operations. The session is stored in the iOS Keychain so the same anonymous identity persists across launches.

3.2 Profile Mirror

We mirror the following structural information to our user_app_profiles table, keyed on the anonymous UUID:

This mirror is used solely to filter push notifications (for example "send to 190 applicants only"). We do not store the lodgement date itself, milestone dates, points totals, English test scores, or any other detail you enter into the App.

3.3 Anonymous Cohort Events

When you record a milestone (biometrics done, medical complete, application lodged, etc.), an event row is upserted into our analytics_events table containing the anonymous UUID, visa context, event type, and event date. These rows are used to compute aggregate cohort statistics — for example, the median time between lodgement and biometrics for 190 applicants. Individual event rows are never displayed back; aggregates require a minimum sample size before they are revealed.

3.4 Push Notification Token

If you grant push permission, your Apple-issued APNs device token is stored in our notification_tokens table, keyed on the anonymous UUID. The token allows Apple to route notifications to your specific device. Revoking push permission in iOS Settings removes the token on the next app launch.

3.5 Subscription State

If you subscribe to OzVisa Pro, RevenueCat fires a webhook to our backend with the entitlement status. We store the status (active / expired / cancelled), the entitlement identifier, and the expiry date in our user_subscriptions table. We do not see your Apple Pay or payment-method details — Apple and RevenueCat handle the transaction.

3.6 Product Analytics (PostHog)

We use PostHog to record anonymous product analytics: app opens, onboarding started / completed / skipped, paywall views and dismissals, and subscription start / lost events. These events are keyed on the same anonymous UUID and are not enriched with user-identifying information. We use them to understand which parts of the App are useful and to optimise the onboarding flow.

4. What We Do Not Collect

5. How and Where Your Data Is Stored

5.1 In Your iCloud (Your Private Domain)

Your detailed profile data — profiles, milestones, dates, points answers, credentials — is stored in your iOS device's iCloud Private Database, a per-user storage area Apple provides. We do not have access to your iCloud Private Database.

5.2 Local File Fallback

If you are not signed into iCloud, the same profile data is stored in a local file on your device only. It is not uploaded anywhere.

5.3 In Our Backend

Only the limited information described in Section 3 is stored on our infrastructure. Our backend is hosted on Supabase (PostgreSQL-as-a-service); see "Third-party services" below.

6. Third-Party Services

OzVisa integrates with the following third-party services. Each is bound by its own privacy practices:

We do not sell, license, or share your data with any party outside the operational integrations listed above.

7. Data Retention

8. Your Rights

You may:

9. Children's Privacy

OzVisa is not directed at children. We do not knowingly collect data from anyone under 13 (or under 16 in EU jurisdictions). If you become aware that a child has used OzVisa without parental consent, please contact us so we can delete the relevant records.

10. International Transfers

Our backend infrastructure is hosted on Supabase in the Australia (Sydney) region. PostHog uses United States infrastructure (US Cloud). By using the App you consent to your data being transferred to these regions where applicable data-protection regimes may differ from your own.

11. Data Accuracy Disclaimer

The data displayed by OzVisa is point-in-time and may be outdated. DHA policies, processing times, ANZSCO eligibility lists, EOI cutoffs, and state nomination program rules change frequently and without notice. OzVisa ingests public data on a periodic schedule (typically monthly for SkillSelect and EOI rounds). Between updates, the displayed information may not reflect current government policy. Always verify against official DHA and state nomination program sources before making any migration decision.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will update the "Last reviewed" date at the top of this page. Material changes will be flagged in the App on next launch.

13. Contact

Questions or concerns about this Policy? Email [email protected].