Security and ethical hacking

Online privacy

Online privacy means you decide what is collected about you and who is allowed to read it, and its heaviest part is the thing you never wrote down: the data that gets inferred from your behaviour. The one principle that works in practice is giving less away in the first place, because anything already collected cannot be taken back.

  • Lesson 9 of 12
  • Beginner
  • Free, no signup

The four layers of data you leave behind

The numbers run from the centre outward: the closer a layer is to you, the less of it you put there yourself.

You
  1. 1

    What is inferred about you

    Age, interests, financial situation, waking hours. You declared none of it, and this layer is the most accurate of the four.

  2. 2

    What you leave behind

    A network address, a time, the page you arrived from, the string the browser says about itself.

  3. 3

    What you agree to

    The permission you granted an app and the terms you ticked at signup. Usually unread.

  4. 4

    What you post

    A post, a comment, the number you left in a form. The only layer everybody thinks about.

The boundary between these four is not always clean. A photograph is layer one, carries a location and a time inside its file, and also feeds face recognition.

Last checked: Facts and tool names in this lesson are re-checked against their sources on this date.

What does online privacy actually mean?

Online privacy means having control over what is collected about you and who is allowed to read it. It is not the same as secrecy. Somebody with nothing to hide still draws the curtains, and not because they are doing something wrong.

The subject has four layers, and the figure above the page is those four layers. The outermost is what you write yourself: a post, a comment, the number you left in a contact form. The next is what you agree to without reading: the permission you grant an app at install, the terms you tick at signup. The third is what you leave behind without writing anything: a network address, a time, the page you arrived from. And the core, the layer almost nobody thinks about, is what gets inferred from the three above it.

Our position is plain: being concerned is right, being frightened is not. Nobody is sitting behind each of your clicks watching. What actually happens is mechanical and slow and statistical, and that is exactly why it can be managed. The distance between a careful user and a careless one is a few small decisions, not one big laborious change.

One distinction is needed too. Security means nobody can get into your account; privacy means how much somebody with lawful, official access to your data gets to know about you. The second has no technical fix and is a decision. For the first, the security track carries the tools separately.

A glass onion whose core is a tiny white note and whose outer shells glow red, green and blue

Where does the thing you never wrote down come from?

Every server in the world writes one line into a log file for every request, and ours is no exception. One real line from this site log, taken in the same window in which this lesson was verified, held these: the visitor network address, the exact time, the page they asked for, the page they came from, and the string their browser said about itself. The visitor had written none of it. Not one.

Now look at what comes out of that single line. The browser string said Android, Chrome version 152 and a phone, so the device, the operating system and even the rough generation of the handset are known. The referrer field said this visitor arrived through a link carrying a came-from-ChatGPT marker, so the route of arrival is recorded too. The time says when they were awake. And if the same line repeats for ten pages in a row, their order says what the visitor was after.

This is the inference layer: the thing nobody declared, assembled by putting traces side by side. The adverts that feel uncannily accurate come from here, not from a microphone. An advertising company does not need to know who you are; it is enough to know what a device with this behaviour responds to.

And this is exactly why "but I never post anything" is not an answer. Three quarters of what is kept about you was never postable in the first place.

What can be derived from a single line

One line in a server logthe visitor wrote none of it
  • Device, operating system and browser

    In the real line we read: Android, Chrome 152, a phone. Which means the rough generation of the device shows too.

    User-Agent
  • The route you arrived by

    That same line said the visitor came through a link carrying a came-from-ChatGPT marker.

    Referer
  • Country and operator, not a home address

    Its precision is imagined to be greater than it is. It gives a country and an internet company, not a street.

    Network address
  • The hour and the order of pages

    It says when you are awake and what you were after. The heaviest field once it repeats over days.

    Time

None of these four identifies you by name. Their value appears when thousands of lines are put side by side.

Why is giving less away the only principle that actually works?

Because everything else happens after the data is collected and is therefore late. Encryption, a privacy policy, a delete-account button: none of them take back what has already been copied. Data minimisation means giving less from the start, and it is the only move whose effect is not reversible by somebody else.

In practice that is four habits. A form asking for name, email, phone and date of birth when it exists to hand you a file should be asking for the email only. An account you have not opened in three years should be closed, not abandoned. An app that does its job with one grant of access should not get permanent access. And whatever you write in a public group or comment should be written on the assumption that it is permanent, because it is.

