Privacy at Police Here

Data used and its purpose

Name, email, authentication data, sessions and verifications maintain your account. Passwords are hashed, not stored as plain text. Sessions may include technical information such as IP and browser.

Emergency contacts include name, channel, destination, consent and no-response permission. Preferences include language, emergency number and chosen phrases.

With permission, we store the last position, accuracy, timestamp and available address, plus app presence, location requests, push token and alert results. We do not maintain continuous coordinate history.

Location, consent and private links

A private link remains valid while the contact is registered; removing the contact or deleting the account revokes access. Anyone holding the link can request and access positions authorized for it. Do not forward links.

Outside an active emergency, approving a request shares one timestamped position, not permanent tracking. No-response access is off by default and requires prior per-contact permission, a one-minute wait and stale app presence. Pending requests expire after five minutes.

No response does not prove a phone is switched off. During an owner-activated emergency, registered contacts can follow updates while the app is open, connected and permitted. Stopping an emergency ends live access; previously authorized positions can be revoked separately.

Microphone and notifications

The optional microphone recognizes phrases while the app is open. Police Here does not record audio. The system recognition service may process audio under its own policies.

Push notifications may announce requests without sending coordinates to the push service. Acceptance does not guarantee receipt or automatically authorize sharing.

Storage and external services

Accounts and safety data are stored in MongoDB hosted on Google Cloud. Web authentication uses cookies; native session cookies and the last position use secure device storage. Preferences and the last position may also use browser storage.

Twilio processes SMS/WhatsApp content and destinations; Resend processes email; Expo and APNs/FCM participate in push. Google or Microsoft participate when you choose their login. Opening or displaying a map sends coordinates and normal web-request data to Google Maps.

We do not add advertising trackers to the site. External services have their own processing and retention policies.

Retention and deletion

Account and safety data remain while needed for use. Tokens and sessions have logical expiration; expired records may remain physically until maintenance cleanup. The last position remains until account deletion; signing out removes local cache, not the database position.

Account deletion removes identifying profile data, contacts, position, credentials, sessions and emergency records. A blocked opaque-ID marker without name, contacts or location prevents in-flight requests from recreating deleted data.

Sent messages cannot be recalled. Provider records and any backups follow their own retention; immediate deletion in external systems is not promised.

Your choices and contact

Control system permissions, remove contacts, revoke authorized positions, edit details and delete your account. See “Delete data” for instructions.

Request access, correction or deletion at contatc@policehere.com. Ownership confirmation may be needed; never send your password or private links.

Support

contatc@policehere.com