Privacy

Last updated October 1, 2026. This page is written in plain language on purpose; where it is unclear, the plainer reading applies.

Who we are

My Community Gates is a service of GTP LLC (“we”). It lets residents of gated communities manage their own gate credentials in UniFi Access, and lets community managers oversee them. Contact us at support@mycommunitygates.com.

Two kinds of people, two roles for us

Community data. Each community (an HOA, a village, a managed property) is our customer and decides who its residents are and what they may do. For that data we act on the community's instructions: the community is the controller and we are its processor.

Website inquiries. When you fill in the “Get started” form or email us, we hold that information ourselves to reply to you.

What we hold about residents

  • A copy of the directory on the community's UniFi Access console: name, email address, phone number if the console has one, the address group the person belongs to, account status, and which credentials exist (whether a PIN is set, the display numbers of cards and tags, license plates).
  • Which phones hold the person's UniFi Identity credential, read from the console when the page is shown; not stored.
  • Sign-in records: the email address, when a code was requested and used, the IP address and browser used.
  • An audit log of changes made through the portal: who, when, which gate, what action, whether it succeeded.

We never store the value of a PIN, the secret token of a card or tag, or a sign-in code once it is used. The console holds those; we only know whether they exist.

What we hold about communities

  • The community's name, time zone, and the office contact details it chooses to show residents.
  • Each console's address on the private tunnel, its TLS certificate fingerprint, and its API token, stored encrypted.
  • The email addresses of community managers and when they last signed in.
  • Vendor PINs the community sets through the portal, stored encrypted so the office can look them up later.

Why we use it

  • To show each resident their own gates and let them change their own credentials.
  • To let community managers manage addresses, people and credentials, and to tell them when a console stops answering.
  • To keep the service secure: rate limiting sign-in codes, detecting abuse, and keeping an audit trail the community can inspect.
  • To reply to inquiries sent through this website.

Who sees it

  • Residents see only their own records and, for household and visitor features, the people and shared accounts at their own address.
  • Community managers see every resident of their own community and nothing of any other.
  • Our platform administrators can see every community in order to set it up and support it. Their actions are in the same audit log.
  • Service providers who process data for us: Google Cloud (hosting, in the United States) and Resend (sending email). They act only on our instructions.
  • Nobody else, unless the law requires it. We do not sell or share personal data for advertising.

How long

  • The directory copy is refreshed from the console every few minutes and reflects what the console holds; people removed at the console disappear from the portal at the next sync.
  • Sign-in codes expire in ten minutes; sessions expire in 24 hours (8 hours for staff) and are pruned once expired.
  • Audit log entries are kept for two years, then pruned.
  • Website inquiries are kept until the conversation ends and then for up to two years for our records.
  • When a community ends its service, its data is exported for it on request and deleted thirty days after the end of service. Encrypted nightly backups age out after ninety days.

Security

Consoles are reached only over private WireGuard tunnels, never from the open internet, and each console's certificate is pinned. API tokens and vendor PINs are encrypted at rest. Staff sign in with an emailed code plus a passkey. The server receives automatic security updates and nightly backups, and we are alerted when it is unreachable.

Your choices

Residents: your community decides what is on file for you. To correct your email or remove yourself, contact your community office; the portal shows its contact details on your gate page. Communities: contact us to export or delete your data, or to change what the portal reads.

Changes

If this page changes in a way that matters, we tell community managers by email and update the date at the top.