Last updated: November 17, 2026
PayBooqs is operated by Jerusalem Booqs & more LLC ("PayBooqs," "we," "us"). We provide a hosted payment portal and invoicing platform that connects a business's QuickBooks account to its payment processor.
We share information only as needed to run the Service, with service providers bound to protect it, with the tenant whose customer you are, as required by law, or in a sale or reorganization of our business (with notice). We do not share one tenant's data with another tenant. Our main providers are:
| Provider | What for |
|---|---|
| Cloudflare | Hosting, data storage, email routing and the bot checks (Turnstile) on forms and sign-in. |
| Intuit (QuickBooks) | The accounting data a tenant connects; we read and write only what the tenant's features need. |
| Sola / Cardknox (payment processor) | Collecting and tokenizing card and bank details, processing charges and refunds, settlement reports. Card and bank numbers go straight to the processor. |
| Resend and similar email delivery services | Sending invoices, receipts, reminders, notices and system email. |
| Google (Workspace / Gmail) | Our own support mailbox, which is PayBooqs's own Google account, connected through a separate Google app that is used only by PayBooqs (not the one companies use to send from their own Gmail). Email sent to our support addresses is read and answered there; the text of a support email may be given to our AI service to sort it into a ticket (see Anthropic below). Separately, a company can connect its own Gmail address so PayBooqs can send its invoices from it (see "Sending from your own Gmail address"). |
| Anthropic (AI service) | Reading the details from an image of a check that a user uploads, reading vendor bills and documents that a company uploads or emails to its Payables inbox (only for companies that use Payables), and helping sort incoming support email into support tickets. We send only what is needed for that task, under terms that do not allow the content to be used to train their models. |
| Calendly | Scheduling demo calls requested from our website. |
Providers may change as the Service develops; we keep this list current. Tenants may also connect their own tools, which have their own policies.
Card numbers and security codes are entered into secure fields run by our payment processor and tokenized there, so they never reach PayBooqs. Bank account and routing numbers are sent from the customer's browser over an encrypted connection, through PayBooqs, to the payment processor, and we do not store them. We keep tokens and limited reference details (such as card brand, last four digits, expiry and account type) so a customer can pay with a saved method and a tenant can reconcile payments.
When a tenant connects QuickBooks, PayBooqs asks Intuit for access to the company's accounting data (the "accounting" permission, which Intuit grants as both read and write). We use it to display invoices in the portal, record payments and deposits, and, if the tenant enables those features, to create customers, items, invoices, estimates, sales receipts, refund receipts, purchase orders, bills, journal entries, attachments and similar records at the tenant's request. We keep a working copy of the data needed to run the portal quickly. We use Intuit's data only to provide features to that tenant and we do not use it for any other purpose.
We change or delete a record in QuickBooks only when a person at the tenant takes that action in PayBooqs, for example editing an invoice, removing an attachment, deleting a payment, or undoing a bank deposit that PayBooqs recorded, or when PayBooqs cleans up a leftover record that it created itself while recording a transaction. A tenant can also switch on a setting that makes PayBooqs do one narrow thing by itself: for example, adding a payment link to the message of each new QuickBooks invoice. That setting is off until the tenant turns it on, and it only adds a line to the invoice message; it changes nothing else on the invoice. We do not otherwise edit or delete a tenant's existing QuickBooks records. We do not request access to QuickBooks Payroll.
We never see or store a tenant's QuickBooks username or password. For QuickBooks Online we hold only the access tokens Intuit issues for that connection, and for QuickBooks Desktop only the connection login PayBooqs creates for the company's Web Connector. A tenant can disconnect at any time, from QuickBooks or from its PayBooqs account. When it disconnects in PayBooqs, we tell Intuit to revoke the connection and delete our stored tokens, so PayBooqs can no longer read or write that company's data. When a subscription ends, we remove the connection the same way after 30 days. The working copy we keep is then handled as described under "How long we keep information."
The PayBooqs for Email extension for Chrome and Edge works inside the Gmail or Outlook on the web compose window. When you press its button it sends the customer name or invoice number you typed, the recipient address in the To field (only to find the matching customer), and the invoices, credit memo, sales receipt, refund receipt or payment you pick, to your own PayBooqs account, and receives back an invoice, a credit memo or receipt, or a payment receipt (the invoices paid, the amount, and the card brand and last four digits, authorization code and reference number of the payment), a link and a PDF, which it places in the message you are writing. If you tick a credit memo together with invoices and confirm, PayBooqs applies that credit memo to those invoices in your QuickBooks Online (a record QuickBooks keeps as "credit applied"), then places the invoices, the credit and the balance after it in the message; nothing is applied without your confirmation. It does not read your mailbox, your messages or your contacts, and it does not send anything you write to PayBooqs. Where it cannot attach a PDF or insert text, it sends PayBooqs a short problem report (what went wrong and the browser version) so we can fix it; the report holds no message content. With each request it also tells PayBooqs which version of the extension it is, so your company can be told when a newer one is available.
On QuickBooks Online's invoice email page (the page with the "Send invoice" button), the same extension shows a "PayBooqs link" button. When you press it, it sends PayBooqs the number of the saved invoice that is open (taken from the page address) and receives back that invoice's payment link, which it types into the email's "Email body" box; PayBooqs can also add the link to the invoice's own message in your QuickBooks, as you chose in your PayBooqs settings. To place its button and the link, the extension reads the page address, the names of the buttons on that page and the text of that one email box. It does not collect, store or send any other QuickBooks data, and it never sends the email.
On QuickBooks Online's invoice, estimate, credit memo, sales receipt and refund receipt pages the extension can also show a "Send with PayBooqs" button (only when your company has switched it on in PayBooqs), and on a saved invoice a "Take payment" button (only when your company has it and you may use it). When you press one, the extension presses QuickBooks's own Save button when needed and opens its own window. For "Send with PayBooqs" that window sends PayBooqs the number of the saved document and what you type in it: the recipient address, subject, greeting, message, button text, notes and footer, any deposit you ask for on an estimate, and any deposit credit you tick on an invoice. It receives back the email, its PDF, the customer's address and any credit on the customer's account, and shows them to you. If you send from PayBooqs, PayBooqs emails it to your customer. If you choose your own Gmail or Outlook, the extension opens a compose window on that site and fills it in, and you send it yourself; the email is held in the browser's temporary session storage for a few minutes only, to hand it to that window. "Take payment" sends PayBooqs the number of the saved invoice and opens PayBooqs's own payment window for it, signed in for you; the card or bank details are typed into PayBooqs's own page, never into the extension. When you press Close, the extension presses QuickBooks's own Save and close button (or Close or Cancel). It collects nothing else from the QuickBooks page.
Sending from your own Gmail address. A company can connect one or more of its own Gmail or Google Workspace addresses to PayBooqs (Settings, "Their own Gmail addresses"). The company's administrator signs in on Google's own page and approves a single permission: to send email as that address (Google's "gmail.send" permission), plus the address itself so we know which account it is. PayBooqs cannot read, search, list or delete any email in that account. When you send an invoice or estimate with "PayBooqs, from their own Gmail address", PayBooqs gives that one message (to your customer, with its PDF) to Gmail, and it goes out from your address and appears in that account's Sent folder. PayBooqs keeps a long-term access key for the address in the company's own protected storage, kept encrypted, only to send those messages; it is used for nothing else. The administrator can disconnect an address at any time in PayBooqs (the key is then revoked at Google and deleted), or remove PayBooqs under "Third-party apps with account access" in the Google account, and sending stops at once. PayBooqs's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use this access for advertising, do not sell it, and do not let anyone read the mail. Information we receive from Google through this connection (the connected address and the permission to send) is not used to develop, improve or train artificial-intelligence or machine-learning models, and is never given to an AI service or to any third party; the only thing sent through the connection is the message you asked PayBooqs to send, to the recipient you chose. When an address is disconnected, the stored key is revoked at Google and deleted.
Sending from your own Outlook or Microsoft 365 address. In the same way, a company can connect one or more of its own Outlook.com, Hotmail or Microsoft 365 addresses to PayBooqs (Settings, Email Sending). The company's administrator signs in on Microsoft's own page and approves a single permission: to send email as that address (Microsoft's "Mail.Send" permission), plus the address itself so we know which account it is. PayBooqs cannot read, search, list or delete any email in that mailbox. A message sent with "PayBooqs, from their own Outlook address" goes from that mailbox to your customer, with its PDF, and is kept in that mailbox's Sent Items. PayBooqs keeps a long-term access key for the address in the company's own protected storage, kept encrypted, only to send those messages. The administrator can disconnect an address at any time in PayBooqs (the key is deleted at once), or remove PayBooqs from the Microsoft account's app permissions, and sending stops. We do not use this access for advertising, do not sell it, and do not let anyone read the mail.
The extension keeps your PayBooqs address and a connection key in the browser's local extension storage. The key can search invoices, credit memos, receipts and payments, build the invoice or receipt block, fetch PDFs, make the payment link of one saved invoice or the approval link of one saved estimate, apply a credit memo you confirmed to invoices you ticked, open the payment window for one saved invoice, and prepare or send the email for one saved document through PayBooqs, nothing else. You can remove a connection any time under Settings in PayBooqs, or by removing the extension, and the key stops working immediately. We do not sell or share any extension data, and we do not use it for advertising.
We use only what is needed to run and secure the Service: sign-in session information, saved preferences, and security and bot-check cookies from Cloudflare Turnstile. We do not use advertising or cross-site tracking cookies. Because we do not track you across other sites, we do not respond to "Do Not Track" signals. We do not sell or share personal information, so there is nothing to opt out of.
We use safeguards that are appropriate to the sensitivity of the information, including encryption in transit (HTTPS/TLS), encryption at rest provided by our hosting platform, separation of each tenant's data, access controls and authentication for admin and customer accounts, rate-limiting and bot checks, activity logging, and regular security testing. No method of transmission or storage is perfectly secure. If we become aware of a breach that affects your information, we will notify the affected business or you, and regulators, as the law requires.
Depending on where you live (for example California, and other states with privacy laws), you may have the right to know what personal information we hold about you, to access or get a copy of it, to correct it, to delete it, and to be free from discrimination for exercising these rights. We do not sell personal information or share it for targeted advertising, so there is nothing to opt out of.
The Service is for businesses and is not directed to anyone under 18. We do not knowingly collect personal information from children. If you think we have, contact us and we will delete it.
The Service is designed for businesses in the United States. Information is processed and stored on infrastructure operated by our providers, which may be in the United States or other countries where they operate. We do not offer the Service to consumers in the European Economic Area or the United Kingdom.
We will post updates here with a new "last updated" date, and for material changes we will notify tenants by email or inside the Service before they take effect.
Jerusalem Booqs & more LLC, doing business as PayBooqs
Privacy questions and requests: support@paybooqs.com