Security & data handling

PBJ Preflight is deliberately narrow. It is designed to work with the minimum staffing data needed to prepare and reconcile a PBJ file.

Your uploaded files stay in your browser during preflight. Payroll and staffing file contents are parsed locally in your browser. ChaseDesk does not upload those file contents to ChaseDesk servers as part of the preflight workflow. Before Stripe checkout, ChaseDesk creates a temporary encrypted checkpoint in this browser so the filing can be restored when you return.

What you should upload

Only the fields needed for PBJ preparation, such as employee identifiers, work dates, hours, roles and pay type information.

What you should not upload

Social Security Numbers
resident or clinical records
bank account information
passwords or iQIES credentials
unrelated compensation or payroll fields

Temporary checkout checkpoint

To avoid making you re-upload files after payment, ChaseDesk encrypts the current workspace with the browser Web Crypto API and stores it temporarily in IndexedDB on this device. The encryption key stays in the current tab session. The checkpoint is set to expire after two hours and is never sent to Stripe.

Submission control

ChaseDesk does not sign in to iQIES or submit PBJ data on your behalf. You download the prepared file, submit it yourself and review the Final Validation Report.

Payment data

Checkout is handled by Stripe. ChaseDesk does not ask you to type payment-card details into the PBJ application itself.

What this page does not claim

ChaseDesk does not claim to be CMS-approved, SOC 2 certified, HIPAA certified or otherwise certified unless and until that is actually true. The current product is a preparation and reconciliation tool.

Questions

For data-handling or security questions, contact hello@chasedesk.com.