Data we collect
Account data
Sign-in identity, email address, display name, profile image, account tier, workspace settings, and authentication state through Firebase Authentication and Firestore.
Workspace and map data
Saved maps, topology content, publish state, comments, bookmarks, likes, forks, and related workspace metadata that you create or interact with.
YouTube page data
When you choose to analyze a YouTube page, the extension may read data from the active page such as title, URL, description, chapters, comments, playlist/channel context, available transcript/captions, and public metadata needed to generate learning summaries, Q&A, recommendations, or knowledge maps.
Billing and support data
Payment-provider IDs, product/variant identifiers, entitlement status, support emails, and refund/cancellation metadata. Full card details are handled by the payment provider, not by Human Highlight.
How data is used
- To sign you in, maintain your workspace, and sync paid workspace features.
- To generate, cache, display, publish, moderate, and recommend knowledge maps.
- To enforce quotas, paid entitlements, Power Points, BYOK access, and abuse controls.
- To provide support, troubleshoot errors, handle refunds, and respond to legal or abuse reports.
- To measure site reliability and basic product usage through analytics and error monitoring.
Important boundaries
| YouTube history | Human Highlight does not need your full YouTube watch history. The extension reads the YouTube page you actively choose to analyze, and transcript-backed video summary/Q&A requires a manual user action that can be reset from the extension Options page. |
|---|---|
| Raw transcripts | Available transcript/caption text is used to generate the video-learning output you requested. Raw transcripts are not used for advertising and are not intended to be permanently stored unless you explicitly save, export, publish, or share derived content. |
| BYOK keys | Bring-your-own Gemini API keys are stored in the browser and sent in request headers only with BYOK AI requests to the Human Highlight server proxy. They are not logged or persisted server-side as account records. |
| Google APIs and Limited Use | Human Highlight's use and transfer of information received from Google APIs follows the Chrome Web Store User Data Policy, including the Limited Use requirements. Google API data is used only to provide or improve the user-facing learning, sign-in, sync, support, security, and entitlement features described in this policy. |
| Public maps | If you publish a map, that map and its public metadata may be visible to other portal visitors. Private workspace material remains private unless you publish or share it. |
| Children | Human Highlight is not intended for children to create accounts without appropriate parent or guardian involvement. KidMap-style features are learning surfaces, not a child-directed account system. |
Choices and contact
You can contact us to request help with account access, deletion, privacy questions, or legal concerns. Some records may be retained where needed for security, abuse prevention, billing records, dispute handling, or legal compliance.
Email contact@humanhighlight.co for account/privacy requests and legal@humanhighlight.co for legal notices.