Account security
Passwords, passkeys, two-factor authentication, sessions, re-authentication, and what happens to your data when you leave.
Signing in
Sign in with an email address and password, a passkey, or GitHub. All of the settings below are under Settings → Account. You can link a GitHub identity to an existing account and unlink it again. Unlinking needs a password on the account, so if you signed up through GitHub, set one first.
Changing your password signs out every other session and keeps the one you are using. Resetting a forgotten password signs out every session.
Passkeys
A passkey signs you in with Touch ID, Windows Hello, or a security key, with no password. The device verifies you, so a passkey sign-in does not also ask for a TOTP code. Each passkey shows when it was added and last used, and whether it syncs between your devices. Rename one at any time. Removing one stops that device signing in with it.
Two-factor authentication
TOTP, from any authenticator app. Enrolment shows a QR code and the secret, and confirming it returns one-time recovery codes. You can regenerate the codes at any time, which invalidates the previous set, and disabling TOTP removes them. The team member list shows who has a second factor enrolled.
Sessions
Sessions lists every browser and app signed in as you, with its IP address, when it signed in, and when it was last active. Sign out any one of them, or every session except the one you are using. A signed-out session ends on its next request. Access tokens are not sessions: signing out, changing your password and resetting it all leave them working. Revoke those under Access tokens.
Re-authentication
Some actions ask for your password again even though you are signed in, and accept it for five minutes: enrolling or disabling TOTP, regenerating recovery codes, adding or removing a passkey, creating an access token, signing out other sessions, linking or unlinking GitHub, transferring team ownership, force-deleting a site, and deleting your account. Running a command as root asks as well, with a shorter window. An access token can never satisfy this check.
Exporting your data
Download a JSON export of your personal data and your team's resources under Your data. It leaves out secrets: no private keys, database passwords, integration tokens, TOTP secret, or environment variable values. Environment version history is included without the contents. Public keys are included, so you can rebuild the setup elsewhere.
Deleting your account
You delete your account yourself, under Your data, and it cannot be undone. It needs your password and your email address typed to confirm. Provisore erases everything it holds for you and the team you own: server and site records, deployments, environment versions and their contents, certificates, jobs and their logs, databases, daemons, cron entries, firewall rules, SSH keys, notification channels, alert rules, backup configuration and history, integration tokens, and every session.
Stripe keeps the customer record your team's invoices are attached to. If you agreed to link product analytics to your account, your PostHog profile is deleted with it. The Privacy Policy says what each holds.
Your servers are not touched. Nothing is uninstalled and no cloud instance is destroyed. Your sites keep serving and you keep root access, and Provisore stops managing the machines. Delete the servers first if you want the cloud instances removed too.
Provisore cancels an active subscription before it erases anything, and deletes nothing if the cancellation fails. It also refuses if you are the sole owner of a team with other members. Transfer ownership first.
Provisore connects over SSH as a deploy user with sudo, using a key installed during provisioning and the host key recorded then. Removing the server from Provisore, or removing that key from authorized_keys, ends the access.