What we collect, why we collect it, and what we do with it. The short version: as little as possible.
Plain language. This policy is written to be understood, not to be lawyered. If anything is unclear, ask us.
flebop is software, not a service. flebop is open source software that anyone can self-host. This privacy policy is a template for node operators — it describes the data practices of this specific node, not of any central authority. The developers of flebop do not operate this node and have no access to any data on it. The operator of this node is solely responsible for their data practices.
When you create an account on this node, we collect:
When you use the platform, we store:
For federation, this node also stores:
We use two cookies, both strictly necessary for the platform to function:
sessionid) — keeps you logged in.csrftoken) — protects against cross-site request forgery.No consent banner is needed because these cookies are essential for the service to work. There are no optional, analytics, or marketing cookies.
flebop is a federated platform. When you interact with servers on other nodes:
Your account data (username, password) stays on this node and is never shared with other nodes in the federation.
You have the right to:
For anything not covered by the above, contact the node operator.
Your data is stored for as long as your account exists. If you delete your account, your personal data will be removed. Messages you sent in public servers may be retained but will be disassociated from your identity.
Passwords are hashed using industry-standard algorithms. Node operators are responsible for configuring TLS — connections should be served over HTTPS. Only data that is operationally required to run the service is stored — nothing more.
This policy may be updated as flebop develops. Significant changes will be communicated to users via an in-app notice.