FlagdayPrivacy
Privacy without fine-print surprises
Flagday is designed to work offline without advertising, behavioural analytics or tracking. The iOS app uses Firebase Crashlytics solely for the crash diagnostics described below. The website may show a small number of adverts from selected partners, but uses no tracking cookies. Visitor statistics use the third-party Umami service, cookie-free and without storing directly identifying personal information.
Data controller
Information handled by the app
Country, language, display and notification preferences are stored on your device. On iPhone, the settings are shared with Flagday's widget through Apple's App Group storage and sent to a paired Apple Watch through WatchConnectivity; the watch stores them locally. Axcode does not receive them. If you choose to save the flagpole position, its coordinate, accuracy, capture time and the time zone resolved by Apple through a one-time Core Location and Apple Maps lookup are stored. Apple may process the lookup under its privacy policy. The position is then stored locally, sent from iPhone to a paired Apple Watch and used for calculations on the device; the Mac app can store a separate local position. The position is not continuously updated as you travel and is not sent to Axcode. A personal flag day includes its name, date, an optional note and your notification, widget and calendar choices. When iCloud is available, Apple CloudKit synchronises this through your private iCloud database. Records are controlled by your Apple ID and are not available to Axcode; Apple's processing is governed by its privacy policy and your iCloud settings.
Calendar and notifications
Calendar export is optional and requires the calendar permission shown by iOS. Flagday creates all-day events in a dedicated calendar through Apple EventKit, in the account configured as the default for new events. An optional note is included only when that personal flag day is included in calendar export. The account's calendar provider may store or synchronise the event under its own terms; Axcode does not receive or access your calendar. Calendar export is not performed by the watchOS or macOS apps. Official and personal reminders are scheduled locally through Apple's notification system; Axcode receives neither your preferences nor a notification history.
Optional Supporter purchase
If you choose to support Flagday with the optional one-time purchase, Apple processes the payment through the App Store. The purchase is not a subscription and unlocks no features. The app asks Apple's in-app purchase system whether the verified purchase is active so it can acknowledge it, restore it on your devices and stop showing the purchase action. This does not require a Flagday account or an Axcode purchase-tracking server. The app uses only the product identifier and whether its verified entitlement is active. Axcode does not receive your Apple Account identity or payment details from the app; Apple's processing of the purchase and purchase history is governed by Apple's terms and privacy policy.
Network, location and tracking
Apart from the crash diagnostics described below, Free 1.0 sends no app usage, flag days or other personal information to Axcode. The app includes no advertising or behavioural-analytics SDK. Location access is optional and is requested only after you choose to save the flagpole position and tap the location button. Flagday makes a one-time request while you use the app and does not monitor your location in the background. The coordinate is sent once to Apple's Core Location and Maps service to resolve the correct time zone; Axcode does not receive the request, coordinate, time zone or resulting solar times. You can use all other features without granting location access. Flagday does not combine information with third-party data, sell information, use it for advertising or track you across apps or websites. External links are subject to the destination's terms. The website requests your location only after you explicitly choose exact solar times. The calculation happens locally in your browser; coordinates and your IANA time zone are stored locally on your device and are not sent to Axcode. The website's primary-country and theme choices are also stored locally in your browser. You can remove the website's local data through your browser's site settings. When you visit the website root, CloudFront uses an approximate country code derived from the request IP address to choose a language. The language choice itself stores neither the IP address nor the country code. The Flagday website uses no tracking cookies. It may show a limited number of adverts from selected partners. The adverts are contextual and are not based on cross-site tracking. The website uses the third-party Umami service for cookie-free visitor statistics. Umami records page views and technical information such as referring URL, browser, operating system, device type and approximate country of origin without storing directly identifying personal information; the web host may also process ordinary technical access logs.
Crash diagnostics
The iOS app uses Google Firebase Crashlytics solely to identify and fix crashes and important technical failures. Crashlytics is not included in the widget or the watchOS or macOS apps. A report may contain a stack trace and relevant app state, the app version, device model, operating-system version, a timestamp, and pseudonymous Crashlytics and Firebase installation identifiers. Flagday does not set a user ID or attach the saved flagpole position, personal flag days, calendar or notification content, or other user-entered content. Firebase Analytics is not included. Axcode and Google use the information only to maintain app reliability, not for advertising, profiling or tracking. Google processes it on Axcode's behalf under its data-processing terms, based on Axcode's legitimate interest in maintaining a secure and reliable app. Google states that crash stack traces and their associated identifiers are retained for 90 days before their removal process begins.
Support communications
If you contact Axcode by email, we receive the address, message and anything you choose to include. It is used only to answer the request, maintain service security and reliability, and meet applicable legal obligations. It is not collected by the app and is retained only as long as reasonably needed. Email providers may process the message for Axcode. The legal bases are taking steps you request, Axcode's legitimate interest in support and service protection, and applicable legal obligations.
Payments through Stripe
If you choose to support Flagday, an external Stripe payment page opens. Stripe processes payment-method details and the contact and billing information you enter, together with technical and fraud-prevention data such as IP address and device or browser information, to complete and secure the payment and meet legal obligations. Axcode receives transaction and receipt information, such as the amount, time, payment status or reference and receipt contact details, but not full card details. Axcode retains accounting records for as long as applicable bookkeeping rules require. More information is available in Stripe's Privacy Policy.
Deletion and retention
You can delete a personal flag day in the app; deletion synchronises to your private iCloud database when CloudKit is active. Flagday calendar events can be removed through the app's export controls or your calendar app. You can remove the saved flagpole position from the solar-time settings at any time. Removing an app deletes its local settings according to the operating system's behaviour. iCloud data may remain available for synchronisation until you delete it through the app or your iCloud data controls.
Your rights
Depending on where you live, you may have rights to access, correct, erase or restrict processing. Because Axcode does not receive on-device or private-iCloud information, actions concerning it are normally performed directly in the app, Calendar or iCloud settings. Contact us about crash diagnostics, support communications and other questions. Because Flagday does not set a Crashlytics user ID, Axcode normally cannot link a particular diagnostic report back to you. If your request concerns a crash, include only the app version, operating-system version and approximate time; do not send sensitive or user-entered content. You may also complain to your local data-protection authority; in Sweden this is the Swedish Authority for Privacy Protection (IMY).
Changes
This policy will be updated before a Flagday version introduces server-based live content, Flagday-operated push delivery, subscriptions or any materially different data handling. The effective date above identifies the current version.
Send privacy questions to support@flagday.app.