Privacy Policy

Effective date: October 6, 2026

This policy explains how nzoey processes personal information in its mobile app and website. The policy itself does not constitute consent to every processing activity. Where consent is required, we explain the activity and obtain consent separately.

Service operator: NEAR2 (Korean legal name: 니어2), business registration number 402-32-95290. nzoey is operated by NEAR2.

Contact email: support@nzoey.co

1. Information and purposes

Accounts: Email, authentication information, social-login identifiers and profiles, nickname, profile image and language settings for authentication and service delivery.
Content and conversations: Public and private character settings, prompts, chats, context and summaries, attached images, posts, comments, follows and likes for storing and displaying content, generating conversations, analyzing images, creating characters and translating. Free image attachments still involve transmission for AI analysis. Avoid entering your own or others’ sensitive information.
Purchases and rewards: Account-linked product, transaction and receipt identifiers, purchase times, subscription status and expiry, pass start and expiry, credit grants, usage, refunds and reconciliation, attendance and mission records for verification, duplicate prevention, benefits, refunds and support. We do not directly collect or store full card numbers.
Notifications: Push tokens, preferences, scheduled times and time zones, delivery and error records for scheduled and message notifications. A character name or message preview may appear on your lock screen.
Operations and analytics: IP, device, OS, app and browser information, access, screen usage and error records, and tracking permission status for reliability, security and usage analysis. The mobile app uses Firebase Analytics.
AI operational records: Model, gateway, routed provider, chat-room identifier, token and cache usage, cost, latency, retries and errors for quality, cost and incident management. These records are separate from conversation content.
Support: Email, inquiry details and necessary transaction information for support and rights requests.

Processing necessary to deliver the service supports contract performance; statutory retention supports legal obligations. Other processing requires a lawful basis under applicable law. Declining optional permissions may limit the related feature; advertising tracking consent is not a prerequisite for basic chat.

2. AI processing and visibility

Inputs, relevant conversation context and summaries, character settings, and images or image URLs needed for an AI feature pass through OpenRouter to the model provider handling the request. Private settings may be transmitted when necessary to generate a reply. Private visibility concerns other users; it does not mean there is no external AI processing.

This policy does not grant blanket consent or permission to train or fine-tune nzoey’s own models on conversations. Any expansion to that purpose requires separate information about purposes, data, legal basis and necessary consent. External AI providers’ retention and training practices depend on the provider, contracts and routing settings. We do not guarantee zero retention or complete anonymization for every request. See OpenRouter’s privacy policy and provider data policies.

Public character profiles, posts and comments are visible to other users. Private chats and private character settings are not public posts. Copies already made by others cannot necessarily be recalled.

3. Processors and external services

Necessary information is transmitted to:

Supabase: Authentication, account, content, conversation and transaction databases, and server functions.
Cloudflare and R2: Web and media delivery, uploaded images and files, and network processing.
OpenRouter and the routed model provider: Inputs and request information needed for conversations, image analysis, generation and translation.
RevenueCat and the store/payment provider actually used: Account-linked identifiers, transactions, receipts, products, subscriptions and refund status. Available products and payment channels appear at checkout.
Google Firebase: Mobile analytics, push tokens, and message and device information required for notification delivery.
Social-login providers: Authentication through the login you choose.

We may disclose necessary information for legal requirements or lawful protection of rights. This policy does not authorize selling personal information or using conversation content for advertising targeting.

4. Cookies, permissions and advertising

Web cookies and local storage maintain login sessions, language and preferences. Browser controls can remove or block them, affecting login. Photo, camera and notification permissions are requested for the corresponding features and can be changed in device settings. iOS tracking permission is separate from notification permission.

When advertising features become available, we explain the providers, data, purposes and necessary consent and refusal controls. This document does not activate unreleased advertising or rewarded-ad features.

5. Retention, account deletion and erasure

Account and service data are processed for as long as needed for service purposes. Request account deletion in settings or contact the email below for erasure. Account deletion removes the authentication account; related records undergo deletion, disassociation or content hiding according to their type. Deleting an account does not transfer copyright in public characters to us.

Account deletion does not mean immediate permanent erasure of uploaded media, backups or operational records. A person with an image URL may still access stored media; request media deletion through support as well. Payment, refund and dispute records subject to statutory retention are kept only to the extent and for the periods required, with use limited accordingly. Information is deleted or rendered non-identifying when its purpose and retention obligations end. We explain request outcomes and legal retention exceptions to the requester.

Retention schedule

We manage personal data retention and deletion according to the following standards. Service data and statutory records are treated separately; retaining a transaction record does not justify retaining entire chats or photos.

Information	Period and end condition
Accounts, profiles, chats, summaries, characters, posts and attached media	While the account and relevant service are maintained. On withdrawal, erasure or purpose completion, erase without undue delay except for legally retained records. Disassociation or hiding alone is not completed erasure.
Push tokens and scheduled-notification preferences	While notifications are provided; delete on disconnection, withdrawal or confirmed token invalidity.
Personally linked access, error, notification-delivery and AI cost/usage records	Up to 3 months from creation; then delete or remove personal links such as account and chat-room identifiers for non-identifying aggregates.
Ordinary support inquiries	1 year from resolution; use the 3-year rule below where they constitute consumer complaint or dispute records.
Contract/withdrawal and payment/service or goods supply records	5 years from each record’s creation; separately retain only necessary transaction identifiers, amounts, products, delivery and refund facts.
Consumer complaint and dispute handling records	3 years from creation of the relevant handling record.
Display and advertising records	6 months from creation; this does not mean retaining every user’s ad clicks for six months.
Recovery backups and pending-erasure copies controlled by us	Rotate out or delete within 30 days of erasure from the live system. Use only for recovery and reapply erasure requests after restoration. Statutory archives are separate.

