Security & Privacy

Private by construction,
not by promise.

On most networks, privacy is a policy the operator asks you to trust. On Pixelmine it is a property of the mathematics: the content of your private messages and followers-only posts is sealed on your own device before it leaves, and no node — and not the company — holds the keys to open it.

Operator-blind

The people running the service
cannot read what you share.

The messages in direct and group chats, and the content of followers-only posts, are encrypted on your device and can only be opened by the people you intend. The nodes and the coordination service that store and relay them handle that content only as sealed data they cannot decrypt, and there is no master key that opens your conversations. Some details around the content are not encrypted — they are listed further down this page.

Sealed on your device

Message and post content is encrypted before it is sent, so its plaintext never leaves your phone.

Stored blind

Nodes hold that content only as ciphertext and wrapped keys — meaningless without the right key.

Only you hold the keys

Decryption happens solely on the devices of the people you chose to share with.

The encryption

Future-proof by default.

Pixelmine’s key exchange and signatures use standards designed to remain secure even against the quantum computers of the future. Each message and post is sealed with its own fresh key, and that key is then wrapped so that only the people in the conversation — or, for a followers-only post, each follower — can open it.

  • A future-proof key exchange establishes a shared secret only you and your contact can derive — never the network in between.
  • Every message and post is encrypted with its own key, which is itself wrapped under the key for that conversation, so the network never sees it in the clear.
  • For a followers-only post the key is wrapped separately for each follower; in a chat it is wrapped with the conversation’s shared key. Either way, nodes only see sealed data they cannot open.
Sealing to an audience

Only the right people can open it.

A followers-only post is sealed with a single key, and a copy of that key is wrapped individually for each accepted follower — so exactly those people can read it, however far the post travels. Group chats share one key among their members, delivered to each member individually.

  • Accepting a follower runs a one-time key exchange with them — done once, then reused for every future post.
  • Each post carries a small manifest: its key, wrapped separately per follower. Nodes store the manifest but can open none of the keys in it — although they can see which followers it lists.
  • When someone joins, leaves or is removed from a group, the group key is rotated, so new messages are sealed with a new key.
Integrity

Verifiable, not just private.

Because the network is made of independently run nodes, authenticity cannot rest on trusting the machine that hands you data. Instead records carry their author’s signature, and nodes check it before accepting data from one another — so a node does not have to take the machine that handed it data on trust.

  • Posts, follows, reactions, comments, ratings and flags on the main feed are signed with a key only you hold, and nodes check that signature before storing them.
  • Your account ID is the fingerprint of your own key, and nodes check that it matches, so no one can bind your ID to a key they control. Display nicknames are not tied to keys.
  • Altering the signed content of a record makes its signature stop verifying, and nodes refuse it when it arrives.
Your identity

You are a key you hold,
not a password we store.

Your identity is derived from a cryptographic key generated on your own device and never uploaded to anyone. There is no password to phish or leak: what proves a post or a message is yours is the signature your key makes. The company never holds your key, so it cannot reset it or sign anything as you.

Recovery & control

Yours to keep, yours to take.

Owning your identity means owning its recovery too. Your keys export as a single encrypted file, unlocked by a 12-word recovery phrase, and restore on any device — the company is never in that loop. The keys that unlock your conversations are stored on nodes sealed to your own key, so you can recover them on a new device without exposing them to a node.

Portable backup

An encrypted key file, secured by your 12-word recovery phrase, restores your account anywhere.

No back door

There is no reset button we can press, and no key of ours that opens your messages or posts.

Your data, portable

Your public and followers-only posts are copied across many nodes, not locked inside one company’s servers.

What we can and can’t see

Drawing the line, honestly.

End-to-end encryption is a strong guarantee, but an honest one is worth more than an overstated one. Here is exactly where the line falls.

What stays private

  • The content of your direct and group messages, and of followers-only posts.
  • Your private keys, and the account settings stored with you on nodes.
  • Media in chats and followers-only posts — stored encrypted on nodes, meaningless without the key.

What isn’t hidden

  • Public posts are public by design, so they can be discovered and shared.
  • That communication happened — encryption hides content, not the fact of it.
  • The timing of activity and the broad shape of the network remain observable.
  • Who is in a chat, group chat names, descriptions and photos, comments, tags and mentions are stored without encryption.
  • Editing a followers-only post currently saves its new title and text without encryption.
  • Your name, date of birth, gender and nickname are also sent to Pixelmine’s servers, and identity documents or payout details you submit can be opened by Pixelmine to review them.
The honest limits

What encryption can’t do.

Strong privacy is worth stating precisely. Encryption protects the contents of your communication — it does not erase the fact that communication took place, and it is not a cloak of total anonymity.

  • Metadata is not hidden: who is in a conversation, when they are active, and the broad shape of the network remain observable.
  • Direct messages use one long-lived shared key per conversation, so they do not offer forward secrecy — if that key were ever compromised, the conversation’s history could be read. Group keys change when membership changes, which limits what an old key can open.
  • Anyone you shared something with can screenshot or keep it; encryption controls who can open a thing, not what they do with it afterward.
  • Media you open is decrypted onto your own device, so it is only as private as that device.
The building blocks

Standards, not homegrown crypto.

Pixelmine does not invent its own cryptography. It uses published, standardized algorithms — the same ones being adopted to resist future quantum computers.

Key exchange

A post-quantum key-encapsulation standard (ML-KEM-768, FIPS 203) establishes shared secrets.

Signatures

A post-quantum signature standard (ML-DSA-65, FIPS 204) authenticates identity and signed records.

Content encryption

AES-256, in CBC mode, seals the actual messages, posts, and files; the signature on each record protects it from tampering.

In short

Your private content doesn’t depend
on trusting us.

The content of your private messages and posts rests on keys only you hold and encryption no operator can undo. That is the difference between a promise and a guarantee.