TicketSaver Sign in

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").

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:

  1. Operate TicketSaver: sign-in, tickets, review, approval, PDF and file exports.
  2. Send service messages: sign-in codes and links, invitations, and "ticket sent back" or "new ticket" notices.
  3. Keep the service secure: rate limits, an audit history of actions, and the investigation of faults and misuse.
  4. Give support when a Company asks for it.
  5. 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:

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:

CompanyPurposeData
Cloudflare, Inc.Hosting, database, file storage, network securityAll service data
Resend (Plus Five Five, Inc.)Sending emailEmail address, the message text
Twilio Inc.Sending and checking sign-in codes by textMobile number
Intuit Inc.QuickBooks Online, only when an owner connects itThe invoice or estimate lines, quantities, and prices that TicketSaver writes for the Company
Google LLCFont files for the app screensYour 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.

DataHow long
Tickets, files, history, settingsWhile 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 sent45 days
Open sign-in codes and links10 to 15 minutes. The records of old sign-in requests and security limits are deleted in a daily cleanup.
SessionsA crew member: 30 days. Office and owner: 30 days after the last use, 90 days at most.
Server logs7 days
Database recovery copies30 days
QuickBooks tokensUntil the owner disconnects QuickBooks, the account closes, or the tokens expire
Copy of the QuickBooks customer list and list of products and servicesUntil 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

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

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.