Privacy Policy

TeloGate (“the app”) is provided by ZipDX LLC (“ZipDX”, “we”, “us”). This policy applies to both the iOS and Android versions of the app. TeloGate lets you open TeloGate‑controlled gates from your phone — manually, and optionally hands‑free as you approach a gate. This policy explains what information the app handles, how it is used, and your choices.

Summary

  • We do not sell or share your personal information with third parties for advertising.
  • The app contains no ads, no third‑party analytics, and no tracking SDKs.
  • The app does not track you across apps or websites owned by other companies.
  • Your location is used only on your device to detect when you’re approaching your gates; it is not transmitted to us or to any third party.
  • Your TeloGate sign‑in credentials are stored encrypted on your device and are sent only to the TeloGate service (portal.telogate.com) to authenticate you.

Information the app handles

  1. TeloGate account credentials. When you sign in, you provide your TeloGate email and passphrase. On iOS these are stored in the iOS Keychain (protected by device encryption and, when you use Face ID / Touch ID sign‑in, gated by biometric authentication). On Android they are stored in the Android Keystore with Google Tink envelope encryption. Credentials are transmitted only over an encrypted (HTTPS) connection to portal.telogate.com — the TeloGate service operated by ZipDX LLC — solely to authenticate you. They are not shared with any third party.
  2. Location. Only if you enable Location tracking (off by default) and grant the corresponding permission, the app accesses your device’s precise location, including in the background to detect when you are driving up to a configured gate so it can open automatically (“Auto Open”). Your location is processed only on your device to trigger your gates. It is never sent to ZipDX or any third party, and it is not retained, except a single optional “home” reference point that you may choose to save. The home coordinate is stored encrypted on your device. You can turn Location tracking off at any time in Settings, which stops all location access.
  3. Gate configuration. The list of gates (“entrances”) available in the app is downloaded from portal.telogate.com after you sign in, using the same secure session as your sign‑in. For
    each gate the list includes the name, coordinates, trigger URL, phone contact, and a status flag indicating whether the gate is currently online. This data is stored on your device. Your
    per‑gate Auto Open preference is stored locally and is not transmitted to us. Administrators may also add, edit, or delete entrances, and export or import the entrance list as a JSON file to a location they choose; any such file is created only at your request and is not sent to us automatically. This configuration is not shared with third parties.
  4. Profile information. An optional mobile phone number and your saved home coordinates are stored encrypted on your device. They are not transmitted to us.
  5. Community identifier. A small numeric identifier for the gate community you belong to (for example, a residential community’s ID) is captured from the TeloGate portal after you sign in and stored on your device in application preferences. It contains no personal information and is used only to fetch your community’s gate list from portal.telogate.com.

How the information is used

Solely to provide the app’s features: signing in to your TeloGate account, opening your gates manually, and — if you enable it — opening them automatically as you approach. We do not use your information for advertising or profiling.

Sharing

We do not sell your information and do not share it with third parties for their own purposes. Your credentials are transmitted only to the TeloGate service (portal.telogate.com) to operate
the gate functionality you requested. The app integrates no third‑party advertising SDKs, analytics SDKs, or tracking SDKs of any kind.

App tracking

The app does not track you across apps or websites owned by other companies. It does not use Apple’s Advertising Identifier (IDFA) or Android’s Advertising ID, and it does not request App Tracking Transparency permission because it does no tracking.

Data retention and deletion

Your credentials, gate configuration, and profile data are stored on your device and remain until you delete them in the app or uninstall it. You can:

  • Clear individual data in the app (e.g. clear a saved home location, or delete an entrance if you are an administrator).
  • Deactivate your account from Settings, which removes the app’s saved credentials and ends the session.
  • Request deletion of your TeloGate account data by contacting us at the address below.

Security

On iOS, credentials and sensitive profile data are stored in the iOS Keychain with the accessibility attribute kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly (data is device‑bound and not synced to iCloud, backups, or other devices). Face ID or Touch ID may be used to unlock saved credentials for interactive sign‑in. On Android, equivalent protections are provided by the Android Keystore with Google Tink envelope encryption. All network communication with
portal.telogate.com uses HTTPS, enforced by iOS App Transport Security or the Android network security configuration; plain HTTP is not permitted, and only system‑trusted certificate
authorities are accepted.

Permissions the app requests

  • Location (precise; “Always Allow” on iOS / “Allow all the time” on Android) — optional; off by default. Required for hands‑free Auto Open.
  • Background execution / foreground service (location) — on iOS, to receive location updates while the app is backgrounded; on Android, a foreground service briefly runs a high‑accuracy check as you approach a gate, so Auto Open can trigger.
  • Notifications (Android) — to show the ongoing “watching for gates” notice and gate‑opened confirmations.
  • Speaker / audio output (iOS) — to speak an audible confirmation of an Auto Open event.
  • Face ID / Touch ID (iOS) or Biometrics (Android) — optional; used to protect saved credentials.
  • Internet / network state — required to communicate with the TeloGate service.

Required‑reason API declaration (iOS)

Per Apple’s requirements, the app declares its use of the following required‑reason API categories in its Privacy Manifest (PrivacyInfo.xcprivacy):

  • UserDefaults (reason CA92.1) — to persist your app preferences.
  • File timestamp (reason C617.1) — to display the app’s build date on the sign‑in screen and to enforce a size limit on JSON files you import as an administrator.

Children

TeloGate is not directed to children under 16, and we do not knowingly collect information from them.

Changes to this policy

We may update this policy; material changes will be reflected by the “Last updated” date above.

Contact

ZipDX LLC – support@zipdx.com