Bug Beacon Privacy Policy
Last updated: October 7, 2026
Bug Beacon is a product of Airship Labs LLC ("Airship Labs," "we," or "us"). This policy explains what Bug Beacon collects at bugbeacon.ai, in the Bug Beacon dashboard, and through the Bug Beacon report form that our customers add to their own websites, and what we do with it. Our Terms of Service also apply.
Two kinds of people
- Customers are the developers and teams who sign up for Bug Beacon and add it to their websites. For customer account data, Airship Labs decides how the data is used.
- Reporters are the people who send a bug report through a customer's website. For reports, Airship Labs works on the customer's behalf. The customer decides to collect the report and where it goes. We process it only to deliver it to them. If you're a reporter, the website you were using is responsible for your report. Their privacy policy applies to it, and you can contact them about it.
What we collect
From customers
- Your GitHub profile. You sign in with GitHub. We receive your GitHub ID, name, email address and profile picture. We don't receive your GitHub password.
- Your Bug Beacon settings. We store your applications, their allowed website addresses, and the GitHub Project each one delivers to.
- Your GitHub Project token. You give us a GitHub token so Bug Beacon can add reports to your Project. We store it encrypted and use it only for that.
- Sign-in sessions. We keep a session record with your IP address and browser details. Sessions last up to 7 days.
- Messages to us. If you email us, we receive your message and anything you attach.
From reporters, on behalf of customers
- The report. The title and description the reporter types.
- The website address. The origin of the site the report came from, such as https://app.example.com, not the full page address.
- Abuse protection. The form uses Cloudflare Turnstile to check that the reporter is a person. Turnstile processes the reporter's IP address and browser and device signals. We store a keyed digest of the IP address, not the address itself, to enforce rate limits.
The Bug Beacon button and form don't read the customer's page content, full page address, cookies or browser storage. They don't take screenshots or recordings and don't fingerprint the reporter's browser. Reporters choose what they type, and the form asks them not to include passwords or other secrets.
From visitors to bugbeacon.ai
- The waitlist. If you join the waitlist, we collect your email address and, if you choose, which issue tracker your team uses.
- Analytics. Our site pages use Vercel Web Analytics and Speed Insights. Web Analytics doesn't use cookies, doesn't track you across other sites, and discards visitor sessions after 24 hours, so we see only totals. Speed Insights measures page speed along with the page address, browser and device type. Neither runs inside the report form on customer websites.
- Request logs. Vercel hosts Bug Beacon and processes technical request information, including IP addresses, to deliver pages and protect against abuse.
How we use it
We use this information to run Bug Beacon: to sign you in, deliver reports to your GitHub Project, show delivery status, prevent abuse, fix problems, understand how the site is used, send the waitlist updates you asked for, and answer your messages.
We don't sell personal information or use it for advertising. We don't use reports to train AI models.
Who we share it with
We use these service providers to run Bug Beacon. Each one gets only what it needs to do its job for us.
| Provider | What it does |
|---|---|
| Vercel | Hosts Bug Beacon, runs scheduled delivery, and provides Web Analytics and Speed Insights |
| Neon | Hosts our PostgreSQL database |
| Cloudflare | Turnstile abuse protection on the report form |
| Clerk | Owner sign-in. GitHub is the only social connection. Clerk holds the dashboard session. |
| GitHub | Identifies the owner during Clerk sign-in, and receives delivered reports in the customer's GitHub Project |
| Loops | Stores waitlist sign-ups and sends waitlist emails |
| Google Workspace | Email you send to support@airshiplabs.com. We also use AI assistant tools from our service providers to help read and reply to email, and they process messages only to provide that service to us. |
When Bug Beacon delivers a report, it becomes a draft item in the customer's GitHub Project. From then on, GitHub holds it under the customer's GitHub account and GitHub's terms.
We may also share information when the law requires it, to protect the rights or safety of Airship Labs or others, or with a buyer or successor if Airship Labs is merged or sold.
Cookies
Bug Beacon uses only necessary cookies: Clerk's session cookies for the owner dashboard and a short-lived encrypted cookie (up to 30 minutes) that links your optional waitlist answer to your email. We don't use advertising or analytics cookies.
How long we keep it
- Reports. We delete report text from Bug Beacon 30 days after it's received. The copy in your GitHub Project stays until you delete it there.
- Account data. We keep it while your account is open. When you close your account, we delete your account, applications, tokens and any remaining reports within 30 days.
- Rate-limit records expire shortly after their time window ends. Dashboard sessions are Clerk sessions. They end when you sign out or when Clerk ends them.
- Waitlist data. We keep it until the waitlist ends or you ask us to delete it. We may keep an unsubscribe record to respect your choice.
- Our providers keep their own logs for the periods in their policies.
Your choices and rights
You can ask us for a copy of your information, or ask us to correct or delete it, by emailing support@airshiplabs.com. We'll respond within 30 days. We may keep information when the law requires it. Waitlist emails include an unsubscribe link.
If you're a reporter, please contact the website where you sent the report. If you contact us instead, we'll pass your request to that customer and help them respond.
Where data is stored
Bug Beacon is hosted in the United States. If you use it from elsewhere, your information is transferred to and processed in the United States.
Security
We encrypt data in transit, encrypt GitHub tokens at rest, check ownership on every dashboard action, and keep report text out of our logs. No system is fully secure. If you find a security issue, email support@airshiplabs.com.
Children
Bug Beacon is for businesses and adults. It isn't directed to children under 13, and we don't knowingly collect their information. Customers may not add Bug Beacon to sites or apps directed to children under 13. If you believe a child has sent us information, contact us and we'll delete it.
Changes to this policy
If we change this policy, we'll update the date at the top. If a change is significant, we'll make that clear on this page or email account holders.
Contact us
Airship Labs LLC. Email support@airshiplabs.com.