Privacy policy

What we store

• Account: email address, display name, handle, linked OAuth accounts
• Decks: the files you publish and their generated HTML/poster derivatives
• Devices: names of signed-in app instances and token metadata (not raw tokens)
• Abuse reports you file, including your email if you provide it

Analytics — view counts, not surveillance

When someone views a deck we record a small event describing the view itself: which deck and version, which slides were seen, how long the view lasted, whether the view completed, the viewer's coarse country (from the edge header — never a precise location), the referring domain if any (domain only, never the full URL), the device class (desktop, tablet or mobile), and whether the view came through a portal page or an embed.

Analytics are cookieless. We never set a tracking cookie, never store the viewer's IP address or user-agent string, and never fingerprint browsers. Per-day deduplication uses a hash of IP + user-agent with a salt that rotates daily — the hash can't be reversed and can't follow anyone across days. Raw events are kept for 30 days, then deleted; only daily aggregate counts survive.

• Signed-in users can disable analytics for their own browsing and viewing on the portal in Settings → Privacy.
• A deck owner's own views are never counted.
• Browsers sending Global Privacy Control (GPC) get engagement tracking turned off — only the base view count is recorded.
• Decks embedded on other sites send the same minimal data — nothing extra for being off-portal.

Third parties

No third-party advertising or analytics today. Hosted decks load no external resources — fonts and data are embedded at publish time.

Contact & deletion

Delete a deck from your dashboard and its files are purged. To delete your account or ask a question, email [email protected].