Information stored on your device
T6 Briefer stores limited preferences on your device, such as your selected TOLD airfield, schedule name, and squadron. Your schedule name is used locally to match events. If you enable event-only alerts, your entered schedule name is also stored in Firebase to match assignments before sending notifications. The app also caches recently viewed schedules for offline access. Your personal event notes, TOLD values, and quiz answers are not sent to the developer.
Personal event notes, manual TOLD values, and quiz answers are processed and stored only on your device. Event notes remain until you delete them, clear the app's storage, or uninstall the app. Your operating system or device backup service may retain app data according to your backup settings.
Weather requests
When you open the TOLD page, T6 Briefer requests the latest KNSE and KNGP observations from the National Weather Service Aviation Weather Center at aviationweather.gov. Native iOS and Android apps request the observations directly. Because the Aviation Weather Center does not permit browser cross-origin requests, the web version retrieves the same observations through the app's Firebase service. Normal network information, including an IP address and user-agent or device request information, may be processed automatically by the service receiving the request.
Weather requests do not include your name, email address, contacts, precise device location, or manually entered TOLD values.
App delivery and updates
T6 Briefer is distributed through the Apple App Store and Google Play and uses Expo Application Services to deliver compatible app updates. Apple, Google Play, Expo, and their infrastructure providers may process limited technical information needed to install, secure, and update the app, such as platform, app version, network information, and update-request metadata. Their handling of that information is governed by their respective privacy policies.
Personal schedules and optional notifications
Schedule requests send the selected squadron and date to the T6 Briefer schedule service hosted on Google Firebase. The service retrieves public CNATRA PDFs and caches parsed schedules, including names already present in those public PDFs, for up to 30 days. Your entered name is not included in these requests; event matching happens on your device. Normal network information may be processed by the service and hosting providers.
Notifications are optional. The app requests notification permission when you first save your name and unit or explicitly enable a unit alert, not merely on launch. First-time profile setup selects your squadron or FITU for alerts; you can change or disable alerts using the independent unit controls in Settings. Allowing permission registers with Apple or Google and Expo to obtain a device push token. Enabling alerts creates a persistent anonymous Firebase device identity and stores your selected alert units, Expo push token, and subscription timestamps in the developer's Firebase database. These identifiers are used only to manage your alert subscription and deliver notifications; your entered name is uploaded only when you enable event-only alerts. Turning that option off removes the entered name from the subscription when the server update succeeds. Turning off all unit alerts or removing your profile deletes the subscription when connected; inactive subscriptions expire after 90 days without renewal.
The server checks for new front pages every five minutes for subscribed units. Alerts are sent when a new schedule appears, whether or not you have events. Turn off schedule alerts in the app to request server-side removal, or use Remove my name & turn off alerts to clear your name and viewed-schedule cache too. Internet access is required to confirm removal; failed removal is retried when you return to the app. Revoking system permission stops notification display and requests subscription removal on the next app refresh. Uninstalling does not immediately remove a server subscription; inactive subscriptions expire after 90 days, and invalid delivery tokens are removed when reported by the push service.
Optional feedback
If you choose to send feedback in Settings, the app sends the feedback category and message to the T6 Briefer Firebase service along with a persistent anonymous Firebase device identity, server timestamp, app version, platform, curriculum version, current screen, and selected unit when available. An optional source or publication reference is included when you provide one. The service forwards that feedback to the developer at t6briefer@gmail.com through the configured email delivery provider. Feedback is used to investigate reported issues and prioritize improvements. Do not include sensitive, personal, or operationally sensitive information in feedback. Feedback is not linked to your schedule name by the app.
Optional public study-game leaderboards
Emergency Procedures, Operating Limits, and Course Rules game scores are stored locally by default. After a completed game, the app may send the game category, aggregate score, and correct and incorrect answer counts with a persistent anonymous Firebase device identity to determine whether the score qualifies for that game's global top-five leaderboard. Individual quiz questions, selected answers, and schedule profile are not included in that check.
If a score qualifies, you may choose to submit a display name and squadron or FITU. The display name, unit, score, and correct and incorrect counts are publicly visible to other app users on that game's leaderboard. Display names are checked by a server-side content filter before publication. The anonymous Firebase identity is converted into a pseudonymous leaderboard player identifier so the service can limit each device to one position per leaderboard and support blocking and abuse reports; the private Firebase identity is not included in public leaderboard responses.
You can press and hold a public leaderboard name to report and hide it. Reporting immediately hides that player on the reporting device and sends the selected entry, report reason, pseudonymous reporter and player identifiers, and timestamp to Firebase for moderation. Reports are also forwarded to the developer through the configured email delivery provider. Reports from five different devices automatically remove that player from the public leaderboards and prevent new submissions from the same anonymous identity. Report and moderation records are retained as needed to investigate abuse, enforce leaderboard safety, and prevent duplicate reports. Users may also request review or removal at t6briefer@gmail.com.
AI practice briefs and saved reports
AI practice briefs are optional. When you start one, the app uses your microphone and sends live audio to OpenAI to transcribe your speech, generate the instructor's responses, and produce spoken audio. The app also sends the selected syllabus event code, title, objective, discussion items, selected voice, and a persistent anonymous Firebase device identifier. If you launch a brief from a scheduled event, the selected schedule source and date may be sent to the Firebase service so it can choose the applicable emergency procedure of the day. Your profile name is sent to the Firebase service when checking AI-brief access and starting a brief; it is used to apply the developer's designated test access and is not sent to PostHog.
At the end of a brief, the captured transcript and limited timing information are sent through the T6 Briefer Firebase service to OpenAI to generate the score and feedback report. T6 Briefer does not intentionally store brief audio or transcript text in Firebase. Pending and completed AI-brief reports, including transcripts and feedback, are stored on your device, with the most recent 25 reports retained. Reports you export as PDFs are stored or shared only where you choose through your device's share interface. OpenAI and the hosting providers may process and retain service data under their applicable API privacy and security terms.
Subscriptions and AI-brief credits
Apple or Google processes subscription purchases and payment information. T6 Briefer does not receive or store your full payment-card or bank information. RevenueCat is used to retrieve available subscription products, complete or restore purchases, and report purchase and renewal events to the T6 Briefer Firebase service. The app shares its persistent anonymous Firebase device identifier with RevenueCat as the app user identifier so purchases can be applied to the correct device identity.
RevenueCat purchase events may include the store, product and entitlement identifiers, transaction identifiers, purchase and expiration times, subscription environment, renewal status, and related technical metadata. Firebase stores the anonymous device identifier, remaining AI-brief credits, subscription status and expiration, credit reservations, and processed event identifiers needed to prevent duplicate grants. Apple, Google, RevenueCat, Firebase, and their infrastructure providers handle purchase records under their respective policies and legal retention requirements.
External links
The app includes user-initiated links to CNATRA squadron pages. When you choose an external link, the destination website may collect information under its own privacy policy. T6 Briefer does not control those third-party websites.
Advertising, analytics, and sharing
T6 Briefer uses PostHog to understand which screens and features are used and whether activities are completed. Analytics may include an automatically generated anonymous identifier, screen names, app lifecycle events, app version and build, platform, device model and type, operating-system version, locale and time zone, and aggregate feature results. Events may record syllabus event codes and types, study-guide progress counts, note actions without note content, AI-brief start and completion status, elapsed time, turn and coverage counts, score and readiness, report viewing or export status, available-credit state, and subscription or restore attempt outcomes. PostHog may process ordinary network information, including an IP address, to receive these events, but geographic enrichment is disabled.
T6 Briefer does not send PostHog your profile or schedule name, leaderboard display name, squadron or FITU selection, feedback text, schedule details, note text, manually entered TOLD values, AI-brief audio or transcript text, individual questions, or your answers. Purchase analytics do not include payment-card information or store transaction identifiers. Touch autocapture and session replay are disabled, and the app does not identify users to PostHog or create PostHog person profiles.
Analytics are used only to measure reliability and improve app features. The developer does not sell personal information, use analytics for advertising, or allow PostHog data to track you across other companies' apps or websites. Analytics events are retained according to the project's configured retention settings and PostHog's privacy and security practices.
Data retention and deletion
T6 Briefer does not require a user-facing account. Optional alert subscriptions are stored until you request removal, a token becomes invalid, or the device has not renewed its subscription for 90 days. Public study-game leaderboard entries remain only while they rank in the top five for that game, unless removed through moderation or by request. Leaderboard abuse reports and moderation records are retained as needed to investigate abuse and maintain service safety. Cached server schedules and notification deduplication records are retained for up to 30 days; short-lived delivery receipt identifiers are processed and removed after delivery checking. Firebase retains anonymous authentication and AI-brief access records as needed to operate credits, subscriptions, prevent duplicate grants, and meet operational or legal requirements. RevenueCat and the app stores retain purchase records under their policies and legal obligations. PostHog retains analytics events according to the project's configured retention settings. Hosting, AI, analytics, purchase, and push providers may retain technical logs for operational, reliability, security, or legal purposes under their policies.
You can delete individual personal event notes in the app. The app keeps up to 25 AI-brief reports locally; clearing app storage or uninstalling removes local reports, notes, schedule preferences, game records, and cached schedules, but does not cancel a store subscription or necessarily delete server-side purchase, credit, analytics, feedback, or leaderboard records. Manage or cancel subscriptions through Apple or Google. For a leaderboard removal or a deletion request concerning information you believe was submitted through the app, contact us at t6briefer@gmail.com.
Security
The app uses encrypted HTTPS or secure real-time connections for weather, schedule, notification, leaderboard, AI, purchase, and update requests. The server verifies the Firebase device identity before changing alerts, AI-brief access, or leaderboard entries, and private service-account and webhook secrets are not included in the app. Although reasonable safeguards are used, no network transmission or storage method can be guaranteed to be completely secure.
Children's privacy
T6 Briefer is intended for aviation students and personnel and is not directed to children under 13. The developer does not knowingly collect personal information from children.
Policy changes
This policy may be updated when the app's features or data practices change. The effective date at the top of the policy will be revised when an update is published.
Contact
Privacy questions may be sent to t6briefer@gmail.com.