Skip to content
WisdomKey

Privacy

Updated: 2 October 2026

No account needed to listen, read or ask WisdomKey AI. Guests can ask 5 questions a day; members can ask 50.

When you sign in

  • Sign in with a 6-digit code sent by email (valid for 10 minutes) or with your Google account.
  • Your account stores your email, display name and avatar. Your name and avatar come from Google if you sign in with Google; otherwise your name is the part of your email before @.

What you create is stored with your account:

  • saved items;
  • listening position and history;
  • talk notes;
  • book notes, highlights and reading position;
  • your last 20 searches;
  • WisdomKey AI conversations;
  • content correction suggestions;
  • answer feedback.

General feedback you send is stored with your account and deleted when you delete your account.

When you are not signed in

  • View counts: your browser keeps a random ID. Individual view records are only used to avoid double counting and are deleted progressively once they are more than a day old; WisdomKey keeps the totals.
  • The assistant quota uses a one-way hash of your network range. WisdomKey does not store IP addresses for assistant quotas.
  • Guest chats stay in the open browser tab only. WisdomKey does not store guest questions unless you rate an answer as helpful or not helpful, or flag a wrong citation: that question and answer are then stored with your feedback to improve the assistant.

WisdomKey AI

  • Your question, up to 3 previous question-and-answer turns and relevant excerpts are sent to the model provider (Google Gemini, with Anthropic as fallback) and to Voyage for retrieval.
  • Your account or identity is not sent with them.

Abuse prevention

  • Cloudflare Turnstile checks sign-in attempts, and your IP address is sent to Cloudflare for this.
  • Requests for sign-in codes are limited. Rate-limit records are hashed and deleted after one day.
  • When unusual access exceeds a threshold, WisdomKey stores guests’ IP address, country/city and device/browser information for up to 30 days to protect content; only administrators can view it.

Cookies and browser storage

  • Sign-in cookies.
  • Cookies remember the light/dark theme, language and caption style.
  • Browser storage holds offline audio or books, player settings, reading position and recent searches.
  • WisdomKey does not use advertising cookies or third-party analytics or tracking.

Where data lives

  • Supabase (Singapore), Vercel (Singapore), and Cloudflare R2 (audio and reading files).
  • Backups are encrypted.

Retention

Data is kept until you delete it or delete your account. AI assistant operational logs are deleted nightly once older than 90 days for guests and 12 months for members. Saved conversations and feedback remain managed as described above.

Your choices

You can delete conversations, search history, notes, highlights and saved items in the app.

To delete your account, use the “Delete account” button on the Account page. For other personal-data requests, email wisdomkey.org@gmail.com via the Contact page.

Dāna

When you transfer dāna, WisdomKey receives the bank's transfer notice (amount and memo). Your name is shown publicly only if you write “DANA <name>”.

Estimated daily web listeners

When measurement is enabled, WisdomKey estimates listeners after at least 1 minute of actual web playback accumulated within a day in Vietnam time (Asia/Ho_Chi_Minh). Opening a page, downloading a file, pausing, buffering, seeking and device sleep do not count as listening time.

This measurement uses no cookies, browser-stored IDs, accounts or third parties. Minimal network metadata is processed temporarily in memory; IP addresses are not stored. Hashes use a random salt unique to each day. The salt and deduplication marks are held temporarily for the current measurement day and deleted when the day is finalized; only daily totals remain, with no per-person or per-talk history and no links across days.

This is a network-range estimate, not a count of verified people or a guarantee against bots: shared networks may undercount and changing networks may overcount. Reloading, offline listening, browser throttling, network errors or system restarts may lose unsent listening time or the provisional daily count. Daily counts cannot be added up as weekly unique listeners. Listening through podcast apps is not measured yet.