Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

App security · 21 Nov 2026 · 6 min read

App security basics for founders: storing data and protecting accounts

You do not need to write the code to ask good questions about app security. These are the points a founder can check with a developer.

The short answer

App security begins with a simple rule: the device is not a safe place for secrets. Never store passwords, payment details or server keys in the app itself. Keep sensitive data on the server, protect sign-in with strong rules and optional second checks, send everything over encrypted connections, and ask your developer to explain each choice.

Why app security is a founder's job too

App security is mostly decided by choices made early: what the app stores, where data lives and who can reach it. A founder does not need to know the code to influence those choices, but needs to ask the questions. Mistakes in this area can expose customers, damage trust and lead to store problems, and they are far easier to prevent than to repair.

Nothing here replaces a proper review by a security professional, especially for apps that handle health, financial or children's data. Treat this guide as a list of questions and sensible defaults. Our mobile app development service page explains how security fits into the build.

What an app should never store on the device

Assume anyone can get a copy of your app and look inside it. Devices are lost, apps can be unpacked and files on a device can be read by someone with the right tools. That leads to a short list of things that should not live in the app.

  • Secret keys for your server, database or any paid service. If a key is in the app, it is public. Keep it on the server and let the app ask the server to act.
  • Passwords in plain text. An app should not keep the user's password at all after sign-in.
  • Full payment card numbers. Use the payment provider's tools so card data goes to them and never touches your app or server.
  • Large copies of personal data that the screen does not need. The less stored locally, the less can leak.
  • Debug logs containing personal details or tokens.

Some data has to be on the device, such as a sign-in token that keeps a person logged in. Both iOS and Android provide protected storage for small secrets, and developers should use it, not ordinary files or preferences. Ask which storage your developer uses for tokens and why.

Protecting user accounts

Most real-world harm comes from accounts being taken over, not from clever attacks on code. A few habits make a large difference.

Sign-in design

Do not invent your own password system. Use a well-established sign-in method, and store passwords on the server in a hashed form built for that purpose.

Second checks

Offer a second step for sign-in, such as a code from an authenticator or a device check. Make it optional at first for ordinary apps and required for accounts that can move money or reach sensitive data.

Sessions and tokens

A login should expire, and a lost device should be revocable. Let people sign out of other devices, and end sessions when the password changes.

Limits and alerts

Slow down repeated wrong passwords, and notify people by email when a new device signs in or a password changes. These small messages let the real owner react.

Recovery

Account recovery is a favourite route for attackers. Make it as careful as sign-in itself, and avoid recovery questions that can be guessed from public profiles.

Keep the secrets on the server

The server, not the app, should decide who can see or change what. A common weakness is an app that hides a button but whose server will still do the action if asked. Every request should be checked on the server: is this person signed in, and are they allowed to see this record?

Use encrypted connections for all traffic between the app and the server, and ask your developer how the app checks that it is talking to the right server. Do not add exceptions that switch the protection off for testing and then forget them. For the wider picture of how apps, interfaces and databases fit together, read app backend basics.

Third-party code deserves care as well. Analytics, advertising and login tools run inside your app with your permissions. Include only those you need, keep them updated, and know what each collects.

Questions to ask your developer

You can learn a lot from how a developer answers. Good answers are specific and calm. Evasive or vague ones are a warning.

  1. Where is each type of data stored, on the device or the server?
  2. How are passwords stored, and how does sign-in work?
  3. How are tokens stored on the device, and when do they expire?
  4. Does the server check permissions on every request?
  5. Which third-party tools does the app include, and what do they collect?
  6. How are secrets kept out of the code and out of version control?
  7. How will we hear about a security problem, and who fixes it?
  8. Has anyone other than the author reviewed the app for security?

Ask for the answers in writing and keep them with your project documents. They are also useful when you complete the privacy forms for each store.

Lost, shared and old devices

Plan for the device leaving the owner's hands. A lock screen is the first defence, and the app can add its own lock, such as a device check before showing sensitive screens. Hide previews of private content when the app moves to the background. Clear cached data when a person signs out, so the next user of a shared device sees nothing. Give people a way to sign out everywhere from a web page, since the lost device is the one they cannot reach.

Rooted or modified devices are a harder question. Some apps detect them and limit sensitive features, but detection is imperfect and can block honest users. Decide based on the risk of your data, and ask your developer to explain the trade-off.

Security and the app stores

Store review does not replace a security check, yet security-related choices appear in review. Apps can be rejected for privacy declarations that do not match behaviour, for unsafe handling of user data, or for missing account deletion in apps that allow sign-up. The details are in each store's current guidelines. Our piece on app store rejection explains how to read and answer a message, and the guide on account deletion and user data covers the deletion side.

User experience supports security as well. A sign-in flow that is confusing pushes people to reuse weak passwords. For help with the design side, see app UX basics for first-time founders.

After launch: updates and incidents

Security is not finished at launch. Libraries age, new weaknesses are found and operating systems change. Plan to update dependencies on a schedule, and keep a way to push a fix quickly. If an old version has a known flaw, you may need to ask people to update, and we describe that in app versioning and update prompts.

Write a short incident plan before you need it. Decide who is told first, how users are informed, which keys will be replaced and who speaks to customers. Rules about telling people when their data is exposed differ by country, so ask a qualified lawyer what applies where you operate.

Related guides

Questions and answers

What should an app never store on the device?

Secret keys for servers or paid services, plain-text passwords, full payment card numbers and large copies of personal data the screen does not need. Small secrets such as sign-in tokens should go in the protected storage each operating system provides.

How do I protect user accounts in my app?

Use an established sign-in method, store passwords on the server in a hashed form, offer a second step for sign-in, expire sessions, slow repeated wrong attempts and email people about new device sign-ins. Make account recovery as careful as sign-in.

What should I ask a developer about app security?

Ask where each type of data is stored, how passwords and tokens are handled, whether the server checks permissions on every request, which third-party tools are included and who reviews the app for security. Ask for answers in writing.

Is app store review enough to prove an app is secure?

No. Review checks policy compliance and basic behaviour, not if your server or storage is safe. Arrange your own review, especially for apps that handle health, financial or children's data.

Do I need a security professional?

For simple apps, good defaults and careful questions go a long way. For apps with payments or sensitive data, an independent review by a security professional is sensible. Rules and expectations differ by sector and country.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote