Reference
Account and privacy
The account identifies who uses Deck and records that you accepted the terms. It holds none of your code, and usage metrics go off with one click.
Why there is an account
The account identifies you in the app and in support, and it keeps the record that you accepted the terms. It syncs nothing: projects, sessions and connections stay with that installation, on that computer.
Sign in or sign up
There are two ways in, and both reach the same account when the email is the same:
- Email and password. The password needs at least 12 characters. Firebase Authentication is what looks after it, and it is never written to your computer.
- Google account. The app opens your browser to sign in and gets back a single throwaway code. The attempt is good for ten minutes, and the returning code lasts one minute and works once.
Signing up asks for your name and for you to accept the terms of use. After that, the session lives in the system keychain, which is Keychain on macOS and DPAPI on Windows.
If the system has no secure storage available, Deck does not write the credential in plain text. The login then lasts only while the app is open, and the screen says so.
Offline
After one successful login, Deck keeps working with no internet. What needs the network is the agent itself, not the app.
When the connection comes back, a revoked credential asks for a new login. Installations that already existed before the account became mandatory get a 14 day grace period to create the account without interrupting work.
Sign out and switch accounts
Signing out clears the stored credential, and that is all it does. Projects, sessions, worktrees and the GitHub and ClickUp connections stay on the computer, because they belong to the installation.
Switching accounts in Deck does not separate environments. Anyone with access to the same operating system account reaches the same files and the same sessions. To keep people apart on one machine, use separate system accounts.
If you suspect someone got into your account, change the password and use the option to end every session, which invalidates access on all computers at once.
What Deck keeps
| Where | What |
|---|---|
| On the server | Name, email, account id, and the version and date of the terms you accepted. |
| On your computer | Projects, sessions, terminal history, preferences and connection tokens, encrypted. |
| Nowhere | Your code, your prompts and what the agents answer. None of it goes through a Maze Analytics server. |
The full list, with legal basis and retention periods, is in the Privacy policy.
Turn off usage metrics
The app sends operational usage events, such as version, platform and the life cycle of sessions. They come on and go off with one click:
- Open Settings.
- Look for Usage metrics.
- Turn the switch off. Sending stops at once and whatever was queued is dropped.
Prompts, answers, typed commands, keystrokes and full folder paths are never part of these events. The project name, as you wrote it in Deck, is.
Delete the account
Write to deck@mazeanalytics.com.br and ask for deletion. We confirm your identity before we run it.
Deleting the account erases nothing from your computer. The local files stay where they are, and the list of them is in Where the files live.