Privacy Policy
Last updated: November 15, 2026
JMJ Billing LLC operates:
- JMJ Billings — accounts-receivable follow-up for businesses (portal.jmjbillings.com);
- JMJ Build — job management for contractors: estimates, schedules, purchase orders, change orders, job budgets and costs, bills and vendor payments, crew and team accounts, invoicing and payments (build.jmjbillings.com). JMJ Build was previously called JMJ Office; some addresses, emails and settings may still use that name;
- our website at jmjbillings.com, including its chat assistant and contact form;
- Lyakon (sales CRM).
This policy covers each of these. Where a practice applies to only one, we say which.
Who is who. You are our customer, the business that holds an account. Your team are the people you invite to your account. Your customers are the people and businesses you quote, bill or follow up with. Your vendors are the subcontractors and suppliers you record in JMJ Build. Your vendors' portal users are people at your vendors who sign in to the vendor portal at your invitation. Most personal data we handle belongs to your customers, vendors and team, and we process it on your instructions.
1. What we collect and store
About you and your team
- Account details: business name, contact name, email, phone, industry, and account settings.
- The product(s) you chose at signup and the version of our Terms you accepted.
- Sign-in data, handled by our authentication provider (Supabase), including two-factor enrolment. Sign-in sessions and authentication events record IP address and browser user agent. Vendor portal users sign in with a one-time email link and may turn on two-step sign-in.
- Team invitations: the invitee’s email address and role. The invitation link is stored only in hashed form.
- Roles: whether each person is an owner, project manager or crew member.
- Time records (JMJ Build): hours worked per team member or vendor crew on each scheduled task, as prefilled from your schedule or job assignments and confirmed or edited by your project manager or owner; if you turn on crew clock in / out, the time each crew member clocks in and out on a job; who confirmed them and when; overtime hours you mark and their multiplier; and a permanent history of edits with who made each change and why. The pay rate, day rate, and optional burden multiplier you set for each team member, used for job cost and payroll-input files. Crew members cannot see rates or pay. We do not collect location (GPS) data.
- Payroll-input files (JMJ Build): the files you generate, kept so you can download the same file again.
- Daily logs (JMJ Build): notes added to a job’s daily log, who wrote them and when, which can show who was on site on a given day.
- Schedule history (JMJ Build): when a scheduled item is moved, who moved it, when, and the dates before and after.
- Job status history: which team member moved a job from one status to another, with the time and any reason. This history is permanent (§6).
- Photos uploaded by you or your team (JMJ Build), with the uploader, upload time, file size and caption.
- A record of actions taken in the service, with timestamps, for audit and support.
- When our staff view your account to support you, we record who did so, when, and from which IP address and browser.
About your customers (entered by you, synced from a system you connect, or received by email)
- Name, email, phone, billing address, and whether they are a business or an individual.
- Invoices, estimates and quotes: numbers, dates, line items, amounts, balances, payment status, notes and terms. For invoices synced from accounting software, a copy of the invoice PDF.
- Property and job records (JMJ Build): service address, access notes you enter, job title, schedule, status, and the assigned project manager. Before November 13, 2026, JMJ Build asked whether a job's property was a homestead. We no longer ask. Answers recorded before that date stay stored with the job.
- Electronic acceptance (JMJ Build): when your customer accepts an estimate, or approves or declines a change order, through a link, they first tick a box agreeing to sign electronically. We record the name they type, the time, the IP address, the browser (user agent), the email address the link was sent to, and a SHA-256 hash of the exact document shown, and we keep a copy of the document as accepted. An executed copy with this record is emailed to the signer and to you. Where you record an approval made outside the service, we store who you say approved it, your explanation and any proof you attach.
- Email exchanged with your customers through the service: messages we send on your behalf (including the body) and replies (sender, subject and body; reply attachments are not stored).
- Email engagement: open and link tracking by default; delivery, open, click and bounce events. We do not store the IP address, device or location from those events.
- Unsubscribe and do-not-contact records, including the IP address from which an unsubscribe was submitted.
- If your customer tells us they have paid, we record that claim and the time.
About your vendors (JMJ Build) (entered by you)
- Vendor name, type (subcontractor, supplier, crew, other), contact details, the cost codes you assign, and the last four digits of their taxpayer identification number if you enter them.
- Vendor documents you upload, such as insurance certificates and endorsements, licenses, contracts, lien waivers, and Form W-9, which contains a full Social Security number or Employer Identification Number. We store the file, its type, and its effective and expiry dates. W-9 files are encrypted before storage and only your account owner can open them; every view is logged. We never extract the full number into our database; at most we keep the last four digits you enter.
- Purchase orders and work orders: lines, amounts, dates and status. We no longer ask vendors to accept purchase orders or work orders; acceptance records created before November 9, 2026 are kept.
- Bills and receipts: vendor invoice numbers, amounts, dates, lines, and attached images or files.
- Vendor payments you record: amount, date, method, and the reference you enter (for example a check number or ACH reference). We record these payments; we do not make them.
- Vendor portal users (JMJ Build): name, email, phone, company details, sign-in data (including IP address and browser for sign-in events), invoices and documents they upload (W-9s are encrypted and readable only by your organization's owners), and a record of their actions in the portal.
- If someone opens a file through a share link (for example a crew member, vendor or customer who isn't a JMJ user), we record when it was opened or downloaded, which link and which file, and how many times the link has been used to download, and show that activity to the account that shared it.
- Remit-to address and payment records you or your vendor enter.
About your payment and banking setup
- Payment connection details for your own processors (Stripe, Square) and payment handles (PayPal.me, Cash App, Venmo, Zelle).
- If you choose to show ACH payment instructions, the bank name, routing number and account number you enter. These are shown to your customers on invoices you send (§3).
- API keys and access tokens for connected services are encrypted before storage (AES-256-GCM, key held separately from the database).
Subscription billing for your own account is handled by Stripe; we do not see or store your full card number.
On our website (jmjbillings.com)
- Chat assistant: the messages you type are sent to our AI provider (Anthropic) to generate a reply. Your IP address is used to limit request rates.
- Contact form: your name, email and message are emailed to us through Postmark. Your IP address is used to limit request rates.
- The website does not use third-party advertising trackers.
- We count website visits with Cloudflare Web Analytics, which does not use cookies.
2. How we use it
- To send the emails and documents you direct us to send.
- To follow up on overdue invoices on a fixed, rules-based schedule (JMJ Billings). The schedule is not decided by AI.
- To run JMJ Build: jobs, schedules, estimates, change orders, purchase orders, budgets and job costing, bills and vendor payments, labor costing, vendor document tracking (including expiry warnings), invoicing, payments and year-end exports.
- To keep audit records of what was sent, accepted or changed, when, and by whom.
- To send vendor portal users service emails about work orders shared with them, payments recorded on their invoices, and expiring insurance certificates.
- To secure the service, detect abuse, and support you.
- To answer questions from website visitors and respond to contact-form messages.
AI. We use Anthropic’s Claude models to:
- classify replies from your customers so they are routed correctly (JMJ Billings);
- classify a customer as a business or an individual from name and email;
- draft estimate, quote and invoice line items from text you type or speak (JMJ Build). A person reviews and approves before anything is saved or sent. AI does not calculate money amounts;
- suggest duplicate customer records to merge, using name, email, phone and billing address;
- detect payment promises in replies, and classify messages to our support desk;
- write a short internal summary for an account being prepared for referral to a recovery partner (JMJ Billings);
- answer questions in the chat assistant on our website.
We do not use your data or your customers’ data to train AI models.
3. What leaves the service, and to whom
- Your customers receive the emails, estimates, change orders, invoices and receipts you send through us. These can include amounts, line items, notes, terms, payment links and, if enabled, your ACH details. Acceptance receipts include the signer’s typed name, time and IP address.
- Your vendors receive the purchase orders and work orders you send them.
- Links for your customers and vendors. Estimate, change-order, purchase-order and invoice emails can contain a link that opens the document without signing in. Each link carries a long random code unique to that message and expires after 90 days. Anyone who has the link can view what it shows until it expires. These pages show your business name, not ours.
- Unsubscribe links do not expire, so the ability to opt out is never lost.
- Recovery and lien partners (JMJ Billings, only when you authorize a referral). We send the partner your business name and the invoice details; your customer’s name, email and phone, and the amount and days past due; and an audit package of messages sent, replies received with AI summaries of them, and AI recovery estimates. For lien referrals you are copied.
- Your accountant, or anyone you give an export to. Year-end exports can include vendor names, payment totals, 1099 totals, labor costs and documents. Once you download an export, what happens to it is up to you.
- Your accounting software, if you enable write-back (§4).
- Service providers (§5).
- Our own team receives internal exception notifications, which can include a customer’s email address, a subject line and an AI summary of their reply.
We do not sell personal data, and we do not share it for advertising.
4. QuickBooks and other connected systems
What we request. For QuickBooks Online, the com.intuit.quickbooks.accounting scope, which permits reading and writing. We do not request com.intuit.quickbooks.payment.
What we read. Invoices, customers, and payments, to keep your receivables up to date, plus invoice PDFs, which we store. If you use JMJ Build with QuickBooks sync, we also read vendors, bills, bill payments, purchase orders, estimates, items, and — for jobs you track in JMJ Build — expenses, journal entries, and payroll cost totals tagged to those jobs, along with your chart of accounts, tax codes, classes, and payment terms. We use this only to show your job costs, payables, and profit in JMJ Build and to check that JMJ and QuickBooks agree. We don’t sell it, share it for advertising, or use it to train AI models. A customer’s name and email from QuickBooks may be sent to our AI provider to classify them as a business or an individual. QuickBooks Desktop is read through our connector provider, Conductor.
What we write (JMJ Build only, and only if you turn it on). If you turn on QuickBooks sync, JMJ Build creates or updates these records in your QuickBooks file when you or your team take an action in JMJ Build: customers and jobs (as sub-customers), invoices and draws you send, payments you record as received, vendors, bills you approve, bill payments you record, purchase orders you send, estimates you choose to send, and the product/service items those records use. A payment or bill payment we write is a book record of money that already moved outside JMJ — we never move money. We never delete QuickBooks records; we void or close where needed. We do not send labor or payroll to QuickBooks. Automated systems, including AI, never write to your QuickBooks data. JMJ Billings never writes to QuickBooks. You can turn sync off or disconnect at any time.
Our commitments to Intuit, quoted as submitted: “We never delete any QuickBooks entity, under any circumstance, in either product.” “Writes are deterministic and initiated by the client (or by an operator acting on the client’s instruction).” “No AI-generated content is ever written to a client’s QuickBooks data.”
Other systems. You can also connect Xero, Jobber, FreshBooks, Housecall Pro or Stripe as a source of invoices. We read invoice and customer data from them the same way.
Disconnecting. When you disconnect QuickBooks in Settings, we revoke our access at Intuit and delete the stored tokens. Invoice data already synced is kept unless you ask us to delete your account. If you revoke access from Intuit’s side, our connection stops and is marked for reconnection.
Email accounts. If you send through your own Gmail account, we request permission to send mail as you (gmail.send). For Gmail, we do not read your inbox or any incoming messages. If you send through Microsoft 365, we request Mail.Send; if you choose the dedicated-inbox setup, we also request Mail.Read and read the replies that arrive in that mailbox. We do not access your contacts, calendar or files.
OAuth Permissions and Data Use
Gmail:
openidandemail— confirm the email address you authorized with (used to show which account you connected; not used for marketing)
Microsoft 365:
openid,email,profile— confirm the email address you authorized with (used to show which account you connected; not used for marketing)
- We do NOT use your data to train machine learning models
- We do NOT share your data with third parties for advertising or marketing purposes
OAuth refresh and access tokens are encrypted at rest using AES-256-GCM encryption before being stored in our database. The encryption key is held separately from the database.
You can revoke JMJ Billings’ access to your email account at any time:
- Gmail: https://myaccount.google.com/permissions → find “JMJ Billings” → Remove access
- Microsoft 365: https://account.microsoft.com/privacy/app-access → find “JMJ Billings” → Remove access
After revoking access, JMJ Billings cannot send chase emails on your behalf until you reconnect. We retain the encrypted tokens in our database in case you want to reconnect with the same account, but you can request full deletion by emailing info@jmjbillings.com.
JMJ Billings complies with the Google API Services User Data Policy, including the Limited Use requirements. We comply with Microsoft’s Identity Platform terms and the requirements for Verified Publisher status.
How We Handle QuickBooks Data
- We do NOT sell, rent, license, or otherwise share Intuit data with third parties for advertising or marketing purposes.
- We do NOT use Intuit data to train machine-learning models. Our reply-intent classifier operates only on the content of inbound reply emails (which is not Intuit data). Where AI is used to classify a customer as a business or an individual, only that customer’s name and email address are processed for that classification.
- We use Intuit data only to provide the JMJ Billings and JMJ Build features you’ve turned on.
Intuit data we sync is stored in our Postgres database hosted in the United States by our subprocessor Supabase, Inc. OAuth refresh and access tokens issued by Intuit are encrypted at rest using AES-256-GCM at the application layer before being written to the database; the encryption key is held separately from the database.
You can revoke JMJ Billings’ access to your QuickBooks Online company at any time from Intuit’s account security page. After revoking, JMJ Billings cannot sync new data from your QuickBooks company until you reconnect.
5. Service providers and where data is stored
| Provider | What they do for us |
|---|---|
| Supabase | Database, file storage (invoice PDFs, job photos, vendor documents including W-9s, bill and receipt attachments) and sign-in |
| Vercel | Application hosting (portal, build and partners sites) |
| Postmark (ActiveCampaign) | Sending and receiving email; delivery, open and click events; website contact form |
| Anthropic | AI processing (§2), including the website chat assistant |
| Stripe | Our subscription billing; payment links on your own Stripe account, if you connect it |
| Square | Payment links on your own Square account, if you connect it |
| Intuit | QuickBooks Online, if you connect it |
| Conductor | QuickBooks Desktop connection, if you use it |
| Xero, Jobber, FreshBooks, Housecall Pro | Invoice sources, if you connect them |
| Google, Microsoft | Sending from your own mailbox, if you connect it; our support inbox runs on Google |
| GitHub | Stores copies of our database backups |
| Cloudflare | DNS; hosting for our website and its chat assistant |
Location. Our database is hosted by Supabase in the United States (AWS US West, Oregon). Our application runs on Vercel in the United States.
6. How long we keep data
We state what the system does today.
- Records designed to be permanent. Job status history, signed contract records, accepted estimate, change-order and purchase-order records, schedule change history, and job-photo records cannot be deleted through the service. A photo can be removed from view, but the image file is kept.
- Job photos. Kept for at least 10 years, reflecting the Texas statute of repose for improvements to real property (Tex. Civ. Prac. & Rem. Code §16.009). No automatic deletion runs today.
- Vendor documents, including W-9s. Other vendor documents are kept for as long as the account exists unless you archive them. W-9s are deleted after the end of the fifth calendar year following the last calendar year in which you recorded a payment to that vendor (or following upload, if no payments were recorded). Each W-9 has its own encryption key, which we destroy on deletion, so backup copies become permanently unreadable; the encrypted key itself may remain in database backups for up to 90 days.
- Email. Content kept for as long as the account exists. This is the record of exactly what a recipient was sent.
- Time records and payroll-input files are kept with your account records ("Kept for as long as the account exists."). Laws that require employers to keep payroll and time records apply to you as the employer; download what you need to keep.
- Everything else. Kept for as long as the account exists. No automatic deletion runs today.
- Account deletion. Self-service account deletion is currently turned off. To ask for deletion, email us (§7). Records described above as permanent are kept even after an account closes.
- Backups. Our database provider takes daily backups. We also take our own database backups before changes, stored on our systems and on GitHub for up to 90 days. Uploaded files (photos and documents) are not currently copied to a separate backup.
7. Your choices and requests
- Disconnect any connected service in Settings; turn off QuickBooks write-back at any time.
- Your customers can unsubscribe from follow-up emails using the link in every such email.
- Account owners can remove team members at any time.
- To ask about, correct or delete your organization’s data, email info@jmjbillings.com. Requests about an individual’s own personal data — from a team member, crew member, partner, or one of your customers or vendors — go to privacy@jmjbillings.com.
8. Security
Connections are encrypted in transit. Access to data is restricted per account at the database level. Tokens and API keys are encrypted before storage. Job photos, invoice PDFs and vendor documents are kept in private storage; inside the service, photos are shown through links that expire after one hour. Crew accounts cannot see financial data. Each of our sites (portal, build, partners) uses its own sign-in cookie; moving between them uses a short-lived signed hand-off, not a shared cookie. W-9 files are encrypted in our application with a key held separately from the database. If we determine that personal data was acquired without authorization, we notify the affected account owner immediately and support any notices they must send, as set out in our Terms (Schedule C).
9. Cookies and browser storage
We use first-party cookies to keep you signed in and to complete connections to other services. Sign-in cookies are set separately for portal.jmjbillings.com, build.jmjbillings.com and partners.jmjbillings.com. Your browser stores a marker of your last activity, used to sign you out after inactivity. Inside the service, we do not use third-party analytics or advertising trackers. Emails to your customers use open and link tracking (§1).
10. Changes to this policy
We will post material changes here with an updated “Last updated” date. If a change affects how we use your data in a way you would reasonably object to, we will email account owners before the change takes effect.
11. Contact
info@jmjbillings.com · privacy@jmjbillings.com · JMJ Billing LLC, 1511 W Hwy 71, Ste 110, Bee Cave, TX 78738