Privacy policy
Effective 2026-11-03. Applies to BatchTicket at https://batchticket.com, its installable app, its MCP server and its public plugins (together, the "Service"), operated by Anvil Rock Road LLC ("we", "us").
BatchTicket checks ready-mix batch tickets against an approved mix design. To do that it has to hold the mix designs, pours and tickets you enter, the photographs and documents you upload, and enough about you to run your account. This page says what we collect, what we do with it, who else sees it and how to get it removed.
1. What we collect
Account information
Your name, email address and a password hash when you register with a password. When you sign in through a provider (Google, Microsoft, Procore, HCSS or Trimble) we store the provider's identifier for you, your email address as the provider reports it, and the access token the provider issues so we can act on your behalf where you ask us to (for example delivering a pour record to a Procore project). We never see your password for those providers.
Organizations and memberships
The organization you create or join, your role in it, the people you invite, and the verified work-email domain the organization is created under, which decides who may be seated in it. When a provider such as Procore reports the company you belong to, we mirror that company as an organization and record your membership. We also store the names of the projects the provider lists for you, and which of them you can access, so they appear as jobs.
Content you put into the Service
Mix designs, pours, load tickets, field tests, remarks, the pour records the Service generates, and every file you upload: batch ticket photographs, mix design PDFs and spreadsheets. Uploaded files are stored under your organization, job and pour so they can be opened again and delivered where you ask.
Billing information
Card payments are taken by Stripe; we never receive your card number. We store the Stripe customer and payment identifiers, your prepaid balance, each charge and refund, subscription state, and for invoiced organizations the usage that goes on the invoice and the billing contact's name and address.
Agent and API access
If you connect an AI tool over MCP or create an API key, we store the key (hashed), the OAuth client you authorized, the tokens issued to it, and the time each was last used. The tool acts as you, so its reads and writes are logged against your account like any other.
Technical data
Server logs with your IP address, browser type, the pages and tools you called, timestamps and errors. We keep these for operations and security and do not build advertising profiles from them.
Cookies
Only the cookies the Service needs to work: a session cookie that keeps you signed in and a CSRF cookie that protects forms. There are no advertising or third-party analytics cookies. Signing out or clearing cookies ends the session.
2. How we use it
- To run the Service: store and check your tickets, generate pour records, send the emails you ask for (invitations, pour records to the addresses on a job's or pour's distribution list, receipts, account notices) and keep your organization's work visible to its members.
- AI extraction: when you choose to have a photograph or document read, the image or file and the mix design it is checked against are sent to Anthropic's Claude API, which returns the structured values you then verify. We use Anthropic's commercial API, under terms that do not allow the content to be used to train their models. Hand entry never leaves the Service.
- Billing: to estimate, reserve and settle the charge for each AI read, run subscriptions, issue invoices and keep the records tax law requires.
- Deliveries you request: when a pour is linked to a project in a connected system (Procore today), its ticket images and pour record are uploaded there, as you, when the pour is finished.
- Security and support: to detect abuse, enforce organization isolation, answer your questions and investigate problems you report.
- Industry statistics: only if your organization has opted in, and only in aggregate, we may study mix designs and ticket results across organizations to understand trends in concrete production. The opt-in is off unless an organization administrator turns it on, and nothing in an opted-in dataset identifies a person, a supplier's customer or a project.
We do not sell personal information and we do not use your content to advertise to you.
3. Who else sees it
Your organization
Mix designs, pours, tickets, uploads and pour records created in an organization's workspace are visible to that organization's active members and administrators, who may also export them. Administrators see members' names and email addresses and can remove members. A job imported from a connected system is shown only to members that system lists the project for; pours placed on it stay visible to the organization. Rows in your personal workspace are yours alone.
Service providers we rely on
| Provider | What they do | What they receive |
|---|---|---|
| Railway | Hosting, database and file storage (United States) | Everything the Service stores |
| Anthropic | AI extraction of uploaded documents | The uploaded file and mix design for each read you request |
| Stripe | Payments, subscriptions and invoices | Name, email, card details you give Stripe directly, amounts |
| Postmark | Outgoing email and bounce handling | Recipient address, subject and message body |
| Sign-in providers you choose | Authentication (Google, Microsoft, Procore, HCSS, Trimble) | Your sign-in request; they tell us who you are |
| Connected destinations you link | Receive pour records and ticket images (Procore) | The files for pours you linked to their projects |
Each provider may only use the data to supply its service to us, under its own data-processing terms.
Everyone else
We disclose personal information outside the above only when the law requires it, to protect the Service or its users from fraud or abuse, or as part of a merger, acquisition or sale of the Service, in which case this policy continues to apply until a successor tells you otherwise.
4. Where data is kept
The Service runs on servers in the United States. If you use it from elsewhere, your data is transferred to and processed in the United States.
5. How long we keep it
- Account and content data: for as long as your account, or the organization that owns the rows, exists.
- Uploaded files and pour records: with the pour they belong to, so a record can be reopened and re-delivered later.
- Billing records: seven years after the transaction, as tax and accounting rules require, even if the account is closed.
- Server logs: ninety days.
- Backups: rolling copies that age out within thirty days of a deletion.
6. Your choices and rights
- See and correct: everything you entered is editable in the Service while its pour is open; mix designs export as a workbook.
- Disconnect: provider sign-ins, connected AI tools and API keys can be removed from your Account page at any time, which stops their access immediately.
- Leave an organization: ask its administrator to deactivate your membership; your personal workspace is unaffected.
- Delete your account: email support@batchticket.com from the account's address. We remove your personal information within thirty days. Rows that belong to an organization stay with the organization; rows in your personal workspace are deleted. Billing records are kept for the period above.
- Export or object: if you live somewhere that gives you a right of access, portability, restriction or objection (for example the EU, the UK or California), email us and we will honor it within the time the law allows. We never discriminate for exercising a right.
7. Security
Connections use TLS with HSTS. Passwords are stored as salted hashes. Provider and MCP tokens are tied to the account that issued them and refused once revoked. Every read and write is filtered by the organizations you actively belong to, and that isolation is tested in our automated suite. Our hosting providers encrypt data at rest. No system is perfectly secure; if you believe your account has been compromised, change your password, revoke connected tools, and tell us.
8. Children
The Service is for professional use and is not directed at anyone under 18. We do not knowingly collect information from children; if you think we have, email us and we will delete it.
9. Changes
When this policy changes we update the effective date above and, for changes that reduce your rights, email account holders before they take effect.
10. Contact
Anvil Rock Road LLC · support@batchticket.com