Privacy Policy
Last updated: (version 2026-11-17)
AOG Alerts is operated by Low-Coders LLC (d/b/a AOG Alerts) ("we," "us"). This policy describes information collected through our marketing website and app, and how we use it. It is not a promise that every transmission or record is free of risk.
1. Introduction
This policy covers the AOG Alerts marketing website at aogalerts.com, the app at v2.aogalerts.com, and the same app software on our test host. The marketing website explains the service and links to the app. People use the app to post aircraft-on-ground and maintenance requests, read public request details, and, after they unlock a request, see the locked details and send a quote.
2. Information We Collect
The information involved depends on whether you visit the marketing website or use the app:
- Marketing website (aogalerts.com). The marketing website does not ask you to register or submit an AOG. It stores your cookie choice in your browser under
aog_marketing_cookie_consent, along with the preference version and the time of your choice. You can reopen Cookie preferences in the marketing website footer. The marketing website currently does not load analytics or advertising cookies. Hosting services may process standard technical request information, such as IP address and browser headers, to deliver the website. Its aircraft photograph is loaded from Unsplash, so your browser makes a request to that image provider. - Account. Company email, your name, work phone, job role, company type, country, and an optional base airport. The company record stores the company name and the email domain. A company email is required. Public providers such as Gmail, Outlook, and Yahoo are rejected.
- Sign-in. Sign-in is a one-time link emailed to that address. We do not give you a password. The message log records that a sign-in email was sent. It does not store the link or the token.
- Public alert fields. Title, whether the request is an AOG or an MX event, priority, aircraft and engine, part numbers, error / fault indications / diagnosis, airport, region, country, needed-by date, ATA chapters, and a small image when you attach one. These can be read without an account.
- Locked alert fields. Tail number, aircraft serial, location detail, other details, and the contact name, email, and phone. These stay off the public page until a company unlocks the alert. The posting company's name is also omitted from the public page.
- Quotes and files. A quote can include a message, a price, a lead time, and a quote file. A company can also store trust-center documents. Files are kept in a private store. A clean thumbnail of a posted or closed alert can be shown on the public page. The full file is not.
- Notification settings. Whether you want an email as soon as an alert is posted, whether you want a daily digest, and the filters you save for those emails.
- Phone. The work phone you enter on Complete Your Account is stored on your profile. The optional text-message program is described under SMS Text Messaging. The optional WhatsApp program is described under WhatsApp Messaging.
- Telegram. If you connect Telegram, we store the chat id, user id, username, and display name. That program is described under Telegram Direct Messages.
- Payments. Credit purchases go through Stripe Checkout. We store the checkout id, the payment id, the amount, and the credits added. We do not store your card number.
- Cookies and similar storage. On the marketing website, local browser storage remembers your cookie preference; it is not an analytics or advertising cookie. In the app, a session cookie keeps you signed in. A cookie named aog_next remembers an in-app page for about 15 minutes so the sign-in link can return you there, and it is then cleared. We do not use an analytics or advertising cookie. The sign-in form loads Cloudflare Turnstile. That check can set its own cookie, and we send the result and the request IP address to Cloudflare. We do not store that sign-in IP. We do store a short hash of an IP address to limit repeated requests, and file upload and download events can store the IP address and browser type.
3. How We Use Your Information
We use this information to:
- Remember the cookie preference you select on the marketing website
- Run your account and the company record
- Show public alerts, and show locked details after a company unlocks an alert
- Send the email notices you turned on, send the WhatsApp alerts you opt in to, send the Telegram alerts you connect, and post public alert details to LinkedIn, Telegram, or a WhatsApp group when that destination is switched on
- Record credits bought, spent, refunded, or adjusted
- Scan uploaded files and keep a log of file events and message delivery
- Answer a request you send to support@aogalerts.com
We do not use your information to train machine learning models, and we do not sell it.
4. Data Sharing
We do not sell personal information. We share it with the companies that run parts of the service, and only so those parts can run:
- Supabase stores accounts and the database.
- Vercel hosts the app and the marketing website.
- Stripe takes the card payment.
- Unsplash serves an aircraft image on the marketing website. Your browser connects directly to that provider to load the image.
- Resend sends email. Some messages include a hidden copy for our own records. Other recipients are not shown that address.
- Cloudflare stores private files in R2 and runs the Turnstile check on sign-in.
- Cloudmersive scans uploaded files for malware.
- Twilio sends the text messages and WhatsApp alerts you opt in to. Meta (WhatsApp) delivers those WhatsApp messages. The messages use your number and public alert fields. Routine alerts are not sent on WhatsApp.
- Unipile sends LinkedIn and WhatsApp group posts, and Telegram sends Telegram channel posts, when that destination is switched on. Those posts are for Expedite and Critical alerts, use public alert fields, and do not include locked details. Routine alerts are not posted there. Group posts are separate from the WhatsApp alerts you opt in to. Telegram also delivers the direct messages you connect, using your chat id.
Other visitors can see the public alert fields. A company that unlocks an alert can see the locked details and can send a quote. We may also disclose information if the law requires it, or if the business that runs AOG Alerts is sold and the buyer needs the records to keep the service going.
SMS Text Messaging
SMS. If you opt in to text messages, we use your mobile number only to send the AOG Alerts messages you asked for (new parts-request alerts, notices about your requests, and verification codes). We do not sell, rent or share your mobile number or SMS opt-in consent with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help.
WhatsApp Messaging
WhatsApp. If you opt in to WhatsApp messages, we use that number only to send the AOG Alerts messages you asked for (new parts-request alerts for Expedite and Critical, notices about quotes on your requests, and verification codes). Twilio and Meta (WhatsApp) process the number to deliver those messages. We do not sell your WhatsApp number or your opt-in consent. Message frequency varies. Reply STOP to opt out or HELP for help. A START message does not turn WhatsApp back on.
Telegram Direct Messages
Telegram. When you connect Telegram, we collect your Telegram chat id, user id, username, and display name. We use them only to send the alerts you chose. We share them with Telegram as the delivery provider. We keep them until you disconnect. Consent and delivery logs are kept for audit. Telegram's own privacy policy applies to the Telegram app.
5. Data Security
We use access checks so locked details, quote files, and trust-center files are not on the public page. Uploaded files are scanned before they are treated as clean. These steps reduce risk. They do not make the service free of mistakes, outages, or unauthorized access.
6. Data Retention
On the marketing website, your cookie preference is kept in your browser until you change it or clear that browser storage. We keep account, alert, file, message, and credit records while the company uses the app. The credit ledger is the record of purchases, posts, unlocks, refunds, disputes, and admin adjustments. A Telegram chat id is removed from the active connection when you disconnect. Consent and delivery logs are kept for audit. There is no button in the app that deletes your account or downloads a full copy. Email support@aogalerts.com to ask. We may keep payment and security records after a deletion request when we still need them.
7. Your Rights
Email support@aogalerts.com to ask us to:
- Show you the personal information we hold about you
- Correct it
- Send you an export
- Delete it
The marketing website lets you change your cookie choice through Cookie preferences in its footer. You can also clear its local browser storage. The app does not do the four data-request actions above by itself. We may limit or decline a request where the law allows, including for the credit ledger and security logs. We do not promise a particular number of days for a reply.
8. Third-Party Links
An alert or a quote can include a link to another site. We do not control those sites and we are not responsible for their privacy practices.
9. Children's Privacy
The service is for people using a company email. It is not meant for anyone under 18. The app does not ask for a date of birth, and we do not knowingly collect information from children.
10. Changes to This Policy
When we change this policy we post the new text on this page, change the Last updated date, and change the version. Complete Your Account records the time you first accept the terms. It does not ask you to tick the box again when this page changes.
11. Contact Us
Privacy requests, notices, and support:
Low-Coders LLC (d/b/a AOG Alerts)
Email: support@aogalerts.com
15629 Serengeti Blvd, Spring Hill, FL 34610
