Privacy Policy & Transparency

KeepActive Privacy & Terms

Data retention, permissions, optional native-helper disclosure, and security boundaries

1. Zero-Telemetry Architecture

KeepActive is engineered as a strictly local, privacy-first utility:

  • Zero Remote Communication: The extension makes no requests to analytics endpoints, tracking beacons, advertising networks, font CDNs, or third-party servers. All interface fonts are system fonts.
  • No Account Required: There are no sign-ins, credentials, tracking cookies, or registration profiles.
  • Local Browser Storage: Preferences (work schedules, activity intervals, toggle states) and diagnostics are stored only in chrome.storage.local inside your browser profile.
  • Teams Traffic Is Yours: KeepActive does not proxy, inspect, or upload Teams content. Your browser continues to communicate with Microsoft Teams as part of normal Teams usage.

2. Permissions Justification

KeepActive requests only the APIs needed to operate:

  • power: Requests display keep-awake while Chrome is running. Operating-system or enterprise policy can still lock the device.
  • idle: Reads the operating-system idle state so Smart Pause can stop activity while you are at the keyboard and resume after your configured away period.
  • alarms: Schedules shift transitions, Smart Pause resume checks, session limits, and helper intervals without a background busy-loop.
  • storage: Persists configuration, session totals, and local diagnostics.
  • host_permissions: Restricts the content script to official Microsoft Teams web origins (https://teams.microsoft.com/* and https://teams.cloud.microsoft/*).
  • nativeMessaging (full build only): Lets the separately distributed full build talk to a local helper. This permission is not present in the Chrome Web Store package, and the store package contains no native installer or helper code.

3. Optional Native Desktop Helper (Full Build Only)

The Chrome Web Store package has no native component and cannot control desktop applications. A separate, locally distributed full build can optionally use a helper for Microsoft Teams Desktop. When that build is used, the helper:

  • Runs only on your computer and makes no network connections.
  • Receives a trigger from the extension, checks the OS idle timer, nudges the real pointer by 2-3 pixels, restores it, and optionally sends a harmless Shift key pulse.
  • Refuses to act while you are actively using the keyboard or mouse. It never clicks, types text, or reads screen content.
  • Is disabled when you turn off the helper toggle, and can be removed at any time with the full build's uninstall command.

On macOS, the helper requires the Accessibility permission. Microsoft controls Teams Desktop presence; KeepActive does not guarantee a particular presence state.

4. Operating Caveats & Responsible Use

Notice of Intended Use

KeepActive is designed for legitimate passive tasks such as presentations, monitoring dashboards, data rendering, and long-running jobs. Workplace policies vary; verify that automated activity complies with your organization's acceptable use policy and Microsoft's terms.

KeepActive does not circumvent, disable, or alter endpoint detection and response (EDR) agents, device management policy, or enterprise monitoring software. It does not guarantee that Teams will report you as available.

5. Contact

Questions about this policy or KeepActive's data handling: filmfrenzy777@gmail.com.

If this policy changes, the updated version and its effective date will be published at this address before the change ships.