Privacy Policy

This Privacy Policy explains how Beacon Airport Systems, Inc. ("Beacon," "we," "us," or "our") collects, uses, shares, and protects information in connection with the Beacon website (beaconairports.com) and our general aviation airport management platform, including the Hangar Waitlist tool and related features (together, the "Service").

By using the Service, you agree to the collection and use of information as described in this Policy. If you do not agree, please do not use the Service.

1. Scope: Two Kinds of Information

The Service is used by airport managers and their staff ("Account Holders") to manage information about their own hangar waitlist customers, based aircraft, and insurance records ("Customer Data").

• For information about you that you provide to create and manage your own Beacon account (Section 2.1 below), Beacon is the data controller.
• For personal information that an Account Holder or their organization submits to the Service about a third party — for example, a hangar waitlist applicant's name, contact details, or aircraft information, or an insurance certificate naming individuals — Beacon acts as a data processor / service provider on behalf of that Account Holder's organization, which remains responsible for that information and for having the right to share it with us.

If you are a hangar waitlist applicant, tenant, or aircraft owner whose information was submitted to Beacon by an airport, and you have a question about that information, please contact the airport directly. We will assist the airport in responding to your request.

2. Information We Collect

2.1 Account information

When you create a Beacon account, we collect your name, email address, and password (or, if you sign in via a magic link, no password at all), along with your role and team/airport association. Password-reset, sign-up confirmation, email-change, and re-authentication emails are sent to verify these actions.

2.2 Waitlist and tenant information

Information Account Holders enter or import into the Service about their hangar waitlist applicants and based tenants, including:

• Name and contact details (email, phone).
• Aircraft make, model, and tail/N-number.
• Hangar type preference and waitlist request status (offered, assigned, withdrawn).
• Internal staff notes about customer conversations.
• Responses submitted through a waitlist link (for example, confirming continued interest), which do not require the recipient to create an account.

2.3 Insurance documents

If an Account Holder uploads a certificate of insurance (such as an ACORD 25 form) for a based aircraft, we collect the document itself and use automated document reading to extract details such as policy number, insurer, insured name, effective and expiration dates, and any additional insured parties named on the certificate, so the airport can track coverage and be alerted before it lapses.

2.4 Payment information

If an airport subscribes to a paid plan, billing and payment card details are collected and processed by our payment processor, Stripe. We do not store your full payment card number on our servers.

2.5 Marketing and inquiry information

If you request a demo or submit our contact form, we collect the information you provide (such as name, email, airport/organization, and message) to respond to your inquiry.

2.6 Usage and device information

Standard technical information such as IP address, browser or device type, and general usage patterns, collected automatically to operate, secure, and improve the Service.

3. How We Use Information

We use the information described above to:

• Provide and operate the Service, including hangar waitlist tracking, based-aircraft records, and insurance monitoring.
• Automatically extract data from uploaded insurance certificates to pre-fill and verify policy details, and to send expiration alerts.
• Send transactional messages (account, billing, and insurance-expiry notifications) and, on an Account Holder's behalf, waitlist communications to their own applicants.
• Process payments and manage subscriptions.
• Respond to demo requests and contact-form inquiries.
• Provide customer support, and, where necessary for troubleshooting, access Customer Data with appropriate authorization.
• Monitor, secure, and improve the Service, and prevent fraud or misuse.
• Comply with legal obligations.

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

4. How We Share Information

4.1 Within an Account Holder's organization

Team members and administrators of an airport's Beacon account can see the waitlist, tenant, and insurance information associated with that airport, consistent with the roles and permissions their organization assigns them.

4.2 Service providers

We share information with third-party service providers who process it on our behalf, under contractual confidentiality and data-protection obligations, including:

• Supabase — hosting, authentication, and database infrastructure.
• Stripe — payment processing and subscription billing.
• Lovable — our application platform provider, which delivers transactional and waitlist emails on our behalf and provides the AI-assisted document reading used to extract data from uploaded insurance certificates (which may in turn route requests to third-party AI model providers to perform that extraction).

4.3 Legal and safety reasons

We may disclose information if required by law, subpoena, or legal process, or if we believe in good faith it is necessary to protect the rights, property, or safety of Beacon, our customers, or others.

4.4 Business transfers

If Beacon is involved in a merger, acquisition, financing, or sale of assets, information may be transferred as part of that transaction. We will notify affected customers of any change in ownership or use of their information.

4.5 We do not sell personal information

We do not sell personal information to third parties, and we do not share it with third parties for their own independent marketing purposes.

5. Data Retention

We retain Account Holder and Customer Data for as long as the associated Beacon account is active. If an account is closed, we retain information for a reasonable period to allow export or reactivation and then delete or de-identify it, except where we are required or permitted to retain it (for example, billing records needed for tax or accounting purposes, or as instructed by the Account Holder's organization).

6. Your Privacy Choices

If you are an Account Holder, you may access and correct most of your account and Customer Data directly within the Service, export your data, or contact us at privacy@beaconairports.com to request access, correction, deletion, or export. We do not sell or share personal information for cross-context behavioral advertising.

If your information was submitted to Beacon by an airport (for example, as a waitlist applicant or based tenant) rather than provided directly by you, please contact that airport to exercise rights over your information; we will assist the airport in responding to your request within a reasonable time.

7. Data Security

We use commercially reasonable measures designed to protect information, including encryption of data in transit and at rest through our infrastructure providers, role-based access controls so that an airport's staff see only the data their role permits, and restricted handling of insurance documents and extracted policy data. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

8. Children's Privacy

The Service is intended for airport management professionals and is not directed to individuals under 18. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us so we can delete it.

9. International Users

Beacon is operated from, and its infrastructure is hosted in, the United States. If you access the Service from outside the United States, your information will be transferred to and processed in the United States, which may have different data-protection laws than your home jurisdiction.

10. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will notify affected users by updating the effective date above and, where appropriate, through the Service or by email. Continued use of the Service after changes take effect constitutes acceptance of the updated Policy.

11. Contact Us

If you have questions about this Privacy Policy or wish to exercise your privacy rights, contact us at: