Account help

Signing in

Sign in with Google, your existing password, or a code sent to your email. Email codes are available when the server has email delivery configured. Enter your address, then the six-digit code from your inbox. A new address creates an account after verification.

Codes expire after five minutes and work once. Wait one minute before requesting another; a new code replaces the old one. Never share a sign-in code. If email is unavailable, use Google or your existing password. Restored accounts must use their approved recovery sign-in method; email codes cannot bypass that restriction.

Forgot your password? Use Reset your password. If you verify a previously unverified address with an email code, any password set before verification and other saved sessions are removed. This protects your account if someone else signed up with your address. Previously issued access tokens can take up to five minutes to expire. Already verified accounts keep their password.

Changing your password

Open Account settings while signed in. Enter your current password and a new password. Other sessions are revoked after the change; previously issued access tokens may take up to five minutes to expire. Accounts that use only Google or email codes do not need a Pipetrace password.

Changing email or deleting an account

Contact the server operator through Account settings. They must verify ownership and plan deletion of websites, backend projects and retained data before removing your account. An account request does not immediately delete data or change retention. Export anything you need first. Do not send your password, backend key or recovery link to support.

For self-hosted operators

Set runtime SUPPORT_EMAIL to a monitored address. To enable email codes and password-reset emails, configure RESEND_API_KEY and AUTH_EMAIL_FROM using a verified sender, then redeploy the API. Reset links expire after 30 minutes and can be used once; completing a reset revokes existing sessions. Previously issued access tokens may remain usable for up to five minutes. Monitor delivery failures and validate delivery with your own test account before opening signups.

If email is unavailable, restore delivery or verify the original account identity through your established recovery process. Do not bypass identity checks, edit password hashes by hand or reuse reset tokens. Project cleanup and backup expiry are separate from account access.