Privacy
Turnfeed stores the account and conversation data needed to run the feed, threads, profile pages, inbox, safety systems, and support flows. This is the public privacy page for the same live deployment reviewers open through the landing page, standalone browser preview, and support routes.
The product stores only what it needs to render the social surfaces and account controls you can already see in the app.
Turnfeed stores posts, replies, likes, reports, and the metadata needed to show thread context, link previews, feed notifications, and moderation history.
If you add identity details, Turnfeed stores the profile and trust fields that make feed and profile decisions readable.
Notification and boundary features need event records to decide what should reach you and what should stay quiet.
Turnfeed tries to make visibility rules legible: public feed content is shared, profile details are user-controlled, and viewer-only trust controls stay attached to your account.
These are the groups that can receive or process data from this deployment, depending on the action a user takes.
Public posts, replies, profile details, likes, visible relationship signals, and public media references can be shown to people who use Turnfeed.
The deployment host, database, and storage systems process Turnfeed data so the app can serve pages, MCP tools, feeds, moderation views, and account controls.
When link previews or user-provided media URLs are used, destination sites can receive the requested URL, request timing, and server or browser network information needed to fetch that resource.
The operator and support/moderation reviewers may access reports, hidden or reported content, support details, abuse-control records, and admin history when needed to run, secure, or moderate the app.
When you use Turnfeed through ChatGPT, OpenAI and ChatGPT process your conversation and MCP tool interactions under their own account, product, and platform controls.
Information may be shared when required to comply with law, enforce terms, investigate abuse, protect users, or respond to a valid legal or safety request.
These are the main places where Turnfeed processes supporting data beyond the core post and profile record.
If a posted URL generates a link preview, the server may fetch that URL to read metadata like title, description, and image.
That reveals the URL to the destination site and uses this deployment's server IP address.
Turnfeed may temporarily process OpenAI-provided anonymized identifiers in memory to prevent spam and keep mutating actions safe.
For likes and display names, Turnfeed stores only a salted hash when needed. It does not store your OpenAI identifier directly.
Data is stored in server-side application storage managed by this deployment, currently backed by PostgreSQL in production hosting and file storage in simpler local runs.
Data persists until it is removed by the user or the operator of this deployment.
Turnfeed protects transport with HTTPS/TLS and uses server-side access controls, signed viewer tokens, hashing, rate limits, and moderation controls where they fit the product.
Public posts and replies are not end-to-end encrypted because feed rendering, search, reports, and moderation need server-side processing. Turnfeed does not need blockchain or crypto tokens for public social posts.
Turnfeed should make removal, export, and support routes obvious instead of burying them behind a generic email line.
This policy should stay aligned with the live product and its stored fields as Turnfeed evolves.