Settings stay local. Google ad SDKs, email and Hosting have distinct processing explained here.
Scope and operator
hc.kim explains processing in the first Android release of PairOn and this official website. Contact: appxdevwork@gmail.com.
The release offers Bluetooth discovery, status and manual BLE connections while the app is visible. It has no developer-operated account, login or payment server and does not send Bluetooth lists to a developer server. Background auto-reconnection, TV transfer and media selection are not included. Advertising SDKs, web hosting and support email involve external processing as described below. iOS is planned for later development.
Information processed on your device
Device names, types, Bluetooth addresses, signal strength and connection states support discovery, status and manual BLE connections. Discovery results and app connection states are handled in memory. Leaving the visible app stops scanning and BLE connections made by the app. Language, onboarding, permission-introduction and advertising privacy preferences are kept in app or SDK local storage. Settings left by older development versions do not trigger automatic connections.
Permissions and purposes
- Nearby-device permission on Android 12+: Bluetooth discovery, connections and state.
- Location permission on Android 11 and earlier: OS requirement for Bluetooth scanning. The app does not collect or track GPS location. Advertising IP-based approximate location is separate.
- Internet/network state: Google ads and access to privacy information.
No camera, microphone, contacts, SMS or media-file access feature. The current Android app does not request notification, boot execution or foreground-service permissions. You may revoke permissions in OS settings.
Advertising and external SDKs
PairOn uses Google AdMob / Google Mobile Ads SDK for small in-app banners and UMP for applicable advertising consent. Development builds currently use test ads. SDK processing can occur in both test and live-ad builds.
The first Android release targets users aged 13 and over without collecting ages or dates of birth. It requests non-personalized advertising for everyone, conservative protections equivalent to under-age-of-consent treatment, general-audience ad content, and restricted data processing for applicable US state requirements. These settings do not stop all SDK processing or guarantee ad availability. Advertising choices and loading failures do not block Bluetooth features.
Google’s disclosures describe processing that may include IP addresses, device/app identifiers, ad impressions/interactions, app activity, performance and errors for advertising, measurement, fraud prevention and diagnostics. An IP address may imply approximate location. Use of Android advertising identifiers varies with OS and consent settings. PairOn does not separately provide Bluetooth addresses or selected media to Google for ad targeting.
Google processes advertising data on its servers. The exact data, purposes, retention and deletion depend on SDK version, features, consent and Google’s policies. Consent messages are presented where required; consent-required ad requests must not proceed without the relevant consent. Rejecting personalized ads does not mean all processing needed for limited advertising ceases.
The current iOS app does not request ATT permission or offer IDFA-based tracking. It does not bypass iOS tracking permissions. Any later introduction requires updated disclosures, permission handling and store declarations.
Android disclosure · iOS disclosure · Google partner-app information use
Website and email support
This static website provides app information, support and this policy. Its code includes no advertising, Analytics or visitor-tracking scripts, contact forms, login or marketing cookies. Fonts and images are self-hosted; language selection uses page links.
Google Firebase Hosting delivers the site and processes IP addresses and request information for delivery, security and abuse prevention. Firebase says Hosting may retain IP data for a few months. This is distinct from the developer adding Analytics to track visitors.
Email support processes the sender’s email address, any name, message, attachments and handling records you provide, to reply, troubleshoot and handle rights requests. Gmail receives and stores the messages. Do not send passwords, payment details or unnecessary personal information; redact screenshots. Firebase privacy · Google privacy policy.
Retention and deletion
Live discovery and connection information is handled in memory. OS app-data deletion or uninstall can clear local preferences, subject to OS backup behavior. Support email and attachments are deleted within 30 days after resolution. If legally required, only necessary records are separated and retained for that period. Developer-controlled mail and trash are cleared; provider backups follow provider policies. Google advertising and Hosting data follow provider retention/deletion policies, so the developer cannot promise immediate deletion of all external records.
Your choices and rights
Change Bluetooth permissions in OS settings or stop using the app. Manage advertising choices using the in-app privacy-options entry when UMP requires it, any consent forms presented, OS advertising settings and Google privacy controls. European personalized-ad consent forms may not appear under the all-user protective treatment.
For access, correction, deletion, restriction or withdrawal requests concerning information handled by hc.kim, contact appxdevwork@gmail.com. Only minimal verification is requested and applicable rights are respected. The developer cannot remotely delete device-only data; independently processed Google records may require provider procedures. There is no app member account. Guardians may contact us about children’s information.
Security and updates
Safeguards include local processing, OS permissions and sandboxing, data minimization and developer-account access controls. The current app has no local TV HTTP server and does not permit Android cleartext HTTP traffic. Google ad SDK data uses provider transport encryption. Bluetooth radio-link security depends on the sensor and OS; encryption of every BLE connection is not guaranteed.
Feature, SDK or processing changes require updated disclosures and appropriate notice/consent. Effective and last revised: 19 October 2026. Contact: hc.kim · appxdevwork@gmail.com.