Privacy Policy
Effective Date: March 13, 2026 Last Updated: March 13, 2026
This Privacy Policy describes how F7 Platform, Inc. ("F7," "we," "us," or "our") collects, uses, and discloses information in connection with the F7 AI Workforce Intelligence Platform (the "Service").
1. Who This Policy Applies To
This policy covers:
- Customer organizations that deploy F7 in their workplace
- End users (employees) whose devices run the F7 agent
- Visitors to our website and documentation
- Customer organizations and their users on Atlas, a separate F7 product; where this policy says something specific to Atlas it says so, and everything else on this page describes the F7 agent and controller
2. Information We Collect
From the F7 Agent (Deployed on Employee Devices)
The F7 agent collects work-pattern metadata only. This includes:
- Application focus data: Application name, window title category (never raw window titles for non-work apps), foreground/background transitions
- Input activity metadata: Click count, keystroke count (never individual keystrokes), scroll events, idle periods
- Network metadata: Destination domain, and for AI-provider API calls, the API endpoint path for classification (e.g.
/v1/chat/completions), and approximate request/response byte counts — never query strings, request bodies, or response content - Session structure: Session boundaries, duration, focus time, context switches
- AI interaction metadata: AI provider name, turn count, request/response sizes, time-to-first-response — never prompt or response text
From Employer-Provided Sources
Your organization may provide the following data to F7:
- Job metadata: Job title, employment type, cost center, location
- Org hierarchy: Department, division, team, manager assignment
- Employment lifecycle: Hire date, termination date, active status
- Identity: Email, display name, user principal name (for account linkage)
F7 does not independently collect this data — it is provided by your employer through configured identity, directory, or file-based syncs.
From Third-Party Event Integrations (Opt-In)
With your organization's authorization, F7 can ingest event metadata from configured controller integrations. The currently implemented sources are GitHub, GitLab, Bitbucket, Jira, Linear, Asana, Jenkins, GitHub Actions, GitLab CI, CircleCI, Google Calendar, Microsoft Outlook, LaunchDarkly, Zendesk, and Generic webhooks.
These integrations retrieve event metadata only — never document contents, message text, prompt/response text, code diffs, repository contents, calendar descriptions, support conversation bodies, or file contents. Each integration must be explicitly authorized by an organization administrator and can be disconnected at any time.
What the Agent Never Transmits
- Prompt or response text
- File contents
- Email or chat messages
- Screenshots or screen recordings (see the Mode 3 note and the Atlas Rewind subsection below)
- Clipboard contents
- Passwords or credentials
- Full URLs, query parameters, or page content
- Personal app activity (for user-excluded apps)
Mode 3 — Interpret (opt-in). When an organization enables Mode 3, the agent captures screen frames locally for an on-device vision-language model. Frames are never transmitted off the device. Current macOS builds stream capture bytes through stdout for local inference and scrub stale legacy fseven-vision-*.png temp files on startup, so organizations should still treat endpoint-local screen data as covered by device controls.
For the complete data inventory, see Data Collection Details.
From Atlas Rewind (Atlas Only, Not the F7 Agent)
Atlas is a separate F7 product from the F7 agent described above, and Rewind is a feedback recorder inside it. Nothing in this subsection describes the agent, and nothing in the agent subsections above describes Atlas. In particular, the promises above about screen frames never leaving the device are promises about the agent's Mode 3, which runs on an employee's own machine. Rewind is a different mechanism with different promises, set out here so the two are read together rather than one being mistaken for the other.
What Rewind captures. A reviewer working in Atlas can turn Rewind on. While it is on, it holds a short rolling window of picture-only snapshots of the browser tab or the screen that reviewer chooses in the browser's own share prompt, and nothing is kept unless the reviewer presses a button to keep it. No audio is recorded and no voice is recorded. The reviewer may add words describing what they saw, typed or dictated, and may draw marks on the frames. Dictated words are transcribed by the same third-party speech-to-text provider named in the Atlas privacy policy the customer accepts in the product.
Where a capture stays. A capture is held by the customer's own Atlas instance. There is one exception: the reviewer may ask an AI model to describe the frames they selected, which sends those frames and the reviewer's words to the model provider that instance is configured with. The reviewer is asked for that permission separately for each capture, and it is off unless asked for.
Sending a capture to F7 is planned and is not built. Rewind is designed so that a reviewer can submit a capture to F7 as a bug report. No customer deployment can do this today, and no code for it exists. When it is built, a submission will carry the frames the reviewer selected with their marks drawn into the image, the reviewer's words, the model's description where one was asked for, a note of where in the product the capture was taken, and an identifier for the capture and for the instance. It will leave behind the rest of the recorded window, every frame the reviewer did not select, every other capture, and everything the customer has authored in Atlas. Submitting will send that note and those identifiers whether or not frames go with it, so submission is never a purely local act. F7 has not yet set how long a submitted capture and its frames are kept; that will be stated here before submission is offered to any customer. Today a capture is readable only by the reviewer who recorded it, because Rewind runs only on F7's own internal builds and a capture becomes readable by anyone else only when someone at F7 converts it by hand into an internal bug report; that is stated as today's answer and not as a commitment about what comes next. Who at F7 may open a submitted capture is settled as part of building the submission path, and will be stated here before submission is offered to any customer.
Consent, and when Rewind appears at all. Rewind is not shown on any customer deployment today. Before it is offered on a deployment F7 hosts, that deployment has to be granted it, and it is granted only where the customer has been asked for consent and has given it — never because of a plan or a licence tier. Consent is recorded against the deployment and can be withdrawn, which turns the recorder off. Rewind is never offered on an air-gapped deployment.
From Our Website
We collect standard web analytics (page views, referrer) and information you voluntarily provide (e.g., contact forms).
3. How We Use Information
We use collected metadata to:
- Compute workforce analytics scores (AI adoption, productivity patterns)
- Power management dashboards and team-level insights
- Power individual personal dashboards (planned)
- Improve the F7 service
We do not use collected data to:
- Make automated employment decisions
- Sell to third parties
- Target advertising
- Profile individuals for purposes other than workforce analytics
4. How We Protect Information
- Encryption in transit: TLS 1.3 for all communications
- Encryption at rest: AES-256-GCM (server-side), AES-256 (agent local storage)
- Access control: Role-based access with four roles; row-level database tenant isolation
- Audit logging: Append-only audit log with 24-month retention
- Local processing: On-device AI model processes data locally before transmission
See our Security Overview for full details.
5. Data Retention
| Data Type | Default Retention |
|---|---|
| Raw telemetry | 90 days |
| Aggregated rollups | 12 months |
| Audit logs | 24 months |
Retention periods are configurable by the deploying organization. See Data Retention & Deletion.
6. Data Sharing
F7 does not sell personal information. We share data only:
- With the deploying organization: Aggregated analytics visible to authorized roles (managers see team data, not individual raw data)
- With service providers: Infrastructure providers necessary to operate the Service (see Sub-processors)
- As required by law: In response to valid legal process
7. Your Rights
Depending on your jurisdiction, you may have the right to:
- Access your personal data (via your organization's F7 administrator; personal dashboard planned)
- Delete your data (full erasure on request)
- Correct your data
- Port your data (export via administrator; self-service export planned)
- Object to processing
- Restrict processing (pause observation, exclude apps)
To exercise these rights, contact your organization's F7 administrator or reach us at privacy@fseven.ai.
8. International Data Transfers
For customers outside the United States, data processing may involve transfers to the U.S. These transfers are governed by the Data Processing Agreement, which includes Standard Contractual Clauses where applicable.
On-premise deployments keep all data within the customer's infrastructure.
9. Children's Privacy
F7 is a workplace tool and is not directed at children under 16. We do not knowingly collect information from children.
10. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify customers of material changes via email or in-product notification.
11. Contact Us
For privacy inquiries:
- Email: privacy@fseven.ai
- Mail: F7 Platform, Inc., [address to be published]
Related Documents