01Our approach
Urban Safety is designed to collect the minimum information needed to run a timed safety session and notify the contacts you choose.
Urban Safety lets you start a safety timer before a walk, ride, date, delivery, or similar moment. If you do not check in before the timer and grace period expire, the Service can send an alert to your selected Emergency Contacts with your name, activity details, and last available location or address.
1. We do not sell personal information.
2. We do not use your contacts, alerts, or location for advertising.
3. We do not provide continuous human monitoring or a control room.
4. Most settings, contacts, routines, and history are stored on your device.
Some features require server processing. Timed sessions can create a pending server-side fallback so your contacts can still be alerted if your phone is offline or the app is closed. Support requests, subscriptions, message delivery statuses, and optional analytics also involve the service providers listed below.
02Who we are
The provider of Urban Safety is Urban Safety, Inc., 68 Jay Street, Suite 412, Brooklyn, NY 11201, USA. In this notice, "Urban Safety," "we," "us," and "our" refer to Urban Safety, Inc. and the Urban Safety mobile app, website, backend, and support channels.
You can contact us about privacy at privacy@urbansafety.app. Legal notices may be sent to legal@urbansafety.app.
03What we collect
We collect different information depending on which features you use.
Profile, settings, and device-local data
The app can store your first name, last name, optional email address, avatar URI, language, theme, privacy settings, PIN preference, biometric preference, safety-session notes, visible activity presets, completed session count, routines, Emergency Contacts, and safety-session history. These items are primarily stored on your device using the app's storage layer. On supported native builds, secure storage is used when available; otherwise the app relies on the operating system's standard app sandbox storage.
Authentication and subscription identifiers
The app uses Supabase anonymous authentication so the backend can authorize alert, support, and subscription requests. If RevenueCat is configured, the app links your Supabase user ID to RevenueCat so subscription webhooks can update your Urban Safety Care entitlement.
Emergency Contacts and alerts
Emergency Contact names, phone numbers, relationships, primary-contact status, and preferred channel are stored on your device. When you send a test alert, start a timed session with server fallback, trigger an urgent alert, or let a timer expire, the selected contact details and alert payload are sent to our backend and our messaging provider so the alert can be delivered.
Support and diagnostics
If you contact support from the app, we collect your category, subject, message, optional reply email, and limited troubleshooting metadata such as platform, OS version, app version, locale, premium status, and request timestamp. The backend scrubs metadata keys that look like tokens, API keys, passwords, or PINs before storing the ticket.
04Data, purpose & retention
This table summarizes the main categories. The retention periods below describe our current operational practice and may be shortened when records are no longer needed.
05Location data
Urban Safety requests foreground location permission. If granted, the app may use your last known or current location to center the home map, prepare a timed session, refresh the active-session address, extend a session, confirm a session, or include the last available location in an alert.
- The app does not ask for background location permission.
- The active-session screen refreshes the displayed address about once per minute while the session is open.
- If a timed session uses server fallback, the selected contacts, session details, optional note, address, and available coordinates are sent to our backend before the timer expires.
- If an alert is sent, the alert may include Google Maps and Apple Maps links built from the last available coordinates or address.
06Emergency-contact data
You choose the people who receive alerts. Their names, phone numbers, relationship labels, primary-contact status, and chosen channel are used only to operate the alert feature.
- You should tell each Emergency Contact that you added them and that they may receive safety alerts.
- Free users can send to up to 3 contacts per alert; Urban Safety Care users can send to up to 10.
- WhatsApp delivery, where available, is limited to Urban Safety Care users.
- Emergency Contact data is not sold, shared for cross-context behavioral advertising, or used to build contact profiles.
07Alerts and messaging
Alerts are delivered by Twilio. An alert can be a test alert, an urgent manual alert, or an automatic timed-session alert. The alert may include your name, activity type, duration, optional note, address, map links, and an explanation that the message was sent by Urban Safety.
Our backend also stores per-message delivery status such as queued, sent, delivered, read for supported WhatsApp messages, failed, or undelivered. Delivery status helps the app show whether each selected contact's message was accepted and helps us troubleshoot abuse, fraud, support, and carrier issues.
08Subscriptions and analytics
Urban Safety Care subscriptions are managed through RevenueCat and the Apple App Store or Google Play. We receive entitlement, product, store, expiration, purchase, billing-issue, and webhook event data needed to decide whether Care features should be active.
If Mixpanel is configured, the app can send product analytics events such as app open, session completed, paywall view, and paywall button taps, with limited properties such as activity type, duration, mode, paywall source, plan, and timestamp. We use analytics to understand app reliability and feature usage, not for advertising or resale.
09Security controls
We use practical safeguards designed for a safety app that handles sensitive information.
- Requests to our backend use TLS.
- Server writes use Supabase service-role access; user-facing reads are scoped by row-level security where enabled.
- The app stores the cancellation PIN in Expo SecureStore and can use Face ID or Touch ID through the device OS.
- We do not receive your face, fingerprint, or biometric template.
- Support-ticket metadata is scrubbed for obvious secret keys before storage.
No system is perfectly secure. If you believe you found a security issue, contact security@urbansafety.app.
10Service providers
We use the following service providers to operate Urban Safety.
11How long we keep things
On-device data remains until you change settings, remove it, reset the app, uninstall the app, or the app's automatic history deletion runs according to your selected retention period. The default local session-history retention is 24 hours when auto-delete is enabled.
Server records are retained only as long as needed for the purposes described in this notice, including alert delivery, support, subscription entitlement, fraud prevention, security, accounting, legal compliance, and dispute handling. If you ask us to delete your data, we will delete or de-identify personal information unless we need to keep it for a legitimate legal or operational reason.
12Your privacy rights
Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to the processing of your personal information. You may also have the right to withdraw consent, appeal a denied request, or complain to your local data-protection authority.
- Control local data. You can remove contacts, clear session history, change retention settings, reset the app, or uninstall the app.
- Control permissions. You can disable location, contacts, notifications, and biometric access in your device settings.
- Request server-side access or deletion. Email privacy@urbansafety.app from an address where we can verify and respond to your request.
- California privacy rights. We do not sell personal information or share it for cross-context behavioral advertising. California residents may request access, deletion, correction, and information about our data practices.
13International transfers
Urban Safety is operated from the United States and uses providers that may process information in the United States, the European Economic Area, the United Kingdom, and other countries. Where required, we rely on appropriate safeguards such as contractual commitments, data-processing terms, and transfer mechanisms offered by our providers.
14Children
Urban Safety is not intended for children under 16. We do not knowingly collect personal information from children under 16. If you believe a child provided personal information to Urban Safety, contact us and we will take appropriate steps to delete it.
15Changes
We may update this notice as Urban Safety changes. If a change materially affects your rights or how we process sensitive information, we will provide a reasonable notice in the app, on the website, or by another appropriate channel before the change takes effect when required by law.
16Contacting us
Privacy questions: privacy@urbansafety.app
Security issues: security@urbansafety.app
Legal notices: legal@urbansafety.app
Post: Urban Safety, Inc., 68 Jay Street, Suite 412, Brooklyn, NY 11201, USA