PAWCATCH · TERMS & PRIVACY
Privacy Policy
This notice explains the personal data processed by CatchCatch, the operator of PawCatch: data and purposes, retention, external processing, and how to exercise your rights.
- Company
- CatchCatch (캐치캐치)
- Service
- PawCatch
- Business registration number
- 602-18-80483
- Representative
- 최동연
- Address
- 인천광역시 부평구 갈산2동 동남
- Customer support
- 010-8068-2335
- skylife927@gmail.com
- Online sales registration
- 2026-인천부평-1562
1. Data collected, timing and purposes
We process information you enter or upload, information supplied by your selected sign-in provider, records created through feature use, and device and server-request information. Data for optional features is processed when you use those features. Every sign-in method does not necessarily supply the same fields, such as an email address.
| Feature | Data processed | Timing and purpose |
|---|---|---|
| Account and sign-in | Member identifier; sign-in provider and identifiers; email, name and photo when supplied; nickname. | Authentication and account management during Google, Apple, Kakao or Naver sign-in and profile setup. |
| Profile and relationships | Bio, profile links, selected Instagram information, search visibility settings, follows, blocks, family name, members and invitations. | Identity and sharing-scope management in profiles, search, friends and family features. |
| Dogs | Name, photo and breed; optional birthday, weight, sex, neutering status, temperament, precautions and map color. | Dog registration, editing and walk management. A dog’s birthday and weight are distinct from the owner’s birth date and health information. |
| Location and walks | Latitude, longitude, time, accuracy and speed; route, distance and duration; walker, dogs and poop status; map cells, neighborhood, territory, rankings and item-use locations. | Recording, nearby discovery, game processing, aggregation and chosen sharing when using current-location and walk features. |
| Content and communication | Text, photos, locations and linked records in feeds, comments, chats, reviews, traces and place reports; likes, views, reports and blocks. | Content delivery, safety management and inquiry handling when creating, viewing or interacting with content. Uploaded content itself may contain personal data. |
| Currencies and creation requests | Pawprints and Bones balances and acquisition/use history; products and items held; emoticon creation photos, dog information, style, requests and output. | Granting and deducting balances, duplicate prevention, creation and support when using the shop, rewards and creation features. |
| Business verification | Application materials including business registration number, representative name, opening date, main telephone number and evidence photos. | Authenticity checks and operating-permission review only for businesses applying for PawCatch Places verification. |
| Access and diagnostics | Device, OS, app version and language; push tokens and notification settings; access and request information; usage events, errors, diagnostic information and SDK identifiers. | Notifications, analytics, advertising, troubleshooting and fraudulent-request prevention. Analytics may be linked to member identifiers. |
| Account and data deletion requests | Contact email, sign-in method, optional nickname and request details; consent, receipt and processing information; hashes of email and access addresses to prevent fraudulent submissions. | Identity verification, deletion handling, result notifications, and duplicate/fraudulent-submission prevention when receiving a web request. |
| Advertising and partnership inquiries | Business name, reply email, desired product and period; optional start date, region, destination URL, budget and inquiry details; consent, receipt and processing information; email/access-address hash counters to prevent abuse. | Collected with consent on the business web form for consultation, review, replies and duplicate/fraudulent-submission prevention. Only responsible administrators can access it; it is not published in the general feed. Payment information and original access addresses are not stored in inquiry records. |
| Advertising creation, purchase and management | Firebase member identifier; business name, registration number and contact email; images, alternative descriptions, copy and destination URLs; product, period, creative version, consent time and terms version; order number, payment key, amount, payment/refund status and receipt URL; review and operating records. | Contract formation and performance, payment, review, publication, refunds and support when an advertiser requests creation, saving or purchase. Full card numbers are not stored. Payment features are provided after operational preparation is complete. |
| Paid-ad performance | Ad ID, creative version, one-time display identifier, impression/click status and time; app member identifier for deduplication. | An impression is counted when at least 50% of the ad is visible on an active screen for at least one second; a click when its external link opens successfully. Advertisers receive totals and daily statistics, not member identifiers, precise locations or walk routes. |
You can use features that do not need optional information without supplying it. Do not include unnecessary personal data such as other people’s faces, contact details, addresses or resident registration numbers in text or photos. Sensitive information in public posts can be seen by others; check before publishing and request deletion when needed.
1-1. Processing grounds and your choices
Personal data necessary for authentication, account management and requested features such as walk records and content is processed within the scope necessary to perform a contract under Article 15(1)(4) of Korea’s Personal Information Protection Act. Separate consent, retention and destruction standards under location-information legislation also apply to personal location data.
Where processing relies on consent, including advertising/partnership inquiries, the consent screen explains the data, purposes, retention period and effects of refusal. Refusing consent for information unnecessary to an essential service does not restrict unrelated services.
Records subject to statutory preservation obligations are processed only as necessary under the relevant legislation and Article 15(1)(2) of the Personal Information Protection Act. Publication or viewing of this policy, or simply using the app, is not treated as blanket consent to all collection, advertising, third-party disclosure or overseas transfers.
2. Location and background walk recording
Current-location maps, nearby places and neighborhood checks may obtain your location even before you start a walk. Walk routes are linked to accounts, dogs and times. Encoding routes or dividing a map into a grid does not fully anonymize them.
An active walk may continue recording while your screen is locked or another app is in use. Android location foreground services and iOS background location features are used; behavior depends on location permissions, power-saving settings and OS state.
Closing a screen is different from ending a walk. To stop recording, end the walk in the app or connected watch, or revoke location permission in device settings. This stops further route recording for that walk but does not automatically delete previously saved records.
4. Retention and use periods
Personal data is retained only as needed for its collection/use purposes. As a rule, it must be destroyed without delay when its retention period ends or it becomes unnecessary through fulfillment of purpose, account withdrawal or consent withdrawal. The table below defines retention end points. There is no blanket policy of retaining all information for another one, three or five years after account withdrawal.
The records, grounds and periods in section 4-1 apply only where legislation separately requires preservation. Ordinary walk routes and photos are not retained long term together with transaction records merely because a transaction took place. You can also request deletion of specific walks, posts or photos while keeping your account.
| Data / purpose | Retention period or end point | Handling and considerations |
|---|---|---|
| Account, sign-in and profile / account provision | Until account withdrawal or fulfillment of the account-provision purpose | The authentication account and service profile are deleted separately. See section 4-2 for the authentication provider’s deletion timeline. |
| Dogs, family, follows and blocks / relationship management | Until the purpose ends through information deletion, relationship disconnection or account withdrawal | This standard distinguishes other family members’ independent accounts/records and removes unnecessary connections to a withdrawn user. |
| Saved walk routes, photos, territory and rankings / history and sharing | While the history-viewing and management purpose remains. Ends upon record deletion, retention-consent withdrawal, account withdrawal or fulfillment of purpose. | Optional consent for history after a walk is distinguished. An exception based on separate retention consent after fulfillment of purpose is limited to one year from that consent. You can request deletion of specific records online while keeping your account. Identity and scope are checked before destruction and result notification. Receipt of a request is not automatic deletion completion. |
| Posts, comments, chats, reviews and traces / content provision | Until the purpose ends through content deletion or account withdrawal | Publishing content is not treated as consent to indefinite retention of its personal data. Copies held by recipients are distinguished. |
| Currencies, items, emoticon requests and output / feature provision | Until fulfillment of the relevant purpose, such as request handling or inventory provision, deletion or account withdrawal | Creation originals, outputs and public display data are distinguished. All free-currency history is not treated as paid-transaction data requiring five-year retention. |
| Reports and general support inquiries / fact checking and replies | Until the purpose of the report or inquiry is fulfilled | Section 4-1 applies only when a record qualifies as a statutory consumer-dispute record. A blanket three-year period is not applied to simple inquiries/reports. |
| Live public location / nearby public-walk display | Deletion requested on normal completion or sharing-off; valid about 120 seconds after the last update | Expired data is subject to server cleanup every five minutes. Communication/cleanup failures are retried. The 120-second validity does not mean physical deletion of every copy is complete. |
| Location-sharing and nearby-read authorizations / access control | Public-sharing authorization: up to 12 hours; nearby-read authorization: five minutes | Expired authorizations are cleaned up every five minutes. Authorization validity differs from retention of saved walks. |
| Device route/recovery data / walk recovery and save retries | Until normal saving, cancellation or the end of the recovery purpose | Automatic blanket expiration of failed-save data and recent neighborhood locations is not fully implemented. After checking whether records need preservation, device app-data deletion or support can be used to clarify cleanup scope. |
| Business-verification evidence and authenticity checks / application review | Originals cleaned up when review ends; incomplete applications become subject to expiration cleanup 30 days after the last update | Incomplete applications, processing history and business operating permissions are distinguished. Submission-limiting records are subject to cleanup 48 hours after their last update. Approved operating permissions are managed until their maintenance purpose ends. |
| Account/data deletion requests / identity checks and result notification | While needed to process an open request; 30 days after completion or rejection | Closed records older than 30 days are cleaned up hourly. Submission-limiting hash counters expire after one hour and are cleaned up hourly. |
| Advertising/partnership web inquiries / consultation and replies | Until the earlier of 30 days after rejection/consultation closure or 180 days after initial receipt | Cleaned up hourly. Email/access-address hash counters for submission limits expire after one hour and are cleaned up hourly. This form does not collect payment information. |
| Web language setting / chosen language | Until browser site data is cleared | Stored in localStorage on your device. In-progress inquiry content is held in page state and disappears when the window is closed. |
| Browser advertising drafts / writing recovery | Seven days after the last save | Image Blobs and input are stored in browser IndexedDB, removed on the next access after expiration, and can be cleared immediately through site-data deletion. While payment opening is being prepared, they remain browser-only even after sign-in. Once account saving is provided, they move to a private account draft after sign-in; the browser copy remains if saving fails. |
| Signed-in unpaid drafts and unused uploads / writing recovery | 30 days after the last draft edit; unattached uploads: 30 days after upload | Expired drafts and files are subject to server cleanup. Paid orders and their creatives follow the transaction/advertising standards below. |
| Ad creatives, publication and performance records / proof of delivery | Within six months after the final scheduled publication end date purchased or extended; pre-publication stopped-ad records: six months after stopping | Images, public copies, copy, approval records, totals and daily statistics are distinguished. Fixed contractual items, amounts and creative-version identifiers in orders are preserved separately as payment evidence. If data is linked to several ads, the last linked ad’s period applies. |
| Advertising orders, payments and cancellations / transaction evidence | Expired unpaid orders: 30 days from creation; actual contracts, payments and withdrawal records: five years | On account withdrawal, ads are stopped and refunds handled, then statutory evidence is moved to a separate access-restricted path. Advertising images/body copy are not automatically included in five-year transaction evidence. Only relevant complaint/dispute records are retained for three years. |
| Temporary advertising-display/sign-in data / authentication and deduplication | Display identifier: 60 seconds; web sign-in state: 10 minutes; access-address hash counter: one hour | Expired server data is deleted sequentially by five-minute cleanup jobs. Delays caused by errors or workload are reprocessed. OAuth provider tokens are used temporarily for sign-in checks and are not stored. |
| Advertiser business profile / future orders | Until account withdrawal | Managed separately from dog profiles in the app. A random browser payment-customer ID remains until site data is cleared. Social sign-in state follows Firebase authentication storage behavior; you can sign out. |
Current handling: app account withdrawal and web account/data deletion requests are separate paths. The web form can request deletion of walk/location records only. After receipt, the operator verifies identity and scope, destroys the requested data and reports the result. Receipt or account withdrawal does not mean immediate automatic deletion of all server/device copies. Statutory destruction duties apply regardless of a separate request.
4-1. Separate statutory preservation
These preservation standards apply only when transactions/records covered by the relevant legislation actually arise. They do not justify newly collecting uncollected information or retaining all ordinary member data. Only the minimum identifying details and history needed to confirm the relevant transaction/request are included. They must be separated from ordinary service data, used only for statutory purposes and destroyed when the period ends.
| Record | Period | Ground and scope |
|---|---|---|
| Transaction-related display/advertising records | Six months | Article 6 of the Act on Consumer Protection in Electronic Commerce and Article 6 of its Enforcement Decree; when covered display/advertising records arise. |
| Contract or withdrawal-of-offer records | Five years | Article 6 of the same Act/Decree; limited to actual consumer transactions and withdrawals. |
| Payment and supply of goods/services records | Five years | Article 6 of the same Act/Decree; limited to actual payment/supply records. |
| Consumer complaints or dispute-resolution records | Three years | Article 6 of the same Act/Decree; limited to complaints/disputes concerning the relevant consumer transaction. |
| Confirmation records and handling ledgers for location collection, use and disclosure | Six months from creation. Upon consent withdrawal, data within its scope must be destroyed without delay under Article 24(4). | Article 16(2) of the Location Information Act and Article 6 of the administrative/technical protection standards for location data. This does not require retaining the entire original walk route for six months. |
Web deletion forms and processing history are different from automatic confirmation records of personal location collection/use/disclosure. Stating statutory standards or operating a deletion page does not establish completion of recordkeeping, preservation or notifications to designated third parties. The three-month internet-log provision under the Protection of Communications Secrets Act applies to covered telecommunications operators and communication-confirmation data, not as a blanket basis for retaining every app log.
4-2. External-service retention and deletion
Deletion procedures differ between originals managed by the app and provider authentication, diagnostic and recovery data. The provider periods below do not mean the operator additionally uses every item of personal data throughout those periods.
| Data / provider | Period and deletion standard |
|---|---|
| Firebase Authentication data | Removed from the provider’s live and backup systems within 180 days after a deletion request for the service’s authentication account. Provider guidance states that security IP logs are kept for a few weeks. |
| Firebase Crashlytics crash tracking and associated identifiers | Provider guidance states 90-day retention, followed by the start of deletion procedures in live and backup systems. |
| Firebase Cloud Messaging installation identifiers | Retained until an installation-ID deletion API request, then removed from live/backup systems within 180 days. App account withdrawal alone does not guarantee this API call is complete. |
| Recovery copies of deleted Cloud Storage files | The currently confirmed soft-delete setting is seven days after deletion. Recovery retention differs from the end of public availability/use in the service. |
| Analytics, AdMob, map and hosting operating logs | Depends on each provider’s data types and console/contract settings. This policy does not currently assert a uniform three-month or one-year period. Actual periods and renewal settings need confirmation and supplementary notice. |
4-3. Destruction procedures and methods
Data and related records requiring destruction are identified based on retention expiry, fulfillment of purpose, account/consent withdrawal or a lawful deletion request. Minimum records required by other legislation must be kept separately after their grounds and end dates are checked; the remainder must be destroyed without delay.
Electronic files are deleted so that they cannot be recovered or reproduced. Paper records, if held, are shredded, incinerated or otherwise destroyed. Outsourced data follows the provider’s deletion procedure. Hiding, access blocking and account disconnection are distinguished from permanent destruction of originals.
A dispute alone does not justify indefinite retention of all personal data. Statutory preservation obligations or another lawful basis and the minimum necessary scope must be checked, and data destroyed when the reason ends. Delayed/failed deletion must be rechecked; the requester is informed of the actual scope and outcome.
5. Contractors and external services
External processing includes storage, authentication, servers and push services through Google Firebase/Google Cloud, and website hosting through AWS. Contractor processing is distinguished from independent processing by sign-in, map and advertising businesses, and sharing with other users you choose. Processing contracts must reflect purpose restrictions, safeguards, subcontractor management and supervision under Article 26 of the Personal Information Protection Act, with compliance monitored.
| Provider / service | Role and data |
|---|---|
| Google · Firebase / Google Cloud | Authentication; storage of accounts, walks, content, currency data and images; live locations; account-deletion and advertising/partnership inquiries; server features and push notifications. |
| Google · Analytics / Crashlytics / AdMob | Usage analysis that may be linked to member identifiers, device/app diagnostics, advertising and related identifiers/request data. |
| Google · Apple · Kakao · Naver sign-in | Account linking through the selected provider’s authentication and permitted profile data. Each provider’s policy applies to its own account processing. |
| Naver Cloud · Google Maps Platform | Necessary map, coordinate and search requests for selected maps, place discovery and address lookup. |
| Apple · Google device location services | Device location measurement and exchange of walk controls/status between phones and connected watches. |
| National Tax Service business-authenticity API | Verification of business registration number, representative name and opening date when verification is requested. |
| Amazon Web Services | Website static-file storage/distribution and CloudFront access-request processing. |
| Google Fonts | Website fonts. External requests may transmit IP addresses and browser-request information to the provider. |
| Toss Payments Co., Ltd. | Advertising payments, cancellations, refunds and transaction evidence. Order number, product name, amount, random customer identifier, purchaser business name and email are transmitted. Payment-method information is entered directly on Toss’s payment screen; its terms/privacy notice explain actual data and periods. Applies when the contract and features are activated. |
Dog emoticon creation includes the operator reviewing submitted photos and requests. The actual external AI/image-tool providers, transferred fields and retention terms must be separately explained after operational confirmation; we do not currently assert automatic transmission to a specific AI company.
6. Overseas transfers and processing
Not all data is stored only in Korea. Confirmed storage locations are distinguished from processing requiring further checks. A provider’s business address may differ from the actual storage region.
Overseas transfers require a basis under Article 28-8 of the Personal Information Protection Act. Outsourced processing/storage necessary for a contract must meet Article 28-8(1)(3) and mandatory notice requirements. Transfers relying on separate consent require the necessary information and separate consent. This is not used as a blanket basis for advertising transfers unnecessary for contract performance.
| Recipient / location | Data, purpose, timing and method | Retention, refusal and checks |
|---|---|---|
| Google LLC / Firebase Authentication · United States | Selected sign-in provider identifiers, supplied email/profile data and authentication-request information. Sent over encrypted networks during sign-in/account management. | Processed while needed to maintain the authentication account; after deletion requests, provider removal timelines follow section 4-2. Refusal may limit account features using this authentication. |
| Google / Firebase Realtime Database · Singapore | Live public locations, profiles, sessions and sharing/read authorizations. Sent over encrypted networks during relevant feature use for nearby display and access control. | Location/authorization validity and cleanup follow sections 3 and 4. You can choose not to share or turn it off. Contact support to refuse overseas transfer or request deletion; affected features requiring transfer may be limited. |
| Google / Cloud Storage · United States (Iowa) | Profile/content/creation photos and generated outputs. Sent over encrypted networks for storage/delivery during upload, sharing or creation. | Retained according to the purpose and deletion procedures; soft-delete copies may remain for seven days. You can decline uploads, limiting those features. |
| Google and other sign-in, analytics, advertising, diagnostic and map providers | Authentication, usage events, device and request information for the relevant features is processed through SDKs/networks. | Actual processing countries, detailed fields, periods, contractor contacts and legal grounds are to be supplemented after contract/operational checks. We do not describe all processing as occurring in one country or period without confirmation. |
| AWS CloudFront · Google Fonts | IP, browser and access information from website/font requests may be processed through global delivery networks. | The website-file distribution configuration is in Seoul. Edge locations, log retention and provider-specific conditions require separate confirmation. |
The default Firestore and major Cloud Functions use the Seoul region. Overseas-transfer questions, refusal or processing-suspension requests can be sent to skylife927@gmail.com; affected features and processing scope will be explained. Viewing this page is not overseas-transfer consent.
7. Advertising, analytics and browser storage
The app uses Firebase Analytics to analyze screen/feature events, which may be linked to signed-in member identifiers. Crashlytics processes errors/diagnostics in release environments. These are not described as completely anonymous statistics.
AdMob advertising may process device/advertising identifiers and request information needed for ads. Processing varies with OS/SDK settings. We do not currently state that in-app analytics opt-out or separate consent screens for all ads are fully implemented; these choice procedures require further work.
Check the restrictions available in your device’s privacy, tracking and advertising settings. Names and scope vary by OS. Changing settings does not delete previously stored data. Collection/use requests can be sent to support.
The website stores your language choice in browser localStorage. Clearing site data removes it, and you can choose your language again on returning. The currently reviewed website code has no separate visitor-analytics tags or ad pixels; hosting/external-font access processing is separate.
8. Access, correction, deletion, suspension and withdrawal
You may request access, correction, deletion, suspension of processing or withdrawal of consent for personal data such as accounts, profiles and content. Edit information available in the app directly, or email support. Results are provided according to applicable statutory deadlines and procedures.
Change device location permissions or end a walk to stop additional location recording. Live walk-location sharing can be turned off separately. Refusing location permission may limit current-location recording/discovery features.
To request access, notice or correction of personal location data and collection/use/disclosure confirmation records, temporary suspension, consent withdrawal or deletion, email skylife927@gmail.com. Account/walk-data deletion can also be requested on the web deletion page. Do not send passwords or resident registration numbers. Necessary account-verification methods are explained separately.
The app separately explains and obtains consent for location-service terms, personal-location collection/use and walk-history retention. Live sharing starts on by default but can be switched off each time. You can change or withdraw consent through location-service consent management.
When an agent submits a request, lawful authorization/representation may be checked. Only minimum account-verification information is requested; you do not need to send unnecessary personal data in advance.
If a rights request is refused or restricted, statutory reasons and appeal methods must be explained. Exercising statutory rights does not result in disadvantages in unrelated services.
9. Account and data deletion requests
In the app, go to My → Settings → Delete account. Recent sign-in or other checks may be required to protect your account. If you cannot use the app or need related data deleted, use the account-deletion request page.
Provide a contact email, your sign-in method and the requested scope, such as account, walks, posts or photos. If you cannot access your registration email, use an address where you can be contacted; identity checks will be explained separately. Do not send unnecessary materials such as passwords or identity-card copies.
Current account withdrawal includes cleanup of the authentication account/user profile and follow-up cleanup of push, follow and some creation assets. Simultaneous automatic deletion of all walks, territories, dogs, posts, comments, chats and photos is not fully implemented. Requests to delete specific walk/location data while keeping an account are accepted; after identity checks, the operator confirms the scope and destroys the data.
Statutory destruction obligations may apply regardless of a separate request. This notice explains operational limitations and does not restrict your rights. Results for originals, derived data and separately preserved records are explained.
After submission on the deletion page, identity is checked before deleting the account or requested data. Receipt and completed deletion are separate stages. The verified deletion scope is handled without delay and results sent to your contact email. Deleting the app alone does not withdraw the server account.
10. Children and legal representatives
Consent-based processing of personal data of children under 14 requires verified consent from a legal representative. Notices must also be understandable to children. App-store age ratings or acceptance of general terms cannot replace this process.
Completion of a separate legal-representative verification system has not currently been confirmed. If child data processed without necessary consent is identified, collection/use must stop and necessary actions such as destruction taken. Children and legal representatives can request access, correction, deletion or withdrawal through support.
Guardians of children aged eight or younger and other persons covered by Article 26 of the Location Information Act may, for protection of life or bodily safety, consent to personal-location use/disclosure or exercise suspension, access, correction and withdrawal rights after statutory conditions and guardian status are verified. A family-account connection alone does not establish guardian status. Submit requests to support; necessary evidence and handling are explained individually.
11. Safeguards
Technical controls include authentication, data-access rules, server-permission checks/expiry and encrypted communication. Operating access is managed within necessary scope; errors and fraudulent requests are monitored.
This does not guarantee complete anonymization, end-to-end encryption of all data or absence of breaches in every situation. Administrative/technical protection and retention/destruction systems are continually reviewed.
12. Privacy contacts and remedies
Send personal/location-data requests to CatchCatch Customer Support at 010-8068-2335 or skylife927@gmail.com. This contact handles privacy/location protection and complaints. After checking a request, results or additional verification needs are explained.
The public bodies below provide privacy-infringement consultation and dispute mediation. Your right to statutory remedies is preserved.
| Item | Information |
|---|---|
| Personal data controller | CatchCatch · operator of PawCatch |
| Privacy protection and complaints | CatchCatch Customer Support |
| Contact | 010-8068-2335 · skylife927@gmail.com |
| How to submit | Email or the account/data deletion request page. Minimum identity-verification information is explained separately. |
13. Separate terms and revision history
October 12, 2026, v14: corrected the default live-sharing setting at walk start and actual access to private walks; supplemented confirmation-record retention, guardian rights for children eight or younger and others, and the privacy-support telephone number. Location-service terms were corrected to v7 on the same date. This does not replace consent to new location processing or establish completion of automatic recordkeeping/disclosure notifications.
October 12, 2026, v13: clarified preservation of existing consent without blanket re-consent solely for an app update, requests for deletion of specific walk/location records online and identity/destruction procedures, and the difference between unspecified nearby sharing and designated family sharing. Location-service terms became v6. This does not mean automatic statutory confirmation records or designated-third-party notifications have been implemented.
October 12, 2026, v12: compared location-law guidance with current legislation to clarify retention end points upon fulfillment of purpose/consent withdrawal and maximum separate-consent retention. Location-service terms became v5, supplementing operator contact and user rights.
September 22, 2026, v10: added advertising self-service guest drafts, advertiser profiles/orders/payment-provider handling, performance/access scope and retention/withdrawal procedures. Operational payments and paid in-app ads are activated after separate preparation; this notice does not itself begin live payments.
September 15, 2026, v9: distinguished service-data retention end points, statutory periods limited to applicable records, provider deletion timelines and destruction procedures. Supplemented controller/contact information, processing grounds/choices, consent withdrawal and overseas transfers, and corrected section numbering. This notice does not replace new collection/disclosure consent or extend retention or deploy automatic deletion.
September 13, 2026, v8: added advertising/partnership consultation through the business web form, required collection/use consent, inquiry access and cleanup after 30 days from rejection/closure or a maximum of 180 days for other inquiries.
September 7, 2026, v2: expanded account, profile, family, content, currency, business verification, advertising, analytics and deletion information; reflected actual storage regions and seven-day file recovery. The location-terms draft was separated to /location.
September 7, 2026, v1: explained differences between earlier descriptions and current service, and published location acquisition/sharing/retention information and draft location terms.
Corrections of current processing facts state their publication date and content and are not treated as new consent. Actual policy changes are announced with their content, reasons and application date, and necessary consent obtained separately. Notice is given at least seven days before application, or at least 30 days for important rights/obligations changes.