What "your accounts were merged" means at sign-in

If you've just signed in and seen a "Your accounts have been merged" notice, here's what just happened:

Turtini detected that the email you signed in with belongs to an account that was merged into another one (typically because both shared a verified email and you'd already added the other one as your personal email). To avoid a confusing "wait, where's my data?" moment, the platform automatically swapped your session to the *canonical* account — the one that owns the merged data.

You see this exactly once per merged account, then the next sign-in lands directly in the canonical account without the notice.

What's preserved across the merge:

• Personal data — recipes, dive plans, personal events, activity, favorites, notes, grocery list, saved views — copied to the canonical account
• Vendor relationships — every invoice / subscription / gift card / chat any vendor org has for any of your emails surfaces in your Personal context
• Org memberships — both accounts' memberships consolidate onto the canonical account

What stays "behind" on the absorbed account:

• Nothing functional — the absorbed Firebase Auth identity stays usable as a sign-in alias (you can still type either email when logging in). It's a redirect, not a deletion.
• Reversible — a platform admin can clear the merge pointer if the merge was wrong. Contact support.

The transparent session-substitution flow uses a Firebase custom token minted just-in-time when the absorbed account signs in. The token's auth_time has to be fresh (within 5 minutes) for the swap to happen — a stolen long-lived token can't be parlayed into another account, even one merged with the legitimate owner.

If the auto-swap fails for any reason, you'll be signed out and asked to use the canonical email — no data is lost, just a slightly less seamless sign-in.