Privacy Policy

Our approach

7Frames is a screen-recording and screenshot tool with an optional cloud service for sharing and collaboration. Capture happens on your device by default; uploading to the cloud is opt-in per capture.

We aim to collect only what we need to provide the service, and we do not sell your personal data or use advertising trackers.

The browser extension (local-first capture)

The 7Frames browser extension captures screenshots and screen recordings on your device. Capture only ever happens on an explicit action you take — starting a screenshot, recording, or bug report — nothing is captured passively or in the background.

Your screenshots and recordings are stored locally in the browser (IndexedDB) and stay on your device unless you choose to export them or upload them to the cloud. Uploading is opt-in, per capture.

• chevron_rightMicrophone and webcam: used only if you turn them on for a recording, and only while that recording is running. They become part of the recording you produce; the extension does not access them at any other time.
• chevron_rightScreen and tab capture: the extension records the screen, window, or tab you pick through your browser’s own capture picker. It has no passive access to your other tabs or browsing.
• chevron_rightDeveloper Bug Report (optional): every advanced section is off by default. When you turn them on, a report can include console logs, network logs / HAR (metadata and redacted headers only by default — response bodies are never captured unless you explicitly enable them), a local/session-storage snapshot, and a user-action timeline. The optional “Advanced Dev Logs” mode uses Chrome’s debugger interface, which the extension requests only at that moment, attaches only to the tab you are reporting, and detaches as soon as the capture ends.
• chevron_rightOn-device transcription and captions: if you generate captions in the extension, a small speech-to-text model file is downloaded once from a third-party CDN (Hugging Face). Your audio is transcribed locally in the browser and is never uploaded for this — only the model itself is fetched.
• chevron_rightAutomatic redaction: before anything is exported or pushed, a redaction engine removes tokens, JWTs, API keys, cookies, authorization headers, card numbers, and secret-named fields, and partially masks emails and phone numbers. It runs by default and can only be turned off by an explicit choice in the review step.
• chevron_rightWhere extension data goes: a bug report is sent only to the destination you selected and connected (Jira, GitHub, Linear, Slack, Confluence, or Notion). Connected-provider tokens are stored locally in the extension, masked in the UI, removable by disconnecting, and never written into a report or log. The extension itself runs no analytics, telemetry, or remotely-hosted code.

Information we collect

• chevron_rightAccount information: your email address, name, and authentication details (passwords are stored only as secure hashes).
• chevron_rightContent you create or upload: recordings, screenshots, titles, descriptions, and related metadata, plus any transcripts, AI-generated chapters or summaries, comments, and reactions tied to them.
• chevron_rightSharing and viewer analytics: when you share a recording, we record basic, de-identified engagement (qualified view counts and watch progress) for you as the owner. Viewer IP address and browser user-agent are stored only as salted, non-reversible hashes, never in raw form.
• chevron_rightBilling information: if you subscribe, our payment processor (Stripe) handles your card details; we receive subscription status and billing contact information, never full card numbers.
• chevron_rightSupport and request information: details you provide when you contact us (for example through our Trust Center or a support request).

Cookies and browser storage

7Frames uses essential browser storage to sign you in, keep your session secure, and remember preferences such as your light/dark theme and playback quality. We do not use advertising or cross-site marketing cookies, and we do not load third-party analytics or tracking scripts (such as Google Analytics, Mixpanel, or session-replay tools) on our pages.

How we use your information

• chevron_rightTo provide, maintain, and improve the service.
• chevron_rightTo process recordings you upload and, when you choose to use AI features, to generate transcripts, chapters, summaries, and guides.
• chevron_rightTo enable sharing, comments, reactions, and owner-facing viewer analytics.
• chevron_rightTo send account, security, and product notifications, and to respond to your requests.
• chevron_rightTo process payments and manage subscriptions.
• chevron_rightTo keep the service secure and reliable, including rate-limiting and error monitoring.

Sub-processors and sharing

We use a small set of third-party service providers (sub-processors) to deliver 7Frames - for example object storage, payment processing, optional AI processing, and email delivery. Several are optional and only apply when the related feature is enabled. The current list, with each provider’s purpose and the data involved, is published on our Trust Center.

We do not sell your personal data, and we do not share it with third parties for their own marketing.

Third-party workspace integrations

With your explicit permission, you can connect 7Frames to Slack, Jira, Confluence, Linear, or Notion so you can push a generated document (for example a bug report or guide) into your own workspace. You authorize each connection through that provider’s own OAuth sign-in screen; we never see or store your provider password.

• chevron_rightWhat we read: only what’s needed to confirm the connection and let you pick a destination — your account identity, and the names of your Slack channels, Jira projects, Confluence spaces, or Notion databases the integration can see. We do not read the existing content of your messages, issues, pages, or docs.
• chevron_rightWhat we write: only when you choose to push a document, we create a new Slack message, Jira issue, Confluence page, Linear issue, or Notion page from content generated in 7Frames, plus any files you attach. This is one-way — we do not fetch or store the resulting content afterward, only a link back to it.
• chevron_rightCredential storage: your OAuth access token (and refresh token, where the provider issues one) is encrypted at rest with AES-256-GCM using a server-only key, and is never returned to your browser or written to a log.
• chevron_rightDisconnecting: disconnecting an integration, from your workspace or personal settings, immediately and permanently deletes the stored credential. We keep no copy.

AI processing

AI features (chapters, summaries, transcripts, and guide generation) run only on content you choose to process. Depending on your configuration, this may involve an AI sub-processor listed on our Trust Center. Transcription can be self-hosted, in which case audio is processed on our own infrastructure.

Data retention and deletion

We retain your content and account data for as long as your account is active or as needed to provide the service. You can delete individual recordings at any time, and you can permanently delete your account and associated recordings from the in-app Privacy Center.

You can download a self-serve, portable JSON copy of your data at any time from the in-app Privacy Center. It includes your account profile, recordings and their transcripts, chapters and summaries, share links, comments, saved items, workspaces, and notification settings; your media files stay in your library and secrets are never included.

Deleting a recording moves it to Trash and, after a 30-day recovery window, permanently removes the original media together with its derived files (processed video, thumbnails, captions, transcripts, AI summaries, chapters, and translations) from object storage, and revokes its share links. Temporary artifacts from failed uploads or renders are cleaned up in the background.

Your rights

Depending on your location, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. You can export your data and delete your account directly in the app, and you can make other requests through our Trust Center contact options. We will respond consistent with applicable law.

International transfers

Some of our sub-processors are based in the United States, so your information may be processed there. Where required, we rely on appropriate safeguards for such transfers. See the Trust Center for the providers involved.

Security

We use measures appropriate to the service, including hashed passwords, optional two-factor authentication, private media storage served via short-lived signed links, encryption of connected third-party integration tokens, and rate-limiting on sensitive endpoints. No method of transmission or storage is perfectly secure, but we work to protect your information and review our practices over time.

Uploaded media - recordings, screenshots, thumbnails, and derived files - is stored in a private, S3-compatible object store (Cloudflare R2) and encrypted at rest with AES-256 using provider-managed keys. Customer-managed encryption keys are not currently supported. Traffic is protected in transit with TLS. See the Trust Center for the encryption and sub-processor details.

Children

7Frames is intended for use by adults and is not directed to children. We do not knowingly collect personal data from children.

Changes to this policy

We may update this policy from time to time. When we make material changes, we will update the date above and, where appropriate, notify you.

Contact us

For privacy questions or to exercise your rights, contact us through the 7Frames Trust Center, where our current privacy and security contacts are listed.