TrailframeYour workflow stays on this computer.
Privacy notice · 19 October 2026 · version 2.1.2 preview
Trailframe is a local workflow recorder developed for AK Operations. Start explicitly selects one HTTP(S) tab. Stop ends capture and detaches Chrome's debugger. Paused intervals are excluded and recorded as gaps. There is no recording server, account, telemetry, analytics, advertising or automatic upload.
What workflow mode captures
- Clicks, field changes, focus, submissions, selected navigation keys, scrolling, double clicks, context menus, drag/drop and clipboard action metadata. Clipboard contents and file contents are never read. File selection includes names, types and sizes.
- Non-private typed values, previous values when available, selectors, checkbox/select state and timestamps. No raw password or character-by-character keystroke logging.
- Structured visible page states: up to 700 elements per checkpoint, with text, labels, field state, viewport and frame context. These are not full HTML snapshots or hidden application state. Per-element text and value limits apply.
- Viewport screenshots at changed page checkpoints, at most once every 30 seconds by default, with 1.5, 5 or 90 seconds available, and up to 500 per workflow including a reserved final checkpoint. Images are resized to at most 1600 pixels wide and encoded as JPEG. Recognised private fields and iframe areas are masked before storage. A manual screenshot button is also available. Masking is best effort; other sensitive text and business data can remain.
- Observed request/response metadata, redirects, failures, timings, cache flags, initiator context and redacted readable JSON, plain text, CSV, form or GraphQL bodies up to 512 KiB each. WebSocket text and server-sent events are included when readable body capture is enabled. Binary messages retain metadata only.
- Navigation, console messages (object contents omitted), exceptions, notes, goals, outcomes and browser/language information. Attachment responses include download metadata, without downloaded file contents or completion verification.
Workflow mode enables values, readable bodies, page states and automatic screenshots by default. Each option is visible and can be switched off. Diagnostics mode switches all four off. Captured business data may remain sensitive even when credentials are removed.
Information present in a recorded workflow
Depending on the chosen page and enabled capture options, locally processed evidence can include personally identifiable information, health information, financial or payment information, personal communications, location information, visited URLs within the recorded tab, user activity and website content. For example, a page may display a customer name, a conversation, an address or an invoice. These categories describe content that may be present in your workflow; Trailframe does not request separate access to your contacts, medical records, payment accounts, messages, location sensor or browsing history database.
This information is processed only to record, review and export the workflow you start. Trailframe does not sell it, use it for advertising, determine creditworthiness or send it to a developer-operated service. Recognised private fields and credentials are excluded or redacted, but sensitive information can remain in other page content. Choose appropriate capture options and review the evidence before sharing it.
Redaction and boundaries
Password, payment and recognised private fields are excluded. Query
values, URL credentials, fragments, likely path tokens and unrecognised
headers are redacted. JSON and form keys matching recognised secrets or
personal fields are redacted. Text filters remove recognised emails,
bearer tokens and common secret patterns. Mark private page regions with
data-trailframe-private; the legacy
data-ak-trace-private and data-private markers
also work. Redaction cannot guarantee anonymisation. Review every file
and screenshot before sharing.
Other tabs, new windows, popup workflows, standalone service workers, closed shadow roots, canvas internals, audio, video and server-side work are excluded. Child frame and dedicated-worker observation is best effort. XML, HTML, scripts and binary/media response bodies are excluded. Oversized, unavailable or evicted payloads have explicit states in the coverage report. Before/after page phases refer to recorder events; asynchronous application completion is not guaranteed. Request/action links are temporal associations, not proof of causation.
Storage and deletion
Evidence is stored in this Chrome profile's IndexedDB. New substantial records use lossless gzip compression; older uncompressed recordings remain readable. Checkpoints are saved approximately every second; an abrupt termination may lose recent events. Recordings rotate into numbered storage parts around 2 MiB of active uncompressed evidence or per-part counter limits, retaining pending requests until completion. All parts are included in the workflow ZIP. Stop drains pending traffic briefly; unfinished requests remain marked incomplete.
Maximums: twelve hours, approximately 256 MiB stored evidence per workflow, 4096 storage parts, 500 screenshots, 512 KiB per readable body, 32 MiB of bodies per active part, and 200 notes per part. Parts rotate at 5,000 actions/requests/stream entries, 2,000 console entries or 1,000 page states. New capture is refused at 100 sessions or 400 MiB local library usage; ongoing capture stops if the storage limit is observed or local saving fails. Browser quotas can be lower. Chrome must remain open and awake; no particular duration or file size is guaranteed for every website. Use a continuation recording for longer work.
Unpinned completed sessions expire after 30 days while the extension runs. Pin them to retain them. Deletion removes the workflow and its parts. Uninstalling removes the local library. Exported downloads remain until you delete them separately. Existing AK Trace recordings are retained when updating the same unpacked installation. Keep version 2.1 or later to read new compressed local records; export before an unpacked downgrade. Reinstalling in a different folder can create a different extension ID and library.
Permissions
- debugger: observe the selected tab's Network, Runtime and Page diagnostics, isolated DOM recorder and screenshots. Chrome shows a debugging banner. Closing it interrupts capture.
- activeTab: identify the current website when the toolbar is used.
- storage: keep the active checkpoint identifier locally.
- alarms: enforce duration and retention limits.
No all-sites host permission, remote code, request interception, automatic replay or application writes are used.
AI handover and sharing
Export downloads one local ZIP with lossless text compression, a manifest, chronological timeline, coverage report, numbered parts, network evidence, page states and images. Compact diagnostic exports are also available. You choose whether to send it to another service. The package is reference material: uploading it does not automatically fine-tune an AI or give it permanent memory. The receiving service controls training, access and retention. For help, visit the Trailframe support page.