First, who is responsible
Senol Sahin operates this community. For privacy requests, corrections, deletion, or a larger export, contact: senols@gmail.com.
Your words are public
Your name, handle, bio, posts, replies, author updates, timestamps, visible edit history, and displayed social counts can be read without signing in. There are no private posts or direct messages. Share only what you are comfortable making public.
Mute hides someone from your signed-in views. Block also prevents authenticated interaction and removes follows, thought subscriptions, and Notifications between the accounts. Someone can still sign out to read public writing.
What stays with your account
We store your email, password hash, verification status, profile, preferences, and authentication records. Sessions may include an IP address and browser user agent. Your private email is not included in public profiles or posts.
Saved posts, thought subscriptions, reading progress, mute and block lists, notification preferences, and reports are private account data. The owner can access reports and operational data to run the community. Report text is not published to the person reported.
The browser stores your sign-in cookie, theme, account-specific drafts, and reading position. Account-specific drafts and reading data are cleared on sign-out or account deletion. There are no advertising trackers, contact uploads, media uploads, AI processing, or session-replay tools.
Control and deletion
Settings lets you change your profile and preferences, manage safety controls, download a JSON account export, and delete your account. Exports exclude password hashes and access tokens. Very large exports need operator assistance rather than returning an incomplete download.
Account deletion removes your active credentials and sessions, profile, authored content and edits, saves, subscriptions, reading state, and personal relationships. Deleting an original thought also removes its updates and everyone’s replies beneath it. Non-content moderation audit records can remain with the actor reference removed until expiry.
Deleted content stops appearing in app reads and search. Copies in someone else’s possession, search-engine copies, and email already delivered cannot be recalled. Backup copies expire according to the configured backup policy.
Retention and providers
Content and relationships stay until removed. Sessions expire after 30 days, verification links after one hour, and reset links after 30 minutes. Maintenance removes expired authentication records, Notifications older than 30 days, development mail after 24 hours, expired rate buckets after another day, invitation reservations after 30 days, and non-content audit records after 90 days.
Daily maintenance removes expired records in bounded batches; a backlog or failed run can delay removal. Neon keeps one day of recovery history. Separate operator recovery copies may remain until manually removed; an additional scheduled off-site backup service is not configured. Contact the operator about retained backup copies.
Vercel hosts the application with functions in Frankfurt. Neon stores the database in Frankfurt. Resend processes verification and recovery email in its EU West region; open and click tracking are disabled. These providers also process operational request and delivery data. Application error logs contain operation codes rather than private content, addresses, passwords, or access links.
A small amount of measurement
The launch plan uses weekly aggregate counts and voluntary conversations to understand whether people follow a thought and return for its update. No external analytics tracker is installed. Historical read-event measurement would require a separately reviewed, minimal first-party record and retention policy.