Choose how you show up.

Anonymous: Feedme does not attach an AT Protocol identity to your tip. You can separately opt into an anonymous timeline entry showing the project and date, without your identity or amount. Older anonymous tips stay hidden unless permission was recorded. Payment providers and the recipient may still see the billing information needed to process it.

Private: Your verified DID, amount, and note are available to the creator through private storage. They are not published as a public acknowledgment.

Public: You explicitly publish your DID, the project, amount, and timestamp on the open network. Public records can be indexed and copied. Removing a record later cannot remove every copy. Confirmed public tips also get a public share link with allocation percentages and project progress. Its image omits the tip amount, but public amounts remain available on the timeline and network. Private and anonymous tips never get allocation cards. Refunded or disputed cards become unavailable; other platforms may retain copies of shared images.

For monthly or yearly support, the same amount, project split, and visibility apply to each successful payment. Stop future renewals from Manage support. Billing identifiers stay in private storage; each payment gets its own receipt. The original checkout browser can access recurring billing for up to a year. Stripe also provides email-based recovery using your checkout email.

Your tip note is always private. Supporter timelines include named public tips and explicitly permitted anonymous entries. Private tips never appear. Public totals include only public tips. Private and anonymous tips do not contribute to public counters.

Creator and project follows are public records in your own AT Protocol repository. A separate public message after tipping is optional: it publishes your chosen text and a project link under your identity, or your allocation card and image if your support is public. This can identify you as a supporter even if the payment receipt is anonymous. It never copies your private note or amount. Feedme stores the post’s retry information locally; the original checkout browser or named supporter account is required to share.

Habitat spaces restrict access; they are not end-to-end encrypted. This server keeps an operational copy of the records. The instance operator controls that server. Live mode encrypts the local stored values with an operator-provided key. Complete private recovery records in Habitat include payment references, allocation choices, notes, and subscriptions. If configured by the operator, encrypted backups are also stored in their backup destination. Recovery snapshots and backups can retain earlier versions after a change; ask the operator about their retention policy.

Stripe hosts checkout and stores billing details. Feedme stores payment references and status, never your full card number. Necessary cookies keep you signed in and bind forms to your browser. There are no analytics or advertising cookies in this application.

Project images from external URLs and the Bluesky links you follow may contact other servers. Operators should publish their own contact details, retention schedule, and payment terms before accepting real support.