1. Data Controller
- Trade Name: Zero to One Flow (021flow)
- Representative: Sungtae Ryu
- Email: contact@021flow.com
- Data Protection Officer: Privacy officer: Sungtae Ryu (owner), contact@021flow.com, +82-70-8676-0210
Signup records your self-attested birth year, country, consent time and the Terms/Privacy document versions. This is not independent age verification. Approved age and country rules govern eligibility; contactguardian consent assistance where required. Precise location (coordinates, visit times/places and device-local samples), political ratings, dating processing and marketing are separate from required signup consent. Allow or withdraw each optional purpose in Settings; declining leaves the rest of the app usable. Download your profile and authored content as JSON in Settings.
2. Personal Data We Collect
- Account data: email, name or nickname, sign-in identifier
- Authentication data: social sign-in provider identifier, token metadata
- Payment-related data: payment status, subscription plan, billing dates, receipt/order identifiers, Xsolla user ID or transaction ID
- Usage data: access logs, IP address, browser/device information, usage, error logs
- Support data: inquiry contents, email, attachments, support records
- Cookies and similar technologies: for sessions and analytics
- User-generated content: ratings, comments, posts you submit
- Profile and dating: submitted birth year, gender, country, interests, dating bio/preferences/photos, used for ratings, recommendations and matching. Ratings and submitted content can include sensitive information such as political opinions.
- Messages and voice: DM content, participants/timestamps, uploaded voice messages and attachments, shared with conversation participants.
- Photos and AI: selected, captured or uploaded photos and conversations/content supplied to AI. Content needed for recognition, recommendations, conversations or public-upload review may be sent to the configured Anthropic/OpenAI API.
- Location: latitude/longitude used for nearby searches or ratings, and coordinates/timestamps for separately enabled background visit prompts in the app. Visit detection also runs on-device; nearby-place searches may send coordinates to our server and the configured places provider.
- Calendar: after device permission, event titles, start/end times and notes are returned to the WebView; selected event information is sent to our server when requesting calendar suggestions.
- App notifications and SDKs: Expo/device push tokens, device model, app version/build, notification preferences and marketing consent timestamp. Enabled Firebase analytics and AdMob advertising process events, device/analytics/advertising identifiers and consent state subject to consent conditions.
We do not directly store sensitive payment instrument data such as card numbers or CVC; these are processed by Xsolla or the payment processor.
3. Purposes of Processing
- Account registration and management
- Providing and operating the Service
- Verifying paid plan and subscription status
- Payment, billing, refunds, and tax/accounting
- Customer support and notices
- Security, abuse prevention, and incident response
- Service improvement, statistics, and analytics
- Compliance with legal obligations
4. Sharing & Processors
These are RANQ's integrations and data flows. Transfers depend on the feature, configuration and consent conditions. Service brands do not establish the contracting entity or processor/independent-controller role. Unconfirmed contract details require operator confirmation before launch.
Current operations documentation describes a self-managed server for the web app. MongoDB, Redis and MinIO are storage/cache software, and their names alone do not identify external processors. Infrastructure ownership/management, physical countries and external backups or processing arrangements still require confirmation.
| Service / contracting entity, role, contact | Data processed | Purpose | Retention | Cross-border |
|---|---|---|---|---|
| Xsolla Xsolla (USA), Inc. and the Xsolla group merchant named in your purchase confirmation (data.protection@xsolla.com) — independent controller (Merchant of Record) | Billing email, order/transaction identifiers, payment/subscription status | Web payments, tax, receipts, refunds/billing support (Merchant of Record) When placing web orders or managing subscriptions | While you buy or use content, then in anonymized form for up to 5 years (Xsolla privacy policy) | Yes — on web checkout |
| Apple (Sign in with Apple / App Store / APNs) Apple Inc. / Apple Services Pte. Ltd. (privacyoffice_korea@apple.com) — independent controller of Apple accounts and the App Store | Sign-in identifier/email, purchase receipts/transaction IDs, device push token/notification content | Selected sign-in, iOS billing and push delivery When using Apple sign-in, iOS purchases or notifications | Under Apple’s privacy policy. No period is published for push delivery data | Yes — when using these features |
| Google (Sign-In / Play Billing / Firebase Cloud Messaging) Google LLC and applicable Google affiliates (Korean representative: Google Korea LLC, +82-2-722-7778) — independent controller for Sign-In/Play, processor for FCM | Sign-in identifier/email, purchase tokens/order IDs, device push token/notification content | Selected sign-in, Android billing and push delivery When using Google sign-in, Android purchases or notifications | Undelivered FCM messages up to 4 weeks; installation IDs removed within 180 days of deletion. Sign-In/Play under Google’s policy | Yes — when using these features |
| Google Analytics / Tag Manager / Firebase Analytics Google LLC — processor | Usage events, screen/device/app information, analytics identifiers | Web/app usage analytics When analytics configuration and regional consent conditions permit | 2 or 14 months as configured, then deleted within 180 days | Yes — when analytics is allowed |
| Google AdSense / AdMob / UMP The Google affiliate named in the account terms — independent controller | Ad requests, IP/device information, advertising identifiers and consent status | Web/app advertising and ad consent management Subject to ad configuration/consent. Web AdSense is blocked in EEA/UK/CH and unknown regions | Ad logs: IP partly removed at 9 months, cookie data anonymized at 18 months (Google’s published practice) | Yes — when ads are shown |
| Anthropic API Anthropic, PBC (Korean representative: Anthropic Korea) — processor | Conversations/prompts and selected content/photos sent to AI features | AI conversations/recommendations and photo recognition When using an AI feature configured for Anthropic | 30 days by default; flagged inputs up to 2 years and safety scores up to 7 years | Yes — when using AI features |
| OpenAI API OpenAI OpCo, LLC — processor | Conversations/prompts and selected content/photos sent to AI features | AI conversations/recommendations and photo recognition When using an AI feature configured for OpenAI | Abuse-monitoring logs up to 30 days (varies by endpoint) | Yes — when using AI features |
| Cloudflare Cloudflare, Inc. — processor for traffic and customer logs, independent controller for visitor security data | IP address, request metadata and service traffic | Service connectivity through network edge/tunnel On public service requests | Until the purpose ends or the contract terminates; access logs up to 12 months | Yes — on every public request |
| Expo (Push Service / EAS Update) 650 Industries, Inc. (Expo) — processor | Expo/device push tokens, notification content, update-request IP/app/device information | App push relay and update checks/delivery On push registration/delivery and app update checks | Push content is not stored. No period is published for tokens, receipts or update logs | Yes — on app notifications and updates |
| Google Places Google Asia Pacific Pte. Ltd. (billed through Google Cloud Korea LLC) — independent controller | Coordinates for nearby-place searches | Nearby-place search When using configured Places searches | Under Google’s policy; no period published | Yes — on nearby search |
| HawkEyeOps Operated by Zero to One Flow | Analytics events, visitor identifiers and request information | Usage analytics When that analytics integration is configured and consent conditions permit | As stated for analytics data in this policy | None |
| Self-operated servers, storage & backups Zero to One Flow — stored directly on its own servers and storage, with no outside hosting processor | All account, content and log data stored by the service (database, cache, image storage, backup copies) | Operating the service, storing data, backup and recovery Always | The periods in this policy. Database backups: 14 days | None |
| Support email (Google Workspace) Google LLC or the Google affiliate on the Workspace contract — processor | Support email, message content and attachments | Handling support and data-rights requests When emailing support | 3 years after handling (complaint and dispute records) | Yes — when you email support |
5. International Transfers
Section 4 lists the data, purpose and recipient service; the table below lists timing/method and open contract details. This table does not constitute consent to a transfer. Transfer bases, refusal procedures and feature-specific consequences must be established from actual contracts and applicable law. Contact the support email above for questions or rights requests.
| Service | Destination countries | Timing / method | Retention | Transfer basis / safeguards / refusal |
|---|---|---|---|---|
| Xsolla | United States and the countries listed in the Xsolla privacy policy | When placing web orders or managing subscriptions — Network transfer (API/SDK/browser) | While you buy or use content, then in anonymized form for up to 5 years (Xsolla privacy policy) | Transfer needed to perform your order, with standard contractual clauses. To refuse, do not use web checkout; web purchases are then unavailable |
| Apple (Sign in with Apple / App Store / APNs) | Primarily the United States | When using Apple sign-in, iOS purchases or notifications — Network transfer (API/SDK/browser) | Under Apple’s privacy policy. No period is published for push delivery data | Performing the feature you chose, under Apple’s safeguards. Nothing is transferred if you do not use Apple sign-in, iOS purchases or notifications |
| Google (Sign-In / Play Billing / Firebase Cloud Messaging) | United States and countries with Google facilities | When using Google sign-in, Android purchases or notifications — Network transfer (API/SDK/browser) | Undelivered FCM messages up to 4 weeks; installation IDs removed within 180 days of deletion. Sign-In/Play under Google’s policy | Performing the feature you chose, under SCCs/DPF. Nothing is transferred if you do not use Google sign-in, Android purchases or notifications |
| Google Analytics / Tag Manager / Firebase Analytics | United States and countries with Google or subprocessor facilities | When analytics configuration and regional consent conditions permit — Network transfer (API/SDK/browser) | 2 or 14 months as configured, then deleted within 180 days | You can refuse in cookie settings. Refusal stops the transfer and does not affect the service |
| Google AdSense / AdMob / UMP | United States and countries with Google facilities | Subject to ad configuration/consent. Web AdSense is blocked in EEA/UK/CH and unknown regions — Network transfer (API/SDK/browser) | Ad logs: IP partly removed at 9 months, cookie data anonymized at 18 months (Google’s published practice) | Consent (PIPA Art. 28-8(1)(1)). Refuse in ad-consent or device ad settings; the service remains available |
| Anthropic API | United States and other countries published by Anthropic | When using an AI feature configured for Anthropic — Network transfer (API/SDK/browser) | 30 days by default; flagged inputs up to 2 years and safety scores up to 7 years | PIPA Art. 28-8(1)(3) (disclosed entrustment/storage needed to perform the contract) and the provider’s standard safeguards. Nothing is transferred if you do not use AI features |
| OpenAI API | United States and other OpenAI processing countries | When using an AI feature configured for OpenAI — Network transfer (API/SDK/browser) | Abuse-monitoring logs up to 30 days (varies by endpoint) | PIPA Art. 28-8(1)(3) (disclosed entrustment/storage needed to perform the contract) and the provider’s standard safeguards. Nothing is transferred if you do not use AI features |
| Cloudflare | United States, EEA and Cloudflare network countries | On public service requests — Network transfer (API/SDK/browser) | Until the purpose ends or the contract terminates; access logs up to 12 months | PIPA Art. 28-8(1)(3) (disclosed entrustment/storage needed to perform the contract) and the provider’s standard safeguards. Required to reach the service, so refusal means not using it |
| Expo (Push Service / EAS Update) | United States | On push registration/delivery and app update checks — Network transfer (API/SDK/browser) | Push content is not stored. No period is published for tokens, receipts or update logs | PIPA Art. 28-8(1)(3) (disclosed entrustment/storage needed to perform the contract) and the provider’s standard safeguards. Turning notifications off stops push delivery |
| Google Places | Countries with Google facilities | When using configured Places searches — Network transfer (API/SDK/browser) | Under Google’s policy; no period published | Location consent (PIPA Art. 28-8(1)(1)). Refusing or withdrawing location permission stops the transfer |
| HawkEyeOps | Republic of Korea | When that analytics integration is configured and consent conditions permit — Network transfer (API/SDK/browser) | As stated for analytics data in this policy | No overseas transfer. You can refuse in cookie settings |
| Self-operated servers, storage & backups | Republic of Korea | Always — Network transfer (API/SDK/browser) | The periods in this policy. Database backups: 14 days | No overseas transfer |
| Support email (Google Workspace) | Countries with Google data centers | When emailing support — Network transfer (API/SDK/browser) | 3 years after handling (complaint and dispute records) | Emailing is your choice; you can also call +82-70-8676-0210 |
6. Retention
- Once closure is confirmed, account display name, username, avatar, bio, sign-in linkage, birth year, country, gender and dating/notification settings are cleared or replaced; the account's private life logs, referral records and push tokens are deleted, and active sessions are revoked.
Account deletion clears profile identifiers, private life logs and push tokens, and removes the bodies and attachment references of this account's posts, comments and messages. Owned media files are cleaned by a retryable job, so cleanup can still be pending after the request. Some rating scores, conversation structure, transaction, dispute and operational records and internal account identifiers remain. These records are not considered fully anonymous. Backup and separate-service retention scopes and periods require review. Request removal of remaining personal information through the data rights request process.
- However, payment, transaction, and dispute records subject to statutory retention (e.g. e-commerce law) may be kept for the legally required period.
- Retention and destruction: Contract, withdrawal and payment records 5 years; complaint, dispute, report and sanction records 3 years; display/advertising records 6 months (E-Commerce Act Decree Art. 6); admin audit records 3 years. On account closure, authored text, media and location are deleted; scores and thread references remain under an internal identifier while that aggregate or thread exists. Database backups are deleted after 14 days on both the server and the NAS. Electronic files are deleted so they cannot be recovered. Media cleanup uses a retryable job; ask about retention exceptions or additional erasure through the channel below.
- Minimal records may be retained as needed to prevent abuse.
7. Your Rights
You may request access, correction, deletion, restriction of processing, withdrawal of consent, and account closure. Submit requests to contact@021flow.com.
Use this manual support process to request access, a copy or portability of your personal data. This is not an automatic download service.
- Where possible, send the request from the email associated with your account to contact@021flow.com.
- Include your RANQ username, request type and relevant data scope or period. Do not send passwords, login tokens or authentication codes.
- Account ownership is checked before processing. Information may be excluded or redacted to protect other people's rights and personal data.
- Where the legal conditions for portability apply, request the eligible data in a structured, commonly used, machine-readable format such as JSON or CSV.
For requests covered by the GDPR, the statutory response period is normally one month from receipt. An extension of up to two further months for complexity or request volume requires notice and reasons within the first month. Other jurisdictions follow their applicable deadlines and conditions.
For privacy complaints in Korea, contact KISA (118); for dispute mediation, contact the Personal Information Dispute Mediation Committee (1833-6972).
8. Cookies
- We use cookies and similar technologies for sessions, preferences, and analytics.
- We distinguish essential cookies from analytics/marketing cookies.
- You can refuse cookies in your browser settings, though some features may be limited.
- Analytics cookies (Google Analytics, Google Tag Manager) are used in the EEA, the UK and Switzerland only after you consent, and elsewhere unless you decline. You can change this at any time in .
9. Security Measures
We apply reasonable safeguards including access controls, encryption in transit/at rest, access logging, backups, regular security updates, and administrator access controls.
10. Children’s Privacy
You must be 18 or older. Sign-up checks a self-declared birth year and country; this is not identity verification. We do not knowingly collect children’s data and delete under-age accounts we identify
11. Changes
We may update this policy and will post the effective date and changes in the Service or on this page.
12. EEA/UK users and outstanding launch decisions
Where GDPR/UK GDPR applies, you may request access, rectification, erasure, restriction, portability, objection and withdrawal of consent, and complain to your competent supervisory authority. Withdrawal does not affect the lawfulness of processing based on consent before withdrawal. Personal data is used for rating/interest-based recommendations and dating matching. The operator must review whether any processing constitutes an automated decision with legal or similarly significant effects and which related rights apply.
Lawful basis by purpose
| Purpose | Data | Lawful basis (PIPA; GDPR Article 6, Article 9 for sensitive data) |
|---|---|---|
| Account, sign-in and providing the service | Account data, sign-in identifiers | Contract (PIPA Art. 15(1)(4); GDPR Art. 6(1)(b)) |
| Ratings, comments and published content | User-created content | Contract (PIPA Art. 15(1)(4); GDPR Art. 6(1)(b)); publication follows your choice to post |
| AI conversations, recommendations and photo recognition | Conversations/prompts, selected photos | Contract for the feature you request (GDPR Art. 6(1)(b)), with disclosed overseas transfer |
| Nearby search and visit prompts (location) | Latitude/longitude, visit coordinates/times | Location consent (Location Information Act Art. 15, 19; GDPR Art. 6(1)(a)); withdrawable anytime |
| Taste matching, dating and policy ratings (potentially sensitive data) | Ratings that may reveal orientation, interests or political opinions | Separate consent (PIPA Art. 23(1)(1); GDPR Art. 9(2)(a)), collected before the feature is enabled and withdrawable |
| Usage analytics | Usage events, device data, analytics identifiers | Legitimate interests until you object (PIPA Art. 15(1)(6); GDPR Art. 6(1)(f)), or consent where required |
| Advertising | Advertising identifiers, IP/device data, consent status | Consent (PIPA Art. 15(1)(1); GDPR Art. 6(1)(a)); personalized ads can be refused |
| Payments, subscriptions and refunds | Transaction identifiers, payment/subscription status | Contract and legal obligation (PIPA Art. 15(1)(2),(4); E-Commerce Act Art. 6; GDPR Art. 6(1)(b),(c)) |
| Push notifications and marketing messages | Push tokens, opt-in records | Contract for service notices; consent for marketing (Network Act Art. 50; GDPR Art. 6(1)(a),(b)) |
| Support, data-rights requests and abuse prevention | Support messages, report/enforcement records, request data | Legal obligation and legitimate interests (PIPA Art. 15(1)(2),(6); GDPR Art. 6(1)(c),(f)) |
- EU/UK Article 27 representative: The service launches in Korea and the United States and does not target the EEA/UK, so no Article 27 representative is appointed. This is reassessed before opening those regions
- Location, political and dating data: Location is used only after opt-in and can be withdrawn in settings. Dating and policy-rating data that may reveal political views or sexual life requires separate consent before the feature is enabled