Privacy Policy
Funcia ("the Service") processes personal information as described below, in accordance with the Personal Information Protection Act of the Republic of Korea and other applicable laws.
- Effective date: October 16, 2026
- Operator: Kim, Hwan (individual)
- Service URL: https://funcia.kimhwan.kr
1. Information we collect
| Category | Items | How |
|---|---|---|
| Email sign-up | Username, email address, password (one-way hashed), display name (optional) | Sign-up form |
| Social login | Provider account ID, email address, name or nickname, profile picture URL | Provided by Google, GitHub, Naver or Kakao after your consent |
| Service use | Submitted source code, judging results, solve history, score | Generated while you use the Service |
| Solve process records | Editor insert/delete/paste events and their times while solving, times and durations of switching to other tabs or windows, fullscreen exits | Generated while a signed-in member solves a problem |
| Sign-in and security records | Sign-in time, success or failure, sign-in method, IP address, browser and OS, signed-in devices (sessions) | Generated when you sign in and use the Service |
| Community activity | Discussion posts and comments, votes, shared solutions, problem feedback (likes, difficulty votes, tag suggestions), notifications | When a member uses community features |
| Reports and inquiries | Report type, title and content, related problem or submission, page URL, browser, OS, language and screen size | When a member sends a problem report, bug report or inquiry |
| Consent records | Version and time of consent to the Terms and this Policy, confirmation of being 14 or older | At sign-up |
Information received through social login is limited to what you allow on each provider's consent screen. We never receive your social account password and do not request contacts, friend lists, posts or any other data not needed for sign-in.
2. Purposes
- Identifying members, signing in, and linking accounts (including linking a social account that has the same verified email)
- Email verification and account-security notices
- Judging code and providing submission history, statistics and rankings
- Preventing abuse and keeping operational records
- Ranking integrity: computing paste ratio, tab switching and unusually fast solves from solve process records to mark "self-solved" solutions and investigate cheating
- Account security: showing you your signed-in devices and sign-in history, and alerting you to new-device sign-ins and repeated failures
- Handling reports: checking and fixing problem errors and site bugs, and telling the reporter the outcome
- Running the community: publishing discussions, comments and shared solutions, sending reply and vote notifications, and filtering abuse and spam
We do not use personal information for any other purpose, and we do not use or sell it for advertising or marketing.
3. Google user data
This section describes exactly how Funcia ("the app", https://funcia.kimhwan.kr) accesses, uses, stores, shares, protects, retains and deletes data it receives when you choose Sign in with Google. Signing in with Google is optional; you can also sign up with an email address or another provider.
3.1 Data accessed
Funcia requests only these Google OAuth scopes: openid, email, profile. From them the app receives:
| Google data | Example | Required |
|---|---|---|
Google account ID (sub) | 1043… | Yes |
| Email address and whether Google has verified it | name@gmail.com, verified | Yes |
| Name | Hong Gildong | Yes |
| Profile picture URL | https://lh3.googleusercontent.com/… | Optional (shown if present) |
Funcia does not request access to Gmail, Google Drive, Calendar, Contacts or any other Google service, and does not read any data beyond the items above.
3.2 Data usage
Google user data is used only to:
- create your Funcia account and sign you in;
- show your name and profile picture on your profile, submissions and rankings (you can change the display name in Settings);
- link your Google sign-in to an existing Funcia account that has the same, already verified email address;
- send account-security notices (for example, a sign-in from a new device) to that email address.
Google user data is not used for advertising, marketing, profiling, selling, or training artificial-intelligence or machine-learning models, and is not used for any purpose unrelated to the features above.
3.3 Data sharing
Funcia does not share, transfer, sell or disclose Google user data to any third party. No analytics, advertising or tracking services receive it. The only exception is a disclosure required by law.
3.4 Data storage and protection
- Google user data is stored in Funcia's own PostgreSQL database on servers operated directly by the operator in the Republic of Korea; it is not stored with any third-party cloud provider.
- The database is on an internal network that cannot be reached from the internet, and access is limited to the operator.
- All traffic between your browser and Funcia is encrypted with HTTPS (TLS).
- Google OAuth access tokens are used only during the sign-in request and are not stored. Funcia does not request offline access or refresh tokens.
3.5 Data retention and deletion
- Google user data is kept only while your Funcia account exists.
- Delete your account at any time in Settings → Account → Delete account. Your Google account ID, email, name and profile picture are deleted immediately, and your submissions remain only in anonymized form for problem statistics.
- Unlink Google without deleting your account in Settings → Linked accounts.
- You can also revoke Funcia's access at https://myaccount.google.com/permissions, or ask for deletion by email to akon47@naver.com; requests are handled within 7 days.
- Database backups containing deleted data are overwritten within 30 days.
3.6 Limited Use
Funcia's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
4. Retention
- Account information: until you delete your account, after which your email, username, name, profile picture and social account links are destroyed without delay.
- Submitted code and judging records: on account deletion they are unlinked from you and kept only in anonymized form for problem statistics.
- Sign-in and security records: kept for up to one year, then destroyed.
- Community activity: kept until you delete it or your account; on account deletion your posts and comments remain with the author anonymized. Notifications are deleted after 90 days.
- Reports and inquiries: kept for one year after they are closed, then destroyed; on account deletion they are unlinked from you (anonymized).
- Solve process records: records not linked to a submission are destroyed after 30 days; records linked to submissions are kept until you delete your account, and destroyed with it.
- Where a law requires longer retention, for that period.
5. Publishing solve process records
By default only you and the operator can view your solve process records. Only if you turn on "Publish my solve replays" in Settings are replays shown to other members who have already solved the same problem. You can turn this off or hide individual solves at any time. The self-solved ratio computed by the Service is shown in rankings.
5-1. Sharing and outsourcing
We do not provide personal information to third parties and do not outsource its processing. The Service runs on servers in Korea managed directly by the operator. The only exception is a request made under law.
6. Destruction
Information is destroyed without delay when its retention period ends or its purpose is fulfilled. Electronic files are deleted irrecoverably; copies in backups are deleted when the backup retention period (up to 30 days) ends.
7. Your rights
You may view or correct your information at any time, and request suspension of processing or deletion (account deletion), either in Settings or by contacting us below. Social account links can be removed under Settings > Linked accounts.
8. Children
The Service does not accept members under 14. Age is confirmed at sign-up.
9. Security measures
- Passwords are stored with a one-way hash (bcrypt).
- All traffic is encrypted with HTTPS.
- Databases and internal services sit on an internal network that is not reachable from outside, with access limited to the operator.
- Submitted code runs only in an isolated sandbox.
10. Cookies
The Service uses only essential cookies for keeping you signed in (session) and preventing forged requests (CSRF). No advertising or tracking cookies are used. Editor settings and code drafts stay in your browser's local storage.
11. Privacy officer
- Name: Kim, Hwan
- Email: akon47@naver.com
12. Changes
We announce changes on the Service 7 days before they take effect (30 days for changes unfavorable to users).