Privacy

Privacy Policy

This Privacy Notice for H4SAFE Security LLC ("H4Safe," "we," "us," or "our") describes how and why we collect, store, use, and share personal information when you use the H4Safe Security application, the H4Safe resident portal, and our public information site.

Last updated September 19, 2026

Scope

We are H4SAFE Security LLC, a company registered in Florida, United States, at 2054 Vista Parkway Suite 400, West Palm Beach, FL 33411.

H4Safe Security provides parking enforcement services to gated residential communities and homeowners’ associations, delivered through our own uniformed officers together with two separate applications and a public information site. This notice applies when you visit staff.h4safesecurity.com or resident.h4safesecurity.com, when you use the H4Safe Security application or the H4Safe resident portal, and when you contact us.

What information is available to a user depends on that user’s role, community assignment, and authorized features. This notice does not replace a community’s or an employer’s own privacy notices where that organization independently controls information.

If you do not agree with our policies and practices, please do not use the Services. Questions can be sent to info@h4safesecurity.com.

1. Information We Collect

We collect personal information that you provide, that your community provides on your behalf, and that is generated as you use the Services. What we collect depends on your role and the features you use.

The categories we collect are:

  • names;
  • email addresses;
  • phone numbers;
  • mailing addresses, including unit or lot numbers;
  • passwords and other authentication data;
  • usernames and account identifiers, including officer identifiers;
  • job titles and roles, such as officer, supervisor, administrator, property manager, or board member;
  • contact and notification preferences;
  • vehicle information, including license plate, issuing state, make, model, color, year, type, and decal or QR identifiers;
  • guest registrations, including guest name, phone number where a community requires it, vehicle and license plate details, visit dates and times, pass type, and notes;
  • community, property, and assignment information, including community and property names, unit or lot numbers, and officer, resident, board, or property-manager assignments;
  • security and operational records, including patrol tours, tickets, violations, incident reports, alerts, reviews, community rules, status changes, and audit history; and
  • photographic evidence, including ticket and incident photos and the descriptions and notes submitted with them.

2. Information We Do Not Collect

We do not collect Social Security numbers, driver’s license or state identification numbers, passport numbers, dates of birth, bank or payment card details, insurance policy numbers, health information, biometric or genetic data, or information about race, ethnicity, religion, political opinions, union membership, sex life, or sexual orientation. None of these exist as fields in our systems.

License plates identify a vehicle. They are not driver’s license numbers and we do not hold driver’s license numbers.

We run no analytics, no advertising, no retargeting, and no tracking pixels, and we set no cookies. We do not use automated license plate recognition. We do not profile users or draw inferences about them, and we make no automated decisions that produce legal or similarly significant effects; an officer decides every enforcement action.

3. Sensitive Personal Information

Two categories we process are treated as sensitive personal information under some state privacy laws. We process them only to operate the Services, never to infer characteristics about anyone:

  • precise geolocation, being the latitude, longitude, accuracy, heading, and speed reported by a security officer’s device while a patrol is in progress, together with the route trace recorded for a submitted tour; and
  • account log-in credentials, being a username or email address together with a password.

4. Information Collected Automatically

Some information is collected without anyone entering it. We use no analytics or tracking services; what follows is generated by the application and by the infrastructure that serves it.

  • Log and usage data. Our hosting and backend providers record an Internet Protocol (IP) address and request metadata for each request the application makes, along with error reports and synchronization status. This supports security, troubleshooting, and service reliability.
  • Device data. Basic device and browser characteristics needed to render the Services correctly, along with theme and accessibility preferences you set.
  • Precise patrol location. The latitude, longitude, accuracy, heading, and speed reported by a security officer’s device while a patrol is in progress, together with the route trace recorded for a submitted tour. This is satellite-based device location rather than an approximation derived from an IP address, and where an officer enables it, collection continues while the application is in the background. Section 6 describes this in full.

5. Information From Other Sources

We receive personal information about residents from their own community before that resident has any relationship with us. A homeowners’ association, property management company, or community board provides resident contact details, unit or lot numbers, and property addresses so that resident accounts and community records can be created. A manager may enter these individually or import a file of homes.

Client communities and their authorized representatives are the only outside source of personal information we use. We do not purchase personal information, and we do not obtain it from data brokers, public databases, social media platforms, marketing partners, affiliate programs, or advertising networks.

6. 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, assigned board members, 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.

The current position and the 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. H4Safe does not use patrol location for advertising.

7. How We Use Information

H4Safe uses information to:

  • authenticate users, maintain sessions, and apply role- and community-based permissions, so that each user sees only the communities and records they are authorized to see;
  • 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, such as a supervisor overseeing a patrol in progress;
  • store evidence, preserve operational history, and maintain audit trails of who changed what and when;
  • send invitations, account messages, invoice communications, and other service-related email;
  • support offline work, synchronization, security, troubleshooting, and service reliability;
  • respond to support, privacy, security, and account-deletion requests; and
  • comply with legal obligations, respond to legal requests, and establish or defend legal rights.

8. Marketing

We send no marketing or promotional communications through the Services. Every message the application generates is transactional: invitations, password resets, invoice communications, account notices, and notices of changes to these legal documents.

We do not sell personal information, and we do not share it for cross-context behavioral advertising. We have not sold or shared any personal information in the preceding twelve months.

9. Who We Share Information With

