Updated 19 October 2026. Documentation for PunchScope — Timesheet CSV Review 0.3.5 preview. Installed Chrome validation and publication remain pending.
Publisher display name: AK Frames.
Data you choose to open
PunchScope reads one selected timesheet CSV to explain exceptions and record your review without changing the original file or time system. It processes the complete CSV text, file name, file fingerprint, headers and every original cell, including extra or unmapped columns. Staff identifiers, optional names or email grouping values, timestamps and other supplied content can appear in the open page, optional save and requested outputs.
Provide only the fields needed for this review. Remove unrelated pay, health, address, message and secret information before opening a file; the extension does not automatically scrub it. Keep passwords and access tokens out of files and notes.
The workspace also holds your business reference, column choices, date format, source timezone, review thresholds, derived times and flags, dispositions, notes and decision times. In shared-date/local-clock mode, this includes the recorded timezone context basis, confirmed date/marker semantics and separately derived calendar dates/day offsets; original cells stay intact. Keep the context reference brief and avoid private staff details. An optional reviewer reference is saved, restored and included in audit/history JSON. It is not a verified identity or signature, and is not added as a dedicated reviewer column in row CSVs.
Flags and human review records do not determine wages, payable time, misconduct or payroll approval. There is no clocking, payment integration or source-system write.
Optional encrypted saving
Opening a file does not save it. Current work stays in the page; closing or reloading loses unsaved work. Save locally… → Encrypt and save deliberately keeps one workspace in this browser profile, including the source, settings, business, reviewer, current decisions, notes and times. There is no autosave, startup restore, sync or localhost saving fallback. Save again after later changes.
Enter and confirm a long, unique passphrase of at least 12 characters. Exact characters, spaces and letter case matter; password-manager paste is allowed. Native browser cryptography encrypts the saved copy with AES-256-GCM and a PBKDF2-SHA-256 key derived with 600,000 iterations, using a fresh random salt and IV. The extension does not store, transmit or insert the phrase/key into exports. Phrase fields are cleared after submission or leaving the dialog.
The encrypted saved copy has an 8 MiB limit including overhead. The existing saved value these controls will read has a separate 10 MiB bound, including compatible older plaintext copies. These are not input-file limits or guaranteed available Chrome quota. Large source files plus notes may fit a review but not a save. A failed save preserves the previous copy without dropping evidence to fit.
Opening older saves and history
Older plaintext saves open only through an explicit choice and remain plaintext until successfully replaced with an encrypted save or deleted. Existing downloads and backups are not retroactively encrypted.
Restore rechecks the source, business, settings, engine and derived results before offering a final replacement choice. A matching valid workspace-v2, including an older plaintext-v2, may retain bound decisions and reviewer. Each v2 decision must have its own valid saved timestamp with an explicit offset; missing times are rejected, not invented. A valid schema-v1 save or valid changed engine/interpretation/results offers a fresh unreviewed copy or history instead. Fresh opening discards historical row decisions but can retain valid reviewer metadata.
Failed, cancelled or declined restore keeps current work. Successful matching or fresh replacement clears the row Undo stack and is not an undoable workspace transaction. Opening does not update the saved copy until you deliberately save again.
Export saved history preserves the original captured historical model as readable JSON without a current Temporal re-audit. Historical decisions are unverified evidence, not current approval. Encrypted history still requires the phrase and a supported authenticated wrapper. History export does not replace the open review.
Readable files, recovery and deletion
Reviewed/unresolved CSV, current audit JSON and saved-history JSON are readable staff-data files. They may contain original cells, file details, decisions, notes and times; audit/history can contain the reviewer. Formula neutralization and fingerprints are not confidentiality. Protect downloads and any copies you share or back up.
Encryption covers the optional saved browser copy, not the open page, original files, older plaintext or downloaded outputs. There is no developer recovery key or forgotten-phrase recovery. Downloaded audit/history files cannot be imported to restore the workspace or unlock its encrypted copy. Their readable information remains available for inspection; re-importing the CSV starts a fresh review.
The page keeps up to the last 100 row-decision Undo entries. Save/current audit contain current decisions, not a complete edit history. Start again… clears current work, reviewer and Undo, leaving the save separate. Privacy & saved data → Delete saved workspace… deletes that copy without its phrase and cannot be undone. It leaves current work, originals, downloads and outside backups alone. Removing the extension normally removes its local extension storage.
Connections and limited use
The extension requests only storage for the deliberate browser save. It does not upload staff files, provide developer background access, read websites/history, use analytics or interaction telemetry, or connect to payroll, accounts or billing.
AK Frames limits PunchScope's use of imported data, review information and the unlock phrase to the disclosed review, optional local save/open and export features. The extension does not sell user data, use it for advertising or brokering, or use it for credit or lending decisions.
PunchScope's use and transfer of user data comply with the Chrome Web Store User Data Policy's Limited Use requirements.
Contact and separate website handling
For product or privacy questions, contact AK Frames at akframesltd@gmail.com. Email is voluntary and separate: your sender details, message and attachments go to AK Frames and the email providers handling delivery/storage. The extension sends no automatic support bundle.
Send only a small fictional reproduction and the minimum useful details. Never send your phrase, credentials, real staff records or full audit. Local clearing/deletion does not remove sent email or downloads. The existing Website and support privacy notice describes the separate documentation-host and email handling; local file-processing promises do not mean the website or email provider receives no request information.
Looking for another detail?