The 5-year, 3-year and 6-month periods apply to the relevant records under Article 6 of Korea’s E-Commerce Consumer Protection Enforcement Decree. Other mandatory laws or lawful preservation orders apply only to necessary records, with the reason explained. Three months, one year and 30 days are our minimization standards, not statutory periods. Where account deletion does not automatically remove media, support verifies and handles erasure requests.

Independent provider retention and deletion are distinguished in section 7. Our 30-day backup period is not a guarantee for every external provider.

6. Rights and contact

Edit your profile in settings. Contact support@nzoey.co for access, copies, correction, erasure, consent withdrawal, restriction and rights under applicable law. We may request minimal identity verification and explain lawful restrictions. You may also seek relief from the relevant privacy regulator.

Deleting your account or app does not automatically cancel a store subscription. Cancel it separately through the store.

7. Age and international processing

The service is for users aged 14 or older, with a higher local eligibility or consent age applying where required. We explain necessary guardian consent and investigate and remove information collected from children who do not meet eligibility requirements.

International transfer details

These details reflect production settings and provider disclosures checked on October 6, 2026. Transfers use encrypted networks when the relevant feature is used. Necessary outsourcing and storage for authentication, storage, AI and purchase verification require an applicable basis, including Article 28-8(1)(3) of Korea’s Personal Information Protection Act where applicable, and prior disclosure or notice. Optional processing requiring consent follows separate consent.

Supabase Pte. Ltd. — authentication and databases

Country: United States. Support and subprocessors may involve additional countries.
Data, timing and purpose: At registration, login, content storage and server requests: accounts, profiles, chats and summaries, character settings, posts, purchases, rewards and notification records for authentication, storage and processing.
Retention: Section 5 and our deletion instructions. Contract-end return and deletion follow the Supabase DPA; deleting a user account and terminating our provider contract are distinct.
Contact: privacy@supabase.io.

Cloudflare, Inc. — web, R2 media and delivery

Countries/region: Media storage is in the Asia-Pacific region, without a guarantee of storage in a single country. Web/media delivery and network processing use the global network, including the United States. A fixed country-level location is not currently verified and is not asserted.
Data, timing and purpose: At access, upload and media requests: images, files, URLs, object paths, IP/request information and identifiers needed for authentication, for storage, delivery and access control.
Retention: Stored originals follow section 5. Provider security and service logs follow necessary periods under Cloudflare’s policy; we do not invent expiry dates where no fixed period is published.
Contact: privacyquestions@cloudflare.com.

OpenRouter, Inc. and the routed AI provider — AI gateway and generation

Countries: OpenRouter is a US provider. The default OpenAI-family provider is listed for US processing in OpenRouter’s provider directory; the actual provider can depend on routing. Transfer notices are updated before adding new providers or countries.
Data, timing and purpose: At chat, image analysis, character generation and translation requests: prompts, relevant conversations and summaries, character settings, attached images or URLs and request identifiers. Passwords and payment-card information are not needed for AI requests.
Retention: OpenRouter request logs and routed-provider inputs/outputs have separate policies, contracts and routing settings. No single fixed period or zero retention is guaranteed.
Contacts/policies: OpenRouter privacy contact and provider-specific policies and contacts. nzoey support accepts rights requests and checks the actual processor.

RevenueCat, Inc. — purchase and subscription verification

Country: United States (provider policy).
Data, timing and purpose: At purchases, restoration, renewal, refunds and synchronization: account-linked identifiers, products, transactions, receipt identifiers, purchase times, subscription/pass and refund status for entitlement verification and duplicate prevention.
Retention: Customer data follows contractual instructions and erasure requests, subject to legally required and dispute records.
Contact: compliance@revenuecat.com.

Google LLC — Firebase Analytics and Cloud Messaging

Countries: United States and Google’s global facilities.
Data, timing and purpose: At analytics events: app, device, screen usage and tracking permission information. At notification registration/delivery: installation identifiers, push tokens and message previews. Entire chats and private character prompts are not analytics event fields.
Retention: Actual retention of analytics event/user-level data follows the Analytics property setting. Our configuration management standard is two months. It does not impose that expiry on every aggregate report or legal/security record. Firebase installation identifiers can remain until we call the deletion API; Google discloses up to 180 days after that request to remove them from live and backup systems. Contact support to request deletion of installation identifiers.
Contact: Google privacy inquiries and Firebase support.

Refusal and consequences: Request restriction or erasure through support@nzoey.co. Stop AI/image requests to avoid those transfers; disable notifications in device settings. Ending essential authentication/storage processing may prevent login and stored-content delivery and require account closure. Declining optional analytics or tracking does not block basic chat. We explain outcomes and statutory retention exceptions individually. Your chosen Apple/Google login and store services also apply their own privacy policies.

8. Safeguards and changes

We use encrypted communications, authentication, data access controls and server-side transaction processing. No service can guarantee complete security.

Changes and their effective date are announced before taking effect. Material changes receive at least seven days’ notice, and changes adverse to users at least 30 days. Separate consent is obtained when required by law.

Privacy and support contact: support@nzoey.co