Within the Services, information is made available only as an authorized workflow requires. A community’s own property managers and board members can see the resident, vehicle, guest, and enforcement records for the communities they are assigned to. Residents see only their own records and cannot see other residents’ information. Our own officers, supervisors, and administrators see what their role and assignment permit.

Outside the Services, we use the following providers, each under a written agreement that permits them to process information only on our instructions:

  • Supabase: hosted authentication, database, file storage, realtime updates, and server-side functions.
  • Cloudflare: hosting and delivery for the staff application, the resident portal, and the public information site, including network request information needed to serve those pages.
  • Resend: server-side invitation and invoice-email workflows, processing email addresses and delivery metadata to send those messages.
  • MapLibre and OpenFreeMap: map rendering and map tiles. Requests for map resources can include network information handled by the map provider.
  • Expo and EAS: software and tooling used to build and deliver the application. These do not receive information about users of the Services.

10. Other Disclosures

When an officer escalates a violation, a license plate and location may be communicated to the towing operator that the community has contracted. The community selects and contracts that operator. H4Safe does not tow, boot, immobilize, or move any vehicle.

Information may also be disclosed when required by applicable law or valid legal process, when reasonably necessary to protect users, communities, the Services, or legal rights, or in connection with a merger, financing, or sale of business assets.

11. How Long We Keep Information

There is no single 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. An enforcement record can therefore outlive the account of the person who created it: if a ticket is disputed months later, the evidence has to still exist.

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.

12. How We Keep Information Safe

H4Safe uses safeguards designed to protect information, including authenticated access, role- and assignment-based permissions enforced in the database itself rather than only in the application, 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.

Local preferences are not intended to store passwords, secret keys, or other sensitive authentication credentials. Eligible local data can be reviewed and removed from Settings.

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

13. Minors

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 anyone to create an account independently: every account is created by an administrator, or by a community inviting a resident.

A person who is a minor in the jurisdiction where they reside may hold a resident account only with the permission and supervision of a parent or guardian, who must read and agree to the Terms of Service. This matches the position stated in those terms.

If you believe a child has provided personal information through H4Safe without appropriate authorization, contact us at info@h4safesecurity.com so the situation can be reviewed.

14. Your Privacy Rights

Depending on applicable law and the type of record, you may request access to, correction of, a copy of, or deletion of eligible personal information, and may withdraw consent where we rely on it. These rights are not absolute and may be limited in some circumstances. H4Safe verifies identity and account control before acting on a request.

The ways to exercise these rights are:

  • Go to Settings in the application to change your password or to request account deletion.
  • Visit the Account Deletion page at https://legal.h4safesecurity.com/account-deletion/.
  • Email info@h4safesecurity.com.
  • Ask your property manager or H4Safe to correct your name, role, or community assignment, which users cannot change themselves.
  • Officers can decline or change background location permission in device settings.
  • Eligible local preferences and cached data can be managed through Settings or device controls.

15. United States State Privacy Rights

If you are a resident of California, Colorado, Connecticut, Delaware, Florida, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, or Virginia, you may have the right to know whether we process your personal data, to access it, to correct inaccuracies, to obtain a copy, to request deletion, to opt out of targeted advertising, sale, or profiling, and not to be discriminated against for exercising those rights.

In the preceding twelve months we have collected, and disclosed to the service providers named above, the following statutory categories: identifiers; personal information under the California Customer Records statute; commercial information, in the form of records of personal property such as a resident’s vehicle; internet or other electronic network activity information, in the form of server logs and in-application audit trails; geolocation data; audio, electronic, visual, or similar information, in the form of ticket and incident photographs; professional or employment-related information about our own personnel; and sensitive personal information, being account log-in credentials and precise geolocation.

We have not collected protected classification characteristics, biometric information, education information, or inferences drawn to create a profile. We do not use or disclose sensitive personal information for the purpose of inferring characteristics.

To exercise a right, use any of the methods in the section above. You may designate an authorized agent, who must provide written and signed permission from you. If we decline to act on a request, you may appeal by emailing info@h4safesecurity.com; we will respond in writing with our reasons, and if the appeal is denied you may submit a complaint to your state attorney general.

16. Do-Not-Track

Most browsers include a Do-Not-Track setting. No uniform standard for recognizing these signals has been finalized, and we do not respond to them. This makes no practical difference here: we operate no tracking technologies for such a signal to disable. The same applies to Global Privacy Control signals.

17. Information About People Who Do Not Have an Account

Some information in the Services describes people who do not hold an H4Safe account and have no direct relationship with us. A resident may pre-register a visiting guest, providing the guest’s name, vehicle and license plate details, and visit dates. An officer may record the license plate, vehicle description, and photographs of a vehicle parked in a community, whoever owns it.

We process this information only to operate parking enforcement and guest access for the community concerned. We do not use it for marketing, we do not sell or share it, and we do not combine it with information from other sources to build a profile of anyone.

A person described in one of these records may contact us at info@h4safesecurity.com to ask what is held about them. We verify identity before responding.

18. Updates to This Notice

H4Safe may update this notice when features, providers, business practices, or legal requirements change. The updated date at the top identifies the current version. Where a change is material, users are asked to accept the updated notice at their next sign-in, and H4Safe records which version each user accepted and when.

19. Contact

Privacy questions or requests can be sent to H4SAFE Security LLC at info@h4safesecurity.com, by phone at 561-710-9370, or by mail to 2054 Vista Parkway Suite 400, West Palm Beach, FL 33411, United States.

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