Personal CRM two-factor authentication adds a second step between your password and the relationship context you have chosen to keep. Set it up while your authenticator is in your hand, then store the backup codes somewhere you can reach without it.
That second part is easy to postpone. It is also the part you will care about if your phone is lost, replaced or unavailable.
What two-factor authentication changes
A password is one proof that the person signing in is you. With two-factor authentication, Kinnetly also asks for a current six-digit code from your authenticator app.
That extra check matters if someone obtains your password. A password alone should not complete a normal protected sign-in. The Australian Cyber Security Centre and the US Federal Trade Commission both recommend multi-factor authentication as an added layer for online accounts.
It does not make an account untouchable. It cannot protect a device where you are already signed in, stop every phishing attempt or make a reused password safe. Keep using a strong, unique password.
Prepare the recovery path first
Before you enable 2FA, have three things ready:
- your chosen authenticator app
- access to your Kinnetly account settings
- a protected place for the one-use backup codes
The backup-code location should be available if the device holding your authenticator is not. A password manager or another protected store you can reach independently may fit. Your inbox and your relationship notes do not.
Backup codes are credentials. Do not email them to yourself, paste them into a contact record or keep the only copy on the same phone as the authenticator.
Enable 2FA in Kinnetly
In Kinnetly, open Settings, then Profile & account. Find Two-factor authentication and select Enable 2FA.
Kinnetly will show a setup QR code and a setup key. Scan the QR code with your authenticator app, or enter the setup key manually. The app will begin creating short-lived codes. Enter the current code in Kinnetly to confirm the setup.
Treat the QR code and setup key as secrets. They can be used to produce future sign-in codes, so they do not belong in screenshots, support messages or notes.
Once setup is complete, Kinnetly will ask for a six-digit authenticator code after your password when you sign in.
Save the backup codes before closing setup
Kinnetly provides one-use backup codes during setup. Save them immediately in the protected location you chose.
Each code can be used once. If you regenerate the set later, the old set stops working. Replace the stored copy rather than leaving both versions around and guessing which one is current.
The ACSC also recommends saving backup codes in case you lose access to your authenticator. This is not the same as backing up your personal CRM data. A Kinnetly network backup preserves relationship records. A 2FA backup code helps you pass the account sign-in check. They solve different problems.
If your authenticator is unavailable
Use one saved backup code at sign-in. In Kinnetly, signing in with a backup code after losing the authenticator turns 2FA off. Go back to Settings, enrol a new authenticator and save the new backup-code set straight away.
If you lose both the authenticator and every backup code, recovery is not self-service. Kinnetly's current account guidance says an administrator can reset 2FA, but you should not treat that as an instant recovery path. Use the site's contact page for help.
This is why the best time to prepare recovery is during setup, not after a phone disappears.
Check the setup without exposing a secret
You do not need to publish or deliberately consume a backup code to check your work. Confirm that:
- Kinnetly shows two-factor authentication as enabled
- your authenticator has a Kinnetly entry and is generating codes
- the backup codes are saved outside the authenticator device
- you know how to reach that protected copy
Do not put a real setup QR, one-time code or backup code in a screenshot. Even an example can become a live credential if it was captured from your account.
Keep the control in proportion
Two-factor authentication protects the sign-in flow. It is not end-to-end encryption, an offline vault or a substitute for deciding what belongs in your notes. Kinnetly says its data is encrypted in transit and at rest, but it is not end-to-end encrypted. Those controls address different risks.
If you use Kinnetly as a private personal CRM, enable two-factor authentication while you still have time to store the recovery path properly. Then keep recording only the relationship context you have a reason to remember.
Create your private relationship map with Kinnetly, then enable 2FA in your account settings.
