A clear view of
how your data is used.

01About this policy

This policy covers the Tailgate app, its developer-operated notification relay, and these support and privacy pages. Tailgate is an independent client for Frigate. You do not need a separate Tailgate account to connect to your own server.

Your Frigate server and any services you configure have their own data handling and retention settings. This policy does not control how your server administrator records, stores, or shares camera footage.

02Information on your device

Tailgate stores the server addresses and account credentials you enter, saved server identifiers, connection settings, camera preferences, and caches on your device so it can reconnect and display your cameras. Credentials are sent to the Frigate server you configure to sign in and make authenticated requests; they are not sent to the notification relay.

Video, audio, snapshots, recordings, and event information travel between the app and your configured Frigate server using your chosen connection. They are not uploaded to a Tailgate video-hosting service. If you use Tailscale, the connection may use Tailscale’s network infrastructure as described below.

Permissions you control

• Local network: to connect to Frigate on your network.
• Microphone: when you use push-to-talk, to send audio to your camera through Frigate.
• Photos or storage: when you choose to save a snapshot or recording.
• Notifications: when you choose to enable native alerts.

The app can keep connection diagnostics on your device to help troubleshoot errors. These logs are not automatically uploaded to Tailgate support. You can clear them or turn off log writing in the app. Files you save or share are handled by the destination app or your device’s photo, file, and backup settings.

03Optional push notifications

If you enable notifications, the app creates a random installation identifier and a separate secret credential. The credential is kept in iOS Keychain or encrypted using Android Keystore; the relay stores a hash of it to authenticate management requests.

The relay processes:

• Your installation and saved server identifiers, and your Frigate account identifier, which is combined with those identifiers into a hash to keep registrations separate.
• Your device’s push token, platform, push environment, subscription keys, and notification preferences, including pause, quiet hours, language, and camera cooldown.
• Notification titles, message text, and supplied event, review, or camera identifiers needed to display an alert and open the correct item.
• Receipt timestamps, delivery attempts and results, and hashed identifiers used to suppress duplicate alerts.

Frigate sends an encrypted Web Push message to the relay. The relay authenticates and decrypts it, prepares a native notification, and sends the notification and device token to Apple Push Notification service on iOS or Firebase Cloud Messaging on Android. This is not end-to-end encryption between Frigate and your phone: the relay and the push provider process the alert content.

The relay does not fetch your camera streams, recordings, snapshots, or notification image URLs. However, information included by your Frigate server in notification text or other payload fields is received by the relay. Avoid putting sensitive information in alerts, and use your device’s notification-preview controls if needed.

04Optional Tailscale connections

If you connect Tailscale, the embedded Tailscale client communicates with Tailscale’s authentication, coordination, and, when needed, encrypted traffic-relay services. Tailscale processes the account, device, network, and diagnostic information described in its privacy policy. Your Tailscale sign-in credentials are entered on Tailscale’s sign-in page.

Tailgate stores the resulting node identity and connection state locally. This connection is scoped to Tailgate’s Frigate traffic; the app does not install a system-wide VPN profile. Removing a local Tailscale profile does not remove the device from your Tailscale administration console. You can also revoke that device through Tailscale.

05Service providers and sharing

We share information as needed to operate the features you use:

Cloudflare

Hosts these pages and the notification relay, including its database, message queue, duplicate-suppression storage, and operational logs.

Apple and Google / Firebase

Deliver native notifications on their respective platforms and process device tokens and notification content.

Tailscale

Provides the optional network connection you authorize.

Your Frigate server and services you choose

Handle the camera connections, account requests, media, and any exports or sharing you initiate.

These providers may process information outside your country. Their privacy notices describe their own practices. We may also disclose information when legally required or necessary to protect the service and its users. Tailgate does not include advertising SDKs or third-party behavioral analytics. These pages do not set application cookies or use analytics scripts; the hosting provider may process technical request information.

06How long information is kept

• Local app information: stays until you remove it, clear app data, or your device removes it. Local connection logs have a seven-day retention window, with cleanup when the log store is used. Saved photos, downloads, and device backups are managed separately. Some iOS Keychain items can remain after uninstalling.
• Installation and subscription records: have no automatic expiry in the current relay. Revoking a subscription stops future delivery but does not automatically erase its stored registration, encrypted token, keys, or preferences. You can request deletion by email.
• Notification delivery records: contain encrypted notification content. The relay accepts a message lifetime of up to 24 hours and schedules records for deletion 24 hours after expiry. Cleanup runs hourly and may be delayed by service interruptions.
• Duplicate-suppression markers: expire after 24 hours for review alerts, or after the camera cooldown window (between 60 seconds and one hour in storage).
• Rate-limit records: expire shortly after their request window and are removed by hourly cleanup.
• Support correspondence: is kept as needed to answer your request, follow up on the issue, and meet applicable legal obligations.

Push tokens, receiver secrets, and notification content are encrypted in the relay database; the relay decrypts them when needed to deliver alerts. Service access is restricted, but no storage or transmission method can guarantee absolute security. Provider backups and records retained for legal or security reasons may follow separate retention periods.

07Your choices and privacy rights

You can use Tailgate without enabling push notifications or Tailscale. You can change device permissions in system settings, remove saved servers, clear local connection logs, and revoke Tailscale devices.

To stop a server’s alerts and revoke its relay subscription, open Settings → Notifications → Forget this device for that server. If you are offline, the app queues the removal and retries when connected. Turning off notification permission in system settings only controls presentation; it does not erase relay records.

Depending on your location, you may have rights to access, correct, delete, or receive a copy of your personal information, restrict or object to certain processing, withdraw consent, or complain to a data-protection authority. Contact us to exercise these rights. We may verify your request and retain information where permitted or required by law. Where applicable, we process data to provide the service you request, with your consent for optional features where required, for legitimate security and reliability interests, and to meet legal obligations.

Tailgate is not directed to children under 13. If you believe a child has provided personal information to the service, contact us so we can investigate and take appropriate action.

08Contact and policy updates

For questions about this policy or the Tailgate developer’s handling of your information, email tailgate@tianyi.li. For connection or app issues, visit Tailgate support.

We will update this page when our practices change and revise the date above. Where required, we will provide additional notice or request consent for material changes.