TAIPOPO Privacy Policy
Read the app privacy policy in English below. The policy explains the information processed, storage, external services, retention, deletion and contact details.
Effective date: 2026-08-23
Last updated: 2026-10-14
Data controller and privacy officer: independent developer Jonggeun Hong
1. Data Controller and Contact
Data controller and privacy officer: independent developer Jonggeun Hong
Questions about the processing of personal information, the app data deletion procedure, guidance on deleting Google Drive backups, and exercising your rights can be sent to the email address below.
taipopo.app@gmail.com
2. Information Processed
TAIPOPO stores information needed for attendance, workplaces, photo evidence, settlements, and report management primarily in the app storage area on the user's device. Based on the currently confirmed implementation, TAIPOPO is not structured to upload and store the user's work data on its own server.
- User and worker information: worker name, phone number, email, address and detailed address, wage calculation criteria, payment date, payment method, bank, account number, and account holder
- Workplace information: workplace name, address and detailed address, company name, manager name, contact information, workplace memos, and workplace attachments
- Attendance and work records: check-in and check-out times, work and break time, work memos, settlement data, report data, and related snapshots
- Photo and image information: includes original photos, edited photos, display images, thumbnails and other derived images, user-designated photo categories, markings and annotations added to photos, capture time, and workplace or work information linked to photos
- Location and address information: GPS coordinates and address information when the user grants location permission and uses the related features. To convert coordinates into an address, the app calls the Android operating system’s geocoding service; depending on the device and operating-system configuration, this process may use the network.
- Photo metadata: original photo files may contain capture-related metadata (additional photo information), such as EXIF. The app may read photo orientation information or apply it to derived images to display and share photos and generate PDFs.
- Settings and diagnostics: app settings, notification, camera and backup settings, backup and restore progress information, and app stability and error diagnostic information
3. Purposes and Basis for Processing
The information described above comes from what you enter, capture or attach in the app, or from your direct use of its features. Information is used to provide attendance and work record management, photo evidence storage, settlement, report and PDF creation, backup and restore, notifications, error diagnostics, and inquiry handling. Location, camera, notifications, storage, Google Sign-In, and Google Drive are used when the relevant Android permission, Google OAuth consent, or direct user action is provided.
4. Retention
Work data and photos may remain in the app's storage until you delete individual items, permanently delete photos, reset all data, uninstall the app, or clear its data through the operating system. The trash rules and exceptions in section 10 also apply. Reset All Data deletes settings, work data, photos, generated PDFs, attachments, exported files, backup data, caches, and temporary files within the app-managed area on the device. Copies stored outside the app-managed area must be deleted separately. Google Drive backups may remain in appDataFolder until you delete them in Google Drive backup management. You must delete exported ZIP/PDF/photo files and copies on external storage separately at their saved locations. Diagnostic data sent to Firebase Crashlytics is handled according to Firebase's features and policies.
5. Google Drive and Google Sign-In
Google Drive features are used when the user directly starts Google Drive backup or restore and Google account authentication is required. The app uses the Google account authentication selected by the user, and Drive backups are stored within Google Drive's app-specific appDataFolder. The app does not use permission to access all Google Drive files for this feature.
A Google Drive backup may consist of a single ZIP file or a backup split across multiple files, and may include photos, location and address information, work records, settlements, reports, settings, and app data. The app does not automatically upload work data to Drive unless the user selects the action. Local data reset or disconnecting Google does not automatically delete existing Drive backups. Completed backups remain until the user selects a specific backup in Google Drive backup management and confirms deletion. Google’s policies may also apply to data processed by its services.
App-level encryption has not been confirmed for backup ZIP files or Drive backups. Users are therefore responsible for keeping backup files in encrypted storage or a trusted account.
6. Firebase Crashlytics
In the released app, Firebase and Crashlytics are initialized when the app starts and are used for app stability and error diagnostics. Diagnostic information recorded directly by the app uses error codes with sensitive content removed and safely sanitized call traces. Independently of whether an error occurs, the Firebase SDKs may automatically process diagnostic information related to installation, sessions, devices, and app execution; when an error or crash occurs, they may also process the related records.
Crashlytics diagnostic information is separate from the user's work records, photos, and settlement data. Resetting the app’s local data or uninstalling the app does not automatically delete diagnostic information already sent to Firebase Crashlytics. Related inquiries can be sent to the email below, and the actual handling scope may vary depending on Firebase features and policies.
According to Firebase’s official guidance, Crashlytics retains call traces from the time of a crash and related identifiers for 90 days, then begins the process of deleting them from live and backup systems.
7. ML Kit QR Recognition
Inputs used for QR recognition and recognition results are processed on the device. However, the ML Kit SDK may send measurement information about operation, compatibility, performance, and error diagnostics to Google.
8. Third Parties and External Processing
Based on the confirmed implementation, TAIPOPO does not centrally store your work data on its own server or sell it. However, Google, Firebase, external apps, cloud services, or storage locations and USB or other external storage devices you select may process data when you start Google Drive backup or restore, Google Sign-In, sharing, export or external saving, or when the included Google, Firebase or ML Kit SDKs operate. Each service's terms and privacy policy may also apply.
9. Sharing and Exporting Photos, PDFs and ZIP Files
Photos, PDFs, ZIP files, and other export files may be copied to an external app, storage location, cloud, USB, or external storage device selected by the user only when the user directly chooses to share, save, or export them. Retention and deletion of copies transferred outside the app-managed area may vary depending on the app, storage location, service, and user settings.
10. Deletion and Your Rights
Items moved to the trash, including photos, memos, workplaces, settlements, and reports, can be restored or permanently deleted. Items that have been in the trash for 30 days from the deletion date are permanently deleted the next time the trash is opened and cannot be restored from the app's trash after permanent deletion. A user can also permanently delete an item before 30 days.
Legacy items without deletion-date information are excluded from time-based automatic deletion. Photos still used by other records are protected during deletion. Automatic cleanup may be deferred while data is being restored or records cannot be loaded normally.
Users can view, edit, and delete records in the app, and photos can be restored from the trash or permanently deleted. Reset All Data deletes settings, work data, photos inside the app, PDFs created inside the app, attachments, export/backup data inside the app, and cache/temp data in the app-managed area on the device. App-managed data on the device can be deleted through Settings > Backup & Restore > Data Management > Reset All Data.
Files exported to Downloads, ZIP/PDF/photo files shared or copied to another app, email, cloud, USB, or external storage device, Google Drive backups, and diagnostic information already sent to Crashlytics are separate from local reset. Privacy inquiries and app data deletion procedure questions can be sent to taipopo.app@gmail.com.
Requests for access, correction, deletion, suspension of processing, guidance on the app data deletion procedure, or exercise of rights by a statutory representative can be sent to taipopo.app@gmail.com. While handling a request, the minimum information needed to verify the requester’s identity or legitimate authority may be requested.
11. Security and Automatic Data Collection
The app primarily manages work data and photos in its storage area on your device. Transfers you initiate, such as Google Drive backup or restore, sharing and export, use the transmission and storage security provided by the operating system, Google or the selected service. Based on the confirmed app structure, TAIPOPO does not use its own web cookies or similar files to automatically collect your work data.
12. Children and Policy Changes
TAIPOPO is not designed primarily for children under the age of 14. This policy may be revised according to changes in laws, services, or features, and changes will be announced through an app update or in-app notice.
Information used by this website
This website has no sign-up, advertising trackers or analytics scripts. Only your light or dark theme preference is stored in your browser. Contact buttons open your email app; the website itself does not receive or store your messages.
This website is hosted on GitHub Pages. The hosting provider may process data when you visit. For details, see the GitHub Privacy Statement.