Previous BravoRelay privacy policy — reference text extract, not a certified or complete original-page archive. Formatting was removed; use the dated current Privacy Policy for current disclosures. ← Back to BravoRelay Privacy Policy Last updated October 23, 2026 Plain-language policy written by us, not legal advice reviewed by an attorney. Who we are BravoRelay is operated by Bravo Relay LLC, Iowa City, Iowa. Privacy questions go to info@bravorelay.com . What we collect Account data: name, work email, role, and the organization and locations you belong to. Operational data you enter: tasks, fuel and ramp tickets, hangar layouts, aircraft and customer records, notes. Flight data: ADS-B observations from a receiver at your field, FAA flight-plan information, and third-party schedule feeds (such as JetInsight) for aircraft relevant to your airport. Pilot self-service data: when a pilot uses your QR code or order link, the tail number, contact details, and service requests they enter. These records belong to the operator, the same as any other operational data. Notification data: a push registration for each phone or browser that turns on alerts, so notifications reach the right device. Registrations follow whoever is signed in on that device. Technical data: device and browser information, error reports, and basic usage events used to keep the app working. Your operational data belongs to you Fuel tickets, aircraft movements, task records, hangar assignments, and customer billing detail entered into BravoRelay belong to the operator, not to us. We hold and process that data on your instructions so the software can do its job, and for nothing else. What we do not do with it: We do not sell it, rent it, or trade it. We do not use it for advertising or build profiles from it. We do not share one operator's data with another operator. We do not resell your movement, fuel, or customer records to brokers, fuel networks, or flight tracking services. We do not train outside products on your customer or billing records. How we use it To run the service for your FBO: show your crew what is inbound, dispatch and track work, produce tickets and reports, send push and email notifications you have enabled, support you, and bill you. Aggregate, non-identifying counts may be used to keep the service reliable and to improve aircraft recognition at your own field. Where flight data comes from Live aircraft positions come from ADS-B receiver hardware installed at your own field and read directly by your BravoRelay account. It is not licensed from a commercial flight tracking service, so no third-party attribution, redistribution limit, or display licence applies to what you see on your board. Filed flight plan and departure information comes from public FAA sources, and is advisory only. Where you connect a schedule feed such as JetInsight, we read only the legs for your airport and use them to inform your board; the feed never moves aircraft on its own. Who it is shared with Only with service providers needed to operate: cloud hosting and database, payment processing, email and push delivery, and aviation data sources such as the FAA. Each gets only what its function requires. We also disclose data where the law requires it. Public demo The demo at /try uses simulated data. We record which demo screens are opened and how long visitors stay, anonymously, so we can improve it. Anything you type into the demo's feedback box, including an email address you choose to give, is sent to us so we can reply. Retention, export, deletion We keep your data while your account is active, and you can export tickets, invoice lines, tasks, and aircraft records to CSV at any time, including while cancelling. After cancellation we hold your organization's data only so you can still retrieve it, and we delete it as soon as you ask. Ask at any time and we will confirm when it is done. We keep only what tax or legal rules require us to keep. Diagnostic logs, scheduler history, and demo measurement are purged automatically on a rolling schedule. Security Data is encrypted in transit, access is scoped per organization at the database level, and staff access is limited to what support requires.