A Practical Guide To Privacy Settings In Elementary OS
Privacy on a desktop is shaped by many small decisions: which applications can use a microphone, whether location services are enabled, what gets sent when software is updated, and how much information websites receive through a browser. Elementary OS provides useful controls for these areas, although some depend on the release you are running and the applications installed.
The system’s privacy approach is generally conservative. Elementary OS does not rely on advertising profiles or a central account that tracks everything you do. Apps installed through Flatpak can also use permission portals, giving you more control over hardware access than traditional desktop programs often provide.
That does not mean every privacy setting is automatic. A browser can still reveal an approximate location, an online service can still associate activity with your account, and a third-party application may have its own data policy. Privacy controls work best when combined with sensible application choices and regular system updates.
This guide explains the main settings in plain language, with examples relevant to Australian users. Menu names can change between releases such as elementary OS 7 and elementary OS 8, so treat the exact wording as a guide rather than a fixed map.
Finding Privacy Controls
Open System Settings from the dock or Applications menu and look for a Privacy or Privacy & Security category. In recent elementary OS releases, controls are grouped into areas such as location, camera, microphone, screen recording, and application permissions. On an older installation, some options may appear under separate settings panels.
The quickest way to understand your current setup is to review each permission rather than searching for one master privacy switch. A privacy dashboard may show which apps have requested access, while a separate panel can control recent files, screen locking, or automatic cleanup. If a setting is missing, the application may be using an older permission model.
Flatpak applications commonly interact with hardware through system portals. When an app requests access, elementary OS may display a permission dialogue or place the decision in its privacy settings. Traditional packages installed from a repository can behave differently, because they may have broader access to the user account and filesystem.
This distinction matters when comparing two apps that perform the same job. A Flatpak music recorder may ask for microphone permission, while an older package could rely on direct system access. The application’s packaging format is therefore part of its privacy profile, alongside its reputation and developer.
Managing Location Services
Location services allow the system or an application to estimate where the computer is. On a desktop, this is usually based on nearby Wi-Fi networks, IP address information, or a web service rather than a dedicated GPS receiver. A laptop connected to home NBN in Brisbane, Perth, or Adelaide may receive a city-level estimate, not a precise street position.
If location services are enabled, applications can request an approximate position for weather, mapping, time-zone, or local search features. Review the list of approved applications and disable access for anything that has no clear reason to know where you are. A weather app may benefit from location access; a text editor generally does not.
Turning off the system location option prevents supported desktop applications from obtaining location through the standard service. It does not make you anonymous online. Websites can still infer a broad region from your IP address, and an account such as Google, Microsoft, or a retailer may know your address from information you supplied directly.
For stronger control, disable location access globally and enter locations manually in applications that need them. This is practical for a home desktop in Melbourne or a laptop used mostly at a fixed address. It also avoids unwanted prompts when using public Wi-Fi at a library, university, airport, or café.
Camera, Microphone, And Screen Access
Camera and microphone permissions deserve particular attention because they involve physical sensors. Check which applications can use each device, then remove access from programs that do not need it. Video-call software, recording tools, and browser-based meeting services may require permission, while a calculator or image viewer should not.
A permission switch is useful, but it is not a substitute for physical awareness. A camera cover can block the lens, and a hardware microphone mute key or USB microphone switch can provide an additional barrier. On a laptop purchased through an Australian retailer such as JB Hi-Fi or directly from a manufacturer, check whether the keyboard includes a microphone indicator or privacy shutter.
Screen recording and screen sharing can expose far more than a single window. A meeting application with permission to capture the screen may display password managers, private messages, tax documents, or customer information. When possible, share one application window rather than the entire desktop, and stop sharing as soon as the presentation ends.
Permission prompts should be read before they are accepted. An app that requests a camera while offering a video feature may be behaving normally; an unrelated utility asking for camera, microphone, and full screen access deserves closer inspection. Remove unused applications when you no longer need them, since uninstalling also removes their practical access to the system.
Understanding Telemetry And Usage Data
Telemetry means information sent from a computer to a developer or service about usage, hardware, crashes, or performance. Elementary OS has a privacy-focused reputation and does not build its everyday desktop experience around invasive behavioural tracking. Its developers have also generally favoured transparency and consent when optional usage information is discussed.
The exact options depend on the release and installer. If you see a checkbox for anonymous usage statistics, diagnostics, or improving the operating system, read its description carefully before accepting it. Anonymous hardware information may include items such as the desktop version, processor architecture, or graphics hardware. That is different from sending documents, passwords, or browsing history, although it is still information you may choose not to share.
System updates necessarily contact software repositories to check for new packages. AppCenter also needs network access to display applications, retrieve metadata, process payments where applicable, and download updates. These connections are operational traffic, not automatically a record of everything you do on the desktop.
You can inspect network behaviour with a firewall or network-monitoring tool if you want a more detailed picture. Avoid disabling update services simply to reduce connections: an unpatched browser or desktop component can create a larger privacy and security risk. For an Australian user handling myGov, ATO, banking, or Medicare information, current security fixes are more valuable than eliminating every routine repository request.
App Permissions And Flatpak Sandboxing
Applications from AppCenter may be packaged as Flatpaks, which use sandboxing to restrict access to parts of the system. A sandbox can limit access to personal files, hardware, and system services, while portals provide controlled ways to open a document, print, use a camera, or communicate with another application.
Sandboxing is a useful boundary rather than a guarantee. An application may still access files you deliberately open through it, data stored in its own app directory, or information sent to its online service. If you grant broad filesystem access, the protection becomes weaker. Check permissions with a tool such as Flatseal when you need a detailed view of Flatpak capabilities.
Use the least access that allows the application to work. A note-taking app may need access to a selected documents folder, but not the whole home directory. A music player may need your Music folder, while a simple alarm app does not need access to personal files. Revisit permissions after major app updates, because capabilities and packaging can change.
Applications installed from outside AppCenter require extra care. A downloaded Debian package, shell installer, or binary from an unfamiliar website may run with the privileges of your user account or request administrator access. Verify the developer, prefer official repositories where possible, and avoid installing software merely because a pop-up claims that it is required to view a page.
Browsing, Accounts, And Network Privacy
Elementary OS’s default browser and any browser installed later have their own privacy controls. These include cookie handling, tracking protection, permissions for individual websites, stored passwords, notifications, and location access. Review browser permissions separately from the operating system, because a website can request camera or location access through the browser.
Private browsing windows mainly limit local history and cookies after the window closes. They do not hide activity from an internet provider, workplace, school, VPN provider, or the website itself. A VPN may conceal your home IP address from a website, but it shifts trust to the VPN company and does not prevent account-based tracking.
Be cautious on shared networks. Public Wi-Fi in a Sydney café, hotel, or university should be treated as untrusted, even when a network name looks familiar. Use HTTPS, avoid installing certificates supplied by unknown parties, and do not enter sensitive credentials into a page reached through an unexpected link. A VPN can be useful on public networks, but it should come from a provider you have researched.
Separate browser profiles can reduce accidental crossover between activities. For example, one profile can hold personal shopping sessions while another is used for work or community administration. This will not defeat sophisticated tracking, but it can reduce shared cookies, saved logins, and autofill mistakes.
Privacy Defaults For Everyday Use
A strong baseline begins with a screen lock and a short automatic lock delay. Encryption is also worth considering, especially on a laptop that may be lost on a train, in a car, or while travelling between Canberra and regional areas. Full-disk encryption protects stored data when the computer is powered off, but it does not protect an unlocked session.
Keep backups private as well as reliable. An external drive should be encrypted if it contains personal documents, and cloud backups should use a provider with clear security and retention policies. Files related to Australian tax returns, health records, passports, or rental applications deserve the same care as banking documents.
Limit notifications on the lock screen. Message previews, email subjects, and two-factor authentication codes can reveal sensitive information to anyone near the screen. Disable previews for private apps or configure the system to show that a notification exists without displaying its contents.
The following summary provides a practical starting point. The exact labels can vary by elementary OS version and by the permissions exposed by each application.
| Privacy area | Sensible default | What to check regularly |
|---|---|---|
| Location | Off unless an app genuinely needs it | Approved apps and browser site permissions |
| Camera | Off for apps that do not make video calls | Video meeting tools and unused software |
| Microphone | Off except for communication or recording tools | Mute status and recent app requests |
| Screen recording | Allow only during a known session | Stop sharing and close the meeting app |
| Optional telemetry | Leave off if you do not want usage data shared | Installer or release-specific wording |
| Flatpak permissions | Keep access limited to selected files | Broad home-directory or device access |
| Browser data | Use tracking protection and review cookies | Saved passwords, extensions, and notifications |
| Lock and encryption | Enable automatic locking and encryption where practical | Recovery keys and backup security |
A Practical Privacy Routine
After installing elementary OS, open the privacy settings before adding many applications. Turn off location, camera, microphone, and screen recording access by default, then grant each permission only when a clear feature requires it. Record any encryption recovery key somewhere secure before relying on encrypted storage.
Once a month, review installed applications and remove software you no longer use. Check Flatpak permissions, browser extensions, saved website permissions, and optional diagnostics settings. A short review is easier than trying to reconstruct which program received access after a year of installations.
Before handling sensitive work, lock down the session: close unnecessary browser tabs, use a trusted network, verify the website address, and avoid sharing the entire screen. For accounts used with Australian government or financial services, use unique passwords stored in a reputable password manager and enable multi-factor authentication where offered.
Privacy in elementary OS is best treated as routine maintenance rather than a single switch. Keep the system updated, minimise permissions, protect the device when unattended, and make deliberate choices about applications and online accounts. That combination gives you a practical privacy baseline without sacrificing the everyday usability of your desktop.
