This policy describes how MyPipCam (Chrome extension and macOS companion app) handles information. MyPipCam is created by EarnYour Marketing. The Chrome extension is available on the Chrome Web Store; source code is free and open source on GitHub.
Product site:
https://mypipcam.earnyour.com.
The source of truth for this policy also lives in the repository
PRIVACY.md.
Short version: MyPipCam is local-first. Recordings and secrets stay on your device unless you connect optional cloud features (Google Drive, OpenAI Whisper with your key, or share watch links). We do not sell your recordings or personal data. Contact: steven@earnyour.com.
1. Who this applies to
This policy covers the MyPipCam software you build or install from the repository. It does not cover third-party services you choose to use (OpenAI, Google, Apple, Chrome, etc.). Those have their own privacy policies.
2. Local-first by design
MyPipCam is designed so core recording works without an EarnYour Marketing account and without sending data to EarnYour Marketing.
What typically stays on your device
| Data | Where it lives |
|---|---|
| Video / audio recordings | Browser IndexedDB and/or a library folder you choose on disk |
| Thumbnails, edit metadata, optional local transcripts | Same local library |
| OpenAI API key (Clear removes it immediately) |
chrome.storage.local in the extension (on-device; not
synced)
|
| Recorder preferences (devices, appearance, etc.) |
Extension: chrome.storage · macOS: app preferences
(UserDefaults)
|
| Google Drive folder ID (after you connect) |
chrome.storage.sync so your Chrome profile can reuse
the same Drive folder
|
| Share management credential | Random per-install credential in trusted extension local storage; only its hash is stored by the share service. |
EarnYour Marketing does not receive your recordings, API keys, or camera/mic streams through the MyPipCam code as published in the repository.
3. Permissions we ask for
Chrome extension
- Camera / microphone — for PiP camera and recording audio when you start a capture
- Tab or screen capture — when you record a tab or use Advanced screen/window capture
- Storage / file access — to keep a local library and optionally write to a folder you pick
macOS app
- Camera — to show the floating always-on-top camera bubble (webcam, Continuity Camera, OBS Virtual Camera, etc.)
- Microphone and screen recording — the Mac recorder can capture a selected display or window into a local MP4, with optional microphone or system audio.
- Selected folders — access uses local security-scoped bookmarks. Temporary playback copies are removed on stop, deletion, window close, and the next app launch after an interrupted session.
- Automation — optionally opens the Chrome Library. The bridge URL includes the extension ID; the recording UUID stays in the URL fragment, which is not sent in the HTTP request. The app does not inspect Chrome profiles.
macOS may prompt once per signed app identity. Camera and mic access are controlled in System Settings → Privacy & Security.
4. Optional features that leave your device
Nothing below happens unless you turn it on and authenticate or paste credentials.
OpenAI transcription
If you enter an OpenAI API key in extension Settings and run
transcription, an audio-only WAV is extracted locally and sent to OpenAI’s API using
your key. Handling of that media is governed by OpenAI’s
terms and privacy policy. The key is stored locally in
chrome.storage.local. The video track and original filename are not uploaded for transcription. If extraction fails, no recording is sent.
Google Drive
If you connect Google Drive, recordings you upload go to
your Google account under an app-created
MyPipCam folder (Drive drive.file scope). Folder
IDs and related settings may sync via Chrome sync storage. Google’s
policies apply to uploaded files and OAuth tokens.
Browser and OS vendors
Chrome and Apple may process permission prompts, crash reports, or other system-level data according to their own products. That is outside MyPipCam’s control.
5. Analytics and telemetry
There is no marketing pixel or general product-usage telemetry in the extension. Optional OpenAI and Google APIs serve features you invoke.
Opening a MyPipCam watch page records a view count, timestamp, and coarse User-Agent hash. The application does not store a raw User-Agent, visitor name, email, or IP address in view records. Aggregate rate-limit counters contain share IDs or owner-key hashes, expire within two hours, and are removed on subsequent requests. Hosting providers can process network/request logs under their own policies; infrastructure logs may contain IP addresses.
6. macOS camera bubble behavior
The macOS companion is a real always-on-top window that shows your selected camera feed. It is meant to appear in desktop recordings (for example OBS screen capture). It does not upload that feed to EarnYour Marketing. What appears on your screen can be captured by any screen recorder you run—just like any other window.
7. Sharing, watch links, and view counts
When you Share from the Library, MyPipCam can create a watch page at
mypipcam.earnyour.com/w/… that embeds your Drive file
(with Drive “anyone with the link” access). People who open that page
can view the recording under Google’s access model.
Opening a watch page records a view (timestamp and a coarse browser user-agent hash — not a name or email) so your Library can show view counts and last viewed. You choose when to share and when to revoke access in Google Drive / your Google Account. Disconnecting Drive stops new uploads; existing shared files remain under your Google account until you change them there.
The share service stores recording and Drive file identifiers, a share identifier, readiness, expiry, owner credential hash, and view statistics. Public viewers receive only metadata needed to display an unexpired recording. Changing links or reading private statistics requires the local management credential. Older links remain readable until expiry but cannot be claimed by knowing their URL; sharing again from the updated extension creates a new managed link.
Clearing extension data or reinstalling loses that management credential. Create a new link and revoke unwanted old Drive access manually. Watch links expire after the selected lifetime (30 days by default). Expiry, local deletion, or editing does not revoke an existing public Google Drive file. An edit gets a new upload identity; use Share for the edited version and revoke old files in Drive if needed. The Mac app records locally; the Chrome extension handles optional Drive uploads.
8. Limited use (Chrome Web Store)
User data handled by MyPipCam (including recordings, optional auth tokens, optional API keys, and optional share view metadata) is used only to provide the extension’s single purpose: recording, local library/editing, and optional Drive upload / transcription / share links that you choose. We do not sell or transfer user data to third parties for advertising, and we do not use it to determine creditworthiness or for lending. Optional third parties you connect (Google, OpenAI) process data under their own policies for the feature you invoked.
9. Children
MyPipCam is not directed at children. Do not use it to collect personal information from children in violation of applicable law.
10. Changes
Privacy practices may change as the project evolves. Updates will be reflected in the repository and on this page. Material changes to data leaving the device should be called out clearly.
11. Contact
Privacy and support: steven@earnyour.com, mypipcam.earnyour.com, earnyour.com, or open a GitHub issue. In the Chrome extension, Library → Settings → Report a bug opens a prefilled GitHub issue (or email) with version and install info — no API keys or Drive tokens.
Security vulnerabilities: see SECURITY.md (prefer GitHub Security Advisories).