このバージョンは2026-10-21に効力を生じます。それまでは 現在のバージョンが適用されます。 This version takes effect on 2026-10-21; the current one applies until then.
KR · PRIVACY · v2
U→ME Privacy Policy
Effective: 21 October 2026 / First issued: 19 September 2026 / Version: v2 / Region: Republic of Korea
What changed since v1 is listed under "Amendment history" at the end.
This is an English translation provided for convenience. The Korean text at https://u2me.industrial-dream.com/legal/kr/ko/privacy/v2 is the governing version, and it prevails in the event of any discrepancy.
Industrial Dream, inc. (the "Company") operates the application and website "U→ME" (listed in stores as U2ME, the "Service") in compliance with the Personal Information Protection Act of Korea (the "PIPA") and other applicable law, and processes personal information as set out below.
Notice of transfer abroad. The Company is established in Japan, and personal information in the Service is stored in Japan (Tokyo region). Please read clause 7 carefully.
1. Company details and privacy officer
- Company: Industrial Dream, inc.
- Representative: Hiroyuki Osone (大曽根宏幸)
- Address: Shibuya Dogenzaka Tokyu Bldg. 2F-C, 1-10-8 Dogenzaka, Shibuya-ku, Tokyo 150-0043, Japan
- Corporate number (Japan): 7011001154488
- Privacy officer: Hiroyuki Osone (大曽根宏幸), Representative
- Telephone: +81 3-6825-2492
- Email: contact@industrial-dream.com
You may direct any enquiry, complaint, or request for redress relating to personal information to the contact above. The Company will respond and act without delay.
2. How the Service works
The Service aggregates Answers your friends give anonymously and shows the result to you as a Profile. Who gave which Answer is never shown to anyone, including the subject. Buying a paid feature never lets anyone see individual Answers or respondents. A trait appears only once at least three distinct respondents have answered for it, and the comparison with your own self-answer appears only once at least five respondents have answered. Scores are rounded to the nearest 5, and respondent counts are shown as bands rather than exact numbers.
3. Categories of personal information processed
3.1 Account
When you sign in with Apple or Google, the Company's authentication platform receives and stores the authentication identifier and email address those providers supply. If you use Apple's Hide My Email, what we receive is the relay address Apple issues. We neither receive nor store passwords.
The Service's own database stores:
- authentication identifier (UUID), nickname, country of residence (Korea or Japan), display language, time zone;
- registration and update timestamps, account status;
- avatar colour, notification setting, weekly summary setting.
At registration we ask you to confirm that you are 18 or over. We do not collect your date of birth or your age itself.
3.2 Friend relationships
- the identifiers of Circles you belong to, Circle names, join and leave timestamps;
- the identifiers of users you have blocked.
3.3 Group votes
- where you take part in a group vote, that vote (the game, the person or option you chose, and the timestamp).
A vote is never shown to the person it is about, to anyone else in the group, or back to the person who cast it. Only the leading result is shown, in words rather than as a number of people, and nothing is shown at all where fewer than half the group agreed.
3.4 Answers
- Answers you give about another person (subject, question, selected option, timestamp);
- your own self-answers;
- where an Answer is determined to be invalid, that fact and its timestamp.
3.5 Aggregates
- your published Profile (score per trait, respondent band, confidence, change);
- internal records used to verify an aggregate (hashes of respondent identifiers and answer content).
3.6 Invitations and unregistered respondents
- the hash of an invitation link token, its expiry, use count, and revocation time;
- records of an invitation being created, opened, and completed;
- for respondents who are not registered: the hash of a random value generated by their browser and kept in the browser's local storage, and a hash used to distinguish devices. We do not collect their name, email address, or account information.
3.7 Notifications and Widget
- push notification tokens and platform (iOS / Android);
- hashes and expiry of Widget, share link, and session tokens.
3.8 Billing
- purchase and subscription identifiers, product IDs, status, and expiry in the App Store and Google Play;
- purchase, renewal, cancellation, and refund events received from the billing platform (RevenueCat).
The Company never receives card numbers or other payment credentials. Payment is handled by the stores.
3.9 Support
- the category, body (up to 2,000 characters), status, and our reply.
3.10 Usage
- the name and timestamp of events occurring in the Service;
- a limited set of attributes attached to those events (country, display language, OS, app version, question pack, experiment assignment, referral source).
Where such data is sent to an external analytics platform, the user identifier is replaced by a pseudonym derived irreversibly with the Company's key, and person-profile creation and IP-based geolocation are disabled at the destination.
3.11 Abuse prevention
- rate-limit keys and counts;
- records of suspected abuse;
- the result of the automation check (Cloudflare Turnstile) on the web answer page.
3.12 Consent and audit
- the version of the terms and privacy policy you accepted, and when;
- records of administrator actions (actor, action, target, timestamp).
3.13 Access logs
The Service's delivery and database platforms record IP address, user agent, and request time as a by-product of communication. These are used for incident response and abuse prevention.
3.14 Advertising
Where ads are shown, we collect the device's advertising identifier (IDFA on iOS, AAID on Android). We also record what you decided about personalized ads, and when. See section 9.
4. What we do not collect
- legal name, date of birth, gender, postal address, telephone number;
- the contacts or address book on your device;
- location (GPS);
- photos, camera, or microphone data;
- sensitive information such as ideology or belief, union or political party membership, political opinions, health, sex life, genetic information, or criminal records;
- unique identifying information such as a resident registration number;
- free-text evaluations of other people (all Answers are multiple choice).
5. Purposes of processing
- Providing the Service: generating and displaying Profiles, managing Circles and invitations, delivering notifications.
- Authenticating you and managing your account.
- Providing paid features, checking entitlement status, restoring purchases.
- Responding to enquiries and processing account deletion requests.
- Preventing and responding to fraudulent answers, impersonation, harassment, and excessive access.
- Improving quality, investigating faults, producing statistics.
- Showing ads, and checking that an ad was shown correctly.
- Complying with legal obligations and exercising or defending the Company's rights.
6. Provision to third parties
The Company does not provide personal information to third parties except where:
- you consent;
- there is a specific provision of law, or it is unavoidable in order to comply with a legal obligation;
- it is necessary for the urgent protection of the life, body, or property of a data subject or a third party; or
- it is transferred in connection with a business transfer, in which case we will notify you in advance.
The Company does not provide individual Answers, the link between respondent and Answer, or Profile content to third parties for advertising. That does not change when ads are shown.
7. Entrustment of processing and transfer abroad
The Company is established in Japan and processes and stores the Service's personal information in Japan. It also entrusts processing to the recipients below. This falls under Article 28-8(1)(3) of the PIPA — entrustment and storage necessary to perform the contract with the data subject — and is disclosed through this Policy.
| Recipient | Country | Purpose | Items transferred | Retention |
|---|---|---|---|---|
| Industrial Dream, inc. (head office) | Japan | Operation of the Service | All items in clause 3 | As in clause 9 |
| Supabase, Inc. | United States (entity) / Japan, Tokyo region (storage) | Database, authentication platform | All items in clause 3 | Until the processing contract ends |
| Vercel, Inc. | United States (entity) / Japan, Tokyo region (execution) | Application delivery and execution | Access logs, request content | Until the processing contract ends |
| Google LLC | United States | Sign-in, push notifications (Firebase Cloud Messaging) | Authentication identifier, email address, push token | Until the processing contract ends |
| Google LLC (AdMob) | United States | Showing ads | Advertising identifier, device information, IP address | Per that provider's policy |
| Apple Inc. | United States | Sign-in | Authentication identifier, email address | Until the processing contract ends |
| Cloudflare, Inc. | United States (global network) | Automation checks on the web answer page | IP address, browser information | Until the processing contract ends |
| RevenueCat, Inc. | United States | Managing entitlement status | Authentication identifier, purchase and subscription data | Until the processing contract ends |
- When and how transferred: continuously, over encrypted connections (TLS), at the moment the relevant data is created during your use of the Service.
- The Company sets out the measures necessary for safe handling in its contract with each recipient and supervises compliance.
- You may refuse the transfer abroad. Because the Service cannot be provided without it, refusing means ending your use of the Service by deleting your account.
The analytics platform (PostHog, Inc., United States) and the error-reporting platform (Functional Software, Inc. (Sentry), United States) will be added to the table above by an amendment to this Policy at the time we begin using them. Neither is in use as at the effective date of this Policy.
8. Use of generative AI
The Company may use generative AI to support its own operations. What is sent to generative AI is limited to aggregated metrics covering at least five users and to drafts written by the Company. Individual Answers, nicknames, identifiers, and support message bodies are never sent to generative AI, and generative AI never determines Profile scores.
8.1 Explaining your own Profile to you
Where you ask a question about your own Profile, the answer is written by generative AI running on your own device. Neither your question nor the answer is sent anywhere, including to us. We receive nothing in order to provide it.
What the answer is drawn from is a restatement of already-published values you can read on your own Profile screen; it contains no respondent count, no respondent identifier and no individual Answer.
On-device generative AI can be wrong. Only if you report an answer as incorrect are that question, that answer and the identifiers of the facts it was given sent to us and recorded. We never receive a question or answer you did not report.
Not every device can run it. Where a device cannot, the feature is not shown.
Both capabilities are disabled as at the effective date of this Policy.
9. Advertising
The Service may show ads inside the app. Ads are delivered by AdMob, a Google LLC service.
What we send an ad provider is limited to the device's advertising identifier, the device information needed to render an ad slot (model, OS version, screen size, language), and the IP address that comes with the connection. We do not send individual Answers, who answered what, Profile content, nicknames, the makeup of a Circle, or friend relationships. There is no mechanism in the app for putting any of those into an ad request.
Ads are shown in a fixed slot at the bottom edge of the screen. They are never mixed into the answers or the aggregates. They are not shown in the two-person space (US).
9.1 Consent for personalized ads (behavioural information)
Ads matched to your interests using the advertising identifier are shown only where you have consented in advance. If you do not consent, ads are still shown and nothing about the Service is restricted.
| Item | Detail |
|---|---|
| What is collected and used | Advertising identifier (IDFA / AAID), device information, IP address |
| Purpose | Showing interest-based personalized ads and measuring their effect |
| Retention and period of use | Until you withdraw consent. The record of your decision is kept until the account is deleted |
| Right to refuse | You may refuse, and the Service remains fully usable if you do |
You give and withdraw consent as follows.
- iOS: through the system tracking prompt. You can withdraw at any time in Settings → Privacy & Security → Tracking.
- Android: the initial state is "not consented", and you can consent or withdraw in the Service's settings screen. You can also delete the advertising ID in your device settings.
Either answer is recorded, with the time it was made. The record cannot be edited; changing your mind adds a new record. These records are destroyed when the account is deleted.
10. Retention and period of use
| Information | Retention |
|---|---|
| Account, profile settings, Circle membership | Until the account is deleted |
| Answers (raw), self-answers, published Profiles | Until the account is deleted; destroyed within 30 days of a deletion request |
| Push tokens, Widget and share link tokens | Until the account is deleted or the token expires |
| Support message bodies | Destroyed when the account is deleted |
| Usage events | 400 days from collection, or until the account is deleted |
| Invitation records, hashes of unregistered respondent identifiers | 180 days after the invitation expires, or until the account is deleted |
| Rate-limit records | 7 days |
| Abuse records | 2 years after the matter is closed |
| Group votes | Until the account is deleted |
| Profile facts used for explanation, and generative AI questions and answers | Until the account is deleted |
| Hash of the token that links an Answer to an account | 30 days from issue |
| Billing records | 5 years (records of payment and supply under the Act on the Consumer Protection in Electronic Commerce) |
| Records of consumer complaints or dispute handling | 3 years (same Act) |
| Your decision about personalized ads | Until the account is deleted |
| Consent records, audit logs | 5 years after the account is deleted |
| Backups | Up to 30 days |
When an account is deleted, anonymous aggregates already shown to other users are not recomputed on the spot. Internal verification records retain hashes that cannot be linked back to the deleted respondent.
11. Destruction procedure and method
- Personal information whose retention period has passed or whose purpose has been achieved is destroyed without delay.
- Information held in electronic files is deleted from the database by a method from which it cannot be recovered. Information contained in backups disappears with them once the backup retention period (up to 30 days) has passed.
- Information that must be preserved under law is stored and managed separately from other personal information.
12. Security measures
- Database roles are separated into API, aggregation, administration, billing, and analytics, each with least privilege.
- Row Level Security limits each user to data that concerns them. The public API's privileges cannot reach the schema that holds individual Answers at all.
- Individual Answers are stored in an area separate from the published aggregates.
- Traffic is encrypted, and database connections use TLS with certificate authority verification.
- Only hashes of invitation, share, Widget, and session tokens are stored.
- An account deletion runs only after an administrator has approved it, and only an administrator other than the person being deleted can run it.
- Administrator actions are written to an audit log.
13. Rights of data subjects and legal representatives, and how to exercise them
You may at any time ask the Company to:
- give you access to your personal information;
- correct it where it is inaccurate;
- delete it;
- suspend its processing;
- refuse an automated decision, or have it explained.
How to exercise these rights:
- Access (data export): in the app, Settings → "Export data" returns your profile, self-answers, consent history, Circle membership history, and published aggregates as JSON. The export contains no other user's personal information, no Answers received about you at the individual level, and no tokens.
- Deletion: in the app, Settings → "Contact us" → "Delete account". If you have already removed the app, follow Account deletion and write to contact@industrial-dream.com from the email address you registered with.
- Other requests: write to contact@industrial-dream.com.
To verify your identity we check your sign-in method (Apple or Google) against your nickname. There is no fee, and we act within 30 days of receipt. You may also exercise these rights through a legal representative or an authorised agent.
The Company uses automated computation to generate a Profile, but this does not constitute a decision producing legal effects or similarly significant effects on you, and the Company does not use Profiles to evaluate or screen users.
14. Automatic collection devices and how to refuse them
The Service's web pages use no advertising cookies and no third-party behavioural tracking. For ads and behavioural information inside the app, see section 9. The web pages use:
- Browser local storage: stores a random value that prevents duplicate answers from someone answering through an invitation link. That value cannot be used to identify you. You can refuse it by clearing site data in your browser settings.
- Cloudflare Turnstile: the answer page loads that provider's script to detect automated answers. In doing so the provider collects your IP address and similar data.
15. People under 18
The Service is for people aged 18 or over. We do not knowingly collect personal information from anyone under 18, and we destroy it without delay if we learn we have.
16. Changes to this Policy
Where this Policy is amended, the Company will announce the effective date and the reason inside the Service and on its website at least 7 days beforehand. Where the amendment materially affects your rights, we will give notice at least 30 days beforehand and obtain consent again. Earlier versions remain available at the URL shown to you when you accepted them.
17. Remedies for infringement
You may apply to the following bodies for dispute resolution or advice:
- Personal Information Dispute Mediation Committee: 1833-6972 (https://www.kopico.go.kr)
- Privacy Infringement Report Centre: 118 (https://privacy.kisa.or.kr)
- Supreme Prosecutors' Office, Cyber Investigation Division: 1301 (https://www.spo.go.kr)
- National Police Agency, Cyber Bureau: 182 (https://ecrm.police.go.kr)
Related: Terms of Service / Account deletion
18. Amendment history
| Version | Effective | Change |
|---|---|---|
| v2 | 21 October 2026 | Group votes added to the information collected. Generative AI extended to explaining your own Profile to you, with what is sent stated as a closed list (8). How ads inside the app are handled added (3.14, 5, 6, 7, 9, 10, 14); personalized ads are shown only with prior consent, and the advertising identifier therefore left the list of what we do not collect. The amendment history was numbered 16 twice; that is corrected |
| v1 | 19 September 2026 | First issued |
Earlier versions remain readable at the URL shown when you consented (v1: https://u2me.industrial-dream.com/legal/kr/en/privacy/v1).
The Korean text governs. This English rendition is provided for reference; where they differ, the Korean text prevails.