BlueAirShare Privacy Policy
Who is responsible
BlueAirShare is provided by Konrad Witkowski. For questions about personal data or to exercise your privacy rights, contact witkompapp@gmail.com. This policy covers BlueAirShare on iOS and Android, including optional advertising and the Remove Ads purchase. Desktop and legacy editions do not display these mobile advertisements.
Files and nearby discovery
Files are transferred directly between devices you select, using the local network or Apple's system sharing facilities. BlueAirShare does not upload your files, file contents, transfer history or nearby device list to an application server. Nearby discovery shares a device identifier, device name, platform and connection information with nearby peers; a name you choose may identify you. Transfer peers receive the files and metadata needed for the transfer, such as file names and sizes. Only share with people and devices you trust. A recipient controls copies they save.
Information stored on your device
The app stores preferences, device identity, transfer history, selected save locations, purchase entitlement and privacy choices on your device. Temporary transfer files are used while sending or receiving. Clearing history removes the app's history list, not files saved in Photos, Downloads or a chosen folder. Delete those files separately if needed. Removing the app removes its app-local data, subject to your operating system's backup and storage settings.
QR invitations and camera access
Camera access is optional and used only while scanning a pairing QR inside BlueAirShare. Camera frames are decoded on your device and are not recorded or uploaded by BlueAirShare. A pairing QR contains a local network address, device identity information, an expiry and a one-use invitation secret. The app keeps invitations in memory only and does not put them in transfer history, advertising requests or app logs. An invitation selects a receiver; you must still compare the PIN and explicitly accept the files. When an ordinary camera opens the HTTPS invitation before the app is installed, the pairing data stays in the URL fragment and is not included in the HTTP request to GitHub Pages. The hosting provider still receives ordinary connection metadata as described above. The page uses no analytics or third-party scripts, and store links do not include the invitation. Your browser or system camera may retain its own history under its settings. Installation on iOS does not automatically preserve an invitation: return to the page or scan a valid code again. Do not share invitation links or QR screenshots in support messages.
Permissions
Bluetooth, nearby devices and local network access support finding peers and transferring files. Older Android versions require location permission for nearby discovery; BlueAirShare does not use GPS to track your movements. Photo and file access is used for items you select and destinations you authorize. You can manage permissions in system settings. Refusing an advertising choice does not prevent file transfers or purchases; refusing a network or file permission can prevent the corresponding transfer function. Camera permission is requested only for the optional QR scanner; denying it leaves other device selection and transfer methods available.
Google AdMob advertisements
The free mobile editions display a Google AdMob banner. Google Mobile Ads may process IP addresses (including an approximate location inferred from them), advertising or other device identifiers, ad views and interactions, app interactions, crash information and performance diagnostics to deliver and measure advertising and help prevent fraud. The data sent depends on your platform, privacy choices and the ad configuration. Ad services use internet connections separate from your local file transfers. No file contents are provided to the advertising SDK by BlueAirShare. Google explains its processing at https://policies.google.com/privacy and https://policies.google.com/technologies/partner-sites.
Advertising choices and tracking
Google's User Messaging Platform (UMP) presents privacy choices where required. You can reopen Advertising privacy choices in the app's privacy screen, including after purchasing Remove Ads when Google requires this entry. On iOS we first check the purchase entitlement. For the free edition, we resolve Apple's App Tracking Transparency (ATT) permission before requesting Google consent information and starting ads. Tracking requires ATT authorization and the applicable Google consents; ATT authorization alone is not sufficient. If ATT is denied or restricted, iOS prevents IDFA access and we request only non-personalized ads when UMP allows requests. Publisher First-Party ID is disabled on iOS. If ATT allows IDFA but the app cannot establish the necessary Google permissions, the iOS app suppresses ad requests. Google's SDK also applies its consent signals and may further restrict advertising. On returning to the app, we recheck ATT and privacy choices before resuming ads. You can change ATT in iOS Settings. Android provides advertising identifier controls in its privacy settings. Withdrawing consent applies to future processing and does not undo processing already performed.
One-time Remove Ads purchase
Remove Ads is an optional one-time, non-consumable purchase. Its localized price is displayed by the store before confirmation; there is no subscription. On iOS, Restore Apple Purchases restores only App Store purchases made with the same Apple Account. On Android, Restore Google Play Purchases restores only Google Play purchases made with the same Google account. Each store maintains its own independent entitlement. A verified entitlement removes banner ads and the purchase offer and is retained across app restarts, including offline use. When a purchase is recognized at iOS startup, the app skips ATT and ad SDK initialization. Required Google privacy choices remain accessible, and UMP may refresh their availability. Remove Ads does not delete data already held by an ad provider. Pending payments do not unlock the feature, and refunded or revoked purchases may lose the entitlement when checked again.
Purchase verification
Apple processes iOS payments, and StoreKit verifies transactions on your device. Google processes Android payments, and the app queries and acknowledges purchases directly through Google Play Billing. On Android, the app checks the purchase signature using the public licensing key provided by Google Play. Purchase status is checked with the same store account when you restore purchases. BlueAirShare does not operate a purchase verification server and does not send purchase tokens to an application backend. We do not receive your payment card details or store password. Apple and Google handle payment and transaction information under their own privacy policies.
Purposes and legal grounds
We use the information needed for transfers and purchase verification to provide the services you request, including performance of the relevant contract. Where consent is required for advertising or tracking, we rely on your choice and provide a way to change it. Operational security and fraud prevention may rely on legitimate interests where applicable, and records required by law may be retained to meet legal obligations. Google and Apple also process information under their own policies and applicable legal grounds. We do not use your transferred files for advertising.
Retention and recipients
App-local preferences and history remain until cleared, replaced or removed with the app. Purchase status is cached so a verified customer can remain ad-free offline and is checked again when the store is available. Apple and Google retain transaction and advertising information under their respective policies, including fraud prevention and legal retention requirements. Information handled by these providers may be processed outside your country, including outside the European Economic Area, under their applicable transfer safeguards. Their privacy information is available at https://www.apple.com/legal/privacy/ and https://policies.google.com/privacy. Contact us about app-controlled data. We retain correspondence about a privacy or support request only as long as needed to address it and meet any applicable legal obligation.
Your rights
Depending on your location, you may have rights to access, correct, delete or receive your personal data, restrict or object to processing, withdraw consent, and complain to a data protection authority. In Poland this is the President of the Personal Data Protection Office (UODO); you may also contact your local supervisory authority. Email us to make a request. We may need enough information to identify the data concerned, but do not send payment passwords, private keys or full purchase tokens by email. For information held independently by Apple or Google, their privacy controls and contact channels may also be needed.
Children
BlueAirShare's advertising-supported mobile edition is not specifically directed to children. Do not use the app to send another person's private information without permission. If you believe a child has supplied personal data to us, contact us so we can investigate.
Changes to this policy
We will update this policy when the app's processing changes. Its date and version identify the text bundled with your installed app; the public privacy link provides the latest published version. Significant changes requiring a new choice will be presented before the affected processing where required.
Contact: witkompapp@gmail.com