About Kepotek

Kepotek is an Indonesian technology blog covering Android tips and tricks, smartphone reviews, gadget comparisons, games, app reviews, Windows, and general tech news. Articles are written by contributors including Micael Freddy, Lina Liyana, and Yogi Loka, spanning topics from device specifications to blogging how-tos.

Content is organized across dedicated sections so readers can jump straight to smartphone specs, gadget comparisons, or game guides depending on what they're curious about.

What You'll Find

B

Blog

General tech articles, how-to guides, and posts on blogging, SEO, and web hosting.

G

Games

Game reviews and guides, including a dedicated section for State of Survival.

N

News

Technology news covering gadgets, smartphones, and industry updates.

C

Comparisons

Side-by-side gadget and smartphone comparisons to help with purchase decisions.

Use Google Password Manager securely on Android

Google Password Manager is the password vault built into Android and Google accounts. It can create unique credentials, fill them into apps and websites, flag exposed logins, and store passkeys. That removes the need to reuse a memorable password or keep a handwritten list in a drawer.

Using it securely depends on more than turning on sync. Your Google Account, Android screen lock, recovery details and chosen autofill method all form part of the security chain. Australian Android users often rely on Samsung Galaxy phones, while Google Pixel owners see slightly different menus, so the same setting may sit under Google, Passwords or Autofill.

What Google Password Manager handles

Open Password Manager from the Google apps folder, the quick settings panel, or Settings by searching for “password manager”. Sign in with the Google Account that will hold the vault. The on-screen names differ between Pixel, Samsung and other Android skins, but the essential controls are the same.

Use Password Manager as Android’s autofill service. In Android 9 and later, go to Settings, then Passwords and accounts, then Autofill service; newer releases may place this under Google. Select Google Password Manager, confirm the choice and test it on an ordinary sign-in page. If a password appears only after you tap the field, the service may not be active.

Tap the three-dot menu and choose Settings to turn on password saving and, where available, compromised-password alerts. Google Password Manager can warn when a saved credential appears in a known breach. Treat that warning as a prompt to change the password, not as proof that the account has already been hacked.

Set up Android autofill safely

First, set a strong phone PIN or pattern. A six-digit PIN is better than no lock, although a longer alphanumeric password is stronger where the handset supports it. Biometrics are convenient, but the fingerprint sensor or face unlock should unlock the device and its credential vault rather than replace the PIN entirely. A phone left on a train in Sydney or Melbourne should never expose your saved logins.

Next, review every account already stored in the vault. Remove duplicates, obvious test entries and old shared credentials. Check that each entry points to the correct website because autofill can send a password to the wrong address if a saved URL was edited carelessly.

For device-specific menu help, the collection of Android tips and fixes can help locate the relevant control on different handset makers. Then open Password Checkup, usually found under Security in the Password Manager settings, and address every exposed or very old password it identifies.

Build stronger password habits

Create a different password for every important account, especially email, banking, MyGov and social media. Reused credentials spread one breach across multiple services, a problem often called credential stuffing. Let the generator produce a long combination when you do not need to memorise it.

Before saving a new credential, check its address and app name. Phishing pages can imitate a familiar bank or government service, so a correct-looking name is not enough. If you reached the site through a link in an email, open the app or type the known address directly instead.

Do not treat Google Password Manager as a place for one shared master password for everything. It is designed to store many unique passwords, and its passkey and autofill features can remove even much of that manual work. Keep recovery codes separate from the phone whenever possible.

Prefer passkeys and screen lock

Passkeys are the strongest practical option for supported sites. Instead of sending a reusable secret to the service, the phone creates a cryptographic key pair and confirms the sign-in with biometrics or the screen lock. Open an account’s password options in Password Manager and choose Add a passkey when offered.

Keep the device’s lock screen current, especially after a firmware update. Some biometric prompts can fall back to the PIN, so a forgotten PIN can still become the weak link. Review which apps can use biometrics and disable any that you do not recognise.

Use a hardware security key or another enrolled device as a second passkey where the service allows it. Australian banks and government services increasingly support modern sign-in methods, but availability varies. If a service still sends codes by SMS, protect the mobile account with a carrier PIN or PUK and never share the code with a caller.

Review sharing, alerts and recovery

Check Security notifications for suspicious sign-ins and review active sessions for your Google Account. A new location, impossible travel or an unfamiliar device deserves investigation. Revoke the session, change the affected password and review recovery email and phone numbers.

Family sharing lets partners or household members use selected credentials without exposing the original password. Share only what is necessary, remove access when someone leaves the household and avoid sharing a high-value banking or MyGov login through chat messages. Family groups can also create dependency risks if one person’s account settings are changed.

Recovery is where many otherwise careful users leave a gap. Store backup codes in a secure offline location, ensure a recovery email is active, and test that you can reach it without the current phone. If a security setting is unclear, a second explainer such as Kalemiyet resources can help, but official Google and Australian government guidance should remain authoritative.

Run two quick security checks

Run these checks after setup, then repeat them after restoring or replacing a phone. The lists are deliberately short so they remain realistic on a busy day.

Start with accounts and passwords:

Then check the handset:

The ACCC Scamwatch advice is especially useful when a caller claims there is “no dramas, mate” and only needs a quick code. Genuine banks, telcos and Australian government services will never ask for a password, PIN or one-time verification code. Keep a spare charger and an enrolled second device if you depend on passkeys, and maintain a non-digital recovery plan.

Make secure sign-ins the default

If your phone is slow, lacks current security updates or cannot store passkeys reliably, compare 2025 budget smartphone options before buying. Australian prices are usually quoted in Australian dollars, so confirm local pricing, software-update support and secure unlock features rather than focusing only on camera specifications.

Make a weekly five-minute routine: open Password Checkup, review Security notifications and add a passkey to one important account. Keep autofill selected as Google Password Manager, and use its generator whenever you create a new login. This routine catches reused passwords and suspicious access before they become a full account takeover.

Open Google Password Manager now, enable compromised-password alerts and replace the oldest reused password with a generated one. Then save the recovery codes outside the phone and add a passkey to your primary email account. Secure sign-ins work best as a habit, not a one-off setup.