Privacy Policy

Controller and privacy officer

열하나랩스 processes personal information to provide HARNESS. The privacy officer is 권용현 / Representative. For privacy inquiries or requests for access, correction, deletion or restriction of processing, use the service inquiry screen, call 010-7771-9936, or write to 서울특별시 강남구 개포로110길 38, 102동 1303호.

Account and service information

Email, login identifiers and authentication sessions are used to identify accounts and maintain sign-in. Google sign-in processes the basic profile you permit, such as name, email and profile photo. Project names, categories, places, periods, weekdays, daily goals and target windows; account and project identifiers; daily measured time and time-slot records; and timer status and processing times are used to operate projects and show records.

Place verification and location information

The registered place name, latitude, longitude and verification radius are stored in the project. Location restrictions are optional. Projects with them enabled check location before starting and during recording; while running, checks may continue with an Android foreground-service notification when the screen is off or another app is in use.

Automatic recording processes location to verify a stay only for users who allow it in project settings, manually turn on this device's master automatic-recording switch (OFF by default) and the project switch, and complete separate notice, consent and background location permission steps. Turning automatic recording off or reaching the daily goal stops background location collection for that project's automatic recording. Pre-start location verification on the timer screen is separate. Location permission can be withdrawn in device settings. Manual recording with location restrictions OFF does not require location checks.

Location transmission and storage

Current coordinates, accuracy and measurement time for records using location restrictions are sent to the server to determine whether the designated place and recording interval conditions are met. The 1.1.4 preparation draft changes server record events to retain determination results, accuracy, time and processing status without cumulatively storing raw current-location coordinates. Registered place coordinates remain stored in project settings.

While offline or awaiting transmission, unsent evidence, including current coordinates needed for retransmission and record verification, is temporarily stored on the device. Coordinates are removed from that transmission evidence after server receipt is acknowledged. Uninstalling while data awaits transmission may make unsent device records unrecoverable.

Google Play subscription information

Purchase tokens and token verification values; order, product, plan and account-link identifiers; purchase, renewal and cancellation status; and subscription expiry and processing times are used to verify and restore subscriptions and prevent duplicate processing. Purchase tokens are encrypted and stored on the server and sent to Google to check renewal and cancellation status. Payment method information is entered through Google Play; HARNESS does not directly collect card numbers.

Shared challenges and record sharing

Friend codes, challenge titles and periods, invitations and participation requests, acceptance, rejection and sharing-consent status are used to operate challenges. After consent to participation and sharing, participants in the same challenge can see the participation name, project name, daily goal and progress status, today's recorded time and cumulative time during the challenge. Leaving stops record sharing while preserving personal projects and records.

Optional invitation notifications

When invitation notifications are enabled and device notification permission is granted, the push token is linked to the account, stored on the server and device, and used to send notifications. Device tokens and generic invitation notification text are sent to Expo's push notification service and Google Firebase Cloud Messaging. Notification content does not include friend names, challenge titles or activity records. Notifications can be disabled in device settings.

Inquiries and deletion requests

Inquiry content, related projects, replies, processing status and times, and account deletion requests, identity verification and processing history are used for customer support and exercising rights. Do not enter unrelated health information, identity-document copies or other people's personal information.

Device storage and web access

Device storage holds information needed to maintain sign-in, retain draft projects and selections, and recover timer and purchase processing. During homepage and web access, IP addresses, request paths and device and browser information may be used for page delivery and network protection.

Processors and external services

Supabase Pte. Ltd. (Singapore) provides account authentication and data storage. Cloudflare, Inc. (United States) provides homepage and web-file delivery and network protection. Google LLC (United States) provides sign-in, Google Play payment and purchase verification services.

The place-selection map uses Naver Maps from 네이버클라우드 주식회사 (Republic of Korea), and map display requests are sent to that provider. Place-name searches send the entered search terms to 네이버클라우드, without adding account identifiers or current coordinates to search requests. Optional invitation notifications use Expo and Google push notification services.

For the planned international release, map and place-search features outside Korea use Google Maps and Google Places. The search service sends the search text and requested result language to Google. The prepared search request does not add your HARNESS account identifier or current coordinates. Map display requests are also sent to the map provider. This addition takes effect only when the corresponding international features are released.

Processing outside Korea

During use, account, project and record information is transmitted over the network to Supabase; the primary database region is Seoul. Operational logs and service metadata are processed in the EU. Necessary technical support and operations may involve the main processor in Singapore, a US affiliate and global support personnel. Google sign-in and purchase verification and Cloudflare web delivery are also processed on providers' global servers.

Purposes are authentication, service delivery, purchase verification and security. Retention follows this policy and provider policies. Inquiries and requests to stop overseas processing can be made through the contacts above. If stopping processing limits authentication, subscription or recording functions, this will be explained. Invitation notifications transmit device push tokens and generic notification text to Expo and Google servers.

Website analytics

Optional Google Analytics tracking is not enabled in this international website candidate. If analytics is introduced, the information processed and your choices will be explained before activation. Information needed to deliver web pages and protect the network is handled separately as described in this policy.

Retention and deletion

Account, project, place and activity records and shared-challenge invitation and participation information are retained during service use. If deletion is requested through account management or an inquiry, the operator explains the schedule and outcome after identity and necessary transaction checks. Information with no retention obligation is destroyed without delay; electronic files are deleted so they cannot be recovered. Information required by law is separated and access restricted.

Statutory retention periods

Evidence of contracts, withdrawal, payment and service supply is retained for five years, and consumer complaint and dispute-handling records for three years, then destroyed. Periods are calculated from the relevant transaction or contract, or completion of dispute handling, and only necessary items are retained. General project, place and activity records are not all retained for the same period as transaction evidence.

Technical logs and recovery backups

Authentication, access and error logs are used for service operations and security checks. Current Supabase default retention is one day for API and database logs and one hour for Auth audit logs. Separate external log forwarding is not used. Internal recovery backups are deleted after a maximum of 30 days from creation. Previously completed deletions are reapplied when restoring a backup.

Your rights and safeguards

You may request access, correction, deletion or restriction of processing of your personal information and withdraw consent. Requests are handled after necessary identity verification; legally restricted items are explained with the reason and outcome. Encryption in transit and account-based access restrictions are applied, and operator access is restricted to designated accounts. Important policy changes are announced on the homepage or in the service.

Optional league participation and disclosure

League participation is optional, with explicit consent obtained before information is disclosed. Participants in the same competition group see your league nickname, selected avatar, representative badge, score and rank. Leaving withdraws participation and disclosure consent while preserving personal projects and activity records. Participation, consent and withdrawal status and score and result history needed to operate the league are managed in connection with your account.