Privacy policy
Ministry of Oversight products and account system
Last updated: 2026-04-14
Publisher: Ministry of Oversight
Base extension data
- YouTube page URLs the user actively scans
- Visible YouTube video titles, URLs, and IDs found on the current page
- Local extension library data saved in Chrome storage
- Last-scan recovery data and user-requested exports
Optional account data
- Google sign-in identity data such as email, display name, and verification state
- Free account records
- Paid account records when applicable
- Resolved module entitlement state and expiry data
- Purchase records for fixed-term modules when applicable
- Short-lived extension bridge session records used to sync access back to the extension
How data is used
- Running the Base YouTube workflow locally in the extension
- Allowing users to sign in with Google on the website
- Separating free and paid account states
- Resolving module entitlements and expiry windows
- Syncing module access from the website back to the extension
Storage model
The Base YouTube workflow remains local-first in Chrome storage. When a user signs in, Ministry of Oversight also stores account and entitlement records in the configured Firebase project so the extension can sync module access.
Paid terms
Paid access is time-based rather than open-ended. Supported launch terms are one month, three months, and twelve months. When a paid term expires, the user falls back to Base access unless a new active entitlement exists.
Current emails in use
Temporary live addresses currently in use are aeonimusai@gmail.com and aegis@aeonimus.ai. These remain active for now even though the public product branding is Ministry of Oversight.