Privacy of a shared alarm: what your partner should see

A shared alarm is a logistics tool. It is not a location tracker, a sleep score, or a way to check whether someone is home. The useful version shows the wake plan both people agreed to. Everything else stays off the table unless you add it on purpose.

SyncUpAlarm's privacy policy says the product may use account details you provide, alarm times, labels, sync status, and pairing metadata needed to run the sync, plus device diagnostics. It also says personal information is not sold. Read that page for the legal description. This article is the household version: what to share, what to refuse, and how to pause.

Share the plan, not the person

Both people should be able to see:

• The shared wake time or window.
• Which days it repeats.
• The snooze rule you wrote down.
• Whether the shared alarm is on, paused, or changed.
• The challenge you picked, if you use one.

That is enough to stop the midnight text. It is not a feed of someone's night.

Keep these out of the shared view unless you have a separate, explicit reason:

• Live location, home or away status, or "last seen."
• Health data, sleep stages, or a bedtime score.
• A camera, microphone, or photo check.
• A public streak other people can see.
• A log you would be embarrassed to show the other person.

Apple's Clock app already keeps a personal alarm on one phone. A partner cannot see it unless you tell them. A shared product should be just as obvious about the boundary: pairing is consent, and unpairing ends the shared view.

Consent is the feature

Pair only with someone who asked for the plan. Roommates, friends, and partners all count. A surprise alarm on someone else's phone is not a romantic gesture. It is someone else's morning.

Either person should be able to pause for illness, travel, or a short night without a speech. Put that in the shared wake agreement before you turn the alarm on. If one person cannot pause, the setup is pressure, not coordination.

Mohr, Cuijpers, and Lehman describe supportive accountability as expectations the person helped define, with a supporter who is trusted rather than controlling. A wake challenge fits that only when both people choose it. A challenge that one person uses to catch the other does not.

What a challenge proves

A short challenge — a memory match, an emoji, a tap pattern, or tiny math — shows that someone completed a wake step. It does not show where they are, whether they are safe to drive, or how they slept. Do not treat a missed challenge as evidence of anything except a missed challenge. The fallback you agreed on is a message or a call, not an investigation.

Practical rules

1. Read the privacy policy together once, while you are awake.
2. Name the fields you are willing to share: time, days, on or off, challenge result.
3. Refuse location and health data as part of the wake plan.
4. Test unpair and pause in the daytime so both people know the exit.
5. Change the rules in daylight, not at 6 a.m.

If the product cannot do step 4, do not use it for a shared morning.

Sources

• SyncUpAlarm privacy policy: syncupalarm.com/privacy
• Mohr DC, Cuijpers P, Lehman K. "Supportive Accountability." Journal of Medical Internet Research, 2011. PMC3221353.

FAQ

Does a partner alarm need my location?

No. Waking at an agreed time does not require location. Time zone math can be done once on a calendar. See time zone alarm math.

Can I pause without explaining my night?

Yes. A pause for illness, travel, or a bad night should be enough. The reason can stay private.

Is a wake challenge surveillance?

It is a short task you both chose. It becomes surveillance if it is secret, endless, or tied to location or health data.