stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Purge capture-first screenshot Drafts at every private-data boundary #617

New Issue
Closed
opened 2026-08-12 03:54:11 +00:00 by timmy · 0 comments
timmy commented 2026-08-12 03:54:11 +00:00
Owner
Copy Link

Problem

Capture-first screenshots are stored in IndexedDB stackchain-unfiled-captures-v1, but sign-out/session-revocation cleanup and pre-login cleanup delete only the outbox and offline-work databases. Sensitive screenshots can therefore remain after the UI reports that private device data was cleared.

Scope

  • Include capture-first screenshot storage in authenticated and pre-login private-data purge paths.
  • Include it in the service-worker purge boundary so remote/session cleanup is complete.
  • Preserve unrelated origin storage and fail closed when deletion is blocked.

Acceptance criteria

  • Explicit sign-out, session expiry/revocation, and startup cleanup delete all Stackchain private IndexedDB databases.
  • Cleanup waits for deletion and retains existing error behavior on blocked/failing deletion.
  • Idle lock still preserves Drafts.
  • Behavioral tests prove the new database is purged and unrelated storage is untouched.

Evidence: frontend/background-issue-sync.js creates the screenshot DB while frontend/session.js, frontend/private-device-data.js, and frontend/service-worker.js omit it. Historical issue/title and recent-commit review found no existing fix.

## Problem Capture-first screenshots are stored in IndexedDB `stackchain-unfiled-captures-v1`, but sign-out/session-revocation cleanup and pre-login cleanup delete only the outbox and offline-work databases. Sensitive screenshots can therefore remain after the UI reports that private device data was cleared. ## Scope - Include capture-first screenshot storage in authenticated and pre-login private-data purge paths. - Include it in the service-worker purge boundary so remote/session cleanup is complete. - Preserve unrelated origin storage and fail closed when deletion is blocked. ## Acceptance criteria - Explicit sign-out, session expiry/revocation, and startup cleanup delete all Stackchain private IndexedDB databases. - Cleanup waits for deletion and retains existing error behavior on blocked/failing deletion. - Idle lock still preserves Drafts. - Behavioral tests prove the new database is purged and unrelated storage is untouched. Evidence: `frontend/background-issue-sync.js` creates the screenshot DB while `frontend/session.js`, `frontend/private-device-data.js`, and `frontend/service-worker.js` omit it. Historical issue/title and recent-commit review found no existing fix.
timmy self-assigned this 2026-08-12 03:54:28 +00:00
timmy closed this issue 2026-08-12 04:02:56 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#617
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?