WriteByte Privacy Policy

WriteByte stores account information needed to authenticate users, route access requests, and render author pages. That may include email address, name, username, OAuth client metadata, access-review notes, and article content created through the product.

The MCP connector stores OAuth clients, authorization codes, access tokens, refresh tokens, and server-side session state so connected AI apps can act on the author's behalf after explicit browser approval. Drafts, revisions, comments, and profile edits are stored in the same production database as the public site.

WriteByte uses connected AI hosts only as the interface where the author chooses to work. The product records article content, provenance metadata, lifecycle actions, and related profile updates needed to provide the publishing workflow.

WriteByte uses two sub-processors for telemetry. Microsoft Clarityreceives anonymized interaction events (clicks, scroll depth, session replay with form input masking) so the team can understand how readers move through provenance-marked essays. Azure Application Insights receives server-side request traces, exception data, and MCP tool-call metadata (tool name, success/failure, duration, signed-in user ID). Neither sub-processor receives essay content, comment bodies, or any provenance notes. Both are configured to honor browser Do-Not-Track and Global-Privacy-Control signals.

Users can request support or deletion help through Support. Security and data-handling details are summarized on the Security & Data Use page.