This document outlines the security architecture and data handling policies for DevTime (Chrome Extension). It is strictly designed to assist Information Security (InfoSec) and IT teams in auditing and approving the tool for enterprise and corporate deployment.
Privacy Policy: Privacy Policy
DevTime operates on a strict Local-First architecture.
The extension operates within Chrome's restrictive Manifest V3 environment.
chrome.storage.local to securely isolate tracking data within the browser profile.script-src 'self'; object-src 'self';. No inline scripts or eval() functions are used.When connecting DevTime to third-party services like Google Calendar, the authorization is handled securely via Chrome's native identity APIs (OAuth2). OAuth tokens are securely stored and never exposed to the DOM.
The application uses localized console.error() calls to capture runtime failures. These logs are visible only inside the local DevTools panel and are not accessible to remote servers, third-party error tracking services, or any external party. There is no data exfiltration vector.
DevTime is designed to be deployed silently via corporate IT management tools.