The 10 principles
Think of it like your house: a door with a key, a key you do not hand to strangers, and an alarm code you do not shout in the street. App security is the same, only digital. Each principle has a right and a wrong example.
01Lock the device
The phone or tablet needs its own lock: PIN, pattern or fingerprint. If someone finds the device unlocked, they do not need to hack anything. They just open the app.
It is like leaving the house unlocked because “the door has a lock”. A lock does not help if you do not close it.
Device lock on (PIN or fingerprint), locking automatically after a few seconds of inactivity.
No code “to save time”, and the device stays open in a pocket or on a table.
02Data is stored encrypted
A good app does not write messages, positions and notes as plain text. It writes them encrypted, so they only make sense with the key.
Like a note in a secret code: if someone else finds it, they see gibberish instead of “meet at 6”.
Sensitive data is stored encrypted. Without the key it is useless to whoever finds it.
Stored “bare”, like a plain text file that can be read directly.
03Bluetooth: only with people you trust
Bluetooth is like speaking loudly in a room: it is heard nearby. Connect only to devices you approved yourself, not the first one that shows up in the list.
You do not answer a stranger in the street, but you talk normally to a friend you know.
Pair only with a specific, known device, and disconnect when it is no longer needed.
Accepting a connection from “any” nearby device, without knowing what or who it is.
04Your location does not leave without a reason
GPS tells the app where you are so it can show you on the map. If you choose to share your position with the team, that is your decision. It must not be sent anywhere else without you knowing.
You tell a friend on the phone where you are. You do not shout it into an open microphone.
The position is used for the purpose you gave it for (the map), and you share it only when you choose to.
The position is uploaded to some service “for statistics” without the user knowing.
05Permissions are requested for a reason
Every time the app asks for access to something (camera, files, location), there must be a reason you can see. A map app has no business asking for your photos “in case”.
You lend your house key only to someone who really has business inside.
Location access is requested when the map needs it, with an explanation of why.
The app asks for “everything” at install, with no explanation.
06Updates close holes
No app is perfect on day one. Someone may find a way to trick it. Updates patch those holes, so install them instead of ignoring them.
You learn your lock opens with a credit card and you change it at once, without waiting to be broken into.
Installing the newest version as soon as it is out, especially when it mentions security fixes.
“I will do it later”, for months, on an old version.
07End-to-end encryption
In peer-to-peer two devices talk directly. “End-to-end” encryption goes further: the message is locked on the sending device and unlocks only on the receiving one. Nobody in the middle, not even a server if there is one, can read it.
You hand a sealed envelope straight to the recipient instead of leaving it at a post office that could lose or open it.
The message is locked at the sender and unlocks only at the recipient. Whatever passes in between looks encrypted.
The message unlocks at an intermediate point (for example a server) before it reaches the recipient, where someone else may see it.
08Is Bluetooth encrypted? Yes, but…
After pairing, the communication is locked with a key the two devices agree on. The “but” is what comes before: every Bluetooth device broadcasts an “I am here” signal that anyone nearby can see, unencrypted. Safety depends mostly on whether pairing needs confirmation.
You call out “I am here” and the whole room hears. The talk after you agree is whispered in your own code.
Pairing needs confirmation on both devices before anything is sent.
Automatic pairing with the first device found, with no check.
09Why your own server matters
When data passes through a third-party company's server, that company technically gains access, even if it does not look. It may leak, change policy or stop existing. When the server is yours, you decide who connects and where the data stays.
Your own chest at home, instead of a box in someone else's bank: you hold the keys.
The server runs on infrastructure you control, and no third party sees what passes through it.
All communication goes through a foreign cloud service, with access that depends on another company's terms.
10What if one safeguard fails
No lock is 100% unbreakable. That is why security does not rest on one measure but on several independent ones (“defence in depth”). If a device is lost, you need a plan to change keys and cut its access. The goal is not that nothing ever breaks, but that everything does not break at once through the same crack.
A house with a door, an alarm and a watchful neighbour. If the door is forced, it does not mean they are inside.
Several independent layers of defence and a ready plan to change keys or cut access if something is breached.
One lock for everything. If it breaks, there is nothing else in between.