Privacy Policy

Scope

This policy applies to public pages and tools on the Tarkarn Tools website. Linked external sites and apps follow their own policies.

Local browser processing

Files and input described as locally processed are handled in the user's browser, except when a tool specifically discloses an external connection.

Externally connected tools

REST Client and WebSocket Client send requests or connect directly from the browser to the third-party URL entered by the user. Tarkarn servers do not relay or store that communication. A feature may send part of an input to the disclosed external endpoint to perform a request. Review the notice on each tool before sending data.

Cookies and advertising

Google AdSense and third-party advertising networks may collect or share cookies, device and browser information, IP address, approximate location, and advertising interaction data to provide ads, and personalize and measure ads, limit frequency, and prevent abuse. Preferences can be managed in Google Ads Settings.

Google Ads Settings

Hosting logs

Hosting providers such as Cloudflare may temporarily process technical logs including IP address, user-agent, request URL, time, and response status for security and incident analysis.

Third-party services

Advertising, hosting, external APIs, and links are governed by each provider's privacy policy. Tarkarn does not control third-party content or policies.

Retention and security

Contact and operational records held directly by Tarkarn are retained only as long as needed for their purpose. Reasonable safeguards are used, but absolute security cannot be guaranteed.

Children's privacy

The service is not designed to intentionally collect children's personal information. If such information is identified, Tarkarn will review it and take appropriate action.

Your rights

Requests to access, correct, or delete personal information supplied directly to Tarkarn may be made through the Tarkarn Contact page. Some records may be retained when legally required.

Policy changes

This policy and its review date may be updated when features or legal requirements change. Material changes will be communicated by reasonable means.

Contact

Use the Tarkarn Contact page for privacy, correction, or security concerns. Do not send account passwords or original sensitive files.

Tarkarn Contact

Applies to

This section applies to QRScan and Android package com.tarkarn.scan. QRScan scans QR codes and barcodes, manages records, and creates QR codes.

Scan data on your device

Scan values, formats, times, favorites, notes, tags, batch records, and settings are stored on the device. QRScan does not create accounts or synchronize this data to a Tarkarn server. Camera frames are processed on the device for barcode recognition. On a newly installed device, Google Play services may use the network to download the barcode model.

Exports and sharing you choose

When you choose to copy, share, save, or export CSV, the selected scan value or generated QR image may be sent to the Android clipboard, a receiving app, Downloads, or Pictures/QRScan. Files saved in Downloads or the photo library can remain after you remove the app and can be deleted there. A receiving app handles data it receives under its own policy.

Analytics and diagnostics choice

Firebase Analytics and Crashlytics are included, but collection is off by default. QRScan may send categorized usage events and diagnostic information to Google Firebase only when you opt in to usage analytics and diagnostics in Settings. QRScan is designed to exclude scan values, URLs, email addresses, phone numbers, Wi-Fi information, notes, tags, and batch names from those events and diagnostics.

Advertising and privacy choices

The free features may request advertising. Google Mobile Ads and the User Messaging Platform may process device, browser, or advertising identifiers, network information, approximate location inferred from an IP address, app interactions, and diagnostic information for consent, ad delivery and measurement, frequency limiting, and abuse prevention. Advertising consent is separate from Firebase analytics consent. Where required, you can reopen advertising privacy choices in Settings.

Retention, deletion, and contact

You can delete records from History, and removing Android app storage affects local records and settings in the app. Shared files, public-storage files, and data already handled by Google SDKs follow their separate policies and retention periods. Send privacy questions through the Tarkarn Contact page.

Applies to

This section applies to Airport Mate and Android package com.tarkarn.airportmate. Airport Mate displays flight, parking, congestion, and transport information for Incheon Airport.

Airport information requests and data on your device

To display flight, parking, congestion, and transport information, the app requests the date, terminal, and query conditions needed by public airport data services. Tarkarn does not operate an app server that relays those requests. Favorite flights and parking facilities, display settings, monitoring state, and cached airport information are stored on the device. The app does not create accounts.

Notification monitoring

If you grant notification permission and start monitoring, the app can periodically check selected favorites and airport data in a foreground service on the device and show preparation or parking notifications. Network conditions, device power management, and public-data updates can delay or prevent a check or notification. Do not use this feature for real-time or emergency alerts.

Analytics, diagnostics, and advertising

