Privacy Policy
How and why GIOOT processes information, and how it protects that information.
- Version
- 2026-10-16
- Effective date
- October 16, 2026
This translation is based on the Korean original. If the texts differ, please refer to the Korean original. 한국어 원문
1. Personal Information We Process
GIOOT processes the minimum information needed for registration and the Service. Tokens received through Google, Apple or Kakao sign-in verify identity; the provider type and unique identifier are linked to your account. Email addresses, names, gender, dates of birth and profile photos in authentication responses are not stored as GIOOT account information. We do not request access to Gmail, contacts or Google Drive files.
The personal information processing operator is 비엔비에셋 / 김복기. When you exercise your rights or request customer support by email, your reply address and inquiry are also used to handle the request.
The minimum registration age is 14 for residents of South Korea and 13 for residents of other countries, with any higher local legal requirement taking precedence. Registration does not separately request a country of residence or a response confirming age eligibility. We do not collect a date of birth or identity document for age checks and do not provide verified age authentication. The version and time of terms and privacy acceptance follow the existing retention rules for consent records.
- Registration and sign-in: social sign-in provider type, unique identifier issued by the provider, and @username
- Sessions and security: login session identifiers, token hashes, access logs and error logs
- Service use: posts, photos, reactions, reports and notification settings
- Location-based features: current location you allow us to access, post photo locations and their accuracy, and manually adjusted locations
- App operations: notification device tokens, app version and technical information needed for error and security checks. Optional Firebase Analytics and Crashlytics collection is currently disabled.
2. Purposes of Processing
Information supports account identification and security, nearby maps, post registration and public locations, reports and moderation, notifications, error analysis and quality improvements. Google sign-in information is used only for identity verification and account linking. Personal information is not sold or used for personalized advertising or AI model training.
3. Processing Location Information
The app or web reads your current location only with your permission. Current locations used for map exploration are not stored as a continuous travel history. Locations needed to register posts are separated into public locations and locations for internal verification.
Photo EXIF location may suggest a posting location; EXIF is removed from public image derivatives. You may withdraw location and photo permissions in device settings or select an area manually on the map. Without location permission, current-location checks and some on-site posting features are limited.
4. Retention and Use Periods
Social account connections, login sessions and personal notification information are deleted when account deletion is complete. Posts and local snaps of users who leave are immediately removed from public view, and their text, translations and comment content are deleted. Their photo files are removed progressively through separate deletion jobs, with failures retried. Ordinary post expiration ends map display; it is not the same as permanent deletion of photo files.
The periods below are GIOOT’s operational standards for security, handling inquiries and resolving rights-related disputes, not universal statutory retention periods. Where a legal obligation or an ongoing report or dispute requires preservation, only necessary records are retained separately with restricted access and deleted when that reason ends.
Free-text content of reports submitted by a user who deletes their account is deleted, and the reports are marked withdrawn. Report reason codes and case-linking identifiers may be retained to a limited extent to protect the review history of other users’ content.
Deletion status and internal identifiers for accounts, posts and local snaps are retained only while needed to maintain deletion processing and case links without incorrectly deleting other users’ content. These are not the original social provider identifier or username and are not guaranteed to be fully anonymous. Photos and text are not kept publicly visible as anonymous posts.
- Login cookies and refresh sessions: valid for up to 30 days. Expired server session and token-hash records are used for security checks for up to 90 days after expiry, then deleted. They are deleted immediately on account deletion.
- Ordinary access and error logs: up to 90 days from creation. Authentication tokens, passwords and precise locations are not logged.
- Inquiry, report and case-handling records: one year after resolution. Ongoing records or records requiring preservation are not automatically deleted before the matter ends.
- Evidence of terms and privacy acceptance: during membership and for three years after account deletion. Only document type, version, acceptance/withdrawal timestamps and internal identifiers needed for dispute handling are retained with restricted access.
- Operational permission-change and action audit records: one year from creation. Preservation of ongoing account-restriction or dispute records is reviewed again after resolution.
- Recovery backups: deleted within 30 days of creation. Current RDS automated backups are retained for seven days; manual backups also have a 30-day limit. Access is only for recovery, and existing account-deletion and purge states are reapplied after restoration.
5. Third-Party Disclosure and Outsourced Processing
Your public posts, photos, comments and usernames can be viewed by other users. GIOOT does not disclose personal information to third parties without consent or a legal basis. Social sign-in sends authentication requests to your chosen Kakao, Google or Apple service; that service’s privacy policy also applies.
Amazon Web Services, Inc. (AWS) provides outsourced server operations, database and photo storage, and backups. Primary storage for account identification, Service content, location and notification settings and other operational data is in the Seoul region, Republic of Korea (ap-northeast-2). Public photos may be delivered through AWS CloudFront’s global caches. AWS account numbers, secret keys and internal storage identifiers are not disclosed.
Mapbox, Inc. maps and address search may receive location or map area, IP address and device/network technical information. Google LLC’s Firebase Cloud Messaging and Apple Inc.’s APNs receive push tokens and information needed to deliver notifications. These providers use global infrastructure, including the United States, so these features may involve overseas processing. Data is sent over encrypted networks when a feature is requested, and processed for the periods needed to provide it and under each provider’s policies. Disable location or notification permissions or stop using the feature to limit transmission; some features may be unavailable. Questions about overseas processing: bnbasset83@gmail.com.
Optional Firebase Analytics and Crashlytics collection and automatic content translation are currently disabled. Before activation or changes to providers, transmitted data or processing countries, we disclose the purpose, data, recipient, countries, transfer methods and timing, retention periods and ways to refuse, and obtain consent where required.
6. Deletion Procedures and Methods
After identity verification for account deletion, social connections, sessions and notification information are deleted, and the account username is replaced with a non-public deletion-status identifier. The text and translations of your posts and local snaps, your comments, reactions and block list are deleted. Photos are no longer exposed through the public API, and stored originals, thumbnails and other files are deleted progressively. Deletion jobs are retried even after storage errors or server restarts.
Expired records are deleted after regular checks using methods that make recovery difficult. Other users’ photos and comments are not deleted together; photos of a departing user are deleted separately from the seven-day grace period for ordinary media cleanup. Storage deletion jobs and removal of existing caches or external copies may take time. Recovery backups are deleted within 30 days of creation and are not used for ordinary Service queries.
7. Your Rights
Users may request access to, correction or deletion of their personal information, suspension of processing, and withdrawal of consent. You may delete your account directly through My settings → Delete account in the app or at https://gioot.live/account/delete?lang=en. Without reinstalling the app, you can sign in on the web with the same social account, verify your identity and delete your account.
If you cannot sign in or need help exercising your rights, contact bnbasset83@gmail.com. Do not send passwords, social authentication tokens or an entire identity document by email. The operator will handle the request after verifying account ownership using only the minimum necessary information, and explain the reason if the request cannot be fulfilled.
8. Safeguards
GIOOT applies reasonable technical and organizational safeguards, including access restrictions, protection of data in transit, separation of secrets, storage of token hashes, and review of operational logs. Public APIs do not provide unnecessary account information or precise movement histories.
9. Cookies and Automatic Collection
HttpOnly cookies valid for up to 30 days maintain web sign-in and are removed on sign-out or account deletion. You may delete or block cookies in browser settings, which may limit persistent sign-in. Advertising and tracking cookies are not used. Optional Firebase Analytics and Crashlytics collection is currently disabled.
To understand service usage, we count each browser or app once per Korean calendar day, regardless of sign-in. A random value for the visit day and its delivery status are stored in browser local storage or protected app storage and replaced on the next visit day. Requests contain only the date, platform (web/Android/iOS) and that random value. They are not linked to accounts, social-login identifiers, IP addresses, GPS, advertising identifiers or push tokens. The server stores only a one-way verification value incorporating the date for deduplication.
The dedicated hourly cleanup keeps verification values for the current day and the previous two days and deletes older values in batches; interrupted work resumes after recovery. Date/platform totals without personal identifiers are retained to understand operational trends. Seven- and 30-day figures are sums of daily counts, so visits on different days or devices are included separately. Web counting is skipped for Do Not Track/Global Privacy Control signals or blocked storage, and app counting is skipped when storage is unavailable.
10. Responsible Person and Policy Changes
Operator: 비엔비에셋 / 김복기. Privacy officer: 김복기. Service and privacy inquiries: bnbasset83@gmail.com.
When this policy changes, the effective date and main changes will be announced on public pages and through Service notifications.
Users below the minimum registration age may not register. If you suspect an underage account or a child or youth privacy or safety violation, use in-app reporting or contact bnbasset83@gmail.com. The operator checks the facts and takes protective measures as needed, including account restrictions and deletion of personal information. Information subject to a legal retention obligation is kept separately to the necessary extent.