Privacy policy

Who we are

Frictionlogged is operated by Drew Bredvick. This policy covers the Mac app, frictionlogged.com and our hosted report service. For privacy questions or requests, email privacy@frictionlogged.com.

Before and after you save

The Mac app keeps a rolling screen-video buffer in memory while recording is enabled. Unsaved footage is overwritten locally; we do not upload or save that buffer as a recording file. Pausing, stopping or quitting recording clears unsaved history. The current app records screen video, without microphone or system audio.

When you save a clip, the preceding 30 or 60 seconds become a recording on your Mac. The hosted workflow uploads the saved video, endpoint images, your optional note and capture metadata to make a report. Saved local files remain until you remove them. Cloud deletion does not delete your Mac’s files.

When your Mac is connected, the report shortcut uploads right away; there is no separate review step before upload. To keep a clip local, choose Save clip without a report in the Mac menu.

A recording can contain anything visible on the selected screen, including other people’s information, passwords and private work. Pause capture before sensitive activity and review saved recordings before sharing. We do not automatically redact recordings.

Information we handle

• Your account: name, email, password hash, verification and sign-in records, sessions and connected-device credentials.
• Saved reports: recordings, extracted screenshots, notes, generated and edited text, capture times, duration, technical metadata and sharing settings.
• Capture diagnostics: app/OS/device details and coarse state such as network availability or display settings, when included in the capture. The app does not capture network requests, browsing history or keystrokes as a separate log. Those things may still be visible in a saved screen video.
• Sharing: invited email addresses, invitations, permissions and revocable link credentials.
• Billing: subscription status, payment identifiers and report allowance. Stripe collects payment details directly; we do not receive your full card number.
• Operation and support: request/security records, IP and browser/device information where supplied, usage counts, processing times, model cost and correspondence you send us.

What we use it for

We use this information to sign you in, connect your Mac, generate and store reports, apply your sharing choices, deliver account/invitation emails, manage subscriptions, prevent abuse and improve reliability. We may review relevant saved content when needed to provide support, investigate a failure or abuse report, or meet a legal obligation. We do not sell personal information, use it for targeted advertising or train our own models on your recordings.

Where applicable, we process account/report information to provide the service you request, operational data for legitimate interests such as security and reliability, and billing/legal records to meet obligations. Where consent is required, we ask for it and you can withdraw it for future processing.

Cloud processing and service providers

Our providers process information needed to deliver their part of the service:

The current AI route requires zero-data-retention support and disallows prompt training. These are processing restrictions, not a promise that providers keep no billing, security or service records. Capture diagnostics can appear in your report; they are not currently included as additional model-prompt context.

AI spend reporting associates requests with an opaque internal account ID and feature/environment tags. That ID is pseudonymous, not anonymous. We do not use your email or report content as spend tags.

Providers may process information in the United States and other countries. Transfers are subject to applicable data-protection requirements and provider agreements. We may also disclose information when required by law, to protect people or the service, or in a business transfer with appropriate notice and protections.

You control sharing

Reports start private. Invited viewers sign in and verify the invited email. If you create a public link, anyone with it can view the report, full recording and key screenshots, including coding agents. Agent-readable Markdown/context uses the same access rules. Invitation emails disclose the inviter/recipient email and report link to our email provider.

You can remove a viewer, disable a public link or delete the report. This blocks new access but cannot recall downloaded files, copies, screenshots or information someone has already read.

Cookies and analytics

We use essential cookies for sign-in and session security. Unsaved web-editor drafts stay in the tab’s memory until you explicitly save. Closing the tab or reloading can lose unsaved changes.

Vercel Web Analytics measures pageviews and selected actions, such as saving a report or opening billing. It uses no analytics cookies. We remove query values and replace private report/share paths with route templates. Our event properties exclude emails, report content and account/report IDs. Browser and coarse device/location statistics may still be processed by Vercel. Server metrics measure outcomes, timing and known model cost without attaching report content.

We do not track you across unrelated websites for advertising. We do not change essential service processing in response to a browser Do Not Track signal. You can block optional analytics with browser controls without losing report access.

Retention and deletion

Saved reports remain available until you delete them or we close the account/service under our terms. There is no automatic trial-report expiry. We do not promise permanent hosting; export important material.

Deleting a report immediately removes it from normal access and removes its content from the active report record. We then attempt to remove its stored media; failed cleanup can require another attempt. Limited tombstones, usage/security/billing records and provider backups may remain for security, legal, financial or recovery purposes. Deletion does not erase recipient copies, local files or all provider records instantly.

For account closure or access, correction, export or deletion requests, email privacy@frictionlogged.com from your account address. We verify requests before acting. Account closure is currently handled by support, rather than an automatic delete-account button. Cancel subscription renewal in Your plan separately; deleting a report does not cancel billing.

Your choices and rights

You can stop local capture, edit or delete a report, download its recording, change sharing and cancel renewal. Depending on your location, you may also have rights to access, correct, delete or receive a copy of personal data, object to or restrict processing, withdraw consent, appeal a request decision or complain to a data-protection authority. Contact us to exercise applicable rights; we will not penalize you for doing so.

If someone else recorded or shared your information, contact the report owner or us with enough detail to identify the issue. Please do not send more sensitive information than necessary.

Age, security and policy changes

Frictionlogged is intended for adults and is not directed to children. Do not create an account if you are under 18. Contact us if you believe a child has supplied personal information.

We use access controls, authenticated private-media delivery and transport encryption. No system can guarantee absolute security. We publish policy changes here with an updated effective date and provide notice of material changes where required. Privacy questions: privacy@frictionlogged.com.