Filter first.
Excluded apps and domains—and private title-keyword rules—are applied locally before upload.
PRIVACY & TRUST
Understand the work.
Not the contents.
Useful context starts with a clear boundary. Inspect what can be included, what stays on-device, and what is not captured.
INSPECT AN EXAMPLE FIELD
EXAMPLE DATA PATH
DeviceFilterWork record
Included metadata
Illustrative fields, not a live inspection of your computer.App name
The foreground application name can be part of the work record. It does not include what you write in that application.
{
"app_name": "Code editor",
"started_at": "09:00",
"ended_at": "09:52"
}THE DATA PATH
The strongest privacy claim is the field that never arrives.
FocusMirror’s current privacy model applies exclusions on the device, uploads a strict metadata contract, and keeps the personal product scoped to the individual user.
Metadata only.
The upload contract is designed for app names, permitted domains, time ranges, category hints, and context you explicitly provide—not titles or content.
Personal review.
The personal product is built for the person doing the work, not a manager dashboard or covert employee-observation surface.
Filter on the device.
Excluded activity is dropped before it can become an uploaded work record.
Separate consent.
Tracking permission and AI processing permission are separate decisions. Declining AI does not remove the basic record.
A personal product.
The personal record is for the person doing the work—not a covert employee-observation surface.
Read the current policy.
Storage, processors, retention, and rights belong in the published policy—not an invented badge.
THE CONVERSATIONQuestions are welcome.
Contact the dedicated security and privacy address.
See your work a little more clearly.
Start with the foundation. Explore what comes next.