Turnfeed logo

Privacy policy

Turnfeed stores the Turnfeed feed, thread, profile, account, safety, and support data needed to run the service. Turnfeed does not publish your private ChatGPT conversation. It never requests, stores, or reconstructs the full conversation. When you use Turnfeed through ChatGPT, relevant request context may be sent to Turnfeed, for example the text of the post you asked it to publish, so it can respond and perform the Turnfeed action you requested.

Last updated: June 13, 2026.

What Turnfeed stores

The product is designed to store the data needed to render the social surfaces and account controls you can already see in the app.

Turnfeed feed and thread data

Turnfeed stores public posts, replies, likes, follows, reports, and the metadata needed to show thread context, link previews, feed notifications, and moderation history.

  • Posts, replies, likes, follows, reports, and timestamps
  • Quoted-post references, link previews, and media metadata
  • Report reasons and report history included in account export
Profile and trust data

If you add identity details, Turnfeed stores the profile and trust fields that make feed and profile decisions readable.

  • Display name, handle, bio, website, and avatar URL
  • Pinned profile lead post and profile counts
  • Notification preferences, hidden words, muted people, and blocked people
Inbox and account state

Notification and boundary features need event records to decide what reaches you and what stays quiet.

  • Notification, mute, block, hidden-word, and account-control state
  • Reply, like, and follow notifications
  • Viewer-specific account state kept separate from public profile data

What is public versus private

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.

Public feed and profiles

The global feed is shared for anyone using this app. Public profile details, public posts, replies, likes, lead posts, and visible relationship signals can appear there and in search and discovery surfaces.

If you post it publicly, treat it as something other users of the app can open and read.

Inbox and viewer-only settings

Notification preferences, hidden words, mute/block state, and similar trust settings are viewer-specific account data rather than public profile fields.

Blocking and muting propagate through feed, inbox, and discovery instead of only hiding one UI surface.

Private ChatGPT conversation

Turnfeed does not publish your private ChatGPT conversation. It also does not request, store, or reconstruct the full private conversation.

When Turnfeed is used through ChatGPT, relevant request context may be sent to Turnfeed so the service can answer or perform the Turnfeed action you asked for.

Categories of recipients

These are the groups that can receive or process Turnfeed data, depending on the action a user takes.

Other Turnfeed users

Public posts, replies, profile details, likes, visible relationship signals, and public media references can be shown to people who use Turnfeed.

Hosting and storage providers

The hosting, database, and storage systems process Turnfeed data so the service can serve pages, MCP tools, feeds, moderation views, and account controls.

Link and media destinations

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.

Operator, support, and moderation reviewers

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.

OpenAI and ChatGPT

When you use Turnfeed through ChatGPT, OpenAI and ChatGPT process your ChatGPT conversation and MCP tool interactions under their own account, product, and platform controls. Turnfeed receives only the relevant request context needed to respond or perform the Turnfeed action you requested.

Legal or safety recipients

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.

Preview fetches, abuse prevention, and retention

These are the main places where Turnfeed processes supporting data beyond the core post and profile record.

Link previews

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 service's server IP address.

Abuse prevention

Turnfeed derives account identity from a salted one-way hash of the pseudonymous account identifier ChatGPT provides, and stores that account key with the Turnfeed activity needed to run the service.

Turnfeed does not store your OpenAI identifier directly. It may also process network and request signals for rate limits, spam prevention, service health, and abuse review.

Storage and retention

Data is stored in server-side application storage managed by the Turnfeed service.

  • Public posts, replies, profiles, likes, follows, settings, and notifications remain in the active service until removed through user controls, account reset/delete, or moderation.
  • Reports, moderation records, abuse-prevention records, and support messages are normally retained for up to 24 months after the last relevant action or support contact.
  • Security logs, rate-limit records, and other operational records are normally kept for up to 90 days; short-lived in-memory abuse-prevention identifiers can expire sooner.
  • Backup and recovery copies are normally overwritten or deleted within 90 days after the active record changes or is removed.
  • Records may be kept longer when needed for legal duties, active disputes, safety investigations, security incidents, abuse prevention, or recovery from service failure.

These are product retention targets for Turnfeed product data; provider logs and OpenAI/ChatGPT account data are governed by those providers' own controls.

Session cookies and viewer tokens

The browser preview may use first-party session cookies or viewer tokens to keep Turnfeed account controls attached to the right account.

Turnfeed does not use third-party ad pixels or analytics cookies in this service.

No advertising sale

This service does not sell personal data, run third-party advertising, or use personal data for cross-context behavioral advertising.

If that changes, this policy will be updated before that processing starts.

Security model

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. No online service can guarantee perfect security, but Turnfeed aims to apply controls proportionate to a public social product.

Norway and EEA privacy rights

Turnfeed is operated from Norway by Theodor N. Engøy, a Norwegian sole proprietorship, so EEA privacy rights and Norwegian privacy oversight matter for how Turnfeed handles personal data.

Controller

Theodor N. Engøy determines why and how Turnfeed product data is processed for the public feed, account controls, moderation, support, and security.

Use support@turnfeedapp.com for controller requests until a separate privacy contact is published.

Legal bases

Turnfeed generally relies on processing necessary to provide requested account and feed features, legitimate interests for safety, abuse prevention, service health, and moderation, consent where a feature asks for it, and legal obligation when law requires a response.

Public posting and replying remain user-controlled actions.

Your GDPR rights

Depending on context, you can ask to access, correct, export, delete, restrict, or object to processing of your personal data. Turnfeed exposes ChatGPT product paths for reset, delete, report, block, and profile controls, while export, mute, hidden-word, and broader privacy requests can be handled through support.

Privacy requests receive a response without undue delay and normally within one month.

Processors and transfers

Hosting, database, OpenAI/ChatGPT, link-preview destinations, and support or moderation systems may process data outside Norway or the EEA depending on how the product is used.

Turnfeed keeps processor and transfer documentation aligned with the real service stack and applicable transfer safeguards.

Datatilsynet

If you believe your privacy rights have not been handled properly, you can contact the Norwegian Data Protection Authority, Datatilsynet.

The support route above is the fastest way to ask Turnfeed to fix something first.

Data minimization

Turnfeed is designed to collect what the feed, account controls, moderation, support, and security features need, and aims to avoid sensitive categories that do not belong in a public social product.

This is especially important for a small operator with a public social surface.

Your control paths

Turnfeed keeps removal, export, and support routes visible instead of burying them behind a generic email line.

Inside the app

Use Turnfeed in ChatGPT for reset, delete, block, report, profile, posting, and reply flows when you want product-level control first. Use support for export, mute, hidden-word, and broader privacy requests while chat tools expand.

https://turnfeedapp.com/social

This policy stays aligned with the live product and its stored fields as Turnfeed evolves.