Currently available for Google Chrome.
Overview
- How the extension works at a high level
- What data it collects and what it doesn’t
- What permissions it requires and why
- How the June Device Agent complements it
How It Works
Device Registration
Identifies the user by their browser profile email. If the June Device Agent is deployed via MDM, it also retrieves the device serial number for hardware-level identification.
Configuration
Tracked applications and domain configuration is pulled from June every 6 hours.
Usage Tracking
Measures how long each configured application has active browser focus. Only tracks domains your organization has explicitly configured.
Reporting
Usage data is stored locally throughout the day and only sent to June once the day is complete. Data older than 30 days is automatically discarded.
What It Tracks
| Data | Description |
|---|---|
| Application | Which configured SaaS app was in focus |
| Duration | Time spent actively using the app per day |
| Date | The calendar day the usage occurred |
| Timezone | The user’s local timezone |
The extension only tracks domains explicitly configured by your organization. It does not track browsing history, page content, keystrokes, or any activity on non-configured domains.
Permissions
The extension requests the following permissions, each for a specific purpose:Storage
Storage
Stores usage data locally on the device so nothing is lost if the device goes offline.
Alarms
Alarms
Keeps the extension running on schedule for configuration refresh and usage reporting.
Tabs
Tabs
Detects which tab is in focus to measure active time on configured apps.
Native Messaging
Native Messaging
Communicates with the June Device Agent (if deployed) to retrieve the device serial number.
Idle Detection
Idle Detection
Pauses tracking when the device is idle so only active usage is reported.
User Email
User Email
Reads the browser profile email to associate usage data with an employee.
All URLs
All URLs
Checks if the current page matches a configured app. No page content is read or collected.
June Device Agent
The June Device Agent is a lightweight native application that provides the device serial number to the browser extension. Deploy it via MDM alongside the extension. The agent runs locally only and makes no network requests. It reads the device serial number and passes it to the extension for hardware-level identification.Frequently Asked Questions
Does the extension track browsing history?
Does the extension track browsing history?
No. The extension only measures how long configured applications are in focus. It does not record URLs, page content, keystrokes, or any activity on domains that haven’t been configured.
What happens when a device is offline?
What happens when a device is offline?
Usage data is stored locally on the device. Once connectivity returns, the extension sends the accumulated data on its next reporting cycle. Data older than 30 days is automatically discarded.
How often does it send data?
How often does it send data?
Usage data is reported periodically throughout the day. Only completed days are sent. The current day’s data stays on-device until the following day.
What applications are tracked?
What applications are tracked?
Only the domains explicitly configured in the June dashboard are monitored. No other domains are tracked.
Does it affect browser performance?
Does it affect browser performance?
No. The extension performs a lightweight domain check against the configured app list. No page content is scanned or modified.
Getting Started
Deploy the Browser Extension
Follow the step-by-step deployment guide in the June dashboard to roll out the extension to your organization.