mirror of
https://github.com/privacyguides/privacyguides.org.git
synced 2025-07-16 08:22:44 +00:00
Compare commits
1 Commits
main
...
brave-v8-r
| Author | SHA1 | Date | |
|---|---|---|---|
| f9a75c13ef |
Binary file not shown.
|
Before Width: | Height: | Size: 235 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 236 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 241 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 313 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 310 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 232 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 46 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 230 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 269 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 270 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 271 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 237 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 289 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 232 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 238 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 275 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 232 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 238 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 236 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 221 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 235 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 238 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 210 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 224 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 224 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 259 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 264 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 256 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 266 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 254 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 168 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 279 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 308 KiB |
@ -1,914 +0,0 @@
|
||||
---
|
||||
date:
|
||||
created: 2025-07-15T17:00:00Z
|
||||
categories:
|
||||
- Tutorials
|
||||
authors:
|
||||
- em
|
||||
description: While most social media rely on commercial models harvesting users' data, Mastodon offers an alternative that doesn't seek profits from your data and attention.
|
||||
schema_type: AnalysisNewsArticle
|
||||
preview:
|
||||
cover: blog/assets/images/mastodon-privacy-and-security/mastodon-cover.webp
|
||||
---
|
||||
|
||||
# Privacy and Security on Mastodon
|
||||
|
||||
|
||||
|
||||
<small aria-hidden="true">Illustration: Em / Privacy Guides | Logo: Mastodon gGmbH</small>
|
||||
|
||||
Mastodon is an open-source and decentralized social network that has been growing in popularity for the past few years.
|
||||
|
||||
While most social media rely on commercial models harvesting users' data to sell to advertisers, Mastodon offers a human-centric alternative that doesn't seek profits from your data and attention. This means better social connections, better controls, and better privacy.<!-- more -->
|
||||
|
||||
Mastodon doesn't use your data to make money. This fact alone comes with incredible benefits for data privacy and security. Because the goal isn't to collect as much information as possible on its users, Mastodon embraces data minimization and only requires providing what is truly needed to run the service for you.
|
||||
|
||||
If you do not have a Mastodon account yet, but would like to learn more about its privacy and security practices and features before creating one, the first part of this article will give you an overview of what they are.
|
||||
|
||||
If you already have a Mastodon account, the second part of this article will guide you to use and understand better the controls it offers. If you are already informed about Mastodon's privacy and security, you may want to [**jump directly to the tutorial**](#tutorial-how-to-adjust-and-improve-privacy-and-security-on-mastodon) part.
|
||||
|
||||
This article isn't an onboarding guide to start using Mastodon, but if that's what you seek, take a look at this [short guide](https://docpop.org/2025/02/how-to-get-started-with-mastodon/) from Doc Pop. If you're still unsure about using Mastodon, [this excellent video](https://news.elenarossini.com/fediverse-video/) from Elena Rossini might convince you.
|
||||
|
||||
<div class="admonition info" markdown>
|
||||
<p class="admonition-title">Mastodon the software vs the network vs the instance</p>
|
||||
|
||||
Unless otherwise specified, the word *Mastodon* in this article will refer to the Mastodon *software,* in its default version. The Mastodon *software* is different from the Mastodon.Social original *instance* (server), and is different from the Mastodon *network*.
|
||||
|
||||
**Mastodon software**: The software used by people on the Mastodon network, and installed by administrators to run an instance (what you see).
|
||||
|
||||
**Mastodon network**: The network of interconnected instances using the Mastodon software (all the different Mastodon instances you interact with). The Mastodon network also connects to the larger Fediverse network.
|
||||
|
||||
**Mastodon.Social, the instance**: The largest Mastodon server, managed and moderated by the Mastodon nonprofit organization.
|
||||
|
||||
</div>
|
||||
|
||||
One of the wonderful possibility Mastodon offers is to [self-host your own Mastodon instance](https://docs.joinmastodon.org/user/run-your-own/). While this is the pinnacle of control, security, and privacy for a skilled administrator, self-hosting also means more responsibilities, where more expertise and resources are required. This isn't realistically accessible to everyone.
|
||||
|
||||
For this reason, this article-tutorial will focus on the experience from the **user side**, and not from the administrator side.
|
||||
|
||||
## :octicons-home-16: Choosing a Mastodon instance
|
||||
|
||||
Another particularity of Mastodon compared to commercial social media is its true decentralization.
|
||||
|
||||
The Mastodon network is composed of a [multiplicity of instances](https://joinmastodon.org/servers) that connect with each other, through a protocol called [ActivityPub](https://docs.joinmastodon.org/#fediverse). This collection of connected instances, along with other connected software using the same protocol, is called [the Fediverse](https://jointhefediverse.net/).
|
||||
|
||||
|
||||
|
||||
This article will not go deep into this topic, but it's important to mention that different instances will offer different degrees of privacy and security. Choosing an instance can have an important impact on this.
|
||||
|
||||
This is because the administration team of each instance has the responsibility to configure the software properly, to keep it updated, and to safeguard the server hosting the data. This in itself implies many security duties. It's important to consider the capabilities of the administration team to secure the instance you choose to join.
|
||||
|
||||
Moreover, even when the security part of hosting is well managed, the administration team is also responsible for enforcing policies and moderation. The quality of moderation can have a significant impact on the safety and privacy of a community.
|
||||
|
||||
Choosing an instance where you trust the administration and moderation team is essential to have a good and secure experience on the network. This is true for any other social media as well, even the ones that sadly don't offer any option to move your account if you aren't happy with management.
|
||||
|
||||
To facilitate choosing an instance, the Mastodon official website keeps a list of instances that have all agreed to follow the [Mastodon Server Covenant](https://joinmastodon.org/covenant), committing to the following:
|
||||
|
||||
- Enforcing active moderation against racism, sexism, homophobia, and transphobia
|
||||
|
||||
- Conducting daily backup to avoid accidental data loss
|
||||
|
||||
- Having at least one other person with emergency access to the server
|
||||
|
||||
- Giving at least 3 months of advance notice if the server shuts down and users have to move (this isn't frequent)
|
||||
|
||||
### Changing instance
|
||||
|
||||
Despite these considerations, Mastodon newcomers **shouldn't feel [analysis paralysis](https://en.wikipedia.org/wiki/Analysis_paralysis) over choosing an instance**. This decision isn't permanent, and can be changed later on, once one has acquired a better sense of the platform.
|
||||
|
||||
Indeed, as shown later in the tutorial part, Mastodon makes it possible to easily [move an account](#moving-to-another-instance) from one instance to another!
|
||||
|
||||
If trust is broken by an instance administration or moderation team, users can easily decide to migrate to another one with better practices. This account portability is quite unique to the Fediverse.
|
||||
|
||||
While account content (posts) will unfortunately not get transferred through this process on Mastodon (yet), account followers *and* follows will be moved unharmed during a Mastodon account migration.
|
||||
|
||||
Furthermore, this process might get improved soon! There is work currently being done to implement data portability between two ActivityPub servers (even for account content) with the [LOLA protocol](https://swicg.github.io/activitypub-data-portability/lola). This could eventually allow Mastodon's account migration process to include posts migration as well.
|
||||
|
||||
<div class="admonition success" markdown>
|
||||
<p class="admonition-title">You can always keep a copy of your content!</p>
|
||||
|
||||
Even if the Mastodon migration process doesn't allow for automatic posts transfer (yet), you are still able to keep a local copy of all your content, before moving to another instance or for backup purposes. More on this in the tutorial part.
|
||||
|
||||
</div>
|
||||
|
||||
## :octicons-shield-check-16: How secure is Mastodon
|
||||
|
||||
As explained previously, choosing an instance with a competent and trustworthy administration team is fundamental on Mastodon. Due to a plurality of instances, levels of security expertise can greatly vary from one server to another.
|
||||
|
||||
### Server security
|
||||
|
||||
As for any platform we use online (including commercial social media), it's important to evaluate properly the level of trust we are willing to give before subscribing to a service handling our data.
|
||||
|
||||
In this case, it means trusting the administration team of the instance you choose to safeguard the instance's server and data properly.
|
||||
|
||||
Additionally, like any other social media, Mastodon isn't immune to software vulnerability. When a problem arises, your server's security will depend on the responsiveness of your administrator(s).
|
||||
|
||||
Mastodon's development team has a good track record of acting promptly to fix and transparently inform the community when a critical [vulnerability is found](https://www.theregister.com/2024/02/02/critical_vulnerability_in_mastodon_is/). However, your instance's administration team must also act quickly to implement the fix.
|
||||
|
||||
Due to the decentralization of the Mastodon network, software patches cannot be automatically pushed to all instances at once. Administrators' reaction time may vary for each instance.
|
||||
|
||||
### Software security
|
||||
|
||||
Because the Mastodon software is open-source, anyone can inspect [its code](https://github.com/mastodon/mastodon). This *can* offer the benefit of getting more opportunities to spot and patch potential problems.
|
||||
|
||||
It also allows anyone to verify privacy and security claims, which greatly improves transparency and trust. This is something that cannot be done with proprietary closed-source software like most commercial social media use.
|
||||
|
||||
But open-source code isn't magically secure either. Experts still have to take the time to actually inspect the code for this to have any significant value.
|
||||
|
||||
In 2023, the Mozilla Foundation funded a penetration test for Mastodon that was conducted by the German cybersecurity firm [Cure53](https://cure53.de/). Following the results, the Mastodon development team [promptly fixed](https://arstechnica.com/security/2023/07/mastodon-fixes-critical-tootroot-vulnerability-allowing-node-hijacking/) the critical vulnerabilities found, and informed instance administrators to be ready to patch the software quickly. Mastodon instances updated to the most recent software now benefit from greater security, thanks to the excellent work of Cure53 and the Mastodon development team.
|
||||
|
||||
Additionally, anybody detecting a security vulnerability in Mastodon's code can [report it easily](https://github.com/mastodon/mastodon/security/policy) on the project's GitHub page. Known security vulnerabilities are also transparently reported to the public in the [security advisories](https://github.com/mastodon/mastodon/security/advisories) list.
|
||||
|
||||
Since April 1st this year, the Nivenly Foundation started the Fediverse Security Fund, a [security bounty program](https://nivenly.org/docs/programs/fediverse-security-fund/) to encourage more people to contribute to securing Mastodon and other Fediverse-connected software.
|
||||
|
||||
The experimental program will run **until September 30th, 2025**, and invites individual researchers and contributors to identify or patch vulnerabilities, rewarding them with a one-time sponsorship. If successful, the program could get extended, depending on member votes.
|
||||
|
||||
Regarding the software itself, Mastodon [uses](https://docs.joinmastodon.org/spec/security/) public key cryptography to secure HTTP Signatures and Linked Data Signatures. From [version 4.4](https://blog.joinmastodon.org/2025/07/mastodon-4.4/), Mastodon implemented a number of [security improvements](https://blog.joinmastodon.org/2025/07/mastodon-4-4-for-devs/) to authentication and authorization mechanisms. Mastodon 4.4 now [supports](https://docs.joinmastodon.org/spec/security/#http-message-signatures) incoming HTTP requests to be signed with RFC9421-compatible signatures. Additionally, the older (less secure) OAuth password grant type has been removed, and the OAuth Client Auth with HTTP Basic Auth with SSO has been fixed.
|
||||
|
||||
On the user side, Mastodon gives options to improve account security with the use of **multifactor authentication**, using an authenticator app or a physical security key. Already, this is better account security than what many (if not most) commercial social media platforms propose.
|
||||
|
||||
In addition, Mastodon users can see within their account lists of all sessions open, the authentication history, and all third-party software authorized to access the account. Users can quickly revoke access to any unauthorized or unused sessions or app, as necessary.
|
||||
|
||||
### Data security
|
||||
|
||||
Finally, because Mastodon only requires **minimal information** to create an account, less personal data risks getting exposed, in the unfortunate eventuality of a data breach. For example, no phone number, legal name, or official ID is required. This is excellent for both privacy and security.
|
||||
|
||||
Even if Mastodon has a much smaller security team than larger commercial platforms, its decentralization, transparency, and data minimization gives it significant advantages over for-profit social media.
|
||||
|
||||
Users' private data is protected reasonably well at the software level, but again, this protection also relies on the server security for each specific instance.
|
||||
|
||||
While security and privacy are related concepts that can enhance each other, they differ in many points. A piece of software could be very secure, yet collect and use a lot of private data, regardless of the user's consent or knowledge. Inversely, a seemingly privacy-respectful software could be collecting very little user data, yet not securing it properly.
|
||||
|
||||
Both privacy and security are important to consider for users, and both must be examined when evaluating software.
|
||||
|
||||
## :octicons-lock-16: How private is Mastodon
|
||||
|
||||
When using social media, there are always two sides to data privacy: The data collected by the service, and the data exposed by the user posting content.
|
||||
|
||||
### Data collected by the service
|
||||
|
||||
On Mastodon, the platform collects only minimal information from the user. Besides the content you decide to share for your profile and posts, the software only requires an *email address,* a *username,* and a *password* to sign up.
|
||||
|
||||
Starting from version 4.4, some instances might also collect a *date of birth,* if the instance implements a minimum age policy. This date of birth is only used to validate age requirements and isn't stored anywhere, but it is [checked](https://blog.joinmastodon.org/2025/07/mastodon-4-4-for-devs/) against the minimum age condition server-side.
|
||||
|
||||
Additionally, Mastodon will collect your *IP address(es)*, *applications* used, and the *times* you logged in. This is necessary to provide the service to you. You can increase your account privacy by registering with an [alias email address](https://www.privacyguides.org/en/email-aliasing) (if allowed by your instance), and logging in through a [trustworthy VPN](https://www.privacyguides.org/en/vpn/).
|
||||
|
||||
It's worth mentioning that Mastodon.Social, the instance administrated by the Mastodon organization, recently added to their terms of service an additional clause to [explicitly prohibit scraping](https://techcrunch.com/2025/06/17/mastodon-updates-its-terms-to-prohibit-ai-model-training/) users' data for unauthorized purposes, such as to train AI models. Many other instances might soon add similar clauses (or already have them).
|
||||
|
||||
While this provides little technical protections, it does provide some interesting *legal* protections. These are protections most commercial social media do not offer, as many already exploit users' content to train their own AI models or sell it to third-parties for this purpose.
|
||||
|
||||
This new Mastodon.Social policy is well aligned with the more human-centric values of the Fediverse.
|
||||
|
||||
<div class="admonition abstract" markdown>
|
||||
<p class="admonition-title">Summary of data collected by Mastodon</p>
|
||||
|
||||
- Email address
|
||||
- Username
|
||||
- Password
|
||||
- IP addresses (temporary stored, may vary per instance)
|
||||
- Browser and application types (temporary stored, may vary per instance)
|
||||
- Login history (temporary stored, may vary per instance)
|
||||
- Date of birth (not stored, may vary per instance)
|
||||
- Optional: The data you decide to share with the service (profile information, posts, post timestamps, uploaded media, favorites, boosts, followers, follows, bookmarks, lists, blocks, mutes, personal notes)
|
||||
|
||||
</div>
|
||||
|
||||
### Data you post on the service
|
||||
|
||||
Regarding the content of your profile and posts (including private mentions), no matter how much you restrict access to your account, you should always consider that this content *can* technically be accessed by the administration and moderation team of your instance.
|
||||
|
||||
Concerning people outside your instance's administration team, the privacy of the data you upload yourself will greatly vary depending on how you use and configure your account.
|
||||
|
||||
For more information on how to adjust your account's configuration for better privacy, consult the [tutorial part](#tutorial-how-to-adjust-and-improve-privacy-and-security-on-mastodon) of this article.
|
||||
|
||||
### Who can access your private data
|
||||
|
||||
As described above, the administration team of your instance *can* always technically access *any* data related to your account, regardless of if you make it public or private. This is true for most commercial platforms as well.
|
||||
|
||||
That being said, administration teams are generally much smaller on the Mastodon network, so this might not represent a lot of people. It could even mean only *one* administrator.
|
||||
|
||||
This has both benefits and downsides: The benefit is that fewer people have access to your private account data. The downsides are that, due to limited resources, this data *could* get less protection. That said, large commercial platforms aren't immune to data breaches either, despite all the resources they could use in prevention.
|
||||
|
||||
### Account configuration
|
||||
|
||||
Outside access from the administration team, content privacy will vary per account, depending on configuration. Similarly to any other social media platforms.
|
||||
|
||||
Some people might prefer to share openly with everyone, even with people who do not have a Mastodon account. While others might prefer to lock their account entirely, and reduce content visibility to their approved followers only. Both types of usage are possible on Mastodon.
|
||||
|
||||
Additionally, Mastodon offers much better controls over your data. You can set up automated post deletion with specific thresholds, adjust post visibility for each post, adjust searchability and discoverability to your preferences, and allow or restrict the upcoming [quote posts](#quote-posts) feature.
|
||||
|
||||
All these features are fantastic for data privacy, and often absent from commercial platforms.
|
||||
|
||||
### Users tracking and profiling
|
||||
|
||||
Most important of all, because Mastodon has no interest in monetizing your data, there is **no tracking, no advertising, and no "Mastodon-AI" profiling you** and scanning all your posts. Mastodon doesn't collect any data from you for a reason other than providing the service *to you*.
|
||||
|
||||
This is completely antithesis to commercial social media. And this alone makes Mastodon fundamentally **much more private than any other big tech platforms**.
|
||||
|
||||
## :material-lock-check-outline: Privacy benefits of Mastodon
|
||||
|
||||
Each Mastodon instance will have a different privacy policy that you should consult before creating an account, like for any other platforms. But unless the software was modified, data collection should be similar to what is described here, and remain minimal for the majority of connected instances.
|
||||
|
||||
Here's a summary of some benefits Mastodon can offer for your data privacy:
|
||||
|
||||
### Data minimization
|
||||
|
||||
Mastodon only collects what's necessary. The information required to create an account is minimal. There are no "real-name" policy and no phone number required. Only the data absolutely necessary to provide the service to you is required.
|
||||
|
||||
### Adjustable visibility
|
||||
|
||||
While profile information will be visible publicly, post visibility can be adjusted to your preference for each post. The list of who follows you and who you follow can be visible or hidden. Account searchability, discoverability, and quote posts from unmentioned users can all be disabled.
|
||||
|
||||
### Your data is yours
|
||||
|
||||
On Mastodon, you have full control over accessing and deleting your data. You don't need any third-party software to get your post deleted, and you don't need to wait after a company's customer service to download your data. Those controls are accessible to any user from their own account.
|
||||
|
||||
### No data monetization
|
||||
|
||||
The Mastodon software is developed and maintained by a nonprofit organization, the German [Mastodon gGmbH](https://joinmastodon.org/about). This software is free and accessible to anyone. There is no incentive to generate profit from your data on Mastodon. This is an *immense* privacy advantage over *any* commercial social platforms. There is nothing tracking you around or building an advertising profile on you. Your data is not for sale.
|
||||
|
||||
### Transparency and mobility
|
||||
|
||||
Because the Mastodon code is open-source, anyone can inspect it. This helps quickly verifying claims, proposing new features, and allowing other developers to create their own application for Mastodon.
|
||||
|
||||
With Mastodon, you are not stuck with only one app. If you don't like the official app, just use [another one](https://joinmastodon.org/apps)! Moreover, you can even move your account from one instance to another. This means you don't have to trust your administration team forever. **You can choose who you trust, and your trust (and consent) is revocable, as it should.**
|
||||
|
||||
### Respects your privacy protections
|
||||
|
||||
So many services and websites have adopted a hostile stance towards people using privacy protections such as a VPN server, a privacy-focused browser, or running their phone in [Lockdown Mode](https://support.apple.com/en-us/105120). But with Mastodon, you are free to use all the protections you love. **Mastodon isn't hostile to your privacy.**
|
||||
|
||||
## :octicons-alert-16: What to stay careful about
|
||||
|
||||
While the privacy benefits of Mastodon are numerous, there are also a few things to keep in mind when using the platform:
|
||||
|
||||
### Direct messages (private mentions)
|
||||
|
||||
Direct messages on Mastodon are better described at private mentions. Private mentions are like any other posts (and will sometimes show up in your feed! Don't panic!), but they will only be visible to the people you *mentioned* in it.
|
||||
|
||||
That being said, do **not** type the handle of someone to talk "in private" about them with someone else, because this *mentioned* person *will* also get included in this thread!
|
||||
|
||||
Additionally, private mentions on Mastodon, like private messages on other commercial social media, aren't end-to-end encrypted. The Mastodon interface shows this clearly:
|
||||
|
||||
{width="400"}
|
||||
|
||||
This means that all your private mention posts *could* be accessed by the administration and moderation team of your instance. **Never share any sensitive information using private mentions.** The same advice is applicable to any other social media.
|
||||
|
||||
<div class="admonition info" markdown>
|
||||
<p class="admonition-title">End-to-end encryption could be coming soon!</p>
|
||||
|
||||
That being said, this could change soon! The ActivityPub team is currently [working on integrating end-to-end encryption](https://socialwebfoundation.org/program-protocol-e2ee/) for the protocol. This would be nothing less than revolutionary for platforms using ActivityPub, like Mastodon.
|
||||
|
||||
It's difficult to estimate when this feature could be available to Mastodon users however, because implementing end-to-end encryption properly isn't a simple task. Even once the integration is completed for the ActivityPub protocol, it might take some time before the Mastodon development team implements it for the software as well.
|
||||
|
||||
Nevertheless, Fediverse users can dare to hope this feature may be available relatively soon, perhaps in the next year or two.
|
||||
|
||||
</div>
|
||||
|
||||
### The open web is open to all
|
||||
|
||||
On Mastodon, you don't need an account to see people's profile page and public (or quiet-public) posts.
|
||||
|
||||
This is an **immense benefit for organizations**, to share information with the public without restricting access like on commercial platforms. However, this can also mean more account visibility than some individual users may prefer.
|
||||
|
||||
It's important to stay aware that your account *could* be seen by anyone on the internet visiting your Mastodon account's public page. Your account's public page address is your instance's website address followed by your account's username, in the following format:
|
||||
|
||||
```html
|
||||
https://YOUR_INSTANCE_ADDRESS/@YOUR_USERNAME
|
||||
```
|
||||
|
||||
For example, for the Privacy Guides Mastodon account hosted on the mastodon.neat.computer Mastodon instance, this account's public page address looks like this:
|
||||
|
||||
```html {.copy}
|
||||
https://mastodon.neat.computer/@privacyguides
|
||||
```
|
||||
|
||||
Whether you lock your account (approve followers and use followers-only posts) or not, your display name, biography, profile and header pictures, followers and follows count, date joining the instance, and extra fields will always be visible to anyone from your account's public page.
|
||||
|
||||
Your public posts can even be accessed via [RSS feed](https://fedi.tips/following-mastodon-and-fediverse-accounts-through-rss/) on Mastodon. To limit this, you can adjust the settings to [restrict the visibility](#selecting-post-visibility-and-access) of your posts.
|
||||
|
||||
### Connection with commercial social media
|
||||
|
||||
Some Mastodon instances [connect](https://www.howtogeek.com/threads-now-connects-to-mastodon-and-other-fediverse-platforms/) with larger commercial social media like Threads (from Meta), and Bluesky ([through a bridge](https://techcrunch.com/2024/06/05/bluesky-and-mastodon-users-can-now-talk-to-each-other-with-bridgy-fed/)).
|
||||
|
||||
The Fediverse community is quite [divided](https://wedistribute.org/2024/03/block-threads-to-remain-listed/) on this topic. Some people argue that more connectivity is good, while others want to stay away from commercial platforms entirely, partly due to their questionable data privacy, ethics, and [moderation practices](https://www.wired.com/story/meta-immigration-gender-policies-change/).
|
||||
|
||||
If this is important to you, you can check your instance's policies to see if it allows connections with these commercial social media. If it does, and you do not want this, you can [block specific instances](#blocking-an-instance) at the account level. This isn't a complete protection for your data, but it does reduce visibility from and to these platforms.
|
||||
|
||||
If this isn't enough for you, you can migrate your account to an [instance blocking Threads](https://fedipact.veganism.social/) (or other servers) at the administrator level. This offers stronger protections.
|
||||
|
||||
### Connection with other instances
|
||||
|
||||
It's important to remember that on Mastodon, there isn't only one centralized entity that receives your data.
|
||||
|
||||
For example, if you send a private mention post to someone on a different instance than yours, this person's instance administration team will now have access to your message as well, and your data *for this post* will also be stored on that instance.
|
||||
|
||||
This is very similar to how emails work. If you are a Tuta or Proton email user, and you send a message to someone using Gmail, now Google will also have a stored copy of your message.
|
||||
|
||||
### Decision paralysis trusting an instance
|
||||
|
||||
Finally, probably the biggest block people hit when starting to use Mastodon is *which instance to trust*.
|
||||
|
||||
Sadly, this simple decision has discouraged many potential users. Yet, having to choose an instance is indeed a feature and not a bug.
|
||||
|
||||
Because yes, this choice does burden you to pick who you trust, but **it also empowers you** to be able to *revoke* this trust at any time. No commercial social media gives you the option to stop trusting Mark Zuckerberg and move to another Facebook server that matches better your values, for example.
|
||||
|
||||
Be careful who you trust of course, but don't get paralyzed by this choice. Even if this might feel intimidating at first, this fear of choosing isn't worth staying with possibly even less trustworthy big tech administrators.
|
||||
|
||||
***
|
||||
|
||||
## :simple-mastodon: Tutorial: How to adjust and improve privacy and security on Mastodon
|
||||
|
||||
The second part of this article is a tutorial on how to improve your Mastodon account's security, and how to adjust the different privacy features to your preferences.
|
||||
|
||||
<div class="admonition question" markdown>
|
||||
<p class="admonition-title">Who is this tutorial for?</p>
|
||||
|
||||
- You already have an account on Mastodon
|
||||
|
||||
- You are *not* familiar with all the Mastodon settings yet
|
||||
|
||||
- You are *not* self-hosting your instance
|
||||
|
||||
</div>
|
||||
|
||||
Although many variations and versions of the Mastodon software are in use on the Fediverse, for the sake of simplification and universality, this tutorial will focus on its most recently released version (4.4).
|
||||
|
||||
If your instance software version is different, you will likely still be able to follow this tutorial, but might notice some variations.
|
||||
|
||||
<div class="admonition question" markdown>
|
||||
<p class="admonition-title">What software version is your instance running?</p>
|
||||
|
||||
To check which version your instance is currently running, from the web interface on desktop, check the information in the lower-left corner of your instance website (e.g. [https://mastodon.social/](https://mastodon.social/)). The very last line should list something similar to `v4.4.1` This is your instance's Mastodon version number.
|
||||
|
||||
</div>
|
||||
|
||||
Additionally, this tutorial was created from the desktop web interface. Experiences and setting accesses may vary greatly from a mobile app. It is recommended to follow along from the desktop web interface as well.
|
||||
|
||||
Screenshots for the tutorial were mostly taken from an account on the Mastodon.Social instance, but you will be able to follow along even if your account is on a different instance.
|
||||
|
||||
### Improving account security
|
||||
|
||||
Using a [unique email address](https://www.privacyguides.org/en/email-aliasing/) and a unique and [strong password](https://www.privacyguides.org/en/basics/passwords-overview/) are the starting points for good account security, and this is no different for Mastodon accounts.
|
||||
|
||||
Additionally, you should enable multifactor authentication for your account as soon as you can. This is one of the most important step you can take to increase your account's security, and its protections against account takeover attacks.
|
||||
|
||||
#### Enabling two-factor authentication
|
||||
|
||||
For this, go to "Preferences" (in the right-side menu) > "Account" > "Two-factor Auth", then click on the purple "Set up" button at the bottom.
|
||||
|
||||
|
||||
|
||||
#### Authenticator app
|
||||
|
||||
Confirm your password when prompted. Then scan the QR code with your [authenticator app](https://www.privacyguides.org/en/multi-factor-authentication/), or enter manually the plain-text secret on the right of the QR code. Confirm with entering the two-factor code from your authenticator app, then click "Enable" at the bottom.
|
||||
|
||||
|
||||
|
||||
**Carefully note the recovery codes** provided. You will need to use them if you lose access to your authenticator, for example if you were to lose your phone.
|
||||
|
||||
If you need to change your authenticator app later, you can go back to this menu and select "Edit" on the right of "Authenticator app". You can also return to this menu to generate new recovery codes, if you have lost your older ones or if they were compromised. Generating new recovery codes will invalidate your previous ones.
|
||||
|
||||
|
||||
|
||||
#### Security key
|
||||
|
||||
Once you have enabled two-factor authentication with an authenticator app, you will see the option to add a [security key](https://www.privacyguides.org/en/security-keys/) as well. You can add one if you want to register multiple second factors of authentication for your account.
|
||||
|
||||
<div class="admonition warning" markdown>
|
||||
<p class="admonition-title">Browser compatibility</p>
|
||||
|
||||
Some browsers will not support security key authentication. For example, the Mullvad Browser doesn't support it.
|
||||
|
||||
</div>
|
||||
|
||||
To add a security key, click on "Add" on the right of the listing. Insert your security key, choose a "Nickname" for it, then click on the "Add new security key" purple button.
|
||||
|
||||
|
||||
|
||||
On macOS, you might be prompted with an option to "Choose how to manage your passkeys". If you get this pop-up, click on "Other Options" at the bottom.
|
||||
|
||||
|
||||
|
||||
On the second pop-up, select "Security key" then "Continue". When prompted with "Set Up Security Key", activate your security key (for some keys, this means touching the metal part of it). This step may differ depending on your operating system type and version.
|
||||
|
||||
Once completed, you should see a confirmation that "Your security key was successfully added" on the page.
|
||||
|
||||
|
||||
|
||||
From now, each time you log in your Mastodon account, you will be prompted to select one of your authentication methods after entering your email address and password:
|
||||
|
||||
**To log in using your security key**, click on the "Use security key" purple button when prompted by your browser. Your operating system might present you with a pop-up to choose again between your authenticator app or your security key. On macOS, select "Security key", click "Continue", then insert and activate your key. There may be variations depending on your operating system, but it should be similar to this.
|
||||
|
||||
**To log in using your authenticator app**, click on the "Enter a two-factor code from your phone or a recovery code" link at the bottom, then enter the code from your authenticator app when prompted by your browser (or recovery code if you've lost your authenticator).
|
||||
|
||||
If you try to sign in from a browser that doesn't support security keys after enabling it (or if you lost access to your security key), you can still log in your account using your authenticator app as described above.
|
||||
|
||||
|
||||
|
||||
Keep in mind that adding *more* methods of authentication to your account *doesn't* make it more secure, it's the opposite.
|
||||
|
||||
If you register both an authenticator app *and* a security key, this means anyone who can access *either* your authenticator app *or* your security key could log into your account (if they already have your password). Different second factors aren't added together here, they simply provide more options to *access* your account.
|
||||
|
||||
<div class="admonition warning" markdown>
|
||||
<p class="admonition-title">When enabling multifactor authentication with any account</p>
|
||||
|
||||
Be careful to choose a method you will have access to easily each time you log in. In addition, make sure to note the recovery codes provided *very carefully* and store them in a secure location (ideally offline). Keep in mind these codes will allow you to recover your account, but could also allow *anyone* to bypass your multifactor authentication.
|
||||
|
||||
</div>
|
||||
|
||||
#### Verifying account accesses
|
||||
|
||||
In "Preferences" > "Account" > "Authorized apps", you can see which applications have access to your account.
|
||||
|
||||
There, you will see every application you have granted access to. If you no longer use a mobile app or a service listed there, you should revoke access.
|
||||
|
||||
If you do not recognize a listed service, you can ask your instance administrator to know if this is a legitimate application (some administrators might connect legitimate services to your account you may not recognize, such as Matrix).
|
||||
|
||||
|
||||
|
||||
Additionally, in "Preferences" > "Account" > "Account settings", in the "Sessions" section, you will find a list of authorized browser sessions. Again, you can revoke access to any sessions you no longer use, or do not recognize.
|
||||
|
||||
|
||||
|
||||
Just above this sessions list, you will see a link labeled "View authentication history of your account". Click on it to see a list of past logins, including applications used and IP addresses.
|
||||
|
||||
If you see a login that isn't legitimate, you should *immediately* revoke accesses you aren't using, and consider changing your password.
|
||||
|
||||
|
||||
|
||||
### Adjusting privacy vs discovery
|
||||
|
||||
When using social media, there's usually a sliding scale between privacy and discoverability.
|
||||
|
||||
You might decide to enable the most restrictions on your account's visibility (more privacy), make it as public as possible (more reach), or anything in between.
|
||||
|
||||
**Only you can decide what is best for your unique situation and usage.**
|
||||
|
||||
On Mastodon, you have many options to adjust this to your preferences and needs. In "Preferences" > "Public profile", select the "Privacy and reach" tab at the top.
|
||||
|
||||
|
||||
|
||||
In the "Reach" section:
|
||||
|
||||
- The option "Feature profile and posts in discovery algorithms" allows more people to find your account and public posts (default is unchecked). **Leave it *unchecked* for more privacy.**
|
||||
|
||||
- The option "Automatically accept new followers" allows anyone to be able to follow you (default is checked). Approving each follower can increase the privacy of your follower-only posts. **If you prefer to approve each new follower (locking your account), then *uncheck* this option.**
|
||||
|
||||
In the "Search" section:
|
||||
|
||||
- The option "Include public posts in search results" allows people to be able to find your public posts when searching for keywords in Mastodon (default is unchecked). **Leave it *unchecked* for more privacy.**
|
||||
|
||||
- The option "Include profile page in search engines" allows your Mastodon profile to potentially appear in search engine results, like Google and Bing (default is checked). ***Uncheck* this option to increase your account's privacy.**
|
||||
|
||||
In the "Privacy" section:
|
||||
|
||||
- The option "Show follows and followers on profile" allows anyone to be able to see who you follow and who follows you (default is checked). If you prefer to hide this from the public, ***uncheck* this option for more privacy.**
|
||||
|
||||
- The option "Display from which app you sent a post" will display publicly which application you are posting from for each post (default is checked). If you prefer to not show which app(s) you are using, ***uncheck* this option for more privacy.**
|
||||
|
||||
Once you have adjusted the account options to your preferences, click on "Save changes" at the bottom to confirm your choices.
|
||||
|
||||
|
||||
|
||||
### Selecting post visibility and access
|
||||
|
||||
In addition to your account's privacy preferences, you can also adjust visibility for each post. This is very handy to allow you to pick in a more granular way which information you wish to share more or less openly.
|
||||
|
||||
#### Choosing post visibility
|
||||
|
||||
On Mastodon, you can choose between 4 types of visibility for each post: Public, Quiet public, Followers, and Private mention.
|
||||
|
||||
{width="400"}
|
||||
|
||||
#### Public post
|
||||
|
||||
This post is visible to anyone, whether they follow you or not. This post will also be visible from your account's public page, to people who do not necessarily have a Mastodon account.
|
||||
|
||||
For example, if you log *out* of your account, then go to `https://YOUR_INSTANCE_ADDRESS/@YOUR_USERNAME`, you will see what someone outside of Mastodon could see from your public page.
|
||||
|
||||
|
||||
<small aria-hidden="true">Note: Please do not follow this account. This account is for research purposes only, and is not an official Privacy Guides account.</small>
|
||||
|
||||
#### Quiet public post
|
||||
|
||||
This post is visible to anyone, and is also visible from your account's public page (like a Public post). However, it will not be featured in the "Trending" or "Live feeds" timelines. Additionally, it will not be searchable. This reduces its public exposure slightly, and is sometimes recommended for replies.
|
||||
|
||||
#### Followers post
|
||||
|
||||
This post is only visible to your followers. If you enabled the option to approve each follower, then only people you have approved will see this post. Followers-only posts cannot be boosted (re-posted) by others, and will *not* appear on your account's public page.
|
||||
|
||||
Your Followers-only posts will have significantly less reach, and potentially less engagement, but will be much more private.
|
||||
|
||||
<div class="admonition tip" markdown>
|
||||
<p class="admonition-title">Followers-only post and approving followers</p>
|
||||
|
||||
An important thing to keep in mind when selecting a post's visibility is who your followers are (or could be).
|
||||
|
||||
If you select Followers-only, but anyone could follow you, this restriction will block boosts for this post, and remove visibility from your account's public page, but anyone who decided to follow you can see it.
|
||||
|
||||
However, if you *also* enable restrictions on who can follow you, you will have more control over the visibility of your Followers-only posts, by pre-approving who can follow you and see these posts.
|
||||
|
||||
</div>
|
||||
|
||||
#### Private mention post
|
||||
|
||||
This post is only visible to the people mentioned in it. This works like a "Direct message" feature, except that anyone mentioned will be included.
|
||||
|
||||
Be careful not to write the handle of someone you do not want included in this conversation! Because this *will* include them.
|
||||
|
||||
Additionally, always keep in mind that the administration and moderation team of your instance *could* see all your posts, including your Private mention posts (like it is the case for any other social media). Never share sensitive information in Private mention posts!
|
||||
|
||||
{width="400"}
|
||||
|
||||
<div class="admonition info" markdown>
|
||||
<p class="admonition-title">End-to-end encryption for private mentions</p>
|
||||
|
||||
There is currently work being done to [integrate end-to-end encryption](https://socialwebfoundation.org/program-protocol-e2ee/) to the ActivityPub protocol, potentially making end-to-end encrypted private mention on Mastodon possible one day.
|
||||
|
||||
Implementing end-to-end encryption properly is no small task, and understandably it could take some time for this to be ready for Mastodon users.
|
||||
|
||||
However, it would make your private mentions truly private, being accessible only to its intended sender(s) and recipient(s). This could be groundbreaking for the Fediverse, and for your privacy!
|
||||
|
||||
</div>
|
||||
|
||||
#### Adjusting default post visibility
|
||||
|
||||
Even if you can adjust visibility for each post, you may also want to adjust your account's *default* post visibility.
|
||||
|
||||
For example, this can help by preventing accidentally sharing something publicly if posting to followers only is preferred, especially if your account is locked for more privacy.
|
||||
|
||||
To adjust the default post visibility, go to "Preferences" > "Preferences" > "Other". In the "Posting privacy" section, select your preference in the "Posting privacy" drop-menu for either "Public - Everyone can see", "Unlisted - Everyone can see, but not listed on public timelines", or "Followers-only - Only show to followers".
|
||||
|
||||
Confirm your choice by clicking on "Save changes" on the upper-right.
|
||||
|
||||
|
||||
|
||||
<div class="admonition tip" markdown>
|
||||
<p class="admonition-title">Hide posted media (slighly)</p>
|
||||
|
||||
Additionally, you might want to check the "Always mark media as sensitive" option from the same section. This will label the media as "Sensitive content", and require others to click on it to view the image. This will **not stop anyone from clicking to view it**, including people without a Mastodon account from your account's public page, but it might *slightly* reduce the visibility for certain media.
|
||||
|
||||
Depending on the content, your instance may have some rules requiring to hide certain type of content. Make sure to consult your instance's Server rules about this.
|
||||
|
||||
</div>
|
||||
|
||||
#### Quote posts
|
||||
|
||||
Mastodon version 4.4 is already preparing for the implementation of a new [Quote Posts feature](https://blog.joinmastodon.org/2025/02/bringing-quote-posts-to-mastodon/) coming up in Mastodon 4.5. Quote posts have been long requested and debated on Mastodon.
|
||||
|
||||
Mastodon didn't lack quote posts accidentally, it was a deliberate choice from the development team to [reduce potential abuse](https://techcrunch.com/2025/07/08/mastodons-latest-update-readies-the-app-for-quote-posts-revamps-design/). This is why the team has been very careful, taking the time to implement this new feature properly, and giving options for Mastodon users to opt out.
|
||||
|
||||
Again, this shows how Mastodon differs from commercial social media, by prioritizing users' safety and control over monetizing attention.
|
||||
|
||||
To give control to the users, important options have been planned out:
|
||||
|
||||
1. People will be able to choose if they want their post to be quoted or not
|
||||
2. People will be notified when their post is quoted
|
||||
3. People will be able to **withdraw their post from being quoted** at any time
|
||||
|
||||
These options greatly reduce the potential for abuse when quoting posts, a behavior we have sadly all witnessed on commercial social media with a culture of dunking on others.
|
||||
|
||||
From Mastodon version 4.4, you can already decide which permission you want to allow for your posts to be quoted. This is only in preparation for the feature for now, the final implementation should be available in the [next software update](https://blog.joinmastodon.org/2025/07/mastodon-4-4-for-devs/).
|
||||
|
||||
To adjust this in preparation, go to "Preferences" > "Preferences" > "Other". From the "Posting defaults" section, find the drop-menu labeled "Who can quote", and select either "Everyone", "Followers and mentioned users", or "Only mentioned users".
|
||||
|
||||
Confirm your choice by clicking on "Save changes" on the upper-right.
|
||||
|
||||
|
||||
|
||||
### Verifying yourself and others
|
||||
|
||||
The account verification process on Mastodon is excellent. Not only is it free, but it doesn't require you to provide any official ID or other intrusive documentation to proof your identity. It is a privacy-respectful verification feature.
|
||||
|
||||
The way it functions is very simple: Verification works by providing a *proof of control* over a website, or a web page.
|
||||
|
||||
For example, if you are the official Mastodon account for the privacyguides.org website, you can easily add a simple invisible link to this website to confirm that this Mastodon account is official. Once the verification process is completed, the Mastodon account profile page will display a **verified link in green with a checkmark**, confirming this account is authorized by the owner of this website (or web page).
|
||||
|
||||
From a profile page, it looks like this:
|
||||
|
||||
|
||||
|
||||
All the links displayed in green with a checkmark have been verified from the listed website.
|
||||
|
||||
This is **a feature very important to use for organizations**. It confirms to readers and followers this Mastodon account is authorized and truly belongs to the organization. It's also important for any individuals, writers, and journalists who want to confirm their identity to the public.
|
||||
|
||||
Looking for these verified links, other Mastodon users can validate if an account is legitimate, increasing trust and security.
|
||||
|
||||
#### Verification for journalists and writers
|
||||
|
||||
In addition to the verification process available to anyone, Mastodon recently [added](https://blog.joinmastodon.org/2024/07/highlighting-journalism-on-mastodon/) a feature specifically for writers and journalists!
|
||||
|
||||
Since last year, journalists and bloggers alike can link their articles to their Mastodon account. This validates their identity, while also increasing their Mastodon account's discoverability from article links. This is fantastic feature!
|
||||
|
||||
Popular websites like TechCrunch, ProPublica, and of course Privacy Guides have already adopted it! You might have noticed this feature previously, for example if you found this article from a Mastodon post.
|
||||
|
||||
#### Verifying yourself
|
||||
|
||||
If you would like to verify your own account, here's how you can do it yourself.
|
||||
|
||||
It's easy, and it's free!
|
||||
|
||||
Go to "Preferences" > "Public profile", then select the "Verification" tab at the top. From there, follow the instructions to copy the link to the web page you want to use to verify your account.
|
||||
|
||||
|
||||
|
||||
If you prefer not to add a Mastodon link to your web page, you can simply add this HTML line in the web page's head section (replacing `https://YOUR_INSTANCE_ADDRESS/@YOUR_USERNAME` with the link to your own Mastodon account):
|
||||
|
||||
```html
|
||||
<link href="https://YOUR_INSTANCE_ADDRESS/@YOUR_USERNAME" rel="me">
|
||||
```
|
||||
|
||||
To add author attributions to your articles, scroll down the same page and simply add the provided link to each of your article's HTML page, then lists the website(s) allowed to credit you below:
|
||||
|
||||
```html
|
||||
<meta property="fediverse:creator" content="@YOUR_USERNAME@YOUR_INSTANCE_ADDRESS">
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Deleting and accessing your data
|
||||
|
||||
Data deletion is a fundamental part of data privacy, and a protected right under many privacy laws.
|
||||
|
||||
Mastodon makes data deletion effortless. You will never have to battle the insufferable BigTech™️ customer service to request your data to be deleted on Mastodon. You can control most of it just by yourself.
|
||||
|
||||
#### Automated post deletion
|
||||
|
||||
First, you can easily set up automatic post deletion and adjust it to your precise preferences. This is a rare feature on social media, and demonstrates once again how Mastodon prioritizes users' benefits over data monetization.
|
||||
|
||||
To enable it, go to "Preferences" > "Automated post deletion", then check the option "Automatically delete old posts" on the upper-left. Adjust the "Age threshold" on the upper-right to anything between 1 week and 2 years.
|
||||
|
||||
In the "Exceptions" section below, you can select a number of variables to customize post deletion. Keeping your pinned posts from being deleted is likely a good idea, for example.
|
||||
|
||||
You can also keep the option checked to protect from deletion your own posts that you have favorited. This is very convenient to get a more granular control over automated deletion, purposefully keeping some posts while letting others getting automatically deleted.
|
||||
|
||||
|
||||
|
||||
In the "Exceptions based on interactions" section, you can select a threshold of favorites and/or boosts to protect posts from automatic deletion.
|
||||
|
||||
Once you have adjusted automated deletion to your preferences, click on "Save changes" on the upper-right to confirm your choices.
|
||||
|
||||
#### Data access and backups
|
||||
|
||||
Another important side of digital rights is access to your own data. Here again, Mastodon makes it easy. You can download a copy of your account data any time you want.
|
||||
|
||||
For this, go to "Preferences" > "Import and export" > "Export". From there, you can request a compressed archive of all your posts and uploaded media once every 7 days. This archive will be readable by any ActivityPub-compatible software, or you can open it with any simple text software.
|
||||
|
||||
|
||||
|
||||
Additionally, you can download lists of your Follows, Followers, Lists, Mutes, Blocks, Domain Blocks, and Bookmarks in CSV format any time (also readable with any simple text software).
|
||||
|
||||
Keeping a local copy of your data for regular backup purposes is a good idea in general, and also recommended before an account migration.
|
||||
|
||||
#### Account deletion
|
||||
|
||||
Finally, if you decide to delete your *whole* account, this is again incredibly easy. Simply go to "Preferences" > "Account" > "Account settings", and scroll down to the bottom of this page.
|
||||
|
||||
Once you are ready to delete your data (and have downloaded the data you wish to keep), click on the "proceed here" link. Read the information from the "Account deletion" page, and enter your password when you are ready to confirm.
|
||||
|
||||
|
||||
|
||||
### Blocking users and instances
|
||||
|
||||
You have a lot of control on which information you show and see on Mastodon. Like for other social media, you can block users individually on Mastodon. But additionally, you can also block a whole instance if you aren't happy interacting with it. This, like an individual block, can benefit your privacy by restricting further who can access your posts.
|
||||
|
||||
<div class="admonition info" markdown>
|
||||
<p class="admonition-title">Filtering content and muting users</p>
|
||||
|
||||
This tutorial will not discuss in details all the Mastodon features, as it focuses on privacy and security. However, it's worth mentioning briefly that there are softer options than blocking, if you simply wish not to see some content on Mastodon.
|
||||
|
||||
First, you can use [Filters](https://docs.joinmastodon.org/user/moderating/#filters) to hide specific content or hashtags from your timelines. Second, you can [Mute](https://docs.joinmastodon.org/user/moderating/#mute) a user, temporarily or permanently. However, remember that muting a user will still allow them to see your posts. Since Mastodon 4.4, you can also now use "Remove follower" to simply remove someone from following you, without having to block them.
|
||||
|
||||
</div>
|
||||
|
||||
If you block a user, this person will not be able to interact with you, and will not see your posts from their account anymore. They could however still see your public and quiet-public posts from your account's public page.
|
||||
|
||||
<div class="admonition tip" markdown>
|
||||
<p class="admonition-title">Adding a Personal Note</p>
|
||||
|
||||
If you want to remember why you blocked (or muted) someone, you can [add a Personal Note](https://fedi.tips/what-are-notes-on-mastodon-what-does-click-to-add-note-mean-on-mastodon-profiles/) on their profile page. They will not be able to see this note, but your notes could be read by your instance's administration or moderation team. Be careful what you write there. Notes cannot be transferred during account migration at this time.
|
||||
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
To block a single user, find their profile and click on the 3-dot "Menu" button on the upper-right. From the drop-menu, select "Block `USER_NAME`".
|
||||
|
||||
|
||||
|
||||
<div class="admonition warning" markdown>
|
||||
<p class="admonition-title">Blocked users can still visit your account's public page</p>
|
||||
|
||||
Remember that blocked accounts (and instances) might still be able to see your public and quiet-public posts outside Mastodon, by visiting your account's public page. Although, they will not be able to interact with your posts anymore.
|
||||
|
||||
</div>
|
||||
|
||||
#### Blocking an instance
|
||||
|
||||
If you block an entire instance, *everyone* from this instance will stop seeing your posts, you will stop seeing theirs, and they will be removed from your followers and follows. Nobody from this instance will be able to follow you anymore, and you will not be able to follow them either.
|
||||
|
||||
There are two ways to block a whole instance. The simplest way is to find a user from that instance and click on the 3-dot "Menu" button on their profile. From the drop-menu, select "Block domain `DOMAIN_NAME`".
|
||||
|
||||
<div class="admonition danger" markdown>
|
||||
<p class="admonition-title">This blocks everyone from that instance</p>
|
||||
|
||||
Remember this will block *everyone* using this instance at once, and you will lose *all* followers and follows you may have from this instance as well. You might not be able to recover those followers if you change your mind later.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
Alternatively, you can even "pre-block" an instance on Mastodon. For example, many people used this method when Meta's Threads announced they would connect to the Fediverse, but didn't have any connected accounts yet.
|
||||
|
||||
To do this, go to "Preferences" > "Import and export" > "Export", then download the "CSV" file for your "Domain blocks".
|
||||
|
||||
|
||||
|
||||
Open the `blocked_domains.csv` file as a text file, then type each domain(s) you wish to block. Use one line for each domain (if you want to block more than one). Save this file using the same filename.
|
||||
|
||||
|
||||
|
||||
Back to your account, move to the "Import" section from the left-side menu. From the "Import type", select "Domain blocking list".
|
||||
|
||||
Keep the "Merge" option on if you want to *add* new domains to block, or select "Overwrite" to replace your old list with this new list. Browse to upload the file you just modified, then click "Upload".
|
||||
|
||||
<div class="admonition warning" markdown>
|
||||
<p class="admonition-title">Carefully verify the correct type!</p>
|
||||
|
||||
Make sure to select "Domain blocking list" in the "Import type" or you could accidentally overwrite other important data! For safety, always save a backup of your existing data before doing any modifications like this.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
You will be prompted to confirm. Verify the information is correct, then click "Confirm". You should see a confirmation message with "Your data was successfully uploaded and will be processed in due time". You can now leave this page.
|
||||
|
||||
#### Reporting users
|
||||
|
||||
Reporting users isn't necessarily directly linked to privacy and security (although it can be), but it's still an important mechanism to address the overall safety of the network.
|
||||
|
||||
Because moderators have less resources on the Fediverse, they rely on users reporting problematic posts in order to enforce moderation policies.
|
||||
|
||||
As a member of your instance's community, it's important to report posts violating your instance's Server rules, but it's also important not to misuse report mechanisms when there are no violations.
|
||||
|
||||
To report a post, click on the 3-dot "More" button on the lower-right of the problematic post, then select "Report `USERNAME`".
|
||||
|
||||
Answer the form to the best of your knowledge, and **try to be as helpful to your instance's moderation team as you can, without overwhelming them**.
|
||||
|
||||
|
||||
|
||||
<div class="admonition warning" markdown>
|
||||
<p class="admonition-title">Do not report if there are no policy violations</p>
|
||||
|
||||
People who volunteer to moderate an instance are doing it for the community. It's important to respect their time, to stay kind, and to not abuse reporting mechanisms.
|
||||
|
||||
Only report content that violates the policies of your instance, or theirs. Do not report users simply because you dislike their posts. There are better mechanisms to hide the content you simply dislike, such as Filters, Mutes, or Blocks.
|
||||
|
||||
</div>
|
||||
|
||||
### Opting out with hashtags
|
||||
|
||||
Data privacy and user consent are principles strongly valued by the Fediverse community. Sometimes, developers trying to create tools for the Fediverse or utilizing its user data without prior explicit consent have come into conflict with these values.
|
||||
|
||||
Unfortunately, despite how illegal it may be, there aren't many technical barriers to stop malicious actors from violating users' consent.
|
||||
|
||||
However, many developers creating tools for the Fediverse actually *do care* about respecting these values, and want to build tools the right way.
|
||||
|
||||
Some have implemented methods to opt in or opt out the data they collect or the tools they build. This is why you will sometimes see people adding specific hashtags in their profile biography, such as `#noindex`, `#nosearch`, `#nobot`, `#noai`, `#nobridge`, etc.
|
||||
|
||||
Ideally, all data collection should be prohibited until users' consent is obtained, and data subjects notified (opt in default). This is obligatory by law for many jurisdictions. Sadly, many developers do not follow sound legal practices in reality, and will not seek users' consent, despite their legal and moral obligations.
|
||||
|
||||
Adding these hashtags (and maybe others in the future) to your profile biography *might* help to opt out certain data collection and certain tools built by developers who do respect users' consent. This can effectively *reduce* data scraping, in some situations. If anything, it is at least a public statement against disrespectful (and sometimes illegal) practices.
|
||||
|
||||
### Moving to another instance
|
||||
|
||||
The freedom to move from one instance to another can greatly contribute to keeping Mastodon a place that puts its users first.
|
||||
|
||||
If suddenly your instance were to implement a data scraper for its AI model to train on all your content (like so many commercial social media do now), or drastically drop moderation, you could simply move your account to another instance, one that is more respectful of your values and privacy rights.
|
||||
|
||||
This is a feature completely absent from centralized social media. Allowing them to unleash unchecked user exploitation, knowing fully users feel trapped and somehow forced to endure the abuse on their platforms.
|
||||
|
||||
Mastodon is protected again such abuse, by design.
|
||||
|
||||
When investing your precious time and energy participating in a Fediverse community, you will retain your data and your agency to choose which type of administration you prefer.
|
||||
|
||||
If you are unhappy with your Mastodon instance's management, here's how to leave for greener pastures:
|
||||
|
||||
#### Planning your move
|
||||
|
||||
First, plan your move properly. While moving your account is easy enough to do, there is a 30 days cooldown period in which you will not be able to move your account again. Make sure to choose your new home (instance) carefully, you will be there for *at least* 30 days.
|
||||
|
||||
Then, you might want to inform your followers. While moving followers is done automatically, it may take a few hours before completion, and your followers might be wondering what is going on. It can be a good idea to post about it from the account you are moving away from before moving.
|
||||
|
||||
<div class="admonition success" markdown>
|
||||
<p class="admonition-title">Summary of the steps to follow</p>
|
||||
|
||||
1. Save an archive of your posts (if you want)
|
||||
2. Save a copy of the six CSV files in "Export" (to import later)
|
||||
3. Choose a new instance
|
||||
4. Create a new account on your new instance (you can use the same username if available)
|
||||
5. Alias your two accounts
|
||||
6. Move your old account to the new one
|
||||
7. From your new account: Wait that your followers are all transferred
|
||||
8. From your new account: Import data and verify that everything is transferred properly
|
||||
9. From your old account: Delete your older account (if you want)
|
||||
|
||||
</div>
|
||||
|
||||
#### Backing up your data
|
||||
|
||||
The first step is to back up your data. This is important both for security and to allow you to import it later to your new account (some data isn't transferred automatically).
|
||||
|
||||
Go to "Preferences" > "Import and export" > "Export", then click the "Request your archive" purple button at the bottom.
|
||||
|
||||
Wait for the archive to be ready (you should receive an email notification within a few minutes), then download your precious archive somewhere secure.
|
||||
|
||||
Do not stop there!
|
||||
|
||||
You also need to download the CSV files above to import them manually to your new account. For each line with a CSV option on the table below ("Follows", "Lists", "You mute", "You block", "Domain blocks", and "Bookmarks"), download the CSV file in a secure location. Be careful not to forget anything.
|
||||
|
||||
|
||||
|
||||
<div class="admonition warning" markdown>
|
||||
<p class="admonition-title">Your posts will not be moved!</p>
|
||||
|
||||
Unfortunately, you will not be able to import your posts to your new Mastodon account (yet).
|
||||
|
||||
But this might change soon! The ActivityPub team is currently working on a [live online account portability protocol (LOLA)](https://swicg.github.io/activitypub-data-portability/lola) that could get added to Mastodon relatively soon. This will be a wonderful improvement to this process, and allow even more freedom and agency to Mastodon users!
|
||||
|
||||
</div>
|
||||
|
||||
#### Moving your account
|
||||
|
||||
Once you have backed up your data, informed your followers, and created a new account on your instance of choice, you can start the migration process.
|
||||
|
||||
**From your new account:** Go to "Preferences" > "Account" > "Account settings", scroll down to "Moving **from** a different account", and click on "create an account alias".
|
||||
|
||||
In the field labeled "Handle of the old account", enter the complete handle (`@YOUR_USERNAME@YOUR_INSTANCE_ADDRESS`) of the *old* account you want to move *from*. Then click on "Create alias" at the bottom to confirm.
|
||||
|
||||
This will not initiate the migration yet. It will only create an alias, and it is reversible.
|
||||
|
||||
|
||||
|
||||
**From your old account:** Go to "Preferences" > "Account" > "Account settings", scroll down to "Move **to** a different account", and click on "configure it here".
|
||||
|
||||
Carefully read the information on this page. Enter the *complete handle* (`@YOUR_NEW_USERNAME@YOUR_NEW_INSTANCE_ADDRESS`) of the new account you want to move *to* in "Handle of the new account". Confirm with your current (old) account password on the right, then click on the "Move followers" purple button at the bottom.
|
||||
|
||||
**This will initiate the migration process.**
|
||||
|
||||
|
||||
|
||||
Moving all your followers to your new account might take some time, but normally should be fully completed within 24 hours.
|
||||
|
||||
Besides waiting for your followers to migrate, you will also need to manually import your "Following list", "Bookmarks", "Lists", "Muting list", "Blocking list", and "Domain blocking list". For this, go to "Preferences" > "Import and export" > "Import".
|
||||
|
||||
For **each** of these 6 types of data, select a type in the "Import type" drop-menu, then click on "Browse" to upload the corresponding file you have exported earlier in the [Backing up your data](#backing-up-your-data) step.
|
||||
|
||||
Choose "Merge" on the right if you want to *add* this old data to data your already have on your new account, or "Overwrite" if you want to only keep data from your old account. Then click "Upload" below.
|
||||
|
||||
|
||||
|
||||
There you go! Your Mastodon account was successfully moved from one Mastodon instance to another!
|
||||
|
||||
## :octicons-star-16: Mastodon keeps getting better
|
||||
|
||||
This article only presents an overview of Mastodon's features, and focuses on the features related to privacy and security. But Mastodon is so much more. It's a social platform that truly respects its community.
|
||||
|
||||
Mastodon is genuinely mindful of its users' experiences. In comparison, commercial social media are far behind in terms of customization and respect for their users.
|
||||
|
||||
**On Mastodon, you are not a product, you are a *person*.**
|
||||
|
||||
Moreover, the software and community keeps growing and getting even better every year. For the next Mastodon update planned later this year, we can expect Quote Posts to be fully implemented, while respecting users' consent to have their posts quoted or not.
|
||||
|
||||
Perhaps next year we can hope for improvement of the migration process, allowing users to also transfer their content to a new instance, thanks to the LOLA protocol. Then, we can dream of fully private direct messaging down the road, with the integration of end-to-end encryption.
|
||||
|
||||
Once again, all these features will put Mastodon and other Fediverse software well above any commercial platforms. Keep an eye on the [Mastodon roadmap for more](https://joinmastodon.org/roadmap)!
|
||||
|
||||
Mastodon isn't there to exploit your data and sell it to advertisers. There is no incentive to monetize you. On Mastodon, **you are a person who is part of a community**. This makes all the difference to respect your privacy rights 💛
|
||||
|
||||
## :material-hand-heart-outline: Consider supporting Mastodon
|
||||
|
||||
Mastodon doesn't sell your data, but it still needs money to survive and thrive. Mastodon is supported by its community!
|
||||
|
||||
If you enjoy the platform and can contribute, consider supporting the project by:
|
||||
|
||||
- [Donating to support Mastodon's development and operations](https://joinmastodon.org/sponsors)
|
||||
|
||||
- Donating to your Mastodon instance (ask your administrator)
|
||||
|
||||
- [Buying cute merch from the Mastodon organization](https://shop.joinmastodon.org/)
|
||||
|
||||
- [Contributing to the Mastodon project on GitHub](https://github.com/mastodon/.github/blob/main/CONTRIBUTING.md)
|
||||
|
||||
- [Starting your own Mastodon instance](https://docs.joinmastodon.org/user/run-your-own/)
|
||||
|
||||
- [Talking to your friends and family about joining the Fediverse!](https://jointhefediverse.net/join)
|
||||
|
||||
<div class="admonition info" markdown>
|
||||
<p class="admonition-title">More information</p>
|
||||
|
||||
For more information on Mastodon and the Fediverse, you can visit the excellent website [Fedi.Tips](https://fedi.tips/).
|
||||
|
||||
</div>
|
||||
|
||||
<small aria-hidden="true">Unless credited otherwise, all screenshots from: Privacy Guides</small>
|
||||
@ -271,7 +271,7 @@ At the time of this article's publication, Lex's current [privacy policy](https:
|
||||
|
||||
It goes without saying that you shouldn't email a copy of your passport to anyone, and you should never have to provide *more* information than the app already has on you to get your data deleted. This is especially true if all the data mentioned above gets shared with a third-party advertising company like Google, through the use of Google Forms.
|
||||
|
||||
Privacy Guides has reached out to Lex for clarification on its data deletion practices, but has not received any response at the time of this publication. This article will be updated with new information once we receive an answer.
|
||||
Privacy Guides has reached out to Lex for clarification on its data deletion practices, but has not received any response at the time of this publication.
|
||||
|
||||
Before creating an account with a dating app (or any other app for that matter), it's important to find information on what will be the process to delete your data and account once you are done with the app.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
meta_title: "Privacy Respecting Web Browsers for Android and iOS - Privacy Guides"
|
||||
title: "Mobile Browsers"
|
||||
title: Mobile Browsers
|
||||
icon: material/cellphone-information
|
||||
description: These browsers are what we currently recommend for standard/non-anonymous internet browsing on your phone.
|
||||
cover: mobile-browsers.webp
|
||||
@ -166,7 +166,7 @@ Shields' options can be downgraded on a per-site basis as needed, but by default
|
||||
- [x] Select **Disable non-proxied UDP** under [*WebRTC IP handling policy*](https://support.brave.com/hc/articles/360017989132-How-do-I-change-my-Privacy-Settings#webrtc)
|
||||
- [x] (Optional) Select **No protection** under *Safe Browsing* (1)
|
||||
- [ ] Uncheck **Allow sites to check if you have payment methods saved**
|
||||
- [ ] Uncheck **V8 Optimizer** under *Manage V8 security*
|
||||
- [ ] Uncheck **Javascript optimization & security** under the setting with the same name
|
||||
- [x] Select **Close tabs on exit**
|
||||
- [ ] Uncheck **Allow privacy-preserving product analytics (P3A)**
|
||||
- [ ] Uncheck **Automatically send diagnostic reports**
|
||||
|
||||
Reference in New Issue
Block a user