Privacy notice
Last updated: 10 September 2026
AI Media OS is a private workspace operated by Michael Parker. This notice explains how the workspace handles connected account data. For questions or a request to remove stored data, contact aimedialabservices@gmail.com.
What the workspace accesses
When you connect a mailbox, the workspace accesses its identity, folders, message headers, contents, read status and attachments to display and manage your email. Google and Microsoft access is granted through their sign-in screens. Standard IMAP and SMTP accounts use the server settings and credentials you provide.
Mail permissions support reading, searching, drafting, sending and organising messages when you use those controls. A briefing reads the selected mailboxes and generates a rundown; it does not automatically reply, mark messages as read, move them or delete them.
Storage and protection
Mailbox credentials, sign-in tokens, application secrets, cached briefing excerpts and saved briefing reports are encrypted in the workspace database. Account identities and operational records are also stored so the service can associate accounts, track delivery and measure usage. The workspace requires sign-in and uses secure session cookies.
Messages remain with your email provider. Opening or downloading an attachment retrieves it for your use. Briefing caches can contain message metadata and excerpts; cleanup removes cache entries after 35 days without an update and briefing reports after 90 days. Cleanup runs as part of briefing processing, so paused systems may retain these records until processing resumes.
Optional AI and Telegram
AI triage is off by default. If you enable it, message senders, subjects, dates and limited text excerpts, together with your briefing instructions, are sent through OpenRouter to the selected model provider to classify and summarise your email. Review the selected provider and its data practices before enabling this option. Mailbox passwords and sign-in tokens are not included in these requests.
If you link Telegram and enable delivery, Telegram receives the briefing text and destination chat identifier. The workspace stores the bot token and linked recipient information. Telegram bot conversations are cloud chats and are not end-to-end encrypted. Links to full reports still require workspace sign-in.
Service providers process data needed to supply hosting, email access and the optional features you enable. AI Media OS does not sell connected mailbox data or use it for advertising. Google account data is used for the email and briefing features you authorise, subject to the Google API Services User Data Policy, including its Limited Use requirements.
Your controls
- Disconnect a mailbox in Email settings to remove its saved account credentials and associated briefing cache. This does not delete the mailbox at its provider.
- Revoke Google access in your Google account connections, or Microsoft access at Microsoft app permissions.
- Disable AI processing or scheduled delivery in Briefings settings. Disconnecting Telegram pauses its delivery.
- Existing reports may retain excerpts until cleanup. Contact the operator to request removal of those reports or other retained workspace data. Copies already delivered to Telegram are managed separately in Telegram.
The workspace uses necessary sign-in cookies. This notice may be updated when its data handling changes; the date above identifies the current version.