H4Safe Security App resources

Privacy

Privacy Policy

This policy explains how H4SAFE Security LLC handles information through the H4Safe Security application, resident portal, and related services.

Effective August 16, 2026 Last updated August 16, 2026

1. Scope

H4SAFE Security LLC ("H4Safe," "we," "us," or "our") provides the H4Safe Security application and resident portal for authorized security personnel, administrators, supervisors, residents, board members, and property managers. The information available to a user depends on that user's role, community assignment, and authorized features.

This policy covers information processed through the application and resident portal. It does not replace a community's or employer's own notices where that organization independently controls information.

2. Information we process

Depending on the account and features used, H4Safe processes the following categories:

  • Authentication and account information: name, email address, phone number where provided, account identifiers, role, organization or community links, account status, invitations, and authentication events. Passwords and sessions are handled through the authentication service.
  • Community, property, and assignment information: community and property names, addresses, unit or lot numbers, site instructions, and officer, resident, board, or property-manager assignments.
  • Vehicle and Smart Decal information: license plate, issuing state, vehicle make, model, color, year, type, status, and decal or QR identifiers used by authorized workflows.
  • Guest registrations: guest name, phone number when required by a community, vehicle and license-plate information, visit dates and times, pass type, notes, status, cancellation details, and related audit events.
  • Security and operational records: patrol tours, timestamps, tickets, violations, vehicle descriptions, incident reports, alerts, reviews, assignments, community rules, status changes, and audit history.
  • Photos, evidence, and files: ticket evidence, incident photos, descriptions, notes, community logos, invoice files, and related integrity or storage metadata submitted through authorized workflows.
  • Patrol location: precise latitude and longitude, accuracy, heading, speed, capture time, current patrol position, and the route trace associated with a submitted tour when an officer uses Live Patrol.
  • Business and accounting information: invoice amounts, transaction categories, descriptions, delivery records, dates, notes, and related documents used by authorized administrative features.
  • Local and technical information: theme and accessibility settings, eligible cached or offline operational data, synchronization status, and request or error metadata generated when the application communicates with service providers.

The repository does not include an advertising SDK or a third-party behavioral analytics SDK. The H4Safe application does not use patrol location for advertising.

3. Why information is used

H4Safe uses information to:

  • authenticate users, maintain sessions, and manage account access;
  • apply role- and community-based permissions;
  • provide patrol, parking-enforcement, incident, resident, guest, vehicle, board, property-management, reporting, invoicing, and administrative workflows;
  • display current patrol positions and submitted tour traces to appropriately authorized users;
  • store evidence, preserve operational history, and maintain audit trails;
  • send invitations, account messages, invoice communications, and service-related email;
  • support offline work, synchronization, security, troubleshooting, and service reliability; and
  • respond to support, privacy, security, and account-deletion requests.

4. Foreground and background patrol location

Live Patrol is an officer-only operational feature used during an active parking tour. After an officer sees the in-app disclosure and grants permission, H4Safe can collect precise location while the app is visible in the foreground. Authorized supervisors and other appropriately assigned operational users can view the current patrol position.

If the officer separately grants background or "Always" location access, collection can continue while an active patrol is running when H4Safe is minimized, the device is locked, or the app is not actively on screen. Background access is not required for unrelated features. If it is declined, foreground-only sharing may remain available while H4Safe and the active patrol screen are open.

Current position and submitted trace are different records. Live sharing is designed to stop and the current patrol-position record is designed to be removed when the active tour ends. Location points attached to a submitted tour can remain as an archived operational route trace available to authorized supervisors or administrators.

Officers can change location permission in iOS or Android settings. Ending the active tour stops the Live Patrol workflow.

5. Service providers and disclosures

H4Safe makes information available only as needed for an authorized workflow, including to assigned H4Safe personnel, residents, board members, property managers, communities, or client representatives whose role and assignment permit access.

Verified technology providers and platform services include:

  • Supabase: hosted authentication, database, file storage, realtime updates, and server-side functions.
  • Expo and EAS: software and tooling used to build and deliver the application. The repository does not include an Expo analytics SDK.
  • Apple: iOS, App Store, and iPhone map platform services. Apple may separately process store, device, and map requests under its own terms.
  • MapLibre and OpenFreeMap: Android and web map rendering and map tiles. Requests for map resources can include network information handled by the map provider.
  • Resend: the server-side invitation and invoice-email workflows are implemented to use Resend when those production email features are enabled. Email addresses and delivery metadata are processed to send those messages.
  • Google: Android and Google Play platform services may process installation, device, and store information under Google's own terms.
  • Cloudflare: hosts this public compliance website and may process network request information needed to deliver these pages. This site does not add analytics, advertising trackers, or a user-data form.

Information may also be disclosed when required by applicable law or valid legal process, or when reasonably necessary to protect users, communities, the service, or legal rights. Exact production-provider configurations can change; this policy will be updated when a change materially affects the practices described here.

6. Retention and deletion

The application does not define one universal retention period for every record. Retention depends on the type of information and whether it is an account record, a user-managed resident record, or an operational record belonging to a security workflow or community.

Current Live Patrol positions are designed to be removed when a tour ends. Submitted patrol traces, tickets, incidents, evidence, guest audit events, invoices, accounting entries, and other operational history may remain while needed for the relevant community workflow, security review, evidence integrity, dispute handling, fraud prevention, contractual requirement, or applicable law.

After a verified deletion request, H4Safe deletes or de-identifies eligible account and personal information. If a category cannot be deleted, H4Safe will identify the retained category and the reason during the request process. No fixed deletion-completion period has been approved.

See the Account Deletion page to start a request from the web.

7. Security

H4Safe uses safeguards designed to protect information, including authenticated access, role- and assignment-based permissions, restricted storage, encrypted network connections, and server-side authorization for protected operations. Some app data can be stored locally to support sessions, preferences, and offline work.

No system can guarantee absolute security. Users should protect passwords and authentication codes, keep devices secured, and promptly report suspected unauthorized access through the Support page.

8. Choices and privacy requests

Depending on applicable law and the type of record, users may request access to, correction of, export of, or deletion of eligible personal information. H4Safe may verify identity and account control before acting on a request.

  • Officers can decline or change background location permission in device settings.
  • Users can manage eligible local preferences and cached data through the application or device controls.
  • Account deletion can be requested through the public Account Deletion page.
  • Other privacy requests can be sent to info@h4safesecurity.com.

9. Children's privacy

H4Safe Security is an authorized security, business, resident, and community operations service. It is not directed to children, and the account workflows are not designed for children to create accounts independently. If you believe a child has provided personal information through H4Safe without appropriate authorization, contact us so the situation can be reviewed.

10. Changes to this policy

H4Safe may update this policy when features, providers, business practices, or legal requirements change. The effective and last-updated dates at the top identify the current version. Material changes may also be communicated in the application or through an appropriate account channel.

11. Contact

Privacy questions or requests can be sent to:

H4SAFE Security LLC
Email: info@h4safesecurity.com

Do not send passwords, authentication codes, evidence files, government identification, or unnecessary sensitive information in an initial email.