Privacy Policy

What we collect

AOG Dispatch is operated by Boxx Aerospace Enterprise LLC, which is responsible for the personal information described here. "We", "us" and "our" mean Boxx Aerospace Enterprise LLC.

From operators posting work: your name, phone number, email address, optionally a company name, and the details of the job — tail number, aircraft type, airport, and what is wrong with it.

From mechanics: your name, phone, email, FAA mechanic certificate number, the ratings you hold, Inspection Authorization status and expiry, home base airport, years of experience, and liability insurance details where you provide them.

From a mechanic we invite to join, before they have applied: the name we know them by and, if we note it, where we met them, kept with the invite link we sent them so we can see whether it was used. If it never is, both are deleted about three months after we sent it. We do not keep their phone number or email address for this: we send the link ourselves.

From everyone with an account: a password, stored only as a salted hash we cannot reverse, and — if you turn on two-step sign-in — a secret used to check your codes and a set of one-time recovery codes.

Photos you attach to a job, stored privately and shown only to the people on that job. The location, device and time a phone camera writes into a photo are removed before anyone else sees it.

From a mechanic driving to a job, only if they choose to share it in the app: where their phone is, while they are on their way. One position is kept — the latest — never a route, and it is deleted when they start work, stop sharing, or the job ends.

Automatically: your IP address, used for rate limiting so nobody can flood the job board or guess their way into an account.

If you use the AOG Dispatch app on a phone and turn on job alerts: an address for your phone issued by Apple (on iPhone) or Google (on Android), so we can send it a notification. It identifies the app on that phone, not you; it is deleted when you sign that phone out, turn alerts off, or close your account, and when Apple or Google tell us it no longer works. We also record a name for each signed-in device — "AOG Dispatch on iPhone" — so you can see and sign out your devices.

What we do not collect

We do not store your card number. Payments go directly to Stripe, and we keep only the identifiers Stripe gives us so we can match a payment to a job.

We do not track you across other websites, we do not run advertising, and we do not sell or rent personal information to anyone.

When you rank the job board by distance, we do not receive your location. Your browser will ask your permission — but that calculation happens on your device. Airports are public knowledge, so we send your browser the airport coordinates and it does the arithmetic. Your position is never sent to us, never stored, and never appears in a web address or a server log. The only location we ever receive is the one a mechanic chooses to share while driving to a job, described above.

Why we hold it

To do the thing you came here for: match a grounded aircraft to a mechanic who is near enough, certificated for the work, and able to take it.

To verify that a mechanic is who they say they are, by comparing the details they give us with publicly available FAA airman data.

To take and settle payment, and to handle refunds.

To keep the platform safe — rate limiting, fraud prevention, and an audit trail of administrative actions.

Who else sees it

Mechanics considering a job see the aircraft and the discrepancy. Your contact details are shared with the mechanic once a job is matched, because they need to call you.

Operators see a mechanic's name, home base, ratings, experience and verification status.

We do not sell your mobile number, or share it or your consent to texts with anyone for their marketing. Text-message opt-in data is never shared with third parties.

Messages on a job are between the operator and the mechanic they chose, and our dispatch team. Dispatch can read them, to resolve problems, investigate a report, and keep people safe; the chat screen says so to both people, and each time a dispatcher opens a conversation it is recorded. Nobody else can read them.

If a mechanic shares their location while driving to a job, the operator on that job and our dispatch team see how far away they are, on a street map. Nobody else does. The map itself comes from OpenFreeMap: to draw it, the viewer's device asks OpenFreeMap for the map of the area around the aircraft, so OpenFreeMap learns which area is being looked at and the device's IP address, as any website you load does. It is never sent who is on the job or where the mechanic is — we draw both on top of the map ourselves. Tapping "See on map" or "Open in Maps" opens that one point in your own maps app.

• —Stripe, for payments, payouts, and identity verification.
• —Our email provider, to send notifications you have asked for.
• —Twilio, to send text messages — only if you ticked "Text me updates about this job" when posting it. Twilio receives the phone number and the text: the tail number, the airport, and the mechanic's name and number once one is matched. Reply STOP to any text to stop them, HELP for help.
• —Apple and Google, to deliver job alerts to the phone app, if you turn them on. They receive the alert's text — the airport, the aircraft type and tail number, and what is wrong with it; for an alert about your own job, the mechanic's name and the first line of a message they sent — and the address of your phone, and nothing else about you.
• —Cloudflare, Vercel, Apple and Google, to check that a sign-up or a job post comes from a person using a genuine copy of the app or website rather than a script. They receive technical signals from your browser or phone and its network address — not your name, email or job details — and tell us only whether the check passed.
• —Our hosting and database providers, who store the data on our behalf.
• —Law enforcement, where we are legally required to.

Alerting, and what we deliberately leave out

When something goes wrong we send an operational alert to a channel our own team watches. Those alerts leave our infrastructure, so they carry only what is needed to understand the fault — identifiers, error codes, counts.

They never carry email addresses, phone numbers or certificate numbers. That is enforced by an allow-list in the code rather than a list of things to strip out, so a field added in future is left out by default rather than sent by accident.

Public information

FAA airman certificate data is published by the FAA and is public. We compare what a mechanic tells us against it. We are not the source of that data and cannot correct it — corrections go to the FAA.

How long we keep it

Account and job records are kept while your account is open and for as long afterwards as we need them for tax, accounting and dispute purposes.

Short-lived things are swept automatically: password reset tokens, sign-in rate-limit counters, expired sessions, and invitations to mechanics that were never used.

A mechanic's shared location is deleted the moment they start work or stop sharing, and swept within two hours from any job they are no longer driving to.

A security log of sign-ins, failed sign-ins, lockouts, two-step sign-in changes, password resets and changes to a mechanic's payout status, with the IP address each came from, is kept for a year and then deleted. It is how we answer "was that me?" and spot someone guessing passwords, and the database is set to refuse any change to it.

Records relating to maintenance and payment are kept longer, because both you and the mechanic may need to refer to them.

Maintenance records are not ours to keep

The maintenance record entry required by 14 CFR §43.9 is made by the mechanic directly in your aircraft's logs. We never hold it. Anything this platform shows about completed work is a summary, and deleting your account does not affect the signed entries in your logbooks — they are yours, and they stay with the aircraft.

Your choices

You can update your details from your account at any time. Mechanics can stop receiving job alerts by going off duty, which takes effect immediately.

You can close your account yourself in the AOG Dispatch app, under Account → Close account. That removes your sign-in, your devices and your alerts at once. It waits while a job you are part of is still open or still owed money, and says which, so nobody on the other end of a job is left without a way to reach you.

Closing an account keeps the records of jobs you took part in — the job details, payments and completion summaries — for the tax, accounting and dispute reasons above, and the app tells you so when you close it.

You can also ask us for a copy of what we hold about you, or ask us to delete it. Some records we may need to keep for legal or accounting reasons, and we will tell you which and why rather than quietly keeping them.

Security

Passwords are stored as salted hashes. Two-step sign-in is available, and required for accounts that can change who is allowed to work on the platform. Administrative actions are written to an audit trail that cannot be edited after the fact.

No system is perfect. If you find a security problem here, tell us before you tell anyone else and we will fix it.

Children

This service is not for anyone under 18 and we do not knowingly collect information from children.

Changes

If this policy changes materially, the effective date above changes with it.

Contact

You can close your account yourself at any time: in the app, under Account → Close account, or on our website at aog-dispatch.com/delete-account, which also says what is deleted and what is kept.

To ask what we hold about you, or to ask us to delete it, use the contact route listed on our website.