Little Whale DSH Reader
Privacy notice
What the reader accesses and how its operator handles the records.
Effective 23 October 2026
1. Operator and contact
Little Whale DSH Reader is a personal research application operated through Little Whale Home. It is used only by the project's operator; this website does not let visitors connect Google accounts.
For a privacy question or a data request, contact @LittleWhaleHome on X. Do not post private information publicly. If sensitive details are needed, agree a suitable private channel with the operator first.
2. Information and purpose
The reader uses YouTube API Services with read-only permission to check the connected channel's identity, find videos, and read video metadata. A separate restricted API key reads public comments. Results may include identifiers, titles, descriptions, dates, links, public channel information, comment text, and public author information.
Retrieved information supports research, source checking, drafts, and continuity between sessions. Selected observations may be saved in notes or memory. This connection does not access Gmail or Drive, download audiovisual files, or publish to YouTube. Google's practices are described in the Google Privacy Policy.
3. Where information goes
Google receives authorization and API requests. Research records, conversations, notes, memory, evidence, and backups can be retained on the operator's computer. Credentials are kept separately in a protected local store and are not intended for prompts or drafts.
The reader currently uses DeepSeek's account-based Harness service. Conversation text and tool results are sent to DeepSeek for processing. Its Harness privacy policy allows input and output to be used for model training unless the user opts out. A training opt-out and remote deletion outcome have not been confirmed for this project.
Drafts selected for review or publishing may also be processed through Codex. Local storage does not mean that processing is entirely local. This project does not claim that model providers retain no data or that removing a local record erases their copies.
These pages contain no analytics code, forms, embedded players, or externally loaded assets. They are served through Cloudflare, which processes network requests, including IP addresses and traffic information, to deliver and protect the site. See the Cloudflare Privacy Policy.
4. Retention and requests
The operator handles retention reviews and data requests manually. YouTube's rules require ordinary stored API data to be refreshed or deleted within 30 calendar days, and stored data related to a user to be deleted as soon as possible and within seven calendar days of that user's deletion request. These requirements apply to the relevant YouTube records, not to all of Little Whale's independent memories.
The manual workflow identifies affected API results and related notes, memory, logs, and backups; checks what can be refreshed or removed; and records the outcome. Moving a record to a recycle bin is not treated as completed deletion. Local action, a request to a model provider, and the provider's confirmed outcome are distinguished.
Complete removal from every historical copy and model provider has not yet been verified. No automatic deletion service or guarantee of erasing all remote copies is claimed. The operator must address any identified gaps before treating a request or retention review as complete. Removing project records does not remove data from YouTube itself.
5. Stopping access
The operator can stop the reader locally and revoke its access through Google Account connections. Revocation does not itself erase existing research records or provider copies; those need separate handling through the process above.
For questions or to start a records-related request, contact @LittleWhaleHome on X. Share only the minimum non-private information needed to identify the request publicly.