Software Privacy Settings Checklist: Account First

A software privacy settings checklist ordered by leverage — account retention windows, connected apps, device permissions and telemetry, twice a year.

Fact-checked: 2026-08-15
A technical workbench with computer components arranged in a sequence

A software privacy settings checklist works best as a route rather than a cleanup, and the order matters more than the individual toggles. Start at the account level, because that is where data is collected and retained; the app-level switches most people start with are the least effective place to begin.

Why the order matters

Most privacy advice is a pile of switches with no sequence, which is why people flip a dozen and feel no safer. The useful framing is leverage: some settings govern whole categories of collection, and others govern one app’s behavior on one device.

Work outside in. The account holds history across every device you have ever signed in on. The operating system governs what any app can reach. Individual app settings govern only that app. A software privacy settings checklist that starts at the app is starting at the smallest lever available.

Start at the account, not the app

Your platform account — the one tied to your phone, your email and your browser sync — is the single largest collection point you control. Four settings there outrank everything downstream.

  1. Activity history. Find what the account records: searches, location history, voice recordings, watch and listen history. Turn off what you do not want kept, and delete what already exists.
  2. Auto-delete windows. Where offered, set retention to the shortest available period. This is the single highest-value toggle in this entire checklist, because it acts continuously and needs no maintenance.
  3. Ad personalization. Turning it off does not reduce the number of ads; it reduces profile building, which is the part that matters.
  4. Connected apps and sessions. Review every third-party application with access to the account and revoke anything you do not currently use. This list is always longer than people expect.

The device layer

Operating systems now expose reasonably good controls, and three of them do most of the work.

Location. Set every app to “while using” rather than “always,” with the exception of anything you genuinely need running in the background, such as navigation. Background location is the most valuable data most apps collect and the least necessary for their function.

Advertising identifier. Reset it, and disable tracking permission where the platform offers a single control. This breaks continuity in the profiles built about you.

Cross-app tracking permission. Deny by default. Nothing you use will break.

Application permissions

PermissionDefault answerException
MicrophoneDenyCalls, voice notes, dictation
CameraDenyApps you knowingly take photos with
ContactsDenyAlmost nothing — this uploads other people’s data, not just yours
PhotosSelected items onlyPhoto editors you use heavily
LocationWhile usingNavigation, fitness tracking
NotificationsAllow selectivelyNot privacy, but attention — audit it anyway

The contacts row deserves the emphasis. Granting it uploads the phone numbers and email addresses of people who never agreed to anything, and it is the permission most often requested for reasons unrelated to the app’s function.

Telemetry and diagnostics

Operating systems and major applications collect usage diagnostics, usually with a basic and a full tier. Choosing the basic tier costs you nothing observable and meaningfully reduces what leaves the machine.

The same applies inside individual applications: browsers, office suites and creative tools each carry their own diagnostic setting, and these are set independently of the system-wide one. Checking them is tedious, which is precisely why a written software privacy settings checklist beats good intentions.

Retention and deletion

Turning collection off from today does nothing about what was gathered before today. Both actions are needed, and they live in different places.

Use the account’s data export where you want to see what exists before deleting it — the export is frequently more revealing than any settings page, and it is the fastest way to understand what a service actually holds. Then delete history in bulk and set the auto-delete window so the problem does not rebuild.

Where a jurisdiction gives you a formal deletion right, use it for services you have stopped using entirely. Abandoned accounts are a standing risk: they hold data, they can be breached, and nobody is watching them. Closing them belongs on every software privacy settings checklist.

Make it thirty recurring minutes

Settings reset. Updates introduce new toggles, defaulted on. New apps arrive with fresh permission requests granted in a hurry. A one-time cleanup decays within a year.

Put thirty minutes in the calendar twice a year and run the same route: account activity and retention, connected apps, device permissions, telemetry tiers, then abandoned accounts. Because you are repeating a fixed sequence, each pass gets faster, and the second pass typically takes ten minutes.

The checklist

  • Set auto-delete windows on account activity history to the shortest offered.
  • Revoke third-party app access for anything unused.
  • Set location to “while using” everywhere except navigation.
  • Deny contacts access by default — it is other people’s data.
  • Choose basic telemetry at system level and inside each major app.
  • Export your data once to see what is held, then delete in bulk.
  • Close abandoned accounts rather than leaving them dormant.
  • Repeat twice a year — put it in the calendar now.

Run in that sequence, this software privacy settings checklist takes a single afternoon the first time and half an hour thereafter, and it moves far more than the app-by-app fiddling most people attempt. The leverage is at the account and the operating system; the individual app toggles are the last ten percent.

Sabbir

Sabbir has 20 years of experience in technology and a computer science and engineering background.

RankBoast keeps commercial relationships separate from editorial conclusions. Read our editorial policy.

Join the discussion

Add useful context, ask a focused question or share relevant experience. Comments are moderated to protect readers from spam and promotional links.

Leave a thoughtful comment

Your email address will not be published. Required fields are marked.

Scroll to Top