Airport Mate includes Firebase Analytics and Crashlytics. Google Firebase may process app interactions, device or other identifiers, diagnostic information, and crash logs for usage analysis and error and stability diagnostics. Google Mobile Ads may process advertising identifiers, app interactions, diagnostic information, network information, and approximate location inferred from an IP address for ad delivery and measurement, frequency limiting, and abuse prevention. Where required, you can manage advertising consent through User Messaging Platform options and the advertising privacy choices in Settings.

Retention, deletion, and contact

Favorites, settings, and cached information remain on the device. Deleting an item in the app or removing Android app storage affects the device copy. Public airport data services and Google SDKs apply their own retention and deletion policies to information they process. Send privacy questions through the Tarkarn Contact page.

Applies to

This section applies to Where Shall We Meet? and Android package com.tarkarn.wwm. The app calculates a midpoint from participant locations and displays it on a map.

Locations and records on your device

Participant names and coordinates, calculated midpoints, favorites, and history are calculated on the device or stored in a Room database on the device. The app does not create accounts or send this data to a Tarkarn server. When you request location permission, the app uses the current location only to move the map camera.

Map providers and external actions

The map screen sends style and tile requests that include the current map viewport to a map provider so it can render the map. A version that provides OpenFreeMap maps requests the public OpenFreeMap style directly through MapLibre Android. OpenFreeMap says its standard server logs do not retain IP addresses, but it may temporarily log IP addresses for up to 30 days during a security incident or abuse investigation, and a CDN provider may process information. If you choose to open an external map or share, the midpoint coordinates and selected participant names may be sent to that map or receiving app.

Analytics, diagnostics, and advertising

Firebase and Google Mobile Ads SDKs included in the app may process app interactions, device or advertising identifiers, diagnostic information, network information, and approximate location inferred from an IP address according to Google policies and configuration. Where advertising consent is required, the app uses choices provided by the User Messaging Platform. Map tile requests, Google SDK processing, and an external map or sharing action you choose each follow the relevant provider's policy.

Retention, deletion, and contact

You can remove device copies of favorites and history in the app or by removing Android app storage. Information already shared, or handled by map, advertising, or Firebase providers, follows each provider's retention and deletion policy. Send privacy questions through the Tarkarn Contact page.

Applies to

This section applies to the TMetro app and Android package com.tarkarn.subway. TMetro displays Taiwan MRT lines, stations, and route information on the device. This section and the Tarkarn Tools website policy above each apply to their respective service.

Accounts and data on your device

TMetro does not create accounts or collect sign-in information. Favorite routes, selected region and language settings, and advertising feature state are stored on the device. Station searches and results are handled against built-in station data on the device and are not synchronized to an app server. Android device backup settings may include this local data in a backup.

Data handled by the advertising SDK

TMetro uses the Google Mobile Ads SDK to provide advertising. During an ad request, the SDK may collect and share approximate location inferred from IP address, app interactions, diagnostic information, the Android advertising ID, and App Set ID with Google. It uses this data to provide and measure ads, perform analytics, and prevent abuse.

Data handled by Firebase

TMetro includes the Firebase Analytics and Crashlytics SDKs. Google Firebase processes app interactions, device or other IDs, diagnostic information, and crash logs as a service provider for TMetro usage analysis and error and stability diagnostics. Collection and sharing for advertising are covered by the Google Mobile Ads SDK section and follow Google's policies.

Purposes and third-party processing

TMetro uses the SDK processing above for advertising and measurement, usage analysis, error analysis, and abuse prevention. The app does not send favorite routes, search terms, region, or language settings to a Tarkarn app server or link them to an account profile. Google Mobile Ads SDK sharing and Firebase service processing follow Google's related policies.

Security in transit

The confirmed Google Mobile Ads SDK and Firebase SDK communications use TLS. This statement is limited to those SDK communications and does not guarantee device settings or connections to other services.

Retention and deletion

Local data such as favorites and settings remains on the device. Changing an item in the app or removing app storage through Android affects the device copy. Any copy included in an Android backup follows device backup settings. Retention and deletion of data handled by Google Mobile Ads and Firebase follow the policies for those Google services. TMetro does not include a feature to process deletion requests for this SDK data.

Choices and contact

Where advertising consent is required, you can choose through options presented by the Google User Messaging Platform. Manage the Android advertising ID and Google service privacy controls in Android and Google Account settings. These controls do not stop all data processing by the Google Mobile Ads or Firebase SDKs. For privacy questions, contact tarkarncompany@gmail.com.

Policy changes

We will update this section and its review date when TMetro data handling or its SDKs change.