The server side is exactly the same thing, and we run it on this site. Three of them can be checked right now with any online header tool: the site declares that it will never ask the browser for location, microphone, camera or payment; it does not hand the next site the full address of the page you were on and sends only the domain name; and the logs are kept for seven days and after that they are gone. None of these three makes a visitor feel anything, and none of them is visible. Doing it properly usually looks like this.

Our position, which not everybody shares: a cookie consent banner that sets tracking cookies before you click is worse than no banner. It has both done the thing and claimed a permission it never got. The details are opened up by the internet and networks track, in its lesson on cookies.

How do you review an app permissions?

Once a year, twenty minutes. On Android go from settings into the permissions section; on iPhone go from settings into privacy and security. Both have made one thing easy that used to be hard: instead of walking app by app, you can look from the permission side, that is, see which apps have location, which have the microphone, which have your contacts. It is the second view that surprises people.

The question to ask about each one is in the figure below and it is only one question: does this app do the thing you installed it for without this permission? A maps app does not work without location and that permission is right. A photo editor works perfectly well without contacts, and that permission has nothing to do with its job.

There are three choices most people do not know exist. First, "while using the app" instead of "always"; for location this one matters more than any other setting. Second, approximate location instead of precise, which is enough for a weather app and is not enough for turn-by-turn navigation. Third, one-time access, which is taken back on its own once you close the app.

And one item worth its own minute: access to all photos. Both operating systems now let you hand an app a few selected pictures only. An app that just wants you to set a profile picture has no need whatsoever for your whole library.

The only question a permission needs

Does the app do what you installed it for without this permission

yes

Refuse it

  • contacts for a photo editor
  • location for a game
  • all photos just to set a profile picture
  • the microphone for a text notes app
no

Grant it, but narrowly

  • "while using the app" instead of "always"
  • approximate location, except for navigation
  • one-time access wherever it is offered
  • selected photos only, not the whole library

Refusing a permission sometimes breaks part of an app and you see the message right then. That is not damage, it is the test itself.

Where should you be concerned, and where not?

A simple ordering, arranged by real harm rather than by which item sounds scariest.

The most harm sits where your data ties to money or identity: a national ID number, a photograph of a bank card, the number your one-time codes arrive on, and a password reused across several services. Nobody wants these for advertising; they want them in order to pass themselves off as you. The least harm sits where the data is only used to sell you something; that is irritating and it is recoverable.

Between the two is a category that gets underrated: data that reveals location and relationships. Where you are at seven every day and who you are with is more sensitive than any advertising interest, and it is exactly what an "always" location permission collects quietly.

And what we think is not worth worrying about: a news site knowing you came from a phone, a shop knowing you looked at one pair of shoes three times, Google knowing you like football. If you have a limited amount of energy for this subject, spend it on the first category and let the last one go.

One next step that earns its time: today, open the list of interests that has been inferred for you in your Google account and read it. Most people do not expect that list to be as long as it is, and that single read turns this lesson from a text into an experience.

The fast path, with AI

Your Google account shows the list of interests it has inferred for you, and it usually runs to a few hundred entries. The ordinary way is to page through it and give up after thirty. The fast way is to take the list out and ask a cheap fast model to group it and pull out the sensitive ones, so that instead of hundreds of decisions you make ten.

  1. In your Google account, open the advertising settings and select and copy the list of topics attributed to you. The titles only, nothing else.
  2. Give the recipe below to a fast model together with that list. An expensive model has no advantage here, because the job is mechanical grouping and not judgment.
  3. Open the output and switch off only the items in the sensitive group, on that same Google page. Leave the rest; switching everything off is neither necessary nor durable.
  4. Repeat the same exercise once on the data export of whichever social network you use most. The shape of the list differs, the question does not.

Copy-ready recipe

I am giving you the advertising interest list from my account. For each entry write only three things:

1. The title of the entry, exactly as I wrote it.
2. A category: health, belief and religion, politics, financial situation, relationships and family, work, hobby, ordinary shopping.
3. Sensitive or ordinary. Sensitive means an entry somebody could use against me if they knew it.

After the table, list the ten most sensitive entries in order and write one sentence for each saying why it is sensitive.

Rules: do not add any entry I did not write. Do not guess where it was derived from. If a title is unclear to you, write unknown.

