Privacy by design
Privacy Policy
Last updated: August 22, 2026
What we do not collect
VerifyMover does not require an account, name, phone number, password, or user profile. We do not maintain a database of user search histories.
Official company data
When you submit a USDOT or MC number, our server requests public carrier information from FMCSA. The API response may be cached in Upstash Redis for up to 24 hours to improve reliability and reduce duplicate government API requests. This cache is keyed by carrier number, not by user identity.
Uploaded moving documents
If you choose the document-comparison feature, each selected PDF or image is processed separately in server memory and sent to the OpenAI API for structured extraction. You may submit up to six documents from no more than three companies. VerifyMover does not write original documents to permanent file or object storage, does not create public file URLs, and releases each file after its request completes. Structured extractions and the comparison report remain in the active browser page and are not added to a user-history database.
AI processing and retention
OpenAI processes the uploaded document to identify document facts and short evidence snippets. VerifyMover sends Responses API requests with storage disabled. OpenAI may nevertheless retain API abuse-monitoring logs, which can include customer content, for up to 30 days unless different data-retention controls apply to the API project. OpenAI states that API data is not used to train its models unless the API customer explicitly opts in.
Sensitive information
Moving documents may contain names, addresses, contact details, signatures, inventory, prices, or payment information. Do not upload a document containing a Social Security number, full card number, bank credentials, or information that is not necessary for the comparison. The extraction instructions prohibit returning personal contact details, account numbers, card numbers, SSNs, or signature images, and VerifyMover does not intentionally log document text.
Anonymous paid passes
Before Paddle Checkout opens, VerifyMover creates an opaque browser token. After Paddle confirms a completed transaction, Upstash Redis stores only the token's report credits or one-use document-comparison entitlement for up to 7 days. Paddle transaction and webhook identifiers are retained temporarily for payment idempotency. Tokens contain no uploaded document, extracted document text, phone number, account profile, or password.
Payments and tax data
Paddle is the Merchant of Record. Payment, billing, email, location, and tax information required to complete the transaction is submitted to and processed by Paddle under Paddle's own privacy terms. VerifyMover does not receive or store full card details. Paddle may use buyer country, region, or postal code to calculate and remit applicable sales tax, VAT, or GST.
Browser storage
The anonymous audit-pass token is saved in your browser's localStorage so it can be used without an account. Clearing browser storage removes the token from that browser.
Infrastructure logs
Vercel, Upstash, Paddle, OpenAI, and FMCSA may process standard technical request data under their respective terms. VerifyMover does not intentionally place complete extracted text, personal addresses, phone numbers, email addresses, signatures, or payment data in application logs.
Contact
Questions about this policy can be sent to veryfiymoverhellp@gmail.com.