Questions, answered the way we would want them answered

You, anyone you grant access to, and — for any file you have not encrypted — whoever operates the server. Pod stores your files on our infrastructure as ordinary bytes on disk. There is no encryption at rest, so an operator with access to the machine can read them. That is true of most hosted storage, and it is worth knowing rather than assuming otherwise.

For unencrypted files, yes — technically they can. Nothing in the architecture prevents it; the protection is organisational, not cryptographic, and organisational protection is a promise rather than a guarantee. If you encrypt a file, no: encryption happens in your browser, the key is derived from your passphrase, and the server only ever receives ciphertext. We cannot decrypt it and we cannot recover it for you if you forget the passphrase.

The contents of the individual files you choose to encrypt, and nothing else. Not the file's name — an encrypted file keeps a readable name, so naming one `divorce-settlement.pdf` still tells an observer what it is. Not your folder structure, not your credential list, not the pod as a whole. It is per-file and opt-in by design, because an entirely encrypted pod would be unreadable to the Solid applications that make it worth having.

There is no self-serve deletion today, and we would rather say that than imply a button exists. You can delete individual files, and you can export everything at any time. If you want the whole pod removed, write to us. When a deletion route ships it will be documented here.

No. Authentication goes through auth.solidus.network using Solid-OIDC, and pod receives a token, never a key. The separate passphrase you use for file encryption is also never sent — the key is derived from it in your browser.

Yes, and you get one during sign-up if you do not have one. Your pod's address is derived from that identifier, which is the part that makes it yours rather than ours: the address does not depend on an account we could close.

By uploading them. There is no connector to any other storage service — not to Drive, not to anything else — so you move the files yourself. What you upload keeps its name and its folder structure.

Any type. There is no enforced per-file size limit and no enforced total, because nothing in the server implements one. Very large uploads are limited by your browser and connection rather than by a rule we set.

Not today. Every hosted pod sits on our infrastructure in one location, and there is no region picker. If placement is a requirement for you, the server is open source and running your own is the real answer.

A document an issuer has signed — a KYC result, a diploma, an employment record — so that whoever you show it to can check it came from that issuer and has not been altered. In your pod they are files, in JSON-LD or SD-JWT format, and you can read and export them like anything else.

If it is an SD-JWT credential, yes — you release the fields you choose and the rest are never sent. A JSON-LD credential is presented whole; showing one field means showing all of them. Which format you have is set by whoever issued it, and the credential page tells you which one you are looking at.

It stays in your pod and the list marks it Expired. Nothing is deleted, and nothing is sent to you — there are no reminder emails, so watching the date is on you. Renewal is between you and the issuer.

Open Apps, choose the app, and revoke. That deletes the access-control rules naming it, so its next request is refused. There is no session to expire and no grace period: the rule is gone when the write completes.

Only if you granted write access. Permissions are per-resource and per-agent, so an app can hold read on one folder and nothing anywhere else, and the Apps list shows the exact mode each one has.

Nothing, and there is no paid tier to upgrade to. There is no card, no trial, and no feature held back behind a plan — everything pod does today, it does for every pod.

No. It is a reference figure the meter is drawn against, and nothing enforces it — no upload is blocked at that number. We show it because a meter with no scale is useless, and we say it is not a limit because publishing an entitlement nothing backs would be a lie.

Pod runs on a public testnet and has not completed a third-party security audit. It is a real product doing real work, and it has not been independently examined. Treat that the way you would for any young system holding your documents, and keep an export.

Solid is a W3C-community specification for personal data stores, and it is why another application can read your pod without our permission. We say Solid-compatible rather than Solid-conformant, deliberately: the conformance suite is the bar for that word and we have not run it against our deployment. When we do, the result gets published whichever way it goes.

Yes, and it needs nothing from us. Your pod is served by Community Solid Server, an MIT-licensed project maintained by the Solid community — not by software we wrote. You can run the same server yourself.

The access rules for a resource, stored as a document next to it. It names agents by their WebID and the modes they hold — read, write, append, control. It is readable, it is yours, and it is the same mechanism the interface uses when you share something, rather than a private setting on our side.