Scannable processes personal information for the following purposes. Personal information being processed will not be used for purposes other than the following, and if the purpose of use changes, necessary measures such as obtaining separate consent under Article 18 of the Personal Information Protection Act will be implemented.
Scannable collects only the minimum personal information necessary for service provision.
Of the items above, usage statistics (Firebase Analytics) and error & performance diagnostics (Firebase Crashlytics · Performance Monitoring) are collected to improve the app only with your consent to each purpose, and you can withdraw consent at any time in the app settings. Personalized ads are a separate choice, and an additional ad privacy choice screen is provided when needed (see Article 11 ①–③ for settings).
This information is collected only when you choose to submit a feature request, and is stored on Google Firebase (Cloud Firestore). Please do not enter personal information (such as your name, email, or phone number) in feature requests.
If you email us, we use your reply email address, message, any GPA order number and purchase country you provide, and the handling outcome to respond, verify purchases, process refunds and handle privacy requests. Do not attach unnecessary documents or sensitive information.
Versions with automatic deletion submission enabled process request scope, timestamps, installation identifiers, receipts, and status. App integrity evidence and tokens (App Check and Play Integrity) and connection IP addresses may be processed to protect requests. This does not reauthorize analytics or diagnostics after withdrawal. See Article 3 for retention and Article 7 for international processing checks.
The Company retains information within the periods below. When it is no longer needed following fulfillment of its purpose or withdrawal of consent, we promptly take necessary deletion measures unless legal retention is required. Uninstalling the app does not immediately delete information already sent to servers.
Processing a child's information that requires consent must meet applicable requirements, including consent from a legal guardian for children under 14. The app currently has no guardian-consent verification flow, so the Company does not treat a child's optional analytics, diagnostics, or personalized-ad consent as valid.
If we learn that a child's information has been collected, we stop further processing and take necessary deletion measures. Children or their guardians may contact Article 12's address. We request only the minimum information needed to verify the request and authority. Do not send a complete identity document or unnecessary national identification numbers.
The Company processes users' personal information only within the scope notified in Article 1 and does not process or provide it to third parties beyond that scope without prior consent. However, exceptions are made in the following cases:
Advertising identifiers and ad interaction data may be transmitted to Google AdMob to provide advertisements, and Google may process personal information independently under its advertising terms. The advertising contracting party is Google Asia Pacific Pte. Ltd.; international transfer details are set forth in Article 7. For advertising choices, see Article 11; for Google's processing standards, see the Google Privacy Policy.
① Scannable outsources personal information processing as follows for smooth operations:
| Outsourcing Partner | Outsourced Tasks |
|---|---|
| Google's Firebase services | Processing of error logs and performance metrics; storage and handling of feature requests and, in versions with automatic submission enabled, deletion requests (Cloud Firestore and Cloud Functions). Google Analytics is subject to separate terms, and detailed international transfer information is set forth in Article 7. |
② If there are any changes to the outsourced tasks or partners, the Company will promptly disclose them through this Privacy Policy.
The Company outsources and stores personal information with overseas entities as described below to provide services, improve app stability, and deliver advertisements. This transfer complies with Article 28-8, Paragraph 1, Item 3 of the Personal Information Protection Act by disclosure through this Privacy Policy.
| Service and Purpose | Recipient and Country | Data, Timing, and Method | Retention and Refusal Effect |
|---|---|---|---|
| Google Analytics / Usage statistics | Google LLC (United States and global Google data centers) | App events and screen activity, app/device info, and app instance identifiers, sent over TLS during use after consent is saved. | Events: 2 months. User data: 14 months after last activity (reset by new activity). You may withdraw consent at any time in app settings; withdrawal stops new transmissions without restricting core features. |
| Firebase Crashlytics & Performance / Diagnostics | Google LLC (United States and global Google data centers) | Crash records, installation identifiers, device state, performance metrics, and IP addresses, sent over TLS when events occur after consent. | Retention and deletion criteria are as set forth in Article 3. You may withdraw consent at any time in app settings; withdrawal stops new transmissions without restricting core features. |
| Google AdMob / Ad delivery, measurement, and security | Google Asia Pacific Pte. Ltd. (Singapore) and Google LLC (United States, etc.) | Advertising identifiers, device info, IP addresses, and ad interactions, sent over TLS with permitted ad requests. | Subject to Google's Privacy Policy. Turning off personalized ads continues ad delivery with non-personalized/limited ads (removable via Premium in-app purchase). |
| Cloud Firestore / Feature and deletion requests | Google LLC (United States multi-region nam5) | Feature request title, content, category, app info, and submission time; deletion request scope, identifiers, receipt, and handling records. Sent over TLS upon submission. | Until purpose achieved or up to 1 year (Article 3). If you do not submit a feature request, no transfer occurs and core features remain fully functional. |
Users may withdraw consent for usage statistics, diagnostics, and personalized ads at any time in the app (Settings > Info > Data & privacy).
The Company promptly destroys personal information when it is no longer needed, such as when the retention period has expired or the purpose of processing has been achieved.
When a user uninstalls the app, scanned documents and app data stored in the app's private local storage are automatically and permanently deleted. However, copy files explicitly exported by the user via external sharing or gallery saving remain preserved on the user's device even after app deletion.
① Subject to applicable law, you may exercise rights including access, correction, deletion, restriction, portability, or objection to processing. You may withdraw consent for processing based on consent without affecting the lawfulness of earlier processing.
② You may send privacy requests to the email address in Article 12. We respond within applicable legal deadlines and explain any minimal verification information needed.
③ See Article 11 for in-app collection and advertising settings and deletion requests. You may also restrict ad tracking through device settings.
④ The same applicable privacy rights and request procedures apply to previously collected personal data.
Scannable has implemented the following measures to ensure the security of personal information:
① Usage analytics and error/performance diagnostics: Collection to improve the app starts only with your consent to each purpose. Optional choices start OFF in the initial consent screen. Choosing “Agree to all” saves consent to the required Terms and all optional purposes and continues immediately. Alternatively, you can select or clear individual purposes and confirm with “Save choices”, which is enabled only after you accept the required Terms. Analytics and diagnostics are managed separately; the diagnostics choice controls both Crashlytics and Performance Monitoring. Existing refusals are preserved, and a purpose is not collected without confirmed consent. You can review and edit saved choices in Settings > Info > Data & privacy > Privacy choices. Individual switches do not change collection until you save. Leaving all optional choices OFF and choosing “Save choices” confirms refusal. Closing without saving discards the edits. Declining optional choices does not restrict app features.
② Personalized ads: The app's personalized-ad option is initially unchecked. We only permit personalization in an ad request if you select it. Turning personalization off does not remove ads, and data needed to provide ads may still be processed.
③ Ad privacy choices: When needed, we provide an additional ad privacy choice screen and an entry in app settings to change those choices. Ads are provided according to your choices. Advertising choices and usage analytics/error and performance diagnostics settings can be managed separately.
④ Withdrawal and deletion requests: Turning a previously granted analytics or diagnostics choice OFF and selecting “Save choices” stops new collection and transmission for that purpose and records a deletion request on your device. Initial refusal or unsaved edits do not create a past-data deletion request. App versions with automatic submission enabled attempt delivery when connected and retain unsuccessful requests for retry. Use email on versions where automatic submission is unavailable. Uninstalling the app or clearing app data may remove requests that have not yet been sent.
⑤ Receipt and processing status: Waiting on your device, receipt by the Company, submission to a provider, and verified deletion are separate stages. A receipt does not mean deletion from servers and backups is complete. The Company verifies the scope and your authority and promptly takes necessary deletion measures, explaining any verification needed or legal retention exception. Provider processing takes time; deletion associated with Firebase installations may take up to 180 days across live and backup systems. Submission or status-check failures do not turn withdrawn collection back on. When you save a new consent, the relevant identifier is reset to separate new collection from the earlier deletion target. Collection stays off if the reset or saving fails. Re-consenting does not cancel the earlier deletion request.
⑥ Identifiers and email requests: Settings > Info > Data & privacy > Request deletion of my data prepares an email draft, which you must review and send. An App Instance ID or Firebase Installation ID obtained and saved while the relevant collection was permitted helps identify past data. Collection is not enabled merely to retrieve a new identifier after withdrawal. The identifiers apply to different services; deleting one does not delete every service's data. Missing or changed identifiers do not prove that no past data exists. We explain available verification methods and the scope we can process. For feature-request deletion, provide clues such as submission time, category, and title. Do not send scanned documents or unnecessary identity documents.
Scannable has designated the following Data Protection Officer to handle all matters related to personal information processing, complaints, and damage remediation:
Data subjects may apply for dispute resolution or consultation with the following organizations for remedies related to personal information infringement:
You may complain to the competent privacy supervisory authority without contacting us first.
In the event of any additions, deletions, or modifications to this Privacy Policy, the Company will provide prior notice at least 7 days before the amendment on this Privacy Policy page (the screen linked from the app's settings) and, where appropriate, via in-app notice screens. However, for significant changes affecting users' rights, such as changes to the items of personal information collected or purposes of use, at least 30 days' prior notice will be given, and user consent may be obtained again if necessary.
This Privacy Policy was originally effective March 19, 2026, and this 3rd revision is effective as of September 9, 2026.
Revision history: 2026-03-19 enacted · 2026-06-26 2nd revision · 2026-09-09 3rd revision (purpose-specific consent and agree-to-all action, in-app consent changes/ad choices/deletion requests, and support/refund handling). View previous revision