Last updated: July 27, 2026
Privacy Policy
This policy explains how PDF2TEXT handles account data, uploaded documents, extraction results, payments, optional analytics, and support requests.
Information We Process
We process the information you provide when you create an account, upload documents, run extraction jobs, buy export packs or subscriptions, use API keys, contact support, or interact with the product.
Uploaded files, page images, extracted text, structured tables, metadata, exports, usage events, and billing references may be stored so your workspace, exports, support, fraud prevention, and billing records work as expected.
How We Use Information
We use information to provide document extraction, save workspaces, deliver exports, process purchases, prevent abuse, debug failures, answer support requests, improve reliability, and maintain accounting and security records.
Documents and AI Processing
Documents are processed by PDF2TEXT systems and selected service providers needed to deliver OCR, extraction, storage, infrastructure, support, analytics, and payments. We configure OpenAI extraction and classification requests not to store API outputs for model training or product improvement on their side where the API supports that setting.
Service Providers and Subprocessors
PDF2TEXT uses limited subprocessors for the service: AI extraction providers, payment processing, hosting and storage, email delivery, support tooling, and analytics (in the EEA, UK and Switzerland only after consent; elsewhere you can opt out under Cookie preferences in the footer). We do not sell uploaded documents or extracted bank-statement data.
Bookkeeping firms, accounting teams, and other business customers can request current subprocessor details or a data processing addendum path by emailing security@pdf2text.ai.
QuickBooks Online Integration
Connecting a QuickBooks Online company is optional. You authorize it on Intuit's own sign-in page, which gives PDF2TEXT access to that company through Intuit's QuickBooks Online Accounting API (the com.intuit.quickbooks.accounting permission). PDF2TEXT uses this access only to show which company is connected, to list its bank and credit card accounts, and to send the statements you choose to send.
When you send a bank or credit card statement, PDF2TEXT creates one transaction for each statement row in the QuickBooks account you choose: an expense or a deposit for a bank account, a credit card expense or credit for a credit card account. Each transaction holds the row's date, amount and description, the account's currency, and a memo with the description, the PDF2TEXT document number and the row number. It is filed under “Uncategorized Expense” or “Uncategorized Income”, and PDF2TEXT creates those two accounts if your company does not have them. Your uploaded file, its page images, and the statement's header and summary, such as its balances and account number, are not sent.
PDF2TEXT reads only what this needs: the company's name, its list of active accounts (to show your bank and credit card accounts and to find the two Uncategorized accounts), and the ids QuickBooks gives the transactions PDF2TEXT creates. It does not read your other transactions, customers, vendors, invoices, or reports, and it does not change or delete anything else in your company.
PDF2TEXT stores the connection's access and refresh tokens encrypted, the company's QuickBooks id and name, and, for each send, the account you chose (its name, type, and currency), the rows prepared for it, the counts, and any error QuickBooks returned. For each transaction it creates, it keeps the QuickBooks transaction id with the row's date, amount, and a fingerprint of the row, so that sending the same statement again does not create duplicates.
The transactions you send go to Intuit, which handles them as part of your QuickBooks Online company under Intuit's own terms and privacy statement. PDF2TEXT does not sell this data and uses what it stores only to provide the integration, show your send history, and answer support requests.
You can disconnect at any time, from PDF2TEXT's QuickBooks connections page or from the apps connected to your QuickBooks company. When you disconnect in PDF2TEXT, we ask Intuit to revoke the connection, and PDF2TEXT deletes the stored tokens. When you disconnect in QuickBooks, Intuit revokes the connection, and PDF2TEXT deletes the stored tokens as soon as it sees that access was revoked.
Transactions already sent stay in your QuickBooks company. The send history and the duplicate-check records are kept after you disconnect, so that reconnecting the same company does not send the same rows again. To have them deleted, email support@pdf2text.ai.
Retention and Deletion
Uploaded documents, their page images and their extraction results are deleted automatically 7 days after upload if you have not paid, and 30 days after upload if you paid for a document or pages. Subscribers keep them until they delete them, or choose automatic deletion 30 or 90 days after upload on their subscription page. When a subscription ends, files are kept for 30 days, and we email you a week before they are deleted.
You can delete the files in your private workspace yourself at any time. Deleted files and results are erased from our servers; we keep the record that an upload happened (its date, page count and document type) for billing and usage. QuickBooks send records are kept as described above.
You can request deletion of stored documents or account data by contacting support@pdf2text.ai. We may retain limited records when needed for billing, tax, abuse prevention, dispute handling, security logs, or legal obligations.
Payments
Payments are processed by Stripe. PDF2TEXT stores billing references, checkout metadata, invoices, and subscription status, but does not store full card numbers.
Contact
For privacy, deletion, or data handling requests, email support@pdf2text.ai. For security-specific questions, email security@pdf2text.ai.