This page explains Fediview’s approach to privacy and offers general guidance on privacy considerations when using the fediverse.

Fediview’s Privacy Practices

What We Collect

Fediview is a static informational website. Our data collection is minimal:

Server logs: Standard web server logs may include IP addresses, timestamps, pages requested, and browser information. These are used for security and operational purposes only.

No accounts: We don’t have user accounts or registration systems.

No tracking: We don’t use analytics services that track individual users across sessions or sites.

No cookies for tracking: We may use essential cookies for basic site functionality (like remembering preferences), but not for tracking.

What We Don’t Collect

  • Personal information (names, emails, etc.) unless you contact us
  • Social media account information
  • Behavioral profiles
  • Data from your fediverse accounts

Contact Information

If you email us (through our contact page), we receive your email address and message content. We use this only to respond to your inquiry and don’t add contacts to mailing lists without explicit consent.

Third Parties

This site may be hosted on infrastructure that has its own privacy practices. We use:

  • Cloudflare Pages: For hosting and CDN. See Cloudflare’s privacy policy for their data practices.

We don’t embed third-party tracking scripts, social media widgets, or advertising.

Data Minimization Principles

Data minimization is a privacy principle that encourages collecting and retaining only the data necessary for a specific purpose. It’s relevant to both service providers and users.

For Service Providers

If you build fediverse tools:

  • Request only necessary permissions
  • Don’t store data you don’t need
  • Delete data when no longer needed
  • Be transparent about data practices
  • Allow users to export and delete their data

For Users

When using fediverse tools:

  • Review app permissions before authorizing
  • Prefer read-only access when possible
  • Revoke access for tools you no longer use
  • Check what data tools store about you

Privacy in the Fediverse

Understanding privacy on Mastodon and other fediverse platforms:

Post Visibility

Mastodon offers visibility settings, but understand their limits:

  • Public: Visible to anyone, appears in public timelines, can be indexed
  • Unlisted: Visible to anyone with the link, not in public timelines
  • Followers-only: Only your followers see it
  • Direct: Only mentioned users see it

Important Limitations

Direct messages are not encrypted: They’re more like email than Signal messages. Instance administrators can technically access them.

Deleted posts may persist: Deletion requests are sent to other instances, but copies may remain in caches or backups.

Public means public: Public posts can be indexed by search engines, archived by third parties, and seen by anyone.

Instance administrators have access: Admins can potentially access content on their instance, including DMs.

Federated Privacy

Federation adds complexity:

  • Content you post travels to other servers
  • You can’t control what happens on other instances
  • Different instances have different retention policies
  • Blocking an instance doesn’t remove already-federated content

Practical Privacy Tips

  1. Think before posting: Assume public posts are truly public
  2. Use appropriate visibility: Match visibility to your intent
  3. Don’t share sensitive data: The fediverse isn’t designed for private communications
  4. Check instance policies: Understand your instance’s data practices
  5. Review connected apps: Audit apps with access to your account
  6. Consider using alt accounts: Separate identities for different contexts

Web Privacy Concepts

Understanding broader web privacy helps you make informed decisions.

Cookies and Storage

Web applications can store data in your browser through:

  • Cookies
  • LocalStorage
  • IndexedDB
  • Cache API

These enable functionality but can also enable tracking.

Cross-Site Tracking

Third-party trackers can follow you across websites using:

  • Third-party cookies
  • Fingerprinting
  • Tracking pixels
  • Embedded content

Fediview doesn’t use these techniques.

Browser Protections

Modern browsers offer privacy features:

  • Cookie controls
  • Tracker blocking
  • Fingerprint protection
  • Private browsing modes

Consider using these features for general web browsing.

For comprehensive information on web privacy concepts and how cookies work, Google’s Privacy Sandbox documentation provides detailed technical explanations.

Your Rights

Depending on your jurisdiction, you may have rights regarding your data:

  • Right to know what data is collected
  • Right to access your data
  • Right to correct inaccurate data
  • Right to delete your data
  • Right to data portability
  • Right to opt out of certain processing

If you have questions about data Fediview may have (primarily email correspondence), contact us at privacy@fediview.com.

Changes to This Policy

We may update this page to reflect changes in our practices or for legal compliance. Significant changes will be noted in our changelog.

Frequently Asked Questions

Does Fediview access my Mastodon account?

No. Fediview is an informational website. We don't have any connection to your social media accounts.

Do you sell data?

No. We collect minimal data and don't sell or share it with third parties for marketing or other purposes.

How long do you retain server logs?

Standard hosting logs are retained briefly for operational purposes. We don't maintain long-term archives of visitor data.

How can I contact you about privacy concerns?

Email privacy@fediview.com with any privacy-related questions or concerns.

Contact

For privacy-related inquiries: privacy@fediview.com

For general inquiries: See our contact page

Last updated: January 4, 2026