Legal

Privacy Policy

Last updated: 16 August 2026

This policy explains what information Jum collects when you use the Jum app, why we collect it, and how it's handled. It's written in plain language on purpose — if anything here is unclear, contact us and we'll clarify it.

TODO (for confirmation before publishing publicly): this policy is structured and grounded in Jum's actual data model, but the sections marked below still need a named legal entity, governing jurisdiction, and confirmed retention periods before this is a complete, binding policy.

Information we collect

Jum collects only what's needed to run your community's events and ledger:

  • Account information — your name, email address, and (optionally) mobile number, used to create and secure your account and to identify you to the communities you join.
  • Community & membership data — which communities you belong to, your role in each (Admin, Member or Guest), and your join history.
  • Event & RSVP data — events you create or respond to, your attendance status, team assignments, and any guests you bring.
  • Financial ledger data — expenses you log, your share of a settlement, and your balance within a community. Jum tracks who owes whom; it does not process payments or hold funds — see our Terms of Service for detail.
  • Device & push notification data — a device token used to deliver push notifications via Firebase Cloud Messaging, and basic crash/diagnostic data via Firebase Crashlytics if the app crashes.

We don't ask for a profile photo — avatars in Jum are generated from your initials, not uploaded images.

How we use this information

  • To run the core functions of the app: RSVP, team formation, expense tracking and settlement, within the communities you're part of.
  • To send you notifications you've opted into (event updates, settlement reminders) via push notification and, where applicable, email.
  • To secure your account (email/one-time-code sign-in) and to provide support when you contact us.
  • To monitor and fix bugs, via crash reporting (Firebase Crashlytics) and backend error monitoring (Sentry).

We do not sell your data, and we do not use it for third-party advertising.

Who can see your information

Information you add to a community — your name, RSVP status, team, and ledger balance — is visible to other members of that same community, the same way it would be if the organiser tracked it manually. It is not visible to members of a different community you belong to, or to the public, unless the community itself is set to public and you're viewing a public event.

Third-party services we use

Jum is built on a small number of infrastructure providers that process data on our behalf:

  • Firebase (Google) — push notification delivery and crash reporting.
  • Sentry — backend error monitoring, to help us find and fix problems quickly.
TODO: confirm hosting/database provider and add here once finalised.

Data retention

TODO: confirm and publish concrete retention periods for account data, event history and deleted-account data before this policy is treated as final.

Deleting your account

You can request account deletion from within the app. If you have an outstanding ledger balance or an unsettled event, you'll be shown what needs to be resolved first — deletion isn't a way to walk away from a balance owed to someone else in your community.

Your rights

You can access, correct, or request deletion of your account information at any time from within the app, or by contacting support@jum.sg.

TODO: confirm which specific data-protection regime(s) apply (e.g. Singapore PDPA and/or others, depending on where users are located) and reference the relevant statutory rights here.

Children's privacy

TODO: confirm and publish a minimum age for using Jum before this section is complete.

Changes to this policy

If this policy changes materially, we'll update the date at the top of this page and, where appropriate, notify you in the app.

Contact

Questions about this policy: support@jum.sg.