Privacy Policy

Cape May Aerial Advertising LLC (“we”, “us”) operates the Cape May Aerial Ads apps for iPhone and Android, a public flight-tracking web page, and an admin dashboard. This policy explains what data the apps collect, why, where it’s stored, and who can see it. It applies to two different kinds of users:

• Pilots and staff — accounts created by an admin and used to fly banners.
• Customers — businesses that buy banner flights and use the app to watch their banner’s flight live and review past flights.

The apps are private to Cape May Aerial Advertising — there is no public sign-up. The apps are not directed to children.

What data we collect

From every user (pilot, staff, customer)

• Account info. Username, optional display name, and password (stored only as a bcrypt hash). Created by an admin; we never see plaintext passwords.
• Login + session logs. Every login attempt records timestamp, IP address, user-agent string, and outcome (success / bad password / unknown user). Used to debug sign-in problems and detect password-spray attempts.
• Push-notification device token. If you grant notification permission, your phone’s APNs (iOS) or FCM (Android) device token is stored against your account so we can deliver alerts — e.g., “your banner is in the air”. Your notification category preferences and chosen alert sound are stored alongside the token. You can revoke notifications at any time from your phone’s system settings; the token is rotated by Apple/Google when you do.

From pilots and staff specifically

• Plane GPS location. When a pilot taps “Start banner”, the app records the plane’s GPS position, altitude, heading, and speed every few seconds and sends it to our server. Tracking only runs while a banner flight is active — it stops the moment you tap “Stop”, end the session, or sign out. We do not track location at any other time.
• QR pairing token. When a pilot scans the QR code on a plane or a banner with the in-app camera, the encoded token is sent to our server to pair the pilot with that tail number or banner. The camera is used only for QR scanning; no photo or video is recorded, and no images leave the device.
• Banner-beacon proximity. The pilot app’s Bluetooth scanner listens for short-range iBeacon advertisements from the banner tags we attach to each banner. We log when a known banner tag comes into range so the system can confirm which banner is actually in the air. We do not scan for, log, or transmit data about any other Bluetooth device near the pilot.

From customers specifically

• Banner ownership only. Customers can see the banners owned by their company, the live position of whichever plane is currently towing one of those banners, and the flight history (track, altitude, distance, proof-of-performance shading) for those banners. A customer cannot see other customers’ banners or flights. The customer apps and portal do not request location, camera, or Bluetooth permissions.
• Banner artwork. If you upload a banner image to your account (e.g., a logo) it is stored on our server and rendered as part of the in-app preview and the proof-of-performance PDF for your flights. It is not shared with other customers.

Why we collect each one

• Plane GPS powers the live tracking map, the customer-facing flight history, and the proof-of-performance reports we provide to customers.
• Camera is used only to read QR codes printed on planes and banners, so a pilot can pair without typing long IDs.
• Bluetooth is used only to detect the banner tags described above, to verify which banner a plane is towing.
• Notifications on a pilot phone keep the foreground tracking service from being suspended by Android mid-flight, and (if the pilot opts in) deliver flight-start / pickup-approach alerts. Notifications on a customer phone deliver “your banner is in the air” alerts when one of their banners launches.

Who can see the data

• Pilots see only the planes and banners assigned to them, plus the live fleet map of other pilots in the same operation.
• Customers see only banners owned by their company and the live position / flight history for those banners.
• Admins at Cape May Aerial Advertising can see all of the above for the purpose of running the operation and producing customer reports.
• We do not sell, share, or syndicate any of this data with third parties for marketing or advertising. We do not use the data for analytics, ad targeting, profiling, or training machine-learning models.

Where the data is stored

Data is stored on servers operated by Cape May Aerial Advertising LLC. Connections to those servers use HTTPS. Passwords are stored as bcrypt hashes. Push-notification device tokens are stored alongside the account that registered them and used solely to deliver alerts you explicitly opted in to.

How long we keep it

Flight tracks and audit logs are kept indefinitely while the account remains active so customers can request historic proof-of-performance reports. On request we will delete an account and the associated flight data from the active database; backups are pruned within 90 days. Push tokens are deleted automatically when Apple or Google reports them as invalid (uninstall / token rotation).

Your choices

• You can deny any individual permission (camera, location, Bluetooth, notifications) in your phone’s system settings. The corresponding features (QR pairing, flight tracking, banner-tag detection, reliable background tracking, push alerts) will stop working but the rest of the app will continue.
• Customers can turn the “banner in the air” push alert on or off any time from the in-app Settings screen. Pilots have the same toggles plus optional staff-only alerts (flight launched, pickup approach).
• You can request account deletion or a copy of your data by emailing the contact below, or follow the step-by-step instructions on the Account & Data Deletion page.

Third-party services we use

• Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM) deliver push notifications. They see the device token and the payload of the message we send (e.g., “Your banner is flying”), not the contents of your account.
• OpenStreetMap serves base map tiles for the in-app map; map tile fetches reveal your approximate viewport to their tile server.
• Iowa Environmental Mesonet serves NEXRAD weather radar overlays the same way.
• NOAA / NWS wind forecasts are fetched by our server, not by your device.
• FAA AeroNav tile services provide optional VFR sectional chart overlays.

Contact

Privacy questions, deletion requests, and other inquiries: info@capemayads.com