How Pemo handles source material and account data

Pemo is designed around a desktop app. Documents, notes, and most working data live on the user's local device unless the user chooses to share, export, sync, or send content through a configured service.

This model keeps source material close to the reader and helps users review generated outputs against the original document, transcript, note, or media file.

Pemo Web Clipper may process the current tab URL, title, canonical URL, page metadata, selected text, visible page content, screenshots, image assets, video metadata, and available subtitles when the user chooses to capture or save content.

The extension does not request Chrome cookies permission. It does not collect, read, transmit, sell, or share browser authentication cookies.

The website uses account information such as email address for sign-in, account support, service notifications, billing support, and abuse prevention.

Payment processing is handled by Stripe. Pemo does not store complete credit card information.

Support requests may include device information, version information, error logs, screenshots, and details the user actively provides so the team can diagnose product issues.

Pemo can work with user-configured model, translation, transcription, text-to-speech, embedding, and rerank services. When users configure third-party providers, those providers may process the content sent to them according to the user's configuration and the provider's own policies.

For sensitive workflows, Pemo also documents local-first options such as local models and local processing paths where available in the desktop app.