1. What we collect
Browsing anonymously requires no personal data. If you create an account, Clerk provides the sign-in interface and manages your credentials, authentication sessions, and session tokens. Awesome Video does not receive or use your password for sign-in. Clerk sends us the identity details needed to connect your account, including your account identifier and, when available, your email address, name, and profile image. We store a local account record with those details, your role, and your activity on the site: bookmarks, favorites, learning-journey progress, preferences, and resource submissions. A nullable password field retained from the site's pre-Clerk authentication system may remain on legacy account records, but it is not used for authentication.
Clerk acts as our authentication service provider and processes sign-in details, credentials, sessions, and tokens on our behalf. Clerk may also process information under its own privacy terms when you use its authentication services.
2. Analytics
We use Google Analytics 4, Mixpanel, PostHog, and Amplitude to understand how the site is used, including page visits, popular resources, interactions, performance, and errors. PostHog and Amplitude may also provide session-replay features; PostHog masks page text and all form inputs in those recordings. These services only load after you accept analytics in the consent banner, and you can decline without losing site functionality.
Analytics data can include usage events, technical and device information, pseudonymous identifiers, and your account identifier when you are signed in. After consent, Mixpanel may also receive your name and email address as account profile properties. Mixpanel stores its browser identifier in local storage rather than a cookie.
3. Cookies
We keep cookies to a minimum. Preferences such as your theme and your analytics consent choice are stored in your browser's local storage (not cookies). The cookies you may see are:
| Cookie | Purpose | Lifetime |
|---|---|---|
| __session* | Clerk authentication cookie. Clerk uses it to maintain and verify your signed-in session; the name may include an instance suffix. | Managed by Clerk according to the authentication session |
| GAESA | Infrastructure cookie set by our hosting edge (Google App Engine), not by this application. It supports request routing between the edge and our servers — we do not use it to track you, it carries no analytics, and we never read it. Because it comes from the hosting platform, it appears on your first visit regardless of your analytics consent choice. It applies site-wide (path "/"). You can block or delete it in your browser settings at any time — the site keeps working; the edge may simply set a fresh one on a later visit. | About 30 days from your last visit |
| _ga*, ph_*, AMP_*, AMP_MKTG_* | Cookies used by Google Analytics, PostHog, and Amplitude for analytics identifiers and session continuity. They are only set after you accept analytics; declining keeps these services from loading. | Set and managed by the relevant analytics provider |
Clerk and any sign-in method you choose through Clerk may set additional cookies while you authenticate.
4. Sharing
We do not sell your data. Accepted resource submissions become part of the public directory and may be attributed in the upstream open-source list; your email address is never published.
5. Retention and deletion
Account data is kept while your account is active. To delete your account and personal data, sign in and use Profile → Security → Delete account & data. The request is tied to your authenticated session and handled privately by a maintainer — you never have to post your email or any personal data in a public issue. If you can no longer sign in, open an issue on the project's GitHub repository and mention only your username. Do not include your email or other personal data; the maintainer will verify ownership privately. Approved resources you submitted remain in the directory but are detached from your identity.
6. Changes
We may update this policy from time to time. Material changes will be reflected by the "Last updated" date above.
7. Contact
For privacy, legal, or abuse questions, open an issue on the project's GitHub repository. Issues are public, so do not include private or sensitive personal information.