MadMic Privacy Policy

Account & profile. Name, email, role, and workspace assignment when you sign up or are invited by a workspace admin.

Content. Video files you upload, captions, transcripts generated from those videos, and the metadata you provide (titles, schedules, tags).

Face data (people tagging). If you add people to your workspace and upload their reference photos, MadMic can run automated face detection on the footage you upload to suggest which of your saved people appear in a clip, so the right hosts, guests, and editors get credited. This runs only on your own uploaded content, is used solely to power people tagging inside your workspace, is never used to identify the general public, and is never sold. You can skip it entirely by not adding people or reference photos, and any face data is deleted together with the associated content (see Data Retention).

Connected platforms. When you connect YouTube, Instagram, Facebook, Threads, TikTok, X, LinkedIn, Bluesky, Libsyn, Buzzsprout, or other supported services, we store OAuth tokens and the minimal account identifiers required to publish on your behalf (e.g. channel ID, page ID, open_id). Tokens are encrypted at rest with AES-256-GCM. The specific permissions we request are limited to publishing and analytics — for example: YouTube (youtube.upload, youtube.readonly, yt-analytics-monetary.readonly); Instagram & Facebook (pages_show_list, pages_manage_posts, pages_read_engagement, instagram_basic, instagram_content_publish, instagram_manage_insights, publish_video); Threads (threads_basic, threads_content_publish, threads_manage_insights); TikTok (user.info.basic, user.info.profile, video.upload, video.publish); X (tweet.read, tweet.write, users.read, media.write, offline.access); LinkedIn (openid, profile, email, w_member_social).

Engagement & analytics metrics. To power the Reach leaderboard and your workspace analytics, we periodically pull post-level and account-level metrics from the platforms you connect. Depending on the platform and the scopes you grant, this may include public engagement counts (views, likes, comments, shares, follower counts) and, where authorized, private analytics such as estimated watch time and estimated revenue (for example, via the YouTube Analytics API). We store periodic snapshots of these metrics, not raw viewer-level or audience-identifying data, and we use them solely to display analytics within your workspace.

Usage data. Standard server logs (IP, user agent, timestamp) and product telemetry needed to operate and improve the Service.

Cookies. We use strictly necessary cookies to keep you signed in and to secure your session. We do not use third-party advertising or cross-site tracking cookies.

We use the information above to: (a) provide and operate the Service; (b) authenticate you and protect your account; (c) publish content to platforms you connect, only when you initiate it; (d) compute analytics and leaderboards within your workspace; (e) communicate service notices and account updates; (f) detect, prevent, and respond to abuse, fraud, and security issues.

We do not sell your personal information. We share data only as follows:

Connected platforms. When you publish a post, the content + caption you authored is sent to that platform’s API. Each platform’s privacy policy then applies.

Service providers. Infrastructure providers (Supabase, Vercel, and AWS — including S3 storage and, where you enable people tagging, AWS Rekognition for on-clip face detection) and tools (Deepgram for transcription, Anthropic for content generation, Remotion for video rendering) that process data on our behalf under contractual confidentiality.

Legal. When required by law, court order, or to protect rights, safety, or security.

MadMic’s use and transfer of information received from connected platforms adheres to each platform’s developer policies, including use-limitation requirements. In particular, our use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We only request the minimum scopes needed to publish content you approve and to display the analytics you ask us to show; we do not use platform data for advertising, we do not sell it, and we do not transfer it except to the sub-processors named above to operate the Service on your behalf. Your use of connected platforms remains subject to those platforms’ own terms, including the YouTube Terms of Service and the Google Privacy Policy.

Your data is scoped to the workspace it was created in. Other workspace members may see your uploads, edits, and tagged role attributions as part of normal team collaboration. Across workspaces, data is isolated by row-level security and explicit workspace_id filters. Super admins of the platform may have read access to operate the Service.

We retain content + metadata for as long as your workspace is active. Engagement metric snapshots are pruned after 60 days. When a workspace or account is deleted, we remove its data within 30 days, except where retention is required by law.

Depending on your jurisdiction, you may have rights to access, correct, export, or delete your personal information. Email privacy@madmic.io to make a request and we will respond within 30 days.

How to delete your data. You can delete your data at any time: disconnect any platform from Admin → Integrations (which immediately removes that platform’s stored tokens), or delete your workspace or account from Admin → Settings to remove your content and associated data. You can also email privacy@madmic.io with the subject “Delete my data” and we will permanently delete your account and associated data within 30 days. This section (madmic.io/privacy#data-deletion) is our data-deletion instructions page.

For users in the EEA/UK, our legal bases for processing are performance of our contract with you, your consent (which you can withdraw at any time by disconnecting a platform or deleting your account), and our legitimate interests in operating and securing the Service. We do not sell or “share” personal information as those terms are defined under the CCPA/CPRA; California residents may still submit access or deletion requests at privacy@madmic.io.

You can revoke any connected platform at any time from Admin → Integrations. When you disconnect, we immediately delete the stored OAuth access and refresh tokens for that platform. Metric snapshots we previously pulled from that platform are deleted within 30 days of disconnection (account-level snapshots are pruned on our standard 60-day cycle). Disconnecting does not remove posts already published to the platform; you must remove those from the platform directly. You may also revoke MadMic’s access from within the platform’s own app/connection settings at any time.

We use TLS in transit, encrypted storage for OAuth tokens (AES-256-GCM), and role-based access controls. No system is perfectly secure; we will notify affected users of any breach affecting their data within the timelines required by law.

The Service is hosted in the United States. If you use the Service from outside the U.S., your information will be transferred to and processed in the U.S. under the standards described in this policy.

The Service is not intended for individuals under 18 and we do not knowingly collect information from children.

We may update this policy from time to time. Material changes will be announced in-product or by email; the “Last updated” date above always reflects the current version.

Questions or requests? Email privacy@madmic.io or admin@8482media.com.

8482 LLC
2700 Higgins Canyon Road
Half Moon Bay, CA 94019, USA