Your sessions, backed up and synced

How sync works

Every session has a UUID—a unique, immutable ID assigned at creation. When Moda syncs, it matches sessions by UUID. New sessions upload. Existing sessions update only if the local version is newer than what's on the server. No overwrites. No conflicts.

Supabase Edge Functions handle the backend. They verify HMAC signatures on every session to prevent tampering. If a signature doesn't match, the sync is rejected. You can't fake hours.

New device? Sign in and go.

Got a new iPhone? Sign in with the same account and Moda pulls everything down. Sessions, supervisors, profile, purchase status. It merges remote data with anything stored locally and de-duplicates by session ID. No manual export. No CSV files. No "contact support to transfer."

Transparent by design

There's no manual sync button. Moda syncs in the background whenever you're connected. Open the app, finish a session, edit something—changes push automatically. Failed syncs retry on the next connection.

In Settings, you'll see "Last synced" with a timestamp. That's it. No progress bars, no sync status screens. It just works, and tells you when it last happened.

Family sharing

If you buy Moda, linked drivers on your account get it too. One parent pays, both teens in the family get full access. Your purchase syncs alongside everything else—no separate codes or family plan setup.

Tamper prevention

Every session carries an HMAC-SHA256 signature computed from its data. The server verifies this signature during sync. Edit a session's duration in a database dump and try to upload it? Rejected. The signature won't match. This matters because permit logs need to be trustworthy—and Moda makes sure they are.