privacy

Why Your Photos on Bluesky Are Public by Design

Bluesky's AT Protocol makes all content public and indexable by anyone. Here's what that means for photos and memories you share there.

Bluesky has attracted tens of millions of users since its open beta — many of them fleeing platforms with opaque algorithms and advertising-driven privacy policies. On the surface, it looks like a more trustworthy place to share your life online. And in some ways, it is.

But when it comes to photos, personal memories, and anything you’d consider private, Bluesky works on a fundamentally different model than most people assume. Understanding that model before you share matters a great deal.

The AT Protocol Is Built for Public Content

Bluesky runs on the AT Protocol — an open, decentralized communication standard developed by Bluesky PBC. The design intent is portability and openness: anyone can build a client, run a relay, or crawl the network.

That openness is the core privacy trade-off.

Your posts, photos, likes, reposts, and profile information are stored in what the protocol calls a data repository — a public record that anyone can read. Bluesky’s privacy documentation states this plainly: “User content including profiles and posts will be available to the general public.”

There is no private account option on Bluesky. There is no “friends only” or “followers only” setting for posts. If you post a photo on Bluesky, it is public by design, not as a quirk — as the intended behavior of the protocol.

What “Public by Design” Actually Means for Photos

With traditional closed platforms, your data might be technically public to the company but inaccessible to arbitrary third parties. With the AT Protocol, that distinction largely disappears.

Any third-party developer can run a relay that indexes the entire Bluesky network. They don’t need permission. They don’t need to comply with Bluesky PBC’s terms of service. They just need to run the software.

This means:

  • Photos you post are immediately available to any application or service connected to the AT Protocol relay
  • Search engines and archiving services can index your images without notice
  • Third-party apps built on the protocol can display, analyze, or store your photos under their own terms — not Bluesky’s
  • Even deleted photos carry risk: while Bluesky’s servers remove images when you delete a post, other relays and caches may already have copies

The AT Protocol’s design allows for this because it treats public conversation as its core use case. It was built so that social graphs and posts can move freely between providers. That’s genuinely useful for interoperability — and genuinely problematic for privacy.

Direct Messages: Slightly Better, but Not End-to-End Encrypted

Bluesky’s direct messages are not publicly visible in the same way. They’re private between users in the sense that other users can’t see them.

But Bluesky’s privacy policy makes clear that DMs may be accessed by moderation staff in the course of investigating significant violations of Community Guidelines. DMs are also not end-to-end encrypted — meaning the content exists in a readable form on Bluesky’s servers.

For sharing personal photos, financial documents, or anything sensitive, DMs on Bluesky carry the same risk as DMs on any conventional centralized platform. The decentralized label doesn’t make them private.

Self-Hosting a Personal Data Server Changes Some Things — but Not Much for Most People

The AT Protocol does allow a more privacy-conscious option: self-hosting your own Personal Data Server (PDS). This gives you full ownership of your identity and data, and your content doesn’t sit on Bluesky PBC’s servers.

However, self-hosting a PDS still puts your posts on the public AT Protocol network. The content is still public and still indexable by relays. What changes is who controls the server — not who can see the content. Self-hosting also requires meaningful technical expertise to set up and maintain securely.

For the vast majority of users, the practical experience is: post on Bluesky, and the world can see it.

The Data Portability Framing vs. the Privacy Reality

Bluesky and the AT Protocol frequently emphasize data portability — the ability to take your social graph, posts, and identity from one provider to another. This is a real and valuable feature, especially compared to closed platforms that lock you in.

But portability and privacy are different things.

The AT Protocol ensures you can move your data. It does not ensure your data stays with you. Your photos and posts are accessible to the whole network, not just to you and whoever you designate.

This is worth holding clearly in mind when the conversation turns to “decentralization” as a privacy solution. Decentralization distributes trust and control. It doesn’t inherently restrict access.

When Bluesky Went Down in May

The network reliability question is also relevant. In May of this year, Bluesky experienced a notable outage that left users questioning what access rights they had to their own data during a service disruption. Under UK GDPR, users have the right to request a copy of their personal data — but exercising that right during an outage illustrated the limits of cloud-dependent social platforms regardless of their protocol design.

If your memories are stored only on Bluesky, a service disruption is a loss of access to those memories.

What Kind of Sharing Belongs Where

The public-by-design nature of Bluesky makes it genuinely useful for things that benefit from wide visibility: professional commentary, public journalism, community organizing, open-source project updates.

It’s a poor fit for:

  • Family photos of children
  • Photos from medical appointments or health milestones
  • Travel photos containing location metadata
  • Anything you’d consider a private memory

The friction between “I’m leaving the big platforms” and “but I still want to share my life” is real. Many people move from Instagram or X and assume Bluesky is a more private space. The privacy policy and protocol design say otherwise.

The Metadata Problem

Photos carry EXIF metadata — GPS coordinates, device model, timestamp — embedded in the image file itself. When you upload a photo to Bluesky, that metadata may travel with it depending on whether the client strips it before upload.

Bluesky’s official apps do strip some metadata. But third-party AT Protocol clients vary. And the relay infrastructure that indexes your posts doesn’t guarantee any metadata handling. A photo posted to the public network with GPS coordinates embedded is a photo that reveals your location to anyone who downloads the image and inspects it.

What Private Photo Storage Actually Looks Like

If you want your photos and personal memories stored privately — accessible to you, not to the world — a social platform running on a public protocol isn’t the right tool.

Private file and photo storage means:

  • Your content isn’t indexed by a public network
  • Access is controlled by authentication, not protocol-level openness
  • Deletion is effective, not dependent on whether third-party relays have already cached the file
  • The provider’s privacy policy governs your data, and you’ve read it

Daftei is built for exactly this use case — private storage of photos, documents, and personal files. It runs on the web and through iOS and Android apps. Files are encrypted with AES-256 at rest and protected with TLS 1.3 in transit. Daftei doesn’t sell data, never trains third-party AI on your content, and never runs ads.

When you delete an account, there’s a 30-day grace window — then permanent, irreversible erasure. There’s no relay network distributing your photos to whoever runs the right software.

Choosing the Right Tool for the Right Purpose

None of this is an argument against Bluesky. As a public conversation platform, it does what it’s designed to do, and it does it with more transparency about its design than most platforms offer. The AT Protocol’s openness is a feature, not a bug, for the use cases it’s designed for.

The argument is for clarity: know the tool you’re using and what it’s designed for. A public communication protocol is for public communication. Your private memories, family photos, and personal documents need a different kind of home.

Before you post, ask whether this is something you want searchable, indexable, and accessible to any developer who runs a relay. If the answer is no, it belongs somewhere else.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts