Privacy Policy

Effective date: October 13, 2026 · Last updated: November 3, 2026

This Privacy Policy explains how Four G Holdings and Developing LLC (“we”, “us”) collects, uses, and protects information in Lease Tickets (leasetickets.com), a business-to-business field-ticketing application used by oilfield service companies (each a “Customer Company”), their office staff, and their drivers.

1. Who this applies to

Lease Tickets is sold to businesses. Each Customer Company controls the information its users enter about its drivers, customers, leases, and tickets. For that information we act on the Customer Company’s behalf. Questions about a specific company’s records should go first to that company. Lease Tickets is not intended for consumers or for children under 16.

2. Information we collect

• Account information: names, work email addresses, usernames, role (for example admin, logistics coordinator, developer, driver), the company the user belongs to, and password hashes (we never store plain-text passwords). Password hashes are kept in a server-only database area that browsers cannot read; sign-in is checked on our server, which then issues a Firebase Authentication session.
• Driver information: driver name, username, assigned truck/unit, pay type and pay rate, and payroll records such as hours, settlements, deductions, and loan balances entered by the Customer Company.
• Ticket and job information: customer/operator, lease and well names, dates and times, service line, volumes (for example BBLs), hours, rates, charges, notes, invoice status, and similar field-ticket details.
• Photos and signatures: photos taken or attached by drivers, and handwritten signatures of drivers and customer representatives captured on the ticket, with names and times.
• Company branding and settings: company logo, DOT number, WHP number, emergency phone, billing settings, and the company’s Lease Tickets subscription (services and prices).
• Location: When a driver (or office user) takes a ticket photo, including the scale ticket photo, Lease Tickets asks the device for its current GPS location at that moment. The latitude, longitude and accuracy and the date and time the photo was taken are printed on the corner of the photo and saved with the photo on that ticket. They are visible to the people in that driver’s company who can see the ticket, and on printed tickets that include photos. Location is read only when a photo is taken, not in the background. If location permission is off or no GPS fix is available, the photo is stamped “GPS unavailable” and can still be saved. Office users may also save map coordinates for leases, wells, and destinations; those saved coordinates are copied onto tickets for that place.
• Technical information: basic logs kept by our hosting providers (such as IP address, browser type, and request times) for security and troubleshooting. Some data is also saved in your browser’s local storage so the app works offline.
• Contact form messages: information you send us through the Contact page.

3. How we use information

• To provide the service: create and sync tickets, print tickets and invoices, run billing and payroll reports, and sign users in.
• To keep each Customer Company’s data separate and to secure accounts.
• To send invoices to accounting tools a Customer Company chooses to connect (see Section 5).
• To provide support, fix problems, and improve the service.
• To meet legal, record-keeping, and safety obligations.

We do not sell personal information, and we do not use Customer Company data for advertising.

4. Where data is stored (service providers)

• Google Firebase / Google Cloud (Cloud Firestore and Firebase Authentication) stores ticket data, account data, photos, and signatures. Photos and signatures are stored inside the Cloud Firestore database.
• Netlify hosts the website and the server functions that handle sign-in and integrations.

These providers process data for us under their own terms and security programs. Our Cloud Firestore database is located in the United States (Google Cloud region us-south1, Dallas, Texas).

5. QuickBooks Online and OpenInvoice integrations

A Customer Company admin may choose to connect a QuickBooks Online company. Today the connection works like this:

• Intuit gives Lease Tickets an authorization that lets it create or look up customers, service items, and invoices in that QuickBooks company and read basic company information (company name). We use it only to send the invoices and related records the admin asks us to send.
• Each Customer Company has its own QuickBooks connection. It is shared by that company’s admins and cannot be used by other companies.
• The connection tokens Intuit issues are kept server-side in our Cloud Firestore database (encrypted at rest by Google Cloud). Database security rules block all browser access to them; only our Netlify server functions read them, to send requests to QuickBooks and to renew the connection automatically before it expires.
• Disconnecting: clicking Disconnect under Admin → Integrations deletes the saved connection and asks Intuit to revoke Lease Tickets’ access. You can also remove the app in QuickBooks (Settings → Apps / connected apps).
• Invoice references saved on tickets (such as a QuickBooks invoice number) stay with the ticket record, subject to Section 7.
• We do not sell QuickBooks data or use it for any purpose other than providing the integration.

For OpenInvoice, Lease Tickets creates PIDX XML and CSV invoice files for the Customer Company to download and upload itself. If an admin saves an OpenInvoice webhook address or API key, it is stored server-side for that company, blocked from browser access by our database rules (the key is never sent back to the browser), and used only to send that company’s invoices.

6. Sharing

Except for SMS opt-in data and mobile numbers, which are never shared (see section 6a), we share information only: with the Customer Company that owns it and the users it authorizes; with the service providers above; with integrations a Customer Company connects; when required by law or to protect rights and safety; or as part of a merger or sale of the business, with notice where required.

6a. Text messages (SMS)

Program: Lease Tickets truck availability texts, sent by Four G Holdings and Developing LLC to existing customers who opt in by signing our SMS consent form (see the SMS consent page).

What we collect and how we use it: your name, company, mobile phone number, the date and way you gave consent (a signed paper consent form), and your opt-out (STOP) status. We use this only to send the texts you asked for, to answer HELP requests, to honor opt-outs, and to keep the consent records mobile carriers require. Our SMS provider (Twilio) processes your number and messages only to deliver them on our behalf.

Message frequency varies, up to 1 message per day. Message and data rates may apply. Reply STOP to any message to opt out at any time, or HELP for help.

We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes. All other categories of information sharing in this policy exclude text messaging originator opt-in data and consent; this information will not be shared, sold, or rented to any third parties, affiliates, or lead generators.

See our SMS Terms.

7. Retention

Field ticket records are kept for five (5) years from the ticket date, in line with the Customer Company’s record-keeping policy. Archived tickets are hidden from daily work but kept for that period, and permanent deletion is blocked inside the 5-year window. After that, records may be deleted or exported at the Customer Company’s request.

When a Customer Company cancels: the company has 30 days after cancellation to export its data (each service line’s Records (5 yr) page in Admin has the archive downloads). We keep the company’s data, including account information, for 90 days after cancellation and then delete it, except where the law requires us to keep something longer. Copies in routine backups are overwritten on the normal backup cycle. Because ticket records may need to be kept for five years, each Customer Company is responsible for exporting and keeping its own copy before the export window closes.

8. Security

We use measures such as encrypted connections (HTTPS), hashed passwords, server-side sign-in with Firebase Authentication, database security rules that enforce each user’s role and company, server-only storage for password hashes, and two-step sign-in (an authenticator-app code) that is required for admin and developer accounts and optional for other users. Two-step secrets are stored server-side and encrypted, and recovery codes are stored only as hashes. No system is perfectly secure; please use strong passwords and tell us right away if you suspect unauthorized access.

9. Your choices

Users can ask their company admin to update or correct their information. Depending on where you live, you may have rights to access, correct, or delete personal information; send requests to us and, where the data belongs to a Customer Company, we will work with that company to respond.

10. Contact

Email: dlgarcia@fourghd.com · Phone: 432-701-2268 · or use the Contact page.
Mailing address: Four G Holdings and Developing LLC, 1508 S Colorado St, Monahans, TX 79756

11. Changes

We may update this policy. We will post the new version here and change the “Last updated” date. We will tell Customer Company admins about material changes by email or by a notice in the app.