Security & data handling
This page describes controls that are implemented today. It is a product disclosure, not a claim of SOC 2, ISO, government certification, or legal compliance.
A user must be signed in and hold approved customer workspace access before a document can be stored. Uploaded files are placed in a user-specific storage path, and document records are retrieved by the authenticated owner ID.
The beta accepts a defined set of document formats, rejects files larger than 10 MB, and checks each file signature so its contents match the declared format before storage. File names are normalized before storage.
CPSC API credentials are configured as hosted server secrets. They are not placed in the browser interface or returned to signed-in users.
The current CPSC connection is limited to an authorized operator allowlist and reads account and collection metadata only.
The current application has no enabled certificate-submission route. Preparing or exporting a review does not transmit certificate data to the CPSC.
CertifyPreflight provides preparation support. The importer and its authorized broker or filing partner remain responsible for reviewing the final information.
Customer access is granted, suspended, and expired from a protected operator console. A valid sign-in alone does not unlock real-document analysis.
Sensitive operator consoles and CPSC connection checks require both an approved operator account and two-step verification through the identity provider.
Public fit checks use a hidden bot field and privacy-preserving request-rate key. Authenticated uploads, workspace saves, applications, support requests, payment-session creation, and selected operator actions are protected by server-enforced request limits.
Customers can permanently delete individual documents from their authenticated workspace. The server verifies ownership before deleting both the private file and its record.
Completion-survey responses are stored with the signed-in customer account for product improvement. A customer may allow follow-up about a possible quote, but nothing is published automatically.
A completeness screen may move an eligible Guided Pilot application to payment readiness, but it never makes a compliance determination. Workspace access is activated only after an approved scope and a verified payment event when billing is enabled.
Payment-card entry occurs on Stripe-hosted Checkout. CertifyPreflight stores payment status and identifiers needed for reconciliation, not full card numbers. Signed webhook verification activates or updates customer access after Stripe confirms the payment or subscription event.
Beta limitations
Questions or deletion requests
Individual files can be deleted directly inside the workspace. Account-wide deletion and other data questions are handled through the private Support form. Do not email sensitive product files.
eric@certifypreflight.com