Back to Resettle

Privacy Policy

Effective date: June 27, 2026

This Privacy Policy explains what Resettle collects, why it is used, and how account and device-local data are handled. Resettle accounts remember destinations and account access details, not private case files.

1.Data controller and contact

  • Controller/contact placeholder: Resettle should finalize a legal contact address before public launch.
  • Until then, use the in-product feedback or contact channel for privacy questions.

2.Data we collect

  • Email address when you use Google Auth or email magic link.
  • Authentication provider ID and session-related data handled by auth infrastructure.
  • Account Saved destination references when you are signed in.
  • Device-local data such as local Saved fallback, Recently Viewed, Compare selection, and UI preferences.
  • Technical logs and analytics events where enabled for reliability, security, and product understanding.

3.Google Auth and magic link data

  • If you continue with Google, Google and Supabase may process authentication details needed to sign you in.
  • If you continue with email, magic-link infrastructure may process the email address needed to send the sign-in link.
  • Do not share passwords or sensitive credentials with Resettle. Patch 30B does not add password auth.

4.Account data and Saved destinations

  • Resettle accounts remember destinations, not private case files.
  • Account Saved rows may include user ID, entity code, entity type, source, created timestamp, and updated timestamp.
  • Saved destinations are not eligibility claims, recommendations, or legal advice.
  • Local-to-account merge may copy valid local saved destinations into your account after sign-in.
  • Saved rows do not store full country, state, or province card payloads.

5.Recently Viewed

  • Recently Viewed is stored on this device and is not synced to your account.
  • Recently Viewed uses browser localStorage key resettle.recentlyViewed.v1.
  • Recently Viewed is not written to the database.
  • Clearing recent places does not clear Saved destinations.
  • Recently Viewed is limited to recently opened destinations and does not represent advice or recommendations.

6.Local device data

  • Local Saved fallback, Compare selection, UI preferences, and Recently Viewed may remain in your browser until cleared by you, your browser, or product controls.
  • Local device data remains usable without an account.

7.Future Citizenship Context

  • If introduced, Citizenship Context may use a selected citizenship country to show account-only map signals.
  • Do not upload passports or identity documents.
  • This feature would be a research signal, not legal advice.
  • It should not make eligibility, approval, or relocation-outcome claims.

8.What Resettle does not collect in the current account scope

  • Passport scans, identity documents, visa documents, bank statements, tax records, personal relocation case files, and sensitive immigration case notes are not part of the current account scope.
  • Resettle does not ask you to upload documents or passports in Patch 30B.

9.How we use data

  • Provide account access and session continuity.
  • Sync saved destinations across devices when you are signed in.
  • Keep local product state usable without an account.
  • Improve reliability, understand product usage, and protect the product from misuse.

10.Service providers and processors

  • Supabase may be used for auth and account database features.
  • Vercel may be used for hosting, deployment, analytics, and technical logs.
  • Google Auth is used when you choose Google sign-in.
  • Mapbox is used for map rendering where enabled.
  • Analytics or email providers may be used for product reliability, feedback, or operational email where enabled.

11.Cookies and localStorage

  • Authentication and session tools may use browser storage or cookies to keep you signed in.
  • Resettle uses localStorage for local Saved fallback, Recently Viewed, Compare selection, and UI preferences where applicable.
  • You can clear browser storage through your browser settings; feature-level controls may also clear specific local data such as recent places.

12.Retention, deletion, and export

  • Account data may remain while the account exists or as needed for product, legal, or security reasons.
  • Device-local data remains in your browser until cleared.
  • You can request deletion or export of account Saved data where feasible once account support channels are finalized.

13.Security and international transfers

  • Resettle uses reasonable technical measures, but no system is perfectly secure.
  • Protect your email account and authentication provider access.
  • Infrastructure providers may process data in multiple countries. Do not assume data remains in one jurisdiction.

14.Children and changes to this policy

  • Resettle is not directed to children.
  • This policy may change as the product changes. Material changes should be reflected on this page.