Effective Date: July 2026
Anti-Time Theft Logger is committed to protecting user privacy in compliance with the Personal Information Protection and Electronic Documents Act (PIPEDA) and British Columbia's Personal Information Protection Act (PIPA).
Accountability for our platform data compliance is managed directly by our appointed Privacy Officer. For any data access requests, compliance audits, or privacy inquiries, please contact:
We strictly minimize data collection to protect your privacy wrapper. Anti-Time Theft Logger collects:
github.com, not mail.google.com — subdomains are stripped along with everything else below). We explicitly strip and do not collect full URLs, private sub-paths, subdomains, or query strings to prevent session-token leakage or exposure of an employer's specific internal systems. This is captured continuously for every tab opened or navigated to during a session, not just what's open when the session starts and ends, so a page you visited and closed mid-session is still reflected in the record.On the same supported AI assistant sites listed above, and only while a session is actively running, we capture a short fragment of each prompt you submit — never the full text, and never the assistant's response:
These fragments exist for one purpose: so that if you ever review your own log, you can confirm at a glance what you were actually working on — enough to distinguish "drafting the ATTL SOW" from something unrelated, without the log becoming a searchable archive of your full conversations. This capture happens locally via a content script running on the pages listed above; the same backup and deletion rules in Sections 4 and 5 apply to it.
Adding a site yourself: the extension's settings let you add any additional domain (e.g. an AI tool not on the list above) to this same capture behaviour. Doing so triggers Chrome's own permission prompt for that specific site — nothing is added silently — and the site then follows every rule on this page exactly the same way the pre-listed ones do: capture only while a session is running, same word limits, same never-full-text rule. You can remove a site you've added at any time from the same settings screen.
Under Canadian law, you retain full ownership of your data context. You may request deletion of your historical records at any time by emailing support@oscarpoon.ca with your Backup ID. Deletion is carried out manually rather than instantly through an automated dashboard — see Section 5 below for why.
Your session log is protected by three mechanisms designed so that no one — including us — can quietly alter a past entry:
Full details: How the Log Is Tamper-Proof.
This capability is off by default. It only activates if you separately install a native helper program on your own Mac (via the native-host/install.sh script bundled with this extension) — Chrome extensions cannot see anything outside the browser on their own, and we do not install anything outside the browser automatically.
If you have installed the native helper, and only while a session is running:
git log against that one repository, scoped to your session's start/end timestamps, and record each commit's hash, timestamp, and message. We never read any other repository, and never read file contents or diffs — only commit metadata.Both features run entirely locally between the extension and the helper program on your own machine; neither is sent anywhere except as part of your own session log, under the same collection, deletion, and integrity rules described in Sections 2, 4, and 5 above.