Privacy Policy

Last updated: October 2026

What we collect

• Email address — collected when you activate a license, used only to send verification, license management, and subscription status emails.
• Device information — browser type, OS, language, timezone, and screen size, stored to enforce per-device license limits.
• Anonymous usage events — off by default; opt in or withdraw in Settings. Consented actions such as install, first export, and upgrade clicks use a random per-install identifier, not derived from your email or license and not joined to purchases. Only bounded, allowlisted properties are accepted; no conversation content, titles, full URLs or credentials are included.
• Service error diagnostics — checkout failures and unexpected backend errors create a support reference and redacted technical report. Reports exclude conversation content, request bodies, customer email, raw URLs, cookies and credentials. They may be emailed to the admin/support team, are grouped when repeated, and exclude reports older than 30 days on access and are limited to 200 report groups. Expired rows are pruned on access; inactive Redis report keys expire after 30 days. Operator backups have a separate retention policy.

What we do NOT collect

• Your Claude conversation content — all export processing happens locally in your browser.
• Browsing history or activity outside of claude.ai.
• Passwords or payment card details.

How your data is used

• License validation, device management, subscription management, and account support.
• Sending OTP, license management, subscription cancellation, and support emails.
• Aggregated, anonymous product analytics to guide development.

Image loading

Preview images may be fetched from Claude or a site you explicitly permit. Requests to separately permitted image sites omit cookies and referrers; Claude image requests may use your existing Claude session. Choosing a replacement image reads a file on your device; exports remain local unless you choose a direct provider transfer.

Optional integrations

Sending to Notion transfers selected content directly to Notion using your local token. Google Docs, when configured and explicitly connected, uses Google OAuth with drive.file scope to upload the chosen document directly to Google. No Google passwords or client secrets are collected; token caching is managed by the browser. Disconnect removes the browser token and requests revocation when available.

Data sharing

We do not sell or share your personal information with third parties, except as required to operate the service (e.g., transactional email provider, cloud hosting). Payment, hosting, storage and email providers process operational data under their applicable terms and privacy policies.

Data retention

License, purchase, device, subscription, restore and admin records may be kept while needed to provide Pro access, support purchases, enforce device limits, handle disputes, prevent abuse, meet legal requirements and maintain backups. Consented analytics older than 180 days are excluded from reports and pruned on the next stream read or write. Inactive Redis analytics streams expire within 180 days of their last activity; raw data in an idle stream can remain until that expiry. Historical backups follow the operator retention policy. Offline events remain locally for at most 7 days; withdrawal clears the local queue and random identifier. Archive records, content search and collections are optional and stored locally in IndexedDB. Delete them from Backup & local archive. Downloads permission confirms completed file downloads; native print-dialog saves cannot be observed.

Your rights

You may request access to, correction of, or deletion of your personal data at any time by emailing support@anhbui.dev.

Contact

For privacy questions, contact support@anhbui.dev.