Safety

Privacy and safety basics

A federated network can offer meaningful community control, but it does not make social posts confidential. Share with the expectation that recipients can copy what they receive.

Visibility is not encryption

Post visibility settings control intended distribution and how software presents a post. They cannot prevent screenshots, copying or misbehaving software. Messages exchanged across servers are processed by infrastructure outside your direct control. Do not put secrets or high-risk personal data in a social post because its audience label looks narrow.

Check before you publish

Confirm the selected visibility, attached media and alternative text. Use content warnings where context benefits readers or local rules require them. Ask consent before posting private conversations or identifiable images of other people. The official Mastodon posting guide documents current visibility options and composition tools.

Protect the account

Use layered moderation

Mute when you want to stop seeing an account without a stronger boundary. Block when you want to prevent ordinary interaction. Report conduct that may violate server rules, and include enough context for moderators to assess it. If risk crosses into credible threats or illegal conduct, preserve evidence and use appropriate local support channels rather than relying only on platform tools.

Minimise long-term exposure

Consider whether your profile reveals location, routines, workplace or family relationships. Old posts may be indexed, copied or retained remotely even after deletion requests propagate. Regularly review profile fields, followers, public history and connected applications. Privacy comes from deliberate habits plus trustworthy administration, not from a single setting.

Related: moderation and community rules →