The timer works without an account or advertising profile; sharing is optional and separated from the local record.
A sensitive moment should not become an advertising signal
Contraction timing can reveal that a family may be entering labor. That is intimate context, even when the record contains only timestamps and durations. A free timer does not need to fund itself by turning that moment into an advertising profile.
Between Contractions therefore has no advertising SDK and no analytics SDK. The core timer does not require an account. Product decisions should be understandable without asking a family to read a privacy policy during labor, though the full policy remains available for anyone who wants the details.
What “local-first” means here
In the browser app, contraction history is stored in local browser storage on the current device. Closing and reopening the page can preserve the record, but clearing site data, using a private session, or changing devices can remove or separate it.
On Apple devices, personal history can use the user’s private iCloud container so their own devices stay connected through Apple’s system. That personal record is distinct from the optional Partner Sync relay.
Sharing should be a deliberate mode
Some families want a partner, doula, or relative to see and coordinate the same live timer. That requires data to move between accounts and platforms. Between Contractions treats this as a separate paid feature with an explicit group and pairing flow—not as a hidden side effect of opening the app.
Only the data needed to keep invited devices synchronized should pass through that relay. Personal iCloud data does not pass through it, and the local timer remains available without a subscription or network connection.
Privacy includes honest limitations
Local storage is not the same as an encrypted medical record or a guaranteed backup. Device backups, operating-system diagnostics, and browser behavior remain subject to the user’s platform settings. A privacy-first product should explain those boundaries instead of using “private” as a vague promise.
The practical goal is data minimization: collect less, keep the default record close to the person using it, and make every broader sharing path visible and optional.