Privacy Policy

JETT Watch · a JETTForce product

Effective date: TODO(Lam) — insert publish date

1. Who we are

JETT Watch is a safety-dispatch app operated by JETTForce for residents of guarded communities near Clark, Pampanga, Philippines. This policy explains what we collect through the JETT Watch reporter app, the responder app, and the Command Center, and how it is used to run the SOS dispatch service.

TODO (Lam): Fill in the data controller's registered business name, business address, and Data Protection Officer (DPO) contact — required for a compliant RA 10173 policy. Do not publish this page to the app stores until this section is complete.

2. Information we collect

Account details. When you register with a Command-issued access code, we collect your name, email address, and (optionally) phone number. JETTForce staff (responders, dispatchers, admins) also have a badge ID. Your password is stored as a one-way hash — we never store it in plain text.

Your registered address. Your household's address within your community (e.g. block/lot) — this is a fixed record, not a live GPS trace. It is what an SOS dispatches help to.

Emergency contacts. Up to 5 personal contacts (name + phone number) you add yourself, texted automatically whenever you trigger an SOS.

SOS audio. When you hold to send an SOS, the app automatically records a short audio clip so responders have context, plus any voice-note follow-ups you choose to add afterward.

Photos on reports. If you attach photos from your library to a non-emergency incident report, we store those photos.

Guard location — responders only. While a responder is en route to an incident and has the app open, we receive their device location so Command and the reporter can see their position and ETA. This applies only to the responding guard, only while en route, only while their app is in the foreground — never in the background, and never for reporters.

Notification token. A device token used to deliver push alerts (e.g. "guard assigned"), issued by Expo's push notification service.

Payment reference numbers. If your household pays dues, you submit the reference number from your own bank/e-wallet transfer for our staff to match against your account. We never collect your card, bank account, or e-wallet credentials — payment happens entirely outside the app via a QR code, and we only record the reference number and amount you tell us.

What you type. Incident notes, report descriptions, and in-app messages you send to a responder or dispatcher during an active incident.

3. What we do NOT collect

No live location tracking of reporters, ever. JETT Watch dispatches help to your registered address, not a live GPS position. We never track "your current location" and never show your live location to anyone, including Command or a responder. The only party whose live position is ever shared is the responding guard, and only while en route (see above).

No background location tracking of any kind, for any role.

No public crime map, social feed, or public listing of incidents. Incident data is visible only inside the Command Center and to the responder assigned to that incident — never published.

No advertising, no ad networks, no third-party analytics or tracking SDKs.

No card numbers, bank credentials, or e-wallet credentials.

4. How we use your information

To dispatch a responder to your registered address when you trigger an SOS or submit a report; to notify JETTForce Command, your community's guard house, and your personal emergency contacts by SMS the moment an SOS opens (once per incident — repeat holds on an already-open SOS do not trigger repeat texts); to show Command dispatchers the incident, roster, and audit history they need to run the dispatch desk; to calculate and display a responding guard's ETA; to reconcile household dues payments; and to keep the security logs (login attempts, rate limits) needed to keep the service safe from abuse.

5. Who sees what

JETTForce Command dispatchers can see your account details, registered address, and incident history at all times — this is necessary to operate the dispatch desk and cannot be turned off.

The responder assigned to your active incident can see your registered address (mandatory — a responder cannot be dispatched to an address they cannot see) plus the incident details needed to respond. In Me → Data sharing you additionally control whether that assigned responder can see your full name and profile photo.

When you have not shared your name, the assigned responder sees only “Reporter (name withheld)” — your name is removed on our servers before it reaches their device, not merely hidden in the app.

Partner responders (e.g. third-party rider partners providing supplementary response coverage) are governed by the same Data sharing choices described above.

TODO (Lam): The commercial terms of the partner-responder program (which partner organizations, what incident detail they receive, vetting) are still open questions with the client as of the last requirements review — do not describe partner responders more specifically than "partner responders" until that is settled.

We never sell your information, and we never publish incident data publicly.

6. SMS messages

Every SOS you send with data connectivity triggers one text message each to: JETTForce Command (always, not removable), your community's guard house (always, not removable), and each of your personal emergency contacts (up to 5) — one message per contact, sent once per incident.

If you have no data connection, the app opens your phone's own SMS app with a message pre-filled with your name, an incident reference, and your registered address, addressed to your community's SMS number — nothing sends until you tap your phone's own Send button. A "Call JETTForce" option is offered as a fallback if you can't text.

Texts sent to a JETTForce-operated number are received by a Command-operated SMS gateway, which creates an incident automatically and can text you back an acknowledgment with your incident reference.

7. How long we keep your data

Audio clips — both the automatic SOS clip and any voice-note follow-ups — and photos attached to reports are automatically and permanently deleted 30 days after they're recorded or uploaded (these periods are configurable independently by us; 30 days is the current default for both).

TODO (Lam): Confirm how long account and incident records are kept after an account is closed, and state that period here before publishing.

8. Your controls inside the app

  • Me → Data sharing: choose whether your full name and profile photo are visible to the responder assigned to your incident.
  • Contacts: add, edit, or remove your personal emergency contacts (up to 5).
  • Profile: update your name and phone number, or change your password. Changing your password signs every other device holding your account out.

9. Your rights under the Data Privacy Act of 2012 (RA 10173)

As a data subject under Philippine law, you have the right to be informed about how your data is processed; to access a copy of your personal data; to object to certain processing; to request correction of inaccurate data; to request the erasure or blocking of your data where permitted; to data portability; and to lodge a complaint with the National Privacy Commission (NPC) if you believe your rights have been violated.

10. Requesting deletion of your data

JETT Watch does not currently have a self-service "delete my account" button in the app. To request deletion or deactivation of your account and personal data, contact us using the details below and we will process your request manually.

TODO (Lam): Confirm the deletion-request process and turnaround time with Lam, and add a working contact channel (email or in-app support flow) below. Consider whether a self-service delete flow should be built before wider rollout.

11. Security

Passwords are stored as one-way hashes, never in plain text. Session tokens are stored hashed and expire automatically. Uploaded audio and photos are never publicly reachable — they are served only through authenticated routes to people with a legitimate reason to see them. Login attempts are rate-limited, and accounts temporarily lock out after repeated failed attempts.

12. Children's data

TODO (Lam): JETT Watch is registered per-household and a household account can be shared across family members' devices — confirm with legal whether any household member is expected to be a minor, and whether additional Data Privacy Act / child-data provisions are needed before this section can be written.

13. Changes to this policy

We may update this policy as JETT Watch changes. We'll update the effective date above when we do. Material changes affecting how your data is used will be announced in the app.

14. Contact us

TODO(Lam): Data Protection Officer name, contact email, contact phone, and registered business address.