Security and privacy
Captured company content stays under the user's control.
Bundlepix is designed to perform its core capture, review, redaction, optional OCR, recording, and export work on the Windows PC—not in a Bundlepix cloud service.
- No Bundlepix cloud upload
- No product telemetry
- No desktop account required
Local-first processing
Core evidence work runs on the local machine.
Screen, window, region, and supported scrolling capture; image stitching; annotation; permanent blackout; optional OCR; recording; and export are designed to run locally. Bundlepix does not upload captures, exports, OCR results, recordings, or product-usage telemetry to a Bundlepix-operated service.
Users choose where exported files are saved and how they are shared. A user-selected folder, company sync tool, backup product, clipboard manager, or destination application remains outside Bundlepix’s control.
Evidence integrity
A partial capture should be identified—not silently presented as complete.
Scrolling content can vary by browser, page, and desktop application. Bundlepix is designed to require review when it cannot verify a complete result and to identify a result as partial instead of automatically exporting it as complete evidence.
Important captures should always be reviewed before they are used for a decision, test result, support escalation, or external handover.
Redaction lifecycle
Permanent blackout changes the current saved evidence after replacement succeeds.
Blackout is applied to captured pixels before optional local OCR and export. A replacement becomes the current evidence only after the updated DOCX, PDF, or XLSX artifact is saved successfully; a failed or cancelled replacement leaves the prior artifact in place.
Redaction cannot retroactively erase copies made earlier, version history, backups, cloud-sync history, application caches, swap or process memory, or content retained by third-party clipboard tools. Teams should control those systems separately.
Optional local tools
OCR and media features have explicit third-party boundaries.
Tesseract OCR
Optional OCR requires a separately installed Tesseract executable. Bundlepix passes an in-memory image to that local process; Tesseract still uses ordinary process memory while it runs.
Browser full-page capture
An optional localhost browser-control path can direct Chromium to a target URL. The browser may make the normal network requests needed to load that page; this is distinct from Bundlepix telemetry.
Recording conversion
Compatible recording and GIF operations can depend on local media tooling. Recording remains separate from the screenshot-to-document workflow.
Safe use
Review content and destination controls before sharing.
- Capture only content your team is authorised to retain
- Black out confidential values before OCR or export
- Review every output for completeness and remaining sensitive data
- Store finished files in an approved company location
- Keep the ticket, test case, or document system as the source of record
- Report security concerns privately through your supplied support channel
Workplace preview
Check whether Bundlepix fits your workflow.
Describe what your team captures, documents, trains, or hands over today. Bundlepix will confirm the relevant preview path and current product limitations.