LatchPrivacy Policy
HomeSupport
Public privacy notice

Latch Privacy Policy

Last updated: August 13, 2026

Summary

Latch has no advertising, analytics SDK, or cross-app tracking. It stores the feeding information you enter so the app, its widgets, and trusted caregivers using your family code can provide the features you request.

1. Information Latch handles

Latch handles the information needed to provide feed tracking and family synchronization:

  • Feeding records, including side, start time, optional duration, and update time.
  • An optional caregiver display name attached to records that caregiver creates or edits.
  • A randomly generated installation identifier used to show who recorded a feed.
  • A randomly generated family code used to group records shared by trusted caregivers.
  • Local app state, such as the active timer, recent feed cache, and pending offline changes.

Latch does not require an email address, phone number, or Latch account.

2. Where information is stored

Latch stores recent app and widget data on your device in a shared iOS app container. When iCloud is available, feed records, the optional display name, installation identifier, and family code are stored in Apple's CloudKit service so feeds can synchronize between authorized devices.

Latch uses a CloudKit public database. Records are separated by the family code. Anyone who knows a family code may be able to view or change that family's feed records, so treat the code as private and share it only with trusted caregivers.

3. How information is used

  • To show the latest feed, history, timer state, and suggested side.
  • To update Home Screen and Lock Screen widgets.
  • To synchronize feed history among devices using the same family code.
  • To deliver optional reminders and family activity notifications when you allow notifications.
  • To process edits and deletion requests.

Latch does not sell personal information and does not use feed data for advertising or tracking.

4. Sharing and service providers

Information is shared with Apple only as needed to provide iCloud/CloudKit storage, synchronization, and push notifications. Caregivers who receive your family code can access and modify the same family feed history.

Information may also be disclosed when required by applicable law or a valid legal process.

5. Retention and deletion

Feed records remain in CloudKit until they are deleted. You can delete individual feeds in Latch. To permanently delete all feed records associated with the current family code, open Family Sharing, select the permanent family-data deletion action, and complete the typed confirmation. After the CloudKit deletion succeeds, Latch clears the local feed cache, display name, timer, installation identifier, and family code and creates a new private family code.

Removing the app from a device clears local app data but may not delete synchronized CloudKit records. Use the in-app permanent deletion action first when you want the synced family data removed.

6. Notifications

If you grant notification permission, Latch may schedule a local reminder based on the latest feed and may use Apple push notifications to alert devices when a caregiver changes a shared feed. Notification permission is optional and can be changed in iOS Settings.

7. Children

Latch is intended for parents, guardians, and caregivers, not for children to use directly. Adults are responsible for the information they enter about feeding activity.

8. Security

Latch relies on Apple's platform security and CloudKit transport and storage protections. No system is completely secure. Keep your family code private and reset or delete the family data if the code is shared with someone who should no longer have access.

9. Changes

This policy may be updated when Latch's features or legal obligations change. The revision date at the top identifies the latest version.

10. Contact

For privacy questions or requests, email [email protected].

© 2026 Latch · Home · Support