Security and privacy

A short version of what TileSet stores, what it never stores and how long it keeps things, with links to the full pages.

The full statements are the security page and the privacy policy. The short version:

Your accounts

TileSet never sees your platform passwords. You approve on the platform’s own screen.
Access tokens are stored encrypted and never come back out: not in the dashboard, not to an agent, not in your export.
AI agents and API keys never read your content: no post or review reaches them, only counts and a preview of the widget.
Sign-in is with Google or a one-time link we email you, and the email is verified either way. Session ids and API keys are stored as one-way hashes.
A webhook URL is shown once and stored as a hash.

The widget sets no cookies and carries no visitor id.
Counts are anonymous. TileSet records the site’s domain, never the visitor’s IP address.
Page paths are off unless you turn on page-level insights.
The script comes only from TileSet’s own address, its file hashes are public and checked every day. See How TileSet keeps tileset.js safe.

Cached posts and reviews: overwritten on each update; a copy nothing refreshes expires within 30 days.
Page paths, when enabled: 90 days, and deleted at once if you turn the setting off.
The audit log: 12 months.
Expired sessions are deleted.
A deleted account: removed within 7 days.