정책 문서

Policy Pages

Arctic Habit / Privacy Policy

Privacy Policy

서비스
Arctic Habit
문서
Privacy Policy
시행일
최종 수정일
목차
  1. 1. About this policy
  2. 2. Data we collect
  3. 2.1. Data stored on our server
  4. 2.2. Data kept only on your device
  5. 2.3. Rewarded ads (Google AdMob)
  6. 2.4. App analytics and crash reporting (Google Firebase)
  7. 2.5. Subscriptions
  8. 2.6. Data we don't collect
  9. 3. Why we use your data and our legal bases
  10. 3.1. Legal bases under Korean law (PIPA)
  11. 3.2. Legal bases under the EU/UK GDPR
  12. 4. How long we keep your data
  13. 4.1. How we delete data
  14. 5. Service providers and international transfers
  15. 5.1. International transfers
  16. 6. Sharing
  17. 6.1. Behavioural data collected by the ad SDK (personalised ads)
  18. 6.2. On-device identifiers and how to refuse them
  19. 7. Your rights
  20. 7.1. If you live in the United States
  21. 7.2. If you are in the EEA, the UK or Switzerland
  22. 8. Security
  23. 9. Children
  24. 10. Privacy officer and contact
  25. 11. Where to get help
  26. 12. Changes to this policy

1. About this policy

Arctic Habit (the "Service") is a focus timer that grows your own Arctic island as you focus. It is operated by GO2GYM STUDIO (고투짐 스튜디오, "we", "us"), the data controller for the personal data described here. We comply with Korea's Personal Information Protection Act (PIPA) and other applicable laws. This policy explains what we collect, why, how long we keep it and the rights you have. If this English version and the Korean version differ, the Korean version prevails to the extent permitted by the law that applies to you.

Our core principle: your focus history and your island stay on your device. Our server stores only the minimum data needed for sign-in, invitations and confirming rewarded-ad rewards. The Service uses rewarded ads (Google AdMob), app analytics and crash reporting (Google Firebase), subscriptions paid through Apple, and Focus Lock, which uses iOS Screen Time. Section 2 explains what each of them handles.

2. Data we collect

2.1. Data stored on our server

You need an account to use the Service. You create one with Sign in with Apple, Google Sign-In or an email sign-in code, and we can't create one without an email address, given directly or confirmed by Apple or Google.

