TicketSaver Privacy Policy
Effective date: November 22, 2026
TicketSaver is a service of DayTech Enterprises, LLC, a Texas limited liability company ("DayTech", "we", "us"). This policy tells you what data TicketSaver collects, why, where it goes, and what choices you have.
Contact: privacy@ticketsaverhq.com.
1. Who this policy is for
TicketSaver is a tool for trade contractors. A contractor company (the "Company") opens a TicketSaver account. Its office staff and crew members ("users") make and approve work orders ("tickets").
- The Company decides what goes into its tickets. The Company is responsible for that data. We process it for the Company, on its instructions.
- If you are a customer of a Company and your name, address, or signature is on a ticket, the Company is your first contact for questions about that data. We help the Company to answer you.
- TicketSaver is for business use. It is not for children. We do not knowingly collect data from a person under 16.
2. The data we collect
Account data of users. Name, role (owner, office, crew member), trade class, email address, mobile number. The Company's office enters this data, or the user does.
Sign-in data. TicketSaver has no passwords. We send a one-time code or link by email, or a one-time code by text message. We keep a record of each sign-in request, a session cookie on your device, and the time of your last sign-in.
Ticket data. Customer name, job name, job address, purchase order number, on-site contact name and phone, who ordered the work, work dates, labor hours for each crew member, materials, the description of work, office notes, prices if the Company uses them, and the history of changes.
Files. Photos of the work, photos of receipts, and the picture of a customer signature, when a user adds them.
Company settings. Company name, address, phone numbers, license number, rates, price book, and notification email.
Technical data. IP address, browser type, the time of each request, and error reports. We use the IP address for security limits (for example, a limit on sign-in attempts). We keep identifiers in these limits only as a keyed hash.
QuickBooks Online data (only if an owner connects QuickBooks). See section 4.
We do not collect payment card data. We do not use advertising cookies or tracking pixels. We do not buy data about you from other companies.
3. How we use the data
We use the data only to:
- Operate TicketSaver: sign-in, tickets, review, approval, PDF and file exports.
- Send service messages: sign-in codes and links, invitations, and "ticket sent back" or "new ticket" notices.
- Keep the service secure: rate limits, an audit history of actions, and the investigation of faults and misuse.
- Give support when a Company asks for it.
- Meet legal duties.
We do not sell personal data. We do not share it for advertising. We do not use ticket data, files, or QuickBooks data to train artificial intelligence models.
4. QuickBooks Online connection
An owner of a Company can connect the Company's QuickBooks Online company to TicketSaver. The connection is optional. The owner signs in at Intuit; TicketSaver never sees the QuickBooks password.
What TicketSaver reads from QuickBooks:
- The Company's customer list: for each customer, the id, name, billing address, job address, email, and payment terms.
- The Company's list of products and services: for each item, the id, name, description, sales price, and if it is taxable.
- The records that TicketSaver made (their id, number, and status).
TicketSaver uses these lists to fill in tickets and invoices. TicketSaver does not read bank data, payroll data, or other accounting data.
What TicketSaver writes to QuickBooks: for an approved ticket, TicketSaver makes or updates one sales record (an invoice or an estimate), with the lines, quantities, and prices of that ticket. TicketSaver never changes the Company's customers or products and services in QuickBooks.
What TicketSaver stores: a copy of the Company's QuickBooks customer list and list of products and services (the fields above), the QuickBooks company id, the access keys ("tokens") that Intuit gives, and the id and number of each record it made. The tokens are encrypted. TicketSaver keeps the copy only for the Company that connected QuickBooks. TicketSaver does not copy the Company's other accounting data.
Who sees prices. Prices from QuickBooks are visible only to the Company's office users and owners. Crew members never see them.
Limits on use. We use QuickBooks data only to provide this feature to the Company that connected it. We do not sell it, share it with other parties, or use it for advertising.
Disconnect. An owner can disconnect in TicketSaver (Settings, QuickBooks) or inside QuickBooks at any time. On a disconnect in TicketSaver, we ask Intuit to cancel the tokens. When the owner disconnects QuickBooks, we delete the tokens and our copy of the QuickBooks lists. We also delete them when the account closes. Records that are already in QuickBooks stay in QuickBooks; they belong to the Company.
Intuit's own handling of data is described in Intuit's privacy statement.
5. Who gets the data
We give data only to the companies that help us operate the service, and only what each one needs:
| Company | Purpose | Data |
|---|---|---|
| Cloudflare, Inc. | Hosting, database, file storage, network security | All service data |
| Resend (Plus Five Five, Inc.) | Sending email | Email address, the message text |
| Twilio Inc. | Sending and checking sign-in codes by text | Mobile number |
| Intuit Inc. | QuickBooks Online, only when an owner connects it | The invoice or estimate lines, quantities, and prices that TicketSaver writes for the Company |
| Google LLC | Font files for the app screens | Your browser asks Google for the font files, so Google sees your IP address. No account or ticket data is sent. |
We also disclose data when the law requires it, or to protect the rights and safety of users and of DayTech. If DayTech sells or merges the TicketSaver business, the data can move to the new owner under this policy; we tell the Companies before that.
Within a Company: office users and owners see all tickets of their Company. A crew member sees only that crew member's own tickets. No Company can see the data of another Company.
6. Where the data is and how long we keep it
The data is stored and processed in the United States, on Cloudflare's network.
| Data | How long |
|---|---|
| Tickets, files, history, settings | While the Company has an account, then 90 days, unless the Company asks us to delete it sooner |
| Files of a ticket that was started and never sent | 45 days |
| Open sign-in codes and links | 10 to 15 minutes. The records of old sign-in requests and security limits are deleted in a daily cleanup. |
| Sessions | A crew member: 30 days. Office and owner: 30 days after the last use, 90 days at most. |
| Server logs | 7 days |
| Database recovery copies | 30 days |
| QuickBooks tokens | Until the owner disconnects QuickBooks, the account closes, or the tokens expire |
| Copy of the QuickBooks customer list and list of products and services | Until the owner disconnects QuickBooks or the account closes |
A Company can export its tickets as PDF, CSV, and Excel files at any time.
7. Security
- All traffic uses HTTPS.
- There are no passwords to steal. Sign-in codes are one-use and short-life, with limits on attempts.
- Sessions use a cookie that page scripts cannot read. Sign-in tokens and session ids are stored only as keyed hashes.
- Each Company's data is separated by Company in every database request.
- QuickBooks tokens are encrypted before they are stored.
- Actions on a ticket are written to a history.
No system is perfectly secure. If we learn of a breach of your Company's data, we tell the Company's owners without undue delay and as the law requires.
8. Your choices and rights
- Users: ask your Company's office to correct your name, number, or email, or to remove you. Removal ends your sessions at once.
- Companies: an owner can export data, disconnect QuickBooks, and ask us to close the account and delete the Company's data. Write to privacy@ticketsaverhq.com.
- Customers of a Company: ask the Company. If you write to us, we send your request to the Company.
- Depending on where you live (for example, Texas or California), the law can give you rights to see, correct, or delete personal data, and to appeal a refusal. Write to us and we answer within the time that the law gives.
Text messages. We send a text only when a crew member asks for a sign-in code. We send no marketing texts. Message and data rates can apply.
Cookies. TicketSaver uses only the cookies that are necessary to sign you in and keep you signed in. It keeps unsent tickets in your browser's storage on your device, so that work is not lost with no signal.
9. Changes to this policy
When we change this policy, we change the date at the top. For an important change, we tell the owners of each Company by email before the change starts.
10. Contact
Privacy questions: privacy@ticketsaverhq.com. Help with the service: support@ticketsaverhq.com.
DayTech Enterprises, LLC, a Texas limited liability company.