The list:
{paste the titles here}

Before you trust the output: The list is itself data about you, so before sending it strip out names, emails and any identifier and leave the titles alone. And do not treat the output as a diagnosis: the model does not know where an interest came from, and if you ask it will construct an answer that cannot be checked. What this exercise genuinely gives you is one thing, and that is enough: a short list of topics worth switching off.

AI in this kind of work

On this topic a language model does one job genuinely well: ordering a long list you pulled out of your own account yourself, and turning a long legal text into ordinary language. The job it does badly is telling you what a particular company does with your data. That answer comes out of the model memory, and the model memory belongs to the past.

Tools that actually help

  • Gemini Enough for exactly this grouping of a few hundred titles, and a fast cheap model beats an expensive one here because the work is repetitive rather than judgmental. Google own page says the Gemini app works in more than 230 countries and territories, and Iran is not on that list.
  • Claude For when you want to hold a service privacy policy up against what it actually does, which is careful reading of two long texts and finding the contradiction. Iran is not on Anthropic list of supported countries, so there is no official route to sign up or pay.
  • Gemini Notebook If a privacy policy runs to tens of pages, uploading it and asking from inside that document beats reading a summary, because the answer points back to its own clause and you can open the clause. It runs on a Google account, and Iran is not among the available regions.

Where it backfires

The main risk here is inverted: the tool you use to review your privacy is itself a data collector. Google own help page for Gemini says plainly not to enter confidential information you would not want a human reviewer to see, because some conversations are reviewed to improve the service. So do not upload your whole account export; hand over the list of titles only. The second risk is that the model constructs a fully confident answer to "what does company X keep about you"; Anthropic itself calls this confident invention hallucination in its documentation and writes about reducing it, which means the vendor treats it as a real weakness. The reference is always that company own policy page, never a chat answer. For what paying for these tools looks like from Iran, see the buying guide.

Sources: Google: Gemini Apps privacy notice and data Google: where Gemini Apps are available Anthropic: supported countries Anthropic: reduce hallucinations

Where this advice stops

This lesson is about what is observable from the outside: the headers a site sends, the permissions an app asks for, the list a company shows you. It knows nothing about what happens to your data inside that company and should claim nothing; that can only be read from their own written policy, and believing it is a decision rather than a measurement. The second boundary is legal: a right to delete your data and a right to see it are things European law gave a European user, and there is no clear equivalent in Iran, so some of the tools recommended in foreign articles have no legal lever here. And the third boundary is time: the settings of these services move every few months, and a page that is correct today may carry a different name next year. The final reference is always that service own settings page, not this one.

From our own work

Three things from our own server, all three checkable from outside right now. First, the answer from the rgb.ir front page carries a header saying this site will never ask the browser for location, microphone, camera or payment; the list is empty, meaning neither for ourselves nor for any outside service. Second, we have set the referrer policy header to the mode that gives a destination site the domain name only and not the full page address. We saw the effect in our own log: over a seven hour window about two thousand eight hundred internal referrers carried a full address, and every external referrer a current browser had sent was the bare domain; the single exception was one request that arrived over plain HTTP from a different search engine and brought its search phrase along with it. So the header is not just a claim, it is visible in the data. Third, the logs are kept for seven days and then deleted; that number is written in this server own log rotation file, and before it was written the logs on this server had grown to ten gigabytes.

Real follow-up questions

What exactly does private browsing hide?

It only clears your traces on that one device: history, cookies and what you typed into forms. The site you open, your internet company and the destination server see exactly what they would have seen otherwise. The name is misleading, and its right use is this: hiding from whoever opens that same device after you.

Is clearing history and cookies enough?

Partly for the third layer, not at all for the fourth. What you clear is on your device; what servers have inferred from your behaviour sits on their servers and is untouched by clearing your browser. The more effective move is to switch off ad settings and activity history inside the service itself.

Is my phone listening to me?

That experience everybody has had, talking about something and then seeing the advert, has a simpler explanation: the inference layer. You, your partner and your friend are on one network, you messaged each other, and one of you searched for it. To check for yourself: on both Android and iPhone an indicator lights up at the top of the screen every time the microphone is active, and on that same permissions screen you can see which apps opened the microphone recently. If you have doubts, close microphone access for the apps that do not need it; that move costs you nothing.