Together Privacy Policy

Last updated: 8 September 2026

About this policy

Together is a private beta for sharing small moments between two people, using an iPhone app, a compatible Garmin watch app, and a connected server. This policy explains how 44Mort handles information in Together and the developer-operated beta service.

Offline demo mode uses sample content and does not access Apple Health or send that demo content to the Together server. Connected features require a server connection. If you configure a server operated by someone else, ask that operator about its hosting, access, and privacy practices before sending personal information.

Information Together processes

Account and pairing information includes a display name you choose, time zone, a random account identifier, a protected sign-in credential, invitation and pairing records, sharing preferences, quiet hours, and any reunion date or gesture labels you enter. Together does not require an email address to create an in-app account.

Shared content includes messages, gestures, status updates, walk invitations and responses, workout summaries or completion events, and rhythm postcards you choose to share. Records include timestamps, delivery or acknowledgement information, and identifiers used to avoid sending the same item twice.

The iPhone and watch keep local settings, recent shared content, and pending sends. Connecting a watch uses Garmin device identifiers and connection information. If push notifications are enabled and the service is configured for them, the server stores the device notification token.

The server processes connection information, including the connecting IP address, to receive requests and prevent abuse. Rate-limit records use hashed identifiers. Together's server application logs fixed operational events rather than message bodies or sign-in credentials.

If you email support, the contact mailbox and its email provider receive your email address, message, and any attachments you send. Please avoid including health records, passwords, or pairing codes.

Optional health and fitness information

Apple Health access requires your permission. Automatic workout sharing also requires you to enable it in Together for the current partner and selected source. Shared workout summaries can include the activity type, duration, completion time, source name, and a source identifier. Automatic sharing is limited to eligible new workouts after you opt in.

If you choose a saved heart-rate sample in the iPhone app, Together requests the relevant Health permission and lets you review the sample before sharing a rhythm based on it. The shared postcard can contain the heart rate, source, and measurement time. It is not a live heartbeat recording.

The Garmin beta can send supported workout completion events when sharing is enabled. Real heartbeat capture is disabled in this watch beta. Generated sample rhythm postcards are labelled as examples.

Together does not write to Apple Health, read contacts, or collect GPS routes or precise location. Health and fitness information is used for the sharing features you choose, not advertising, marketing profiles, data brokerage, or sale.

How information is used and shared

Information is used to establish your account and partner connection, deliver and display the moments you share, maintain recent history, honour your sharing preferences, prevent duplicate delivery and abuse, and respond to support or deletion requests.

Your paired partner receives the profile and content shared through your connection. Shared content is also processed by the connected Together server. The server operator can technically access stored content; Together does not provide end-to-end encryption.

When configured, Apple Push Notification service receives device tokens, an event identifier, and a generic notification. Together does not include message text or health values in that push payload. The Garmin companion SDK and Garmin Connect support communication with your watch. Apple and Garmin process information within their services under their own privacy policies.

The current beta has no advertising, third-party analytics, or third-party crash-reporting integration added by Together. 44Mort does not sell or rent Together user information. Information may be disclosed when required by applicable law.

Data submitted to Together is submitted to its developer or your selected server operator, not to Garmin as the operator of Together. Garmin has no responsibility or liability for data submitted to Together.

Storage and retention

Connected beta content is stored on the configured server and cached on participating devices. Remote connections require HTTPS. The iPhone uses protected local files for its private cache and pending sends, excludes those files from device backups, and stores the sign-in credential in the device Keychain. These protections do not prevent a person with access to an unlocked device from viewing the app.

Shared events and workout import records become eligible for server deletion after 30 days. Walk records are pruned 30 days after the planned start. Cleanup runs during normal server activity and maintenance, so an offline server may retain records until it next runs. Invitations expire after one day and their remaining records are removed one day after expiry. Accounts and profiles remain until deletion.

Some events expire for delivery sooner than they disappear from history. Failed or unsent items can remain on a device until you remove them or clear the account. An offline device can keep cached content until it reconnects and refreshes or you reset the watch app.

No automated server backup service is configured for this beta. Deletion from the active database does not guarantee immediate removal from filesystem snapshots or independently created backups. If you run your own server, you control its storage, backups, access, and retention.

Your choices and deletion

You can edit your display name and time zone, disable automatic workout sharing in Together, revoke Health and notification permissions in the relevant iPhone settings, and disconnect your partner. Revoking Health permission stops future authorised reads; it does not automatically recall content already shared.

In the iPhone app, open Settings and choose Delete account to request deletion of your server account, its device tokens and invitations, and the shared relationship data. Disconnecting a pair removes that pair's shared server history for both partners. An account deletion needs a successful server connection; a pending request is retried when you reopen and reconnect.

Deletion cannot recall screenshots, copies a partner has made, or notifications already delivered by another service. Reconnect and refresh offline devices, or use the watch app's local reset, to clear remaining cached shared content.

For access, correction, deletion, or other privacy requests, contact jodiderot@gmail.com. If you cannot use in-app deletion, describe the request without sending your sign-in credential or invitation code. We may need limited information to verify that the request concerns your account.

This public policy page

This page is hosted by Telegraph. Visiting it sends ordinary web request information, such as your IP address and browser information, to the hosting service, which may keep technical logs and page-view counts. This page contains no Together account form and does not connect to the Together app server. Hosting this policy does not upload your app messages or health information to Telegraph.

Changes and contact

This policy applies to the beta features described above. It will be updated when Together's collection, use, storage, sharing, or hosting practices change. The latest version will remain at this address, or this page will direct you to its replacement.

Developer: 44Mort. Privacy and support contact: jodiderot@gmail.com.