Privacy policy for Teak Reader
Teak Reader by yangliu
Teak Reader Privacy Policy
Updated: 11 November 2026
Full policy: https://www.teakreader.app/privacy
Accounts
We store your internal user ID, verified email, Apple identity association and sessions to provide account services. Resend delivers verification codes. Sign in with Apple can use a private relay email.
Usage statistics
The extension can report successful reader opens and signed-in reading activity with random installation/event IDs, time, browser channel and extension version. Signed-in activity is associated with the internal account ID. We do not fingerprint your browser or collect article URLs, titles, content, search terms or browsing history in analytics.
Usage statistics are enabled by default in Chrome and Edge and can be disabled in the translation panel. Firefox follows its built-in technical and interaction data consent. Disabling stops reporting and clears queued events. Private browsing is excluded. Raw events are retained for 30 days and daily activity records for 13 months.
Security and abuse prevention
We process the source IP address to rate-limit verification codes, extension authorization and API requests. Application rate-limit records contain a server-keyed HMAC identifier and counters rather than the raw IP; expired counters are periodically removed. IP addresses are not included in reading analytics or used for advertising, profiling or inferring location. We do not request GPS or device-location permission. Network and hosting providers also process connection information to deliver requests and protect the service.
Translation
When you request translation, article title and text are sent to Microsoft's translation service, separately from usage analytics. Bilingual reading requires a free signed-in account.
AI summaries and code explanations
Only when you request an AI summary or code explanation, the article title and text, or the selected code block and its language, are sent through our backend to DeepSeek. A paid membership is required. The extension and website never hold the provider key or connect directly to DeepSeek. This content is not stored in analytics. Our backend does not persist source text for summaries; results are cached per account in server memory for up to 30 minutes and disappear on restart. Closing the panel, signing out or entering editing stops the current page operation. A started paid model request may finish on the server and be charged using actual token usage. We retain a points ledger without article or code text. AI output is a reading aid.
Saved documents
When you save a document or add an annotation, its text snapshot, title, source link and loaded images are uploaded for access by the same account. Snapshots and images are stored in private Cloudflare R2. The database holds ownership, folders, stars, annotations, thoughts and a searchable text copy. Annotations and thoughts are private to your account. Searches use an account-scoped index; queries and content are not stored in usage analytics. We do not automatically save all browsing history. Deleting a document immediately removes it from library and search results and prevents access to its annotations. Replaced and deleted snapshots and annotations are normally retained for approximately 15 days for recovery, then cleaned up. Deleting a folder moves its documents to Unfiled.
Membership payments
Creem hosts payment collection. We retain account-to-customer and subscription associations, paid periods and point usage to provide entitlements and handle billing, cancellation, refunds or disputes. We do not receive or store full card numbers or security codes. Documents remain stored after expiry; the free plan can read only the 15 most recently saved documents.
Contact
For account data access, correction or deletion, contact yangliu-1995@outlook.com.