All articles
Security

Data Privacy for Web and Mobile Apps: What to Get Right

November 5, 2026 · 7 min read · ShopTech Systems

Almost every app collects some personal information, from an email address to location or payment details. Users, app stores and regulators increasingly expect that data to be handled carefully. Getting privacy right is part of building trust, and it is much cheaper to design for it from the beginning than to fix it later.

This article is general guidance, not legal advice. Rules differ by country and industry, so confirm your obligations with a qualified professional.

Principle 1: Collect only what you need

Data minimisation means asking for the least information required to deliver the service. Every extra field is something you must secure, explain and eventually delete. If you do not need a user's phone number or birth date, do not ask for it.

Principle 2: Be clear and get consent where required

Tell people in plain language what you collect, why, who you share it with and how long you keep it. Where consent is needed, for example for marketing emails or non-essential cookies, make it a genuine choice rather than a pre-ticked box. Keep a record of when and how consent was given.

Principle 3: Protect data in transit and at rest

  • Use HTTPS for all traffic.
  • Encrypt sensitive fields in the database and in backups.
  • Hash passwords with a modern algorithm; never store them in plain text.
  • Restrict who in your team can see production data, and log that access.
  • Keep secrets and keys out of source code and out of mobile app bundles.

Principle 4: Give users control

People should be able to see what you hold about them, correct it, export it and delete it. Mobile app stores now expect apps that let people create an account to also let them delete that account and its data from inside the app or through a clearly documented process. Build this early, with a documented process for what is deleted immediately and what must be retained, such as invoices required by tax law.

Principle 5: Be careful with third parties

Analytics, advertising, payment, support-chat and crash-reporting tools often receive user data. List every one, understand what each collects, and disclose them in your privacy policy. If you show ads, your policy should explain that third-party vendors use cookies to serve ads and how users can opt out. Review these tools periodically, because it is easy to add one and forget it.

What a good privacy policy includes

  • Who you are and how to contact you.
  • What data you collect and the reasons for collecting it.
  • Which third parties receive data, including advertising and analytics providers.
  • How long you keep data and how it is secured.
  • User rights and how to exercise them, including deletion.
  • How you will notify people of changes.

Plan for a breach

Even careful organisations can be breached. Know in advance how you would detect it, who decides what to do, whom you must notify, and how you would tell affected users. Quick, honest communication matters.

Key takeaways

  • Collect less, explain clearly and secure what you keep.
  • Give users access and deletion options, and document third-party tools.
  • Have a simple breach response plan and revisit your privacy policy regularly.

A worked example: designing a sign-up form

A team is building a fitness-class booking app and drafts a sign-up form asking for name, email, phone number, home address, date of birth and emergency contact. It feels thorough, but each field creates an obligation.

Applying data minimisation, the team asks what the service actually needs. Booking classes requires a name and an email. A phone number is useful only if they send reminders by text, so it becomes optional with a clear explanation. Home address and date of birth are not needed at all, so they are removed. The emergency contact is relevant only for certain classes, so it is requested at that point rather than at sign-up.

The result is a shorter form that converts better, a smaller amount of data to protect, and a simpler privacy policy. The team also adds a delete-account button in settings and writes down which records, such as payment receipts, must be kept for accounting purposes and for how long.

Common mistakes to avoid

  • Collecting just in case: gathering data without a defined purpose.
  • Copy-pasting a policy: using a generic privacy policy that does not match what your app really does.
  • Forgetting third parties: adding analytics, ads or chat tools without recording what data they receive.
  • Keeping data forever: having no retention rules, so old data accumulates and increases risk.
  • Logging sensitive data: writing passwords, tokens or personal details into logs.
  • Making deletion hard: requiring emails and long waits when people ask to remove their account.

Privacy-by-design checklist

  • List every piece of personal data the app collects and the reason for each.
  • Remove or make optional anything without a clear purpose.
  • Inventory all third-party tools that receive user data.
  • Encrypt sensitive data in transit and at rest and limit staff access.
  • Provide in-app ways to view, export and delete data.
  • Set retention periods and automate deletion where possible.
  • Publish an accurate privacy policy and update it when features change.

Frequently asked questions

Do I need a privacy policy if I only collect an email address? Generally yes. Even minimal collection usually triggers expectations or legal requirements, and app stores and ad networks often require a policy.

What about cookies? Many regions require clear information and, for non-essential cookies, consent. Check the rules that apply to your visitors.

Do these rules apply to a small business? Many privacy laws apply regardless of size, depending on where your users are and what data you handle. Seek advice for your specific situation.

What is the difference between privacy and security? Security protects data from unauthorised access. Privacy concerns whether you should collect and use the data at all, and how you treat people's choices about it.

Have a project in mind?

ShopTech Systems builds web platforms, mobile apps and business software.

Get a Free Consultation