Your Code. Your Rules.

Account Security

Manage your password, two-factor authentication, trusted devices, and active sessions from Settings → Security.

Change Your Password

Step 1 - Open Settings → Security

Locate the Password card.

Step 2 - Submit Your Current and New Password

Enter your current password and a new password of at least 8 characters. If two-factor authentication is already enabled, confirm the change with a verification code.

Step 3 - Done

git.eu confirms the change and emails a notification to your account address.

Enable Two-Factor Authentication (TOTP)

Two-factor authentication (TOTP) adds a time-based one-time code from an authenticator app to every sign-in.

Step 1 - Start Enrollment

From the Two-Factor Authentication card, click Enable. git.eu generates a scannable QR code plus a manual-entry secret and otpauth:// setup link.

Step 2 - Scan or Enter the Secret

Scan the QR code with an authenticator app, or type the secret manually if your app has no camera access.

Step 3 - Verify

Enter the 6-digit code your app generates to confirm enrollment.

Step 4 - Save Your Recovery Codes

git.eu shows a one-time set of recovery codes right after enrollment succeeds. Save them somewhere safe - each code signs you in once if you lose access to your authenticator app.

Trusted Devices

When two-factor authentication is enabled, you can mark a device as trusted at sign-in to skip the verification-code prompt for a limited period. Manage trusted devices from the Trusted Devices card - revoke a single device, or revoke all of them at once (for example after losing a laptop).

Active Sessions

The Sessions card lists every device currently signed in to your account, with its last-active time. Revoke a single session, or revoke every session except your current one.

Sensitive Actions Require Re-Authentication

Changing your username, email, or password, or deleting your account, always re-confirms your identity with your current password (plus a verification code if two-factor authentication is enabled) - even though you are already signed in. This protects your account if a session is hijacked after sign-in.

Next Steps

Ready to get started?

Manage tokens and authorized apps