LLCUpdated October 21, 2026
Privacy Policy
This policy explains how M2 AI, LLC ("M2 AI," "we," "us") collects, uses, and protects information when you visit m2ai.tech, sign up for our emails or free resources, contact us, or use The Why Bulb Pipeline.
- We collect your email address (and first name, if you give it) only when you ask for something from us, like the free playbook.
- We confirm your email before adding you to our list. You can unsubscribe from any email.
- We don't sell your information, and we don't use tracking or advertising cookies on this site.
- Things you type into tools on our pages, like the slop spotter or prompt fill-ins, stay in your browser.
- The Why Bulb Pipeline connects to an authorized operator's YouTube channel. Its Google and YouTube data practices are explained below.
1. What this policy covers
This policy covers the m2ai.tech website, the emails we send from it, and The Why Bulb Pipeline, our internal tool for The Why Bulb YouTube channel. Our other products have their own privacy notices, for example MeSquared, Change Order Recovery Audit, and Closeout Readiness Check. If you're a client and we've signed an agreement with you, that agreement controls how we handle your business data.
2. Information we collect
Information you give us
- Email signups and free resources. Your email address, your first name if you provide it, the time you signed up and confirmed, which form you used, and the exact consent wording you saw.
- Messages you send us. If you email us, we receive your email address and whatever you include in the message.
Information collected automatically
- Server logs. Our hosting provider records standard request data, such as IP address, browser type, the page requested, and the time. We use it to run and secure the site.
- Abuse prevention. When you submit a form, we briefly use your IP address and email address to limit repeated submissions.
- Download records. When you download a gated resource, we record the email address and the time.
- Fonts. Our pages load fonts from Google Fonts, so your browser sends Google a standard request, including your IP address.
Information that stays on your device
Some pages remember your choices in your browser's local storage, such as sections you've marked done or details you've typed into prompt templates. This data stays on your device and is not sent to us. You can clear it at any time in your browser settings.
We don't use analytics cookies, advertising cookies, or tracking pixels on this site.
3. How we use information
- To confirm your email address and send you what you asked for, such as a download link.
- To send occasional M2 AI tips and updates, if you confirmed your signup. Every one of those emails has an unsubscribe link.
- To reply when you contact us.
- To keep the site and forms secure, including blocking fake or throwaway email addresses and automated abuse.
- To meet legal obligations.
4. Email and your choices
When you request a resource, we first send a confirmation email. Only addresses that click the confirmation link join our email list. Unconfirmed signups are deleted after 30 days.
You can unsubscribe from marketing emails at any time with the link in any email, or by emailing us. After you unsubscribe, we keep a record of your address only so we don't email you again. Emails about something you just requested, like a confirmation or download link, still include a way to opt out.
5. Who we share information with
We don't sell personal information, and we don't share it for cross-context behavioral advertising. We share it only with service providers that help us run the site and send email, under their terms and only as needed to provide their service:
| Provider | What they do for us |
|---|---|
| Vercel | Hosts the website and runs the code that handles form submissions and downloads. |
| Upstash | Stores short-lived data for signups: confirmation links, rate limits, confirmed-signup records, and download records. |
| Mailgun | Delivers our confirmation, download, and tip emails. |
| MeSquared (M2 AI's own email platform) | Keeps our list of confirmed subscribers and sends occasional tips. |
| Zoho Mail | Hosts our email inbox, for messages you send us. |
| Google Fonts | Serves the fonts used on our pages. |
We may also disclose information if the law requires it, to protect our rights or the safety of others, or as part of a merger, acquisition, or sale of assets, with notice where required.
6. How long we keep information
| Information | How long |
|---|---|
| Confirmation links | Expire after 48 hours |
| Download links | Expire after 7 days |
| Unconfirmed signups | Deleted after 30 days |
| Form rate-limit counters | Up to 24 hours |
| Confirmed subscribers | Until you unsubscribe or ask us to delete your information |
| Unsubscribe records | Kept so we don't email you again |
| Download records | Up to 12 months |
| Emails you send us | As long as needed to respond and keep business records |
7. Security
We use reasonable safeguards, including encrypted connections (HTTPS), single-use and expiring links, signed download links, and limited access to our systems and accounts. No method of storing or sending information is completely secure, so we can't guarantee absolute security.
8. Your rights
Depending on where you live, you may have the right to ask what information we hold about you, to correct it, to delete it, or to get a copy. You can also opt out of marketing emails at any time. To make a request, email hello@m2ai.tech. We'll respond within the time the law requires. If we deny your request, you can appeal by replying with the subject line "Privacy appeal."
9. Children
This site is for businesses and adults. It isn't directed to children under 13, and we don't knowingly collect their personal information.
10. Where information is processed
We're based in the United States, and our service providers may process information in the United States or other countries where they operate.
11. Changes to this policy
If we change this policy, we'll post the new version here with a new effective date. If a change is significant, we'll tell subscribers by email.
12. Contact us
M2 AI, LLC2240 FM 1092 Rd, Suite 4020
Missouri City, TX 77459
hello@m2ai.tech
13. The Why Bulb Pipeline
The Why Bulb Pipeline is an internal tool operated by M2 AI, LLC for authorized management of The Why Bulb YouTube channel. It uses YouTube API Services, including the YouTube Data API. Google's handling of information is described in the Google Privacy Policy. The pipeline's Terms of Use also apply.
Data accessed and why
- Authorization. OAuth access and refresh tokens and the permissions granted by the operator. Google handles sign-in; the pipeline does not collect the operator's Google password.
- Channel and video information. The connected channel's identifier and name; video identifiers, titles, upload and processing status, visibility and scheduled publication times; caption-track information; and playlist information needed to place an upload.
- Uploads. The video, thumbnail, captions, title, description, tags, publication time, and other upload settings supplied or approved by the operator. Upload records can include a resumable-upload session address and the result returned by YouTube.
- Analytics. The current version does not retrieve or store YouTube Analytics reports and does not request Analytics permission on new sign-ins. An earlier Google grant may still list that permission until the operator revokes it. Automated performance review is planned. We will update this notice and obtain any required consent before introducing new data use.
We use Google and YouTube data only for the disclosed, authorized channel functions: uploading and scheduling videos, managing captions, thumbnails and playlists, confirming the connected channel, and checking upload results. We do not sell Google data or use it for advertising, ad targeting, or unrelated profiling.
Storage, access, and providers
The pipeline runs on an authorized operator's computer. Its OAuth client, refresh token, policy-acceptance record, and new API upload receipts are stored outside the project directory in the operator's local profile, where Windows permissions limit access to that account, system services, and administrators. Access tokens are held in process memory. Historical upload records entered manually through YouTube Studio remain in the local project and its Git history; other local computer users with access to that folder can read those records. New API receipts are excluded from Git and are not written into episode history.
Google receives authorization requests and the material sent to YouTube. The website's Vercel hosting, signup database, and email services are separate from the pipeline and do not store its OAuth tokens or upload records as part of this implementation.
The content-production workflow uses Anthropic/Claude, OpenAI/Codex, and ElevenLabs for scripts, checks, artwork, or narration. The current implementation does not send Google OAuth tokens, YouTube API responses, or retrieved analytics to those AI providers. Operator-created material used to produce a video is separate from data retrieved from Google.
Retention and operator acceptance
Saved API upload receipts expire after 28 days. Cleanup runs daily while the operator's Windows account is signed in, at sign-in, and before Google API access. If the computer is off or the account is signed out, cleanup resumes when it is available. Updating a receipt does not extend the retention of older data in it. No analytics reports are currently stored.
We keep the refresh token until the operator disconnects, requests deletion, or the pipeline detects that Google has invalidated it. Access tokens remain only in memory for their Google-issued lifetime. The local record of the operator's affirmative acceptance is kept until deletion or replacement by a newer accepted version. Manually entered historical upload records and original scripts and media remain until the operator removes them or requests deletion. A minimal record of local episode identifiers is kept after receipt cleanup to prevent accidental duplicate uploads; it contains no Google video identifiers or API responses.
Before using the pipeline, operators must explicitly accept version 2026-10-21.1 of these pipeline disclosures and the Terms of Use. The CLI blocks normal operation and Google access until acceptance is recorded for the current Windows account. An updated policy version requires new acceptance.
Revoking access and deleting pipeline data
You can revoke the pipeline's Google access through your Google Account's third-party connections. The pipeline also provides an operator disconnect command that asks Google to revoke the grant and removes the local token, acceptance record, and protected API receipts. Revoking through Google alone does not immediately erase local files; the pipeline removes cached receipts through the cleanup schedule and removes the token when a later refresh reports an invalid grant.
For privacy questions or deletion requests, email richard@m2ai.tech, monitored by Richard Machemehl for M2 AI, LLC. We verify that the request concerns your authorized channel and complete deletion within seven calendar days of receiving the request. Our deletion procedure covers the local token and API cache and a separate review of historical manual records, Git copies, and backups under our control.
Deleting pipeline data does not delete videos, captions, or other material from YouTube and does not cancel publication schedules already stored there. Use YouTube Studio or an authorized YouTube tool to manage that material.