Main Technician Dispatch ("we", "our") provides work order and property maintenance software for property management teams, their technicians and, when a property turns it on, its residents. This policy explains what data we collect, why, who helps us process it, and how it is protected.
Who is responsible
Main Technician Dispatch is responsible for the service and for the accounts described in this policy. Property management companies that use Main Technician Dispatch decide which team members and residents they add and what information they enter about them, and they are responsible for that information; we process it on their behalf to provide the service. You can reach us about anything in this policy at [email protected].
What we collect
Team accounts: name, email address, phone number, role, language and workspace. Passwords are handled by our authentication provider and are never visible to us. Your 4-digit Main Technician Dispatch PIN is stored only as a salted hash.
Team member records: the date you joined the company, who you report to and, if you add one, an emergency contact (name, relationship and phone number). Only you and your workspace's managers and supervisors can see them, never other team members. Only you can enter or change your emergency contact.
Fingerprint or face recognition sign-in (passkeys): if you choose to use it, your fingerprint or face never leaves your device. We only store the public key your device creates, which cannot be used to rebuild your biometric data.
Work and operations data: work orders (titles, descriptions, priority, status history, notes and photos), Punch / Go-Back checklists, make-ready boards, inventory and its movements, equipment records, vendor contact details, team messages, notices, events and calendars that your team enters.
Files you import: PDF or image work orders you upload or open with the app ("Open with" / "Send to"). They are stored privately for your workspace. Their text is read on your own device; we do not send them to artificial-intelligence services.
Resident information (only when a property uses the resident portal): name, email, phone number and apartment; maintenance requests with their description, photos, permission to enter and availability; and the notifications and property posts they receive.
Resident profiles kept by the property's staff: household members, door, gate or access codes, permission to enter, vehicles, emergency contact, and an optional photo and ID document. These are visible only to authorized office staff of that property and are stored in private storage.
Usage data: role, activity timestamps and completion history used for team features such as points, trophies and weekly summaries.
Optional team location: if your workspace enables the Map module and its time clock, your company confirms its location policy, and you accept the location notice and allow your browser to use location, we collect your device's latitude, longitude, accuracy, report time and the work action associated with a report. Reporting runs only while the app is open and you are clocked in, outside lunch. Your workspace's authorized managers and supervisors can see your latest position for safety and dispatch. You can decline or stop sharing in Profile › Preferences.
Time clock and pay (optional): if your workspace uses the time clock, we record clock-in, lunch and clock-out times, corrections made by managers with their reason, and on-call travel time. Managers and supervisors may enter a worker's hourly pay, which is used to calculate labor, on-call travel and overtime costs; it is visible only to authorized managers and supervisors, never to technicians.
Performance reviews (optional): if your workspace turns on performance reviews, a manager can write a review of a team member for a period: an overall rating, written comments, and numbers Main Technician Dispatch counts from the work already in the app (completed work orders, Punch / Go-Back, points, monthly goals, emergencies started in time, resident ratings already shared with that person and, with the time clock, days worked). Only the person reviewed (once it is shared with them), the reviewer and the managers above that person can see it; teammates never can. The person may add a comment when confirming they saw it.
On-site clock-in check (optional): if your workspace turns on “Clock in only at the property”, when a technician or supervisor clocks in or comes back from lunch, their device’s location is read once and sent to check that they are inside the property area. It is used only for that check and is not stored; the shift only records whether it was verified on site.
Technical data: sign-in session, theme and language preferences saved in your browser, and, if you turn on notifications, the push address your browser gives us to deliver them. Our hosted website also loads a Cloudflare Web Analytics / Insights beacon to measure visits and page performance.
How we use it
To run the service: assign and track work, show residents the status of their requests (including when the technician is on the way or has arrived at the property, never the technician’s location), and send the notifications and emails you or your property expect.
When your workspace uses the time clock: to calculate hours, on-call travel and overtime under the rules your company sets and, if the on-site rule is on, to confirm that paid time starts at the property. Your employer is responsible for its timekeeping policy and for paying wages and overtime as the law requires.
When your workspace uses performance reviews: to show the reviewer and the person reviewed the numbers for the review period and to keep a record of the review, its sharing and its acknowledgment. Your employer is responsible for its review policy and for the decisions it makes.
When the optional Map module is enabled and you agree, to show authorized managers and supervisors where help is available during a shift. Your employer is responsible for its location policy and how it uses this information.
To keep accounts secure: sign-in, PIN and passkey checks, an automatic bot check on the sign-in screens, rate limits and audit records (for example, who changed inventory).
To measure website visits and page performance using Cloudflare's hosting analytics.
To answer support requests you send us.
What we don't do
We never sell your data or share it for advertising.
We never require a photo to close a work order.
We never collect or store payment card details. Payments are not active today; when they are, billing will happen on the payment processor's own secure page.
Service providers we use
Supabase: database, sign-in and private file storage, hosted in the United States.
Cloudflare: serves the app and website, protects them with encrypted connections, and provides website visit and performance measurements through Web Analytics / Insights. It also runs an automatic security check on our sign-in, sign-up, password-reset, resident sign-in and fingerprint sign-in screens to block automated abuse; it reads technical signals from your browser and device (such as your IP address and browser type), never your password.
Resend: delivers our emails (invitations, sign-in links and codes, notices and alerts).
Browser push services (operated by the maker of your browser or device, such as Google, Apple, Microsoft or Mozilla): deliver push notifications only if you turn them on.
Google Fonts: your browser loads the app's fonts from Google, which receives your IP address for that request.
Map and address services: when you open the Map, your browser requests map styles and tiles from OpenFreeMap; the service receives network request information, such as your IP address, and requests for the map areas being viewed. When you search for a property address, the search text is sent to OpenStreetMap's Nominatim service and, if needed, the Photon service hosted by Komoot.
Weather (Open-Meteo): when a workspace leaves “Weather effects” on and its property is on the map, the team app and the resident portal ask Open-Meteo for the current weather at the property's approximate location (its map point rounded to about 1 km), about every 20 minutes while the app is open, to show soft rain or snow behind the screens. Open-Meteo receives those approximate property coordinates and network request information, such as your IP address. Your own device's location is never used for this, and nothing about you is included in the request. A workspace can turn it off in Profile › My workspace › Ambience.
Vercel: backup hosting; anyone who reaches it is sent to our official addresses.
Microsoft: distributes the Windows app through the Microsoft Store. Microsoft's own privacy statement applies to the Store.
These providers process data only to provide their service to us.
How your data is isolated and protected
Main Technician Dispatch is multi-tenant: every company's data is walled off from every other company's at the database level (row-level security), not just in the app's interface. No user can see or modify another company's work orders, residents, inventory or team data. Data travels over encrypted connections, files are kept in private storage and opened through short-lived links, and repeated wrong PIN attempts lock the PIN temporarily.
How long we keep it
Workspace data is kept while the company uses Main Technician Dispatch, or until the company or the person asks us to delete it.
When you leave a team or are removed from it, your emergency contact is deleted right away and you are no longer shown as anyone's manager. The date you joined stays in that team's history.
The Map keeps only the latest reported position, rather than a route history. That position is deleted when you start lunch, clock out or withdraw location consent. Closing the app stops new reports but does not itself delete the last position. A scheduled hourly cleanup deletes positions whose last report is more than 16 hours old. We keep a separate record of when location consent was granted or withdrawn and the notice version, where supplied.
When the office marks a resident as moved out, we erase that resident's name, email, phone, household, door and gate codes, permission to enter, access notes, vehicles, parking, emergency contact, lease dates and office notes; remove the email and phone from their sign-in account, close it and block it; clear the access notes and availability they wrote on their requests; remove their contact details from work orders; and delete their photo and ID files.
What stays after a move-out, without the resident's name or contact details: the apartment's maintenance history (request descriptions and photos of the problem, work orders and their notes and photos) and an internal record that the move-out happened.
Copies in our database provider's backups remain until those backups are replaced on its schedule, and our email provider keeps delivery records of emails already sent for a limited time.
Local integrations (Windows app)
The Windows app can register as a handler for PDF and image files ("Open with Main Technician Dispatch") so you can open a work order file directly into the app. It only processes files you explicitly choose to open. Main Technician Dispatch does not scan, access or monitor any other files on your device.
Your rights
You can ask for a copy of your data, ask us to correct it, or ask us to delete your account by writing to the address below. Company administrators can deactivate or remove team members directly in the app. Residents can also ask their property's office to update or remove their information.
Children
Main Technician Dispatch is a tool for property teams and adult residents. It is not directed at children under 13 and we do not knowingly create accounts for them. A property may list household members in a resident's profile; staff should enter only what is needed.
Changes to this policy
If this policy changes materially, we'll update the date above and notify active company administrators by email.