Privacy Policy

This policy explains what TechnicianOps does with personal information. It applies to three groups of people: the owners and office staff who hold accounts, the technicians who use the mobile app, and the customers of the businesses that run on the platform.

TechnicianOps is operated by Joshua Lovelace, trading as TechnicianOps. You can reach the operator at [email protected]. Throughout this policy, “we” means that company, “the Service” means the TechnicianOps platform, and “your organization” means the field service business whose account you belong to.

For account and billing information, we decide how the data is used and we are responsible for it.

For everything your organization puts into the Service — its customers, jobs, invoices, photos, notes — your organization decides, and we act on its instructions. If you are a customer of a business that uses TechnicianOps and you want your records changed or deleted, that business is the right place to ask; we will help them do it.

• Account information: name, email address, phone number, a hashed password, and multi-factor settings.
• Organization records entered by your staff: customers and contacts, service addresses, jobs and schedules, estimates and invoices, payment status, notes, uploaded files, photos, signatures and materials used on a visit.
• Technician app data: which stops were visited and when, clock-in and clock-out times, and device location while a shift is running.
• Billing data: plan, billing cycle, and payment status. Card numbers are handled by our payment processor and never stored on our servers.
• Operational records: session cookies, an audit log of significant actions, and technical logs kept to keep the Service secure and reliable.

We do not buy personal information from data brokers, and we do not run advertising on the Service.

Information is used to run the features you asked for: building the schedule, optimising routes, sending confirmations and reminders, taking payment, producing reports, and requesting reviews after a job is finished.

It is also used to keep accounts secure, to answer support requests, to bill correctly, and to meet legal obligations. We do not sell personal information, and we do not use your organization's records to train models for anyone else.

The technician app reports device location so the office can see route progress and give customers an accurate arrival time. Location is collected only while a technician is clocked in, and it is visible to that technician's own organization — never to other organizations on the platform.

Location history is kept for 90 days and then deleted. It is never sold, and it is not used to build any profile beyond the working day it belongs to.

Confirmations, day-before reminders, on-my-way texts, invoices and review requests are sent by your organization through the Service, using its name as the sender. Your organization is responsible for having the right consent to contact those people.

Recipients can stop text messages by replying STOP, and every email carries an unsubscribe path for marketing content. Transactional messages about a booked appointment or an unpaid invoice may continue, because they are part of the service the customer asked for.

Every record in the Service belongs to exactly one organization, and requests are scoped to the organization the signed-in user belongs to. One company can never see another company's customers, schedule or financials.

Inside an organization, access follows the roles its administrators set: office staff, technicians and owners see different things. Significant actions are written to an append-only audit log.

We use a small number of providers to run the Service. They act on our instructions and may only use the data to deliver their part of it.

The current list of named sub-processors is available on request from [email protected], and we will give notice before adding a new one that handles personal data.

The Service sets a session cookie that keeps you signed in, and, if you choose it, a cookie that remembers a trusted device so you are not asked for a second factor every time. There are no third-party advertising or tracking cookies.

Records are kept while an organization's account is active. After an account closes, data is retained for 30 days so it can be recovered or exported, then deleted from live systems; encrypted backups age out within 35 days.

An organization can export its customer list and job history to CSV at any time, including on the way out. Invoices and payment records may be kept longer where tax or accounting law requires it.

• Traffic is encrypted in transit, and passwords are stored only as salted hashes.
• Multi-factor authentication is available to every account and can be required by an organization.
• Access is scoped by role, and significant actions are recorded in an audit log that cannot be edited.
• Access to production systems is limited to staff who need it and is reviewed quarterly.

No system is perfectly secure. If a breach affects your data, we will notify affected organizations without undue delay and, where the law requires, the relevant authority.

Depending on where you live, you may have the right to see the personal information held about you, correct it, export it, or have it deleted, and to object to certain processing.

If you hold a TechnicianOps account, write to [email protected]. If your details are in the Service because you are a customer of a business that uses it, contact that business — they control the record, and we will assist them. We will not charge you for a reasonable request, and we do not discriminate against people who make one.

The Service runs on servers in the United States. If we transfer personal data out of the region it was collected in, we use a lawful transfer mechanism such as the Standard Contractual Clauses.

The Service is a business tool and is not directed to children. We do not knowingly collect personal information from anyone under 16; if that happens, tell us and we will delete it.

We update this policy when the Service changes. Material changes are announced in the Service or by email before they take effect, and the date at the top of this page always shows the current version.

Privacy questions, requests and complaints: [email protected]. A postal address is available on request.