Online Privacy in Practice: What Each Company Actually Knows
Where the data really comes from, which settings are worth changing, and how to tell a real privacy control from a decorative one.
Index
Every guide we have published, newest first. Use the category chips to narrow the list, or search the whole library.
Where the data really comes from, which settings are worth changing, and how to tell a real privacy control from a decorative one.
Everything that happens after you hit submit, plus the checks to run before you do. Most applications are lost on administrative detail.
Why most productivity systems fail in three weeks, and the structure that survives: one inbox, one file structure, and a weekly review.
What the three metrics measure, the thresholds that matter, and which fixes give the best return for the least effort.
The legal lines, the practical safeguards, and a simple test for whether the reason you have is good enough to act on.
Three hundred words, one specific reason, and no sentences that could appear in any other letter. What the cover letter is actually for.
Sync is not backup, why ransomware can reach a synced folder, and the three-two-one approach that actually survives a failure.
What a credit file contains, who is allowed to see it, what genuinely moves the numbers, and the right order of operations for fixing an error.
The mental model first, then the eight commands you actually use daily, and how to undo things without fear.
Typography, spacing and hierarchy: how to make a document that reads fast, survives parsing, and looks like a competent person wrote it.
Two products that sound alike, use overlapping data, and have completely different purposes, costs and rules. The differences that matter.
The full lifecycle of a page load — DNS, TCP, TLS, request, response, parse, render — and where the time actually goes.
A nine-point checklist for judging any online financial product: who runs it, what it costs, what happens when you want to leave, and who to ask when it goes wrong.
The tasks language models genuinely help with, the ones where they are unreliable, and how to check output you did not write.
The mistakes that actually lose interviews, in rough order of how often they appear and how hard they are to fix.
Which records are genuinely public, who maintains each one, and why a record being public does not mean it is unlimited, accurate or usable.
What the padlock actually guarantees, what happens in the handshake, why certificates cost money, and what your browser is warning about.
A repeatable comparison method: normalise the offers, price the whole term, then stress-test the deal against the way you actually behave.
A repeatable method for turning a job history into achievement bullets, plus the phrases that carry no information and should be deleted.
The realistic threat model, the four things that stop real attacks, and a clear response to act on when something has gone wrong.
A field-by-field account of what turns up: court records, registries, credit, social media — and the categories that almost never appear.
What applicant tracking systems actually do, the handful of formatting choices that break them, and how to test a document before you send it.
The words on the terms summary that actually change the price you pay, and the ones that are harmless shorthand.
Recursion, the root servers, record types, caching and TTL, plus the four DNS problems that cause the outages you have actually experienced.
From identity resolution to the final report: the pipeline behind every check, and the specific point where accuracy usually fails.
Why unique passwords matter more than complex ones, what a password manager actually does, and which second-factor method to pick.
What belongs in each section, what to leave out, and how to build a master document you can retarget in twenty minutes.
Where the money comes from, who pays for what, and why the same product can cost you nothing in one place and something in another.
Packets, addresses, routes and the physical layer, explained from observable behaviour rather than from a protocol diagram.
The plain definition, the three broad types, and why the same word covers a ten-second search and a six-week federal investigation.
The distinction is smaller than the internet suggests, but sending the wrong one is a fast way to lose a role you were suited to.
Money problems are usually priority problems, not knowledge problems. A four-part framework for getting the fundamentals in order, in the order that actually helps.