Skip to main content

​
Device Marriage Protocol

Device Marriage is an anti-circumvention security mechanism that binds a CommitT account to a single physical device for the duration of active commitments. This prevents users from logging into their account on a friend’s phone and asking them to verify on their behalf.

​
The Problem

Without device binding, the following exploit is trivial:
  1. User creates a “Morning Gym” commitment with location verification at their gym
  2. User gives their credentials to a friend who lives near the gym
  3. Friend logs in on their own phone and verifies the commitment without the user ever going to the gym
  4. The system records a successful verification — the user cheats without consequence
Device Marriage eliminates this attack vector entirely.

​
How It Works

When a user signs in and creates their first commitment, the system records a device fingerprint consisting of: This fingerprint is stored in the Convex cloud backend alongside the user’s account.

​
Enforcement Rules

​
Example

A user has active commitments on their Samsung Galaxy (Phone A). They try to log into CommitT on their friend’s Pixel (Phone B). The system checks the Convex backend and finds that:
  • Account has 3 active commitments
  • Device fingerprint is bound to Phone A
  • Phone B’s fingerprint does not match
Login is rejected with the message: “This account is currently bound to another device. Complete or delete your active commitments before switching devices.” Once all three commitments are completed or expired, the device marriage is released, and the user can log in on Phone B freely.