Privacy Policy
This page summarizes what html.surf collects and how it is used for the web app, API, MCP server, search, navigation, sharing, and connected AI clients.
Data Collection#
html.surf stores account email, pages, page metadata, links, bookmarks, themes, uploaded assets, share links, API keys, OAuth connector authorizations, page views, and basic usage records.
Use#
Data is used to operate the web app, REST API, MCP server, search, link graph, sharing, asset hosting, and account access controls.
Storage and Retention#
- Pages, assets, links, bookmarks, themes, share links, API keys, and connector authorizations are retained until deleted, expired, or revoked where supported.
- Magic links are short lived.
- OAuth authorization codes expire after 10 minutes.
- OAuth access tokens expire after 1 hour.
- OAuth refresh tokens expire after 30 days; server-side revocation before expiry can be requested at privacy@html.surf.
Third Parties#
html.surf runs on Cloudflare Workers, D1, R2, Vectorize, Workers AI, and Email Routing. Search embeddings and semantic search text may be processed by Cloudflare Workers AI and Vectorize. The AI navigator currently uses Google Gemini, and may send user prompts, search queries, MCP tool inputs, page content, linked-page context, and other relevant context needed to provide search, navigation, and answers. Connected MCP clients such as Claude receive data requested through tools you authorize.
User Controls#
- Delete pages and assets from the app.
- Revoke API keys and share links from account or page controls.
- Remove bookmarks from saved research views.
- Disconnecting Claude from the Claude connected-apps UI stops that client from using the connector.
- Server-side OAuth token revocation before refresh token expiry can be requested at privacy@html.surf.
- Private pages remain private unless you make them public, share them, or grant another user access.
Contact#
For privacy questions, email privacy@html.surf.