Your app looks like one thing. It is really a stack of accounts: the builder, GitHub, the host, the database, Stripe, the domain registrar, and the email inbox behind all of them. If one of them is weak, or if an old freelancer still has a login, the whole app is at risk. This post shows how to secure those accounts without locking yourself out. Vendor facts below come from each vendor's own docs, checked in November 2026. It is about the accounts you use to run the app. For the login your own users see, read hardening login in an AI-built app.
Short answer: Write down every account your app needs, who owns it and who else can get in. Start with your email, because it can reset all the others. Turn on two-factor authentication (2FA) everywhere, save the recovery codes offline, and add a second method. Give people their own invite with a role instead of sharing your password. Lock the domain at your registrar. Remove people and rotate keys when work ends. The checklist in section 7 takes about 30 minutes.
1. Make the list first
You cannot protect what you cannot name. Open a notes file or a spreadsheet. Make one row per account. Use these columns:
- Service: for example Lovable or Bolt, GitHub, Netlify or Vercel, Supabase or Firebase, Stripe, your registrar, your email.
- Owner: whose name and email is the account under? Is it yours, or a freelancer's or ex-cofounder's?
- Who else has access: team members, collaborators, invited emails.
- Reset email: which inbox receives the "forgot password" message?
- 2FA on? yes or no, and which method.
Do not forget the quiet ones: the Google account behind Firebase, the account that holds your DNS, the email service that sends your app's mail, and any AI or API provider with a key in your code.
Now look at the "Reset email" column. The inbox that appears most is your master key. Whoever controls that inbox can click "forgot password" on almost every account in the list. So secure it first. Use a strong, unique password and 2FA. Do not use a shared mailbox that three people read. If an account is registered to a freelancer's personal email, change it to an address you own. See how to hand over app access when you hire a developer for the handover side.
2. Turn on two-factor authentication, service by service
2FA means a password alone is not enough. A thief also needs a second thing, such as a code from your phone. Here is what each vendor's docs say today.
Google account (Gmail, Firebase)
Google's 2-Step Verification page says you can add an extra layer of security "in case your password is stolen." It says "passkeys and hardware security keys protect your Google Account from phishing attacks". If you do not use a passkey, it says "we recommend you use Google prompts as your second step." For lost phones it says "you can use a backup code for the second step." Do this one first, since it is probably your email and your Firebase login.
GitHub
GitHub's 2FA page says "GitHub required all users who contribute code on GitHub.com to enable one or more forms of two-factor authentication (2FA)." The second factor is "a code that's generated by an application on your mobile device or sent as a text message (SMS)." Passkeys "satisfy both password and 2FA requirements", and GitHub adds: "to reduce the risk of account lockouts, you should also configure a fallback 2FA method." If you run a GitHub organization, owners "can require that organization members, billing managers, and outside collaborators use two-factor authentication".
Netlify
Netlify's user settings page says that once you enable 2FA, "you're required to enter a temporary authentication code from your authentication app to access teams or organizations connected to that user ID and email. As a fallback, you can use a backup recovery code." It also says that if your team has a Pro plan or higher, an Owner "may encourage or require you" to set up 2FA.
Vercel
Vercel's 2FA page says "All Vercel users must set up an authenticator app by January 20, 2027." It says you can also add a passkey, and to keep your authenticator app and recovery codes "in case you lose access to your passkey." Team owners can require members to enable 2FA, but "Enabling personal 2FA doesn't enable this team setting."
Supabase
Supabase's MFA page says "You can enable MFA for your user account under your Supabase account settings." It warns that turning it on logs your other sessions out. For teams it says: "If you are an organization owner and on the Pro, Team or Enterprise plan, you can enforce that all organization members must have MFA enabled". This page is about the dashboard where you manage the project, not about your app's users.
Stripe
Stripe's two-step authentication page lists the methods "from most to least secure," with passkeys at the top and text messages at the bottom. It says text messages "are unencrypted, require cell reception to use, and are vulnerable to SIM swap and SS7 attacks." Team administrators can "require two-step authentication for everyone on the Team settings page." Money moves here, so use a passkey or security key if you can.
Which method to pick
Where the vendor lists passkeys or an authenticator app, pick those. Use SMS only if nothing else is offered. A password manager that supports one-time codes also works as an authenticator app, as Vercel's page notes.
3. Recovery: do not lock yourself out
2FA protects you from thieves. It can also lock you out. Plan for a lost or broken phone before it happens.
- Save the recovery codes offline. GitHub's recovery methods page says you "should download and store these codes securely" and recommends "saving them with a secure password manager." It also says "don't share or distribute your recovery codes." Netlify says its codes are "only presented once", so copy or print them during setup.
- Add a second method. A passkey plus an authenticator app, or two devices. Supabase says it does not return recovery codes. It recommends a backup authenticator factor on a different device or app, and warns "we will not be able to restore access to your account" if you lose all your credentials.
- Know the cost of losing everything. GitHub says that if you lose your phone, "you can authenticate to GitHub using your recovery codes", and "Once you use a recovery code to regain access to your account, it cannot be reused." GitHub's 2FA page adds that GitHub Support "will not be able to restore access" if you lose both your credentials and your recovery methods.
- Tell one trusted person where the codes are. A sealed envelope or a shared password vault is enough. If you are the only one with the codes and you are unreachable, the app is stuck.
4. Shared logins versus proper team access
Sharing one password with a freelancer feels fast. It has real problems. You cannot see who did what. You cannot remove one person without changing the password for everyone. And their 2FA code goes to your phone, so you must be awake to let them in. Invite people with their own login and the lowest role that lets them do the job.
- GitHub: the repository roles page lists read, triage, write, maintain and admin. It advises you to "Choose the role that best fits each person or team's function in your project" so people do not get "more access to the project than they need." It also says organization owners have admin access to every repository, so keep owners few.
- Netlify: the team members page covers Owner, Developer and Reviewer roles. To remove someone: "select Options > Remove from team." Note that "every team must have at least one Owner."
- Vercel: the access roles page lists Owner, Member, Developer and more. It says Owners can modify team members and roles, and recommends "at least two individuals have owner permissions" for continuity.
- Stripe: the user roles page has many roles, including Developer and View Only. It warns that Administrator-type roles "can invite users to your account. If an attacker compromises a user with one, they can invite additional users under their control." So give those out rarely.
- Supabase: invite people to your organization as members rather than sharing your login. Check your organization's team settings for the roles your plan offers.
One more Netlify detail worth knowing: deleting a Git contributor "does not automatically remove the user from the associated Git repository." Remove them in both places.
When the work ends, remove the person the same day. Do not wait for "later". Then check the "Who else has access" column again.
5. The domain registrar
Your domain is the address of your whole business. If someone steals it, they can take your site and your email. Two things to do at the registrar:
- Turn on 2FA for the registrar account. Use the strongest method it offers. Make sure the account email is one you own.
- Turn on the transfer lock. ICANN's page on locked domains says domain names "can be locked to protect against unauthorized changes." It says the lock may show as "Registrar lock" or "Client Transfer Prohibited." ICANN's status codes page describes clientTransferProhibited as "reject requests to transfer the domain from your current registrar to another."
The lock is simple to undo when you really want to move the domain. ICANN says to check whether your registrar lets you unlock it yourself, and if not, ask the registrar to remove it. Also check that the domain is set to renew, and that the billing card is current. A domain that expires is as bad as one that is stolen.
6. Secrets and keys
Accounts are one door. API keys are another. A key works without a password or 2FA. So if a person leaves, think about what keys they have seen.
- Rotate keys when someone leaves. That means Stripe secret keys, database service keys, email service keys and any AI provider keys they could see. Create a new key, put it in your host's settings, redeploy, then delete the old key. The post on checking for an exposed API key shows how.
- Do not paste keys into chats. That includes chats with your AI builder, with a freelancer, and in email or Slack. The text stays in history. If you already did it, treat the key as exposed and rotate it.
- Keep keys in environment variables. Not in the code, and not in the GitHub repository.
- Use a password manager for the list. Not a plain notes app that syncs to every device.
7. The 30-minute checklist, ordered by risk
- Email (5 min). Strong unique password, 2FA on, recovery codes saved offline. Check forwarding rules and the list of devices.
- Registrar (5 min). 2FA on, transfer lock on, account email is yours, auto-renew on.
- GitHub (5 min). 2FA on with a fallback method. Look at the collaborators and organization members. Remove anyone who should not be there. Lower roles where you can.
- Host: Netlify or Vercel (5 min). 2FA on. Check team members and roles. Make sure there are at least two owners you trust, as Vercel recommends.
- Database: Supabase or Firebase (5 min). 2FA on the dashboard account (for Firebase, that is the Google account). Check organization members. Turn on the org-wide MFA setting if your plan has it.
- Payments: Stripe (5 min). Passkey or security key if possible. Review team roles. Remove old Administrators. Check the list of API keys.
- Afterwards. Rotate any key a former helper could see. Update your account list with today's date.
If you cannot finish in one go, stop after step 3. Email, registrar and GitHub protect the most.
Want this fixed for you?
I finish and fix apps built with Lovable, Bolt, Cursor or Replit, including checking who can access the accounts your app runs on. Send me the details and I'll reply within 24 hours.