Data When Purpose
Email address When you sign in with an email code, or the email confirmed by Apple or Google when you sign in with them Identifying your account, sending sign-in codes, answering your requests
Sign-in provider identifier and linked sign-in methods When you sign in with Apple or Google Identifying your account and letting you sign in again
Name and profile photo URL Only if Apple or Google provides them during sign-in They may be kept with the sign-in record; we don't display them or use them for anything else
Account ID (a random value), sign-up and sign-in times When you sign up or sign in Managing your account and keeping you signed in
Invite code, invitation relationship (whose code you signed up with), number of friends who signed up with your code, seal unlock record When you sign up or enter an invite code Providing invitations and the seal and orca unlocks they lead to
Rewarded-ad records (where you watched the ad, a random number for the focus session, ad unit, request and reward-confirmation times, Google's reward transaction ID) When you watch a rewarded ad on the focus completion screen Confirming the ad was watched, giving the reward only once per session and preventing duplicate rewards
Apple sign-in refresh token (stored encrypted) Only if you sign in with Apple Disconnecting Apple sign-in when you delete your account
Account deletion record and a keyed hash of the deleted sign-in identifier (pseudonymous data) When you delete your account Confirming deletion and preventing invitation rewards from being claimed again by deleting and re-creating the same sign-in account
Access logs (IP address, device and browser details, request time) Automatically when our server is used Security and troubleshooting

2.2. Data kept only on your device

Your focus history (start and end times, focus time, rewards), your island (animal and decoration placement, terrain), statistics, to-dos and tags, Focus Ice, Focus Lock settings and presets, and sound, language, reminder and aurora display settings are stored only on your device and are never sent to our server. We can't see this data. However, the app analytics in section 2.4 include some usage records, such as focus minutes, in a form that isn't linked to your account.

Focus Lock locks apps during a focus session using Apple's Screen Time, only if you allow Screen Time access. If you are an Arctic Pro subscriber and choose apps to keep unlocked, Apple gives the app only coded references to them, not their names or how you use them. These references and the lock records never leave your device.

There is no sync or backup between devices, so this data can't be recovered if you delete the app or change devices. The daily reminder and the focus status on your Lock Screen (Live Activity) are handled on your device; we don't collect push notification tokens.

2.3. Rewarded ads (Google AdMob)

The only ads in the Service are rewarded ads, and an ad plays only when you choose to watch one on the focus completion screen. Arctic Pro subscribers don't see ads. While an ad is loaded and shown, Google's ad SDK collects the following and sends it to Google:

  • Device and app details (device model, OS version, app version, language), IP address and an approximate location estimated from it
  • Ad impressions, views and clicks, and ad performance and error diagnostics
  • The advertising identifier (IDFA), only if you allow it in iOS's App Tracking Transparency prompt. Ads and rewards work the same if you don't; you then don't see ads personalised with the advertising identifier.
  • Reward confirmation data: to confirm that you watched the ad in full, the app passes your account ID (a random value) and the ad request number to Google, and when the ad ends Google sends them back to our server with a signed confirmation. We never pass your email address or name.

Right after you sign in, iOS shows the App Tracking Transparency prompt once. If you are in the European Economic Area (EEA), the UK or Switzerland, Google's consent form follows, and you can change or withdraw your choice at any time in the app under Settings → Ad privacy options. This option appears only where Google requires consent. Google processes this data to serve and measure ads and prevent fraud, under the Google Privacy Policy.

2.4. App analytics and crash reporting (Google Firebase)

To improve the Service we use Google Firebase (Analytics and Crashlytics) to collect:

  • App usage: events Firebase records automatically, such as first open, app opens and time in the app; focus sessions started (planned minutes), completed (focused minutes, reward tier) or abandoned (planned minutes, minutes focused before stopping); ad rewards applied; animals and decorations placed or moved on the island (item type, number of animals sharing a cell); times the payment (Pro) screen is opened; subscription purchases started (which plan) and their result; the product, price and currency of each new subscription purchase (including free-trial starts); whether you use Arctic Pro (Pro or free); sign-in method; whether the introduction was completed or skipped
  • Device and app details: device model, OS version, app version, language, country and region estimated from your IP address, and an app instance ID that Firebase creates for each installation
  • Crash reports: the error, device state and recent app usage when the app quits unexpectedly

How this works depends on where you are:

  • EEA, UK and Switzerland: app analytics starts switched off and is turned on only if you consent, in Google's consent form, to storing and accessing information on your device. Until then no analytics information is stored on or read from your device. If you withdraw consent in Settings → Ad privacy options, it is switched off again.
  • Everywhere else: app analytics is on.
  • Everywhere: turn off Settings → Share usage statistics in the app and no app analytics is sent; the app instance ID used until then is reset. Crash reports are still sent when this is off.
  • Crash reporting runs in all regions to keep the app stable.

We don't send your email address, name, account ID or invite code to Firebase, and we don't use the advertising identifier for analytics. Google signals and data sharing with Google are turned off. We use this data only in aggregate to improve the app and fix errors.

2.5. Subscriptions

Apple handles payment, renewal, cancellation and refunds for the Arctic Pro subscription in the App Store. We never receive your card number or other payment details. The app checks Apple's transaction records on your device to see whether your subscription is active and whether you have made a first paid purchase (which unlocks the orca), and doesn't send your purchase history to our server. Subscription screen use, purchase results, the product, price and currency of new subscription purchases, and whether you use Pro are part of the app analytics in section 2.4, without being linked to your account (no card numbers or other payment details).

2.6. Data we don't collect

  • Government ID numbers such as Korean resident registration numbers, and your phone number or postal address
  • Precise (GPS) location, contacts, photos, health information or other sensitive data
  • Card numbers or other payment details
  • The names of apps you choose in Focus Lock, or how you use them

We don't sell your personal data. The advertising identifier is used for advertising only if you allow app tracking (section 6.1).

We use the data we collect only to:

  1. Create your account, sign you in and identify your account
  2. Send sign-in code emails
  3. Provide invitations and the seal and orca unlocks they lead to, and prevent invitation-reward abuse
  4. Serve rewarded ads, confirm that ads were watched and give rewards, and prevent duplicate rewards
  5. Check your Arctic Pro entitlement (on your device, through Apple)
  6. Improve the Service through usage statistics and crash analysis
  7. Process account deletion and disconnect sign-in providers
  8. Keep the Service secure, fix problems and answer your requests

Under Article 22(3) of PIPA, we tell you separately which data we process without your consent and which only with it.

Data Legal basis Consent needed
Account data, sign-in code emails, invitation data, rewarded-ad records and reward confirmation data, Apple sign-in refresh token, support emails Entering into and performing our contract with you (Art. 15(1)(4)) No
Access logs, account deletion records, keyed hashes of deleted sign-in identifiers Our legitimate interest in security and preventing invitation-reward abuse (Art. 15(1)(6)) No
App analytics data and crash reports (Firebase) Our legitimate interest in keeping the Service stable and improving it (Art. 15(1)(6)); for users in the EEA, the UK and Switzerland, app analytics only with consent No (consent needed for app analytics in the EEA, UK and Switzerland)
Advertising identifier (IDFA) Your consent (Art. 15(1)(1)), given in iOS's App Tracking Transparency prompt Yes
Storing ad information on your device and personalised ads for users in the EEA, the UK and Switzerland Your consent (Art. 15(1)(1)), given in Google's consent form Yes

You can ask us at any time to stop processing that relies on our legitimate interest (section 7).

If you are in the EEA, the UK or Switzerland, we rely on the following legal bases under the EU/UK General Data Protection Regulation (GDPR).

Purpose Legal basis
Creating and signing in to your account, sending sign-in codes Performance of our contract with you (Art. 6(1)(b))
Invitations and the seal and orca unlocks Performance of our contract with you (Art. 6(1)(b))
Serving rewarded ads you choose to watch and confirming and giving their rewards Performance of our contract with you (Art. 6(1)(b)); storing or reading ad information on your device and personalised ads only with the consent you give in Google's form (Art. 6(1)(a))
Checking your Arctic Pro entitlement (on your device, through Apple) Performance of our contract with you (Art. 6(1)(b))
App analytics (Firebase Analytics) Your consent given in Google's form (Art. 6(1)(a)); you can withdraw it in Settings → Ad privacy options
Crash reporting (Firebase Crashlytics) Our legitimate interest in finding and fixing errors (Art. 6(1)(f))
Preventing invitation-reward and ad-reward abuse Our legitimate interest in keeping rewards fair (Art. 6(1)(f))
Processing account deletion and disconnecting sign-in providers Performance of our contract and legal obligations (Art. 6(1)(b), (c))
Security, troubleshooting and answering your requests Our legitimate interest in running a safe service (Art. 6(1)(f))

4. How long we keep your data

Data Retention
Account data (email, sign-in identifiers, name and photo URL, invite code, unlock record) Deleted without delay when you delete your account
Rewarded-ad records Deleted without delay when you delete your account
Apple sign-in refresh token Deleted without delay when you delete your account or disconnect Apple sign-in in your Apple settings
Account deletion record 30 days after deletion is completed
Keyed hash of a deleted sign-in identifier 90 days after you delete your account
App analytics data (Firebase Analytics) 14 months after collection
Crash reports (Firebase Crashlytics) 90 days after collection
Ad-related data (Google AdMob) According to Google's retention policy
Access logs Deleted automatically after our server provider's log retention period
Sign-in code email records According to the email provider's retention (section 5.1)
Support emails 1 year after your request is resolved
  • If a friend you invited deletes their account, their account ID is removed from the invitation record. Your invitation count and an unlocked seal or orca stay as they are.
  • The keyed hash is pseudonymised with a secret key, so the original identifier can't be read from it. We use it only to stop the same sign-in account from claiming invitation rewards again by leaving and re-joining. We don't process pseudonymised data for statistics or research under Article 28-2 of PIPA.
  • Deleting your account also deletes that account's focus history and island on the device you delete it from. Data on other devices is removed when you delete the app there.
  • Analytics data and crash reports aren't linked to your account, so deleting your account doesn't remove them; they are deleted automatically after the periods above.

4.1. How we delete data

  • Procedure: when a retention period ends or the purpose has been fulfilled, the data is deleted without delay under the responsibility of our privacy officer. Server data tied to your account is deleted automatically as part of account deletion; data kept for a set period is deleted when that period ends.
  • Method: electronic files are deleted so that they can't be recovered or reproduced. Any personal data on paper is shredded or incinerated.
  • Retention required by law: we currently keep no personal data because another law requires it.

5. Service providers and international transfers

We use the following providers to process personal data on our behalf.

Provider Service Data Location
Supabase, Inc. Database and sign-in server The data in section 2.1 Republic of Korea (Seoul)
Google LLC (Firebase) App analytics and crash reporting The data in section 2.4 United States and other Google facilities
Plus Five Five, Inc. (Resend) Sending sign-in code emails Email address, subject and body of the code email, delivery status United States (emails are sent from servers in Tokyo, Japan)
Cloudflare, Inc. Forwarding support emails Your email address and message United States and other Cloudflare facilities
Google LLC (Gmail) Receiving and storing support emails Your email address and message United States and other Google facilities

Apple (Sign in with Apple, App Store payments, Screen Time) and Google (Google Sign-In, AdMob ads) process data for those features under their own privacy policies.

5.1. International transfers

App analytics and crash reporting (Google Firebase)

  • Data transferred: the app usage records, device and app details and crash reports in section 2.4
  • Destination and recipient: United States and other countries, Google LLC
  • Recipient contact: googlekrsupport@google.com
  • When and how: while you use the app, and when the app next opens after a crash, over an encrypted connection (TLS)
  • Purpose: usage statistics, finding and fixing the causes of crashes
  • Retention: analytics data 14 months, crash reports 90 days
  • How to refuse: turn off Settings → Share usage statistics in the app and no app analytics is sent. In the EEA, the UK and Switzerland you can also withhold or withdraw consent in Settings → Ad privacy options. If you don't want crash reports sent, you can ask us to stop this processing at the address in section 10, or stop using the app.

Rewarded ads (Google AdMob)

  • Data transferred: the device and app details, IP address, ad activity and reward confirmation data (account ID and ad request number) in section 2.3, and the advertising identifier if you allow tracking
  • Destination and recipient: United States and other countries, Google LLC
  • Recipient contact: googlekrsupport@google.com
  • When and how: over an encrypted connection when you choose to watch an ad and it is loaded and shown
  • Purpose: serving and measuring ads, confirming ad views, preventing ad fraud
  • Retention: according to Google's retention policy
  • How to refuse: if you don't watch rewarded ads, this transfer doesn't happen. The advertising identifier isn't sent if you don't allow tracking or turn it off in Settings → Privacy & Security → Tracking on your device.

Email sign-in codes (Resend)

  • Data transferred: email address, subject and body of the code email, delivery status
  • Destination and recipient: United States (emails are sent from servers in Tokyo, Japan), Plus Five Five, Inc. (Resend)
  • Recipient contact: support@resend.com
  • When and how: when you ask for an email sign-in code, over an encrypted connection (TLS)
  • Purpose: sending the code email and checking its delivery
  • Retention: according to Resend's retention policy; sent email data is generally kept for 30 days. See the Resend privacy policy.
  • How to refuse: if you sign in with Apple or Google instead of an email code, this transfer doesn't happen.

Support emails (Cloudflare, Google)

  • Data transferred: your email address and message
  • Destination and recipient: United States and other countries, Cloudflare, Inc. and Google LLC
  • Recipient contact: Cloudflare dpo@cloudflare.com, Google googlekrsupport@google.com
  • When and how: when you email us, over an encrypted connection
  • Purpose: forwarding, storing and answering your message
  • Retention: 1 year after your request is resolved
  • How to refuse: if you don't email us, this transfer doesn't happen.

Safeguards for data from the EEA and the UK: our server is in the Republic of Korea, which the European Commission and the United Kingdom have recognised as providing an adequate level of data protection. Where a transfer outside the EEA or the UK (for example to the United States) needs safeguards, we rely on the standard contractual clauses offered by the provider or, where the provider is certified, the EU-U.S. Data Privacy Framework and its UK extension. You can ask us for a copy of these safeguards at the address in section 10.

6. Sharing

We don't provide your personal data to third parties, except where the law requires it and in the case described in section 6.1. The providers in section 5 use data only to provide their services to us. In the invitation feature, the person who invited you sees only the number of friends who signed up with their code — never your email address or name.

6.1. Behavioural data collected by the ad SDK (personalised ads)

When you watch a rewarded ad, Google's ad SDK in the app collects the data below directly, and Google uses it for advertising.

Item Details
Company collecting and processing Google LLC (Google AdMob)
Behavioural data collected Ad impressions, views and clicks, and ad activity in the app. The advertising identifier (IDFA) if you allow app tracking; Google may use it to link your ad activity in other apps and websites for personalised ads
How it is collected Automatically by the SDK when you choose to watch an ad and it is loaded and shown
Purpose Serving ads (personalised ads if you allow app tracking), measuring ad performance, preventing ad fraud
Retention According to the Google Privacy Policy

How to refuse personalised ads

  1. When the app asks to track your activity, choose Ask App Not to Track.
  2. If you already allowed it, turn Arctic Habit off in Settings → Privacy & Security → Tracking on your device. To block tracking requests from all apps, turn off Allow Apps to Request to Track on the same screen.
  3. In the EEA, the UK and Switzerland, you can change your ad consent in the app under Settings → Ad privacy options.

Rewarded ads and rewards work the same if you refuse personalised ads. App analytics data (section 2.4) is never used for advertising. Some US state privacy laws treat this processing, when you allow app tracking, as "sharing" personal information for cross-context behavioural advertising or as "targeted advertising" (section 7.1). You can send questions or complaints about behavioural data to the address in section 10.

6.2. On-device identifiers and how to refuse them

The app doesn't use web cookies. The SDKs in the app do create or read the following identifiers on your device.

Identifier Used for How to refuse
App instance ID App analytics (Firebase Analytics) Turn off Settings → Share usage statistics in the app (this resets the identifier). In the EEA, the UK and Switzerland you can also withhold or withdraw consent in Settings → Ad privacy options
Installation ID Crash reporting (Firebase Crashlytics) Reset when you delete the app
Advertising identifier (IDFA) Rewarded ads (Google AdMob) Don't allow app tracking, or turn it off in Settings → Privacy & Security → Tracking on your device

7. Your rights

You can at any time ask to access, correct, delete or stop the processing of your personal data, and withdraw any consent you have given.

Right How
Delete your account In the app: Settings → My account → Delete account (not available during a focus session)
Turn off app analytics In the app: Settings → Share usage statistics
Change app tracking permission Settings → Privacy & Security → Tracking on your device
Change ad and app analytics consent (EEA, UK, Switzerland) In the app: Settings → Ad privacy options
Cancel a subscription Settings → Apple Account → Subscriptions on your device. Deleting the app or your account doesn't cancel it
Access, correction, stopping processing and other requests Email us at the address in section 10; we'll verify your identity first
Turn off the daily reminder App settings or device settings

You can also make a request through a legal representative or someone you have authorised. We handle requests without delay, and requests under Korean law within 10 days. Apple sign-in is disconnected automatically when you delete your account; if that isn't possible, the app shows you how to disconnect it in your Apple Account settings. We don't make decisions that significantly affect you based solely on automated processing.

7.1. If you live in the United States

Depending on the state you live in (for example California, Virginia, Colorado or Connecticut), you may have the right to know what personal information we collect and how we use and disclose it, to access and receive a copy of it, to correct it, to delete it, and to opt out of the "sharing" or targeted advertising described in section 6.1.

Category What it includes Source
Identifiers Email address, account ID, sign-in provider identifier, name and photo URL if provided, invite code, IP address, Firebase app instance ID, advertising identifier (only if you allow tracking) You, your device, Apple or Google sign-in
Internet or other electronic network activity App usage events, crash reports, ad views and interactions, rewarded-ad records, access logs Your device and our server
Commercial information Subscription purchase attempts and results, the product, price and currency of new subscription purchases, and whether you use Pro (in app analytics) Your device
Approximate location Country, region or approximate location estimated from your IP address (never precise location) Your device's connection
  • We use these categories for the purposes in sections 2 and 3 and keep them for the periods in section 4. We disclose them to the service providers in section 5 for those purposes.
  • The only disclosure that may count as "sharing" or targeted advertising is the one to Google described in section 6.1, and it covers identifiers, network activity and approximate location. We don't sell personal information, and we don't knowingly sell or share the personal information of anyone under 16.
  • Sensitive personal information: we handle only sign-in credentials (the email sign-in code and the encrypted Apple sign-in token), and only to sign you in and to delete your account. We don't use sensitive personal information to infer characteristics about you.
  • How to make a request: email us at the address in section 10. To opt out of sharing, don't allow tracking or turn it off as described in section 6.1. We verify your identity by confirming that you control the email address on your account. You may use an authorised agent; we'll ask for your signed permission and may ask you to confirm your identity with us directly.
  • We respond within 45 days. If we need more time, we'll tell you why, and we may take up to another 45 days where the law allows. If we decline your request, you can appeal by replying to our decision, and if you disagree with the result of the appeal you can contact your state's attorney general.
  • We won't deny you the Service, charge you a different price or give you a different quality of service because you exercise these rights.

7.2. If you are in the EEA, the UK or Switzerland

In addition to the rights above, you have the right to object to processing based on our legitimate interests, to ask us to restrict processing, and to receive the data you gave us in a structured, machine-readable format (data portability). You can withdraw consent for processing based on consent (app analytics, and storing ad information on your device and personalised ads) at any time in Settings → Ad privacy options; this doesn't affect processing before the withdrawal. We respond without undue delay and within one month. You may also complain to the data protection authority in the country where you live or work.

8. Security

  • Administrative measures: we keep the number of people who handle personal data to a minimum and manage access rights to our servers and admin tools.
  • Physical measures: our servers run in the data centres of our providers (section 5), and physical access control follows their security programmes.
  • All traffic between the app and our server is encrypted with TLS.
  • Database access to account data is restricted to server-side permissions.
  • Ad rewards are given only after we verify Google's signed server-side confirmation.
  • Apple sign-in refresh tokens are stored encrypted.
  • Deleted sign-in identifiers are kept only as keyed hashes, never in their original form.
  • Your sign-in session on the device is stored in the iOS Keychain.
  • If personal data is lost, stolen, leaked, altered or damaged, we notify you and the relevant authorities without delay and tell you how to limit the harm and how to seek compensation or dispute mediation.

9. Children

The Service isn't intended for children under 14, and we don't knowingly collect their personal data. If the law of your country sets a higher minimum age for consenting to data processing, that age applies. If we learn that an account belongs to such a child, we delete it without delay. Parents or guardians can ask for deletion at the address in section 10.

10. Privacy officer and contact

  • Controller: GO2GYM STUDIO (고투짐 스튜디오) · Business registration number 862-18-02788
  • Address: 83 Wolpyeongdong-ro (Wolpyeong-dong, Damoa Apartment), Seo-gu, Daejeon, Republic of Korea
  • Privacy officer: Jeonghwan Lee (Representative)
  • Phone: +82-10-7799-8696
  • Email: arctichabit@go2gym365.com

Our representative is also our privacy officer and handles access requests and privacy complaints. You can reach us by the email above or through the Support page.

11. Where to get help

If you need to report or get advice about a privacy violation, you can contact the following Korean bodies.

Body Contact
Personal Information Dispute Mediation Committee 1833-6972 / www.kopico.go.kr
Personal Information Infringement Report Center 118 (in Korea) / privacy.kisa.or.kr
Supreme Prosecutors' Office 1301 (in Korea)
Korean National Police Agency 182 (in Korea)

If you are in the EEA, the UK or Switzerland, you can contact the data protection authority in your country; if you live in the United States, you can contact your state's attorney general (sections 7.1 and 7.2).

12. Changes to this policy

This policy applies from the effective date shown on this page. When we change it, we post the changes and the new effective date here and keep a revision history. For changes that significantly affect you, we give at least 30 days' notice.

  • Revision history: for the first public release (1.0), added rewarded ads (Google AdMob) and App Tracking Transparency, app analytics and crash reporting (Google Firebase; in the EEA, the UK and Switzerland, analytics only with consent), Arctic Pro subscriptions paid through Apple, Focus Lock using Screen Time, to-dos and tags, and a setting to turn off app analytics (Settings → Share usage statistics). Added payment-screen views, the product, price and currency of new subscription purchases, and Pro status to app analytics. Added the legal bases (sections 3.1 and 3.2), how we delete data (section 4.1), international transfer details and safeguards (section 5.1), behavioural data and on-device identifiers (sections 6.1 and 6.2), and the rights of US and EEA users (sections 7.1 and 7.2).