Account and security

A passkey uses a cryptographic credential for GoSavis. Your authenticator asks you to verify yourself using its supported method, such as a device PIN, fingerprint or face. GoSavis receives the sign-in result and public credential information, not your fingerprint, face or device PIN. Passkeys reduce phishing risk, but you must still secure your device and any password-manager account and recovery route.

You can use a supported passkey or an authenticator app. A passkey must satisfy GoSavis’s required user-verification checks where it is relied on for stronger authentication. Choose a method you can keep secure and keep an independent recovery method. Do not assume that a touch confirming presence alone meets every verification requirement.

Open Settings, then Passkeys and two-factor, and choose Add a passkey. Follow the browser and authenticator instructions. Check the entry shown in Settings and save the recovery codes supplied. Keep recovery codes secure and separately accessible; do not share them with anyone claiming to help you sign in.

Where your browser and devices support it, you can use the phone-assisted sign-in option and follow the displayed instructions. A synchronised passkey may also be available through your password-manager account on another device. Availability and recovery depend on that provider’s settings and safeguards; GoSavis cannot restore its account for you.

“Synced” describes the authenticator’s reported ability to make the credential available through its provider. It is not a promise that GoSavis can recover it or that all devices hold independent backup credentials. A device-bound credential, such as one on a security key, may be unavailable if that device is lost. Provider labels and capabilities can differ.

A second copy of the same synced credential may depend on the same password-manager account and is not necessarily an independent backup. Consider a separately protected factor or securely stored recovery codes. Protect the provider’s own recovery route as well as your GoSavis login.

These are single-use codes that can be used in place of an unavailable passkey or authenticator-app code under the sign-in process. Each works once. Store them securely and separately from the device you may lose. Replacing the set in Settings stops the old set working. A completed two-factor reset also revokes the old codes.

The business-management and payment-account functions require the protection explained in the Operator Agreement. Everyone operating or working for a business must set up the required factor. For an ordinary customer account it remains optional and recommended, subject to any separately explained verification for a sensitive action.

Check your provider’s instructions for accessing a synced passkey or transferring an authenticator. Do not erase the old device until you have tested an available sign-in and independent recovery method. Once the new setup works, review signed-in devices and remove unwanted sessions. Removing a GoSavis credential can disable all synced copies of that credential, not just one phone.

Use another available factor or recovery code, then review and end the lost device’s sessions and revoke compromised factors as appropriate. Secure the device and password-manager account through their providers. Do not assume the lost phone is safe merely because it had a screen lock. Before removing a synced passkey, understand that its other copies may stop working with GoSavis too.

After checking your password, we send the initial code to your current account email. If that address changed within the previous 14 days, a separate single-use confirmation goes to the previously verified address in our own change record, never an address supplied in the request. Repeated changes require a complete trusted history and review. A new request within 14 days of a cancellation also needs review. Higher-risk businesses receiving payouts or paying by Direct Debit, and people managing their billing, team or ownership, need independent review and an outbound callback to the onboarding number. A recent ordinary profile edit is not a recovery contact, and possession of the phone alone is insufficient. The onboarding number is held to verify recovery and authority, not for marketing; it is retained while needed for that purpose and removed when the account is erased. Any replacement would need a separate securely verified recovery-contact process; ordinary profile editing cannot establish one. If you cannot complete required historical-email or callback checks, contact support. Our reviewers cannot remove protections immediately, and exceptional recovery is not available until its independent evidence and approval controls are defined. Recovery is not guaranteed.

Use the cancellation route in the message or the verified reset card in Settings. Using an existing valid factor while the reset is waiting cancels it too. Secure your password and email and contact support where needed. For 14 days after cancellation, a new request requires review before its waiting period begins. Do not disclose codes or links to someone offering to cancel the request for you.

Old passkeys, authenticator factors, recovery codes, sessions and remembered-device trust stop working immediately. Sign in through the permitted route and set up a fresh factor before using business functions that require stronger authentication.

For seven days after completion, changing payout destinations or the account email, adding owners, and granting or expanding team access are paused. Ordinary payouts to the existing verified destination and existing authorised team access continue unless a separate justified security restriction applies. Verified security removals remain possible. Export and deletion requests use a verified route; they do not automatically open or become unavailable.

No instant bypass is available. Reviewers cannot remove protections on the spot or treat a recent ordinary phone/email edit as a trusted recovery contact. An exceptional route for people unable to complete the required historical-contact checks is not currently available. We do not routinely ask for identity documents for recovery. We explain the available route and do not guarantee recovery where the required ownership or authority checks cannot be completed.

The additional old-address link is single-use and lasts 72 hours from issue, but cannot be used after the request itself has expired or closed. All request deadlines run from when we received the request. It expires after 14 days unless every required step has been completed and the request approved within that period. The full 72-hour security wait starts only after the last required check, including any required historical-address confirmation, independent review and callback. An approved request that has not completed expires 21 days after receipt. Sending another link does not restart either deadline or shorten the wait. A fresh request follows the applicable review controls and does not revive an expired token.

Supported sign-in methods may be used across devices. Settings lets you review and end sessions. A two-factor reset is different: it ends existing sessions and remembered-device trust. If you suspect unauthorised access, use the verified security routes, secure your credentials and contact support.

Follow the account’s deactivation or erasure process. Those are distinct, particularly where credit entitlements remain. GoSavis can revoke acceptance of a credential, including its synced copies, but cannot remove a copy in your password manager; follow that provider’s instructions for deleting it. Do not destroy your only recovery method before understanding how secure reactivation of the original account works.

Use the "Forgot password" link on the sign-in screen. We will email you a one-time link that lets you set a new password; the link expires after a short time for security reasons. If you do not receive the email within a minute or two, please check your spam folder before requesting another.

Closing your account immediately disables sign-in and removes your profile from the platform. We retain only the information we are legally required to keep (for example, transaction records for tax purposes) and delete or anonymise the rest in line with our Privacy Policy.