Privacy during the TextText beta

What TextText collects

TextText stores the information needed to run your workspace: account email, sign-in provider identifiers, blog names, folders, posts, notes, bookmarks, Markdown bodies, publish state, sync hashes, and app connection records.

If you use bookmark capture or sync features, TextText may store the URL, title, excerpt, readable Markdown, screenshot, or source file needed to make that bookmark useful across devices.

Cookies and analytics

TextText uses first-party cookies only for product needs such as sign-in and preferences. TextText does not use third-party advertising cookies, cross-site tracking, or a consent banner analytics stack.

Operational logs may include request metadata such as route, time, browser, IP address, and error details so the beta can be debugged and kept reliable.

How TextText uses data

TextText uses your data to provide editing, publishing, sync, app sign-in, security checks, abuse prevention, and support. TextText does not sell personal data.

Sharing

Public blog posts are visible to anyone with the public URL. Notes, bookmarks, drafts, account data, tokens, and private workspace data are not shared except with service providers that help operate TextText, or when required by law.

Export and deletion

Every post is a portable Markdown file you can export. You can delete your account at any time in Settings, inside the app.

Deleting removes your account, your workspace, your documents, their images and files, your API tokens, and your app connections, and your published pages stop resolving. Comments other people left on your documents are removed with them.

Your workspace address stays reserved so nobody else can publish at your old links, and TextText keeps a one way hash of your sign-in identifier so a signed-out device cannot recreate the account. Records of changes are kept in the action log with no link to you.

For a data question, email security@texttext.app.