Privacy Policy

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.

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 Visitor), 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.
• Location data — with your permission, your device's approximate (coarse) location, used to suggest communities and events near you. This stays local to your own view of the app — it isn't shared with other members or communities, and isn't used to track you across other apps or websites.

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).
• To understand how the app is used in aggregate, so we can improve it, via Firebase Analytics.
• To understand how this website and our invite links are used in aggregate, so we can improve them, via Google Analytics.
• To serve and measure ads that help support development, via Google AdMob. This includes sharing your device's advertising identifier with Google for ad personalisation and measurement, governed by your iOS app-tracking transparency choice and Android ad-ID settings.

We do not sell your data directly. Jum shows ads to help support development, delivered via Google AdMob. When you see an ad, your device's advertising identifier may be shared with Google for ad personalisation and measurement — this is governed by your iOS app-tracking transparency choice and Android ad-ID settings. For more detail, see "Third-party services we use" below.

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, crash reporting, and app usage analytics.
• Google AdMob (Google) — ad serving and measurement to help support app development. Your device's advertising identifier may be shared with Google for ad personalisation and measurement, governed by your iOS app-tracking transparency choice and Android ad-ID settings.
• Google Analytics — basic usage analytics on this website and on the web page a tapped invite link lands on when it doesn't open the app directly.
• Sentry — backend error monitoring, to help us find and fix problems quickly.
• Cloud hosting — our application and database run on cloud infrastructure, which stores and processes your data on our behalf to operate the app.

Data retention

• Account information (name, email, mobile number) is kept for as long as your account exists.
• Event, RSVP and financial ledger history is shared record-keeping for the communities you're part of — other members' attendance and settlement records depend on it — so it's retained as part of that community's history even after you delete your account, but anonymised: your name is kept only as a snapshot at the time it was recorded, no longer linked to your account, email or any other personal data.
• Deleting your account is immediate and permanent — there's no grace period or recovery window. Your account information is deleted straight away; see "Deleting your account" below for what has to be resolved first.

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 hello@jum.sg.

Jum is a Singapore product, and Singapore's Personal Data Protection Act (PDPA) is the law that governs how we handle your personal data. If you're located outside Singapore, you may have additional rights under your own country's data protection law — contact us and we'll do our best to accommodate them.

Children's privacy

Jum is not intended for children under 13, and we don't knowingly collect personal data from anyone under that age. If you believe a child under 13 has created an account, contact us and we'll remove it.

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: hello@jum.sg.