What the application stores
Accounts store an email address, password hash or provider identity, session information, and the profile details you choose to provide. Public contributions, reputation events, and badges are associated with your account.
Public and private spaces
Profiles and published discussions are public. Private messages and notifications are limited to participants or their account owner. Reports and audit records are restricted to authorized staff.
Confessions and Links pages
Your Links page is public when enabled. Confessions arrive in the page owner’s private inbox. We do not show the sender’s account name or network address. A keyed per-page network hash supports abuse limits and blocking; this does not guarantee anonymity against the hosting provider or someone who recognizes the message. A reply link is a private capability: anyone who has it can read the reply. Public wall sharing requires the sender’s explicit permission and the owner’s action. Message text is excluded from notification emails and audit logs. Authorized staff can review reported content, pause pages, remove messages, and restore mistakes.
Cookies and event counts
Session cookies keep you signed in. Theme preferences are stored in your browser. View events use short-lived pseudonymous keys to avoid counting repeat refreshes. The live activity panel uses daily rotating pseudonymous browser identifiers, expires inactive visits after 90 seconds, and publishes aggregate counts only. Private pages are excluded. Authentication and abuse prevention may process network information.
Links audience analytics
Links analytics uses a browser-session identifier and a 30-minute HttpOnly cookie to associate a visit with a link click. It records a daily per-page hashed identifier, referrer hostname, device class and campaign tags; it does not store raw IP addresses or full referrer URLs in the analytics table. Reports exclude known bots, signed-in owner previews, Do Not Track and Global Privacy Control visits. Page owners see aggregate reports according to their plan. Event history is removed after 366 days by a bounded hourly cleanup. Campaign labels should not contain personal information.
Your account and choices
Use account settings to update your profile, manage sessions and notifications, and request a data export. Contact ReadMeFeed using the private support form below for privacy questions or account removal requests. Never post passwords, access keys, or sensitive personal information in the community.
Hosting and email
Microsoft Azure hosts the application, database, media, and operational logs. Transactional email delivers account verification, password resets, and enabled notifications. Access to private account data is restricted. Backups and security records may retain information after it changes in the live application.