このバージョンは2026-10-21に効力を生じます。それまでは 現在のバージョンが適用されます。 This version takes effect on 2026-10-21; the current one applies until then.
JP · PRIVACY · v2
U→ME Privacy Policy
Effective: 21 October 2026 / First issued: 19 September 2026 / Version: v2 / Region: Japan
What changed since v1 is listed under "Amendment history" at the end.
This is an English translation provided for convenience. The Japanese text at https://u2me.industrial-dream.com/legal/jp/ja/privacy/v2 is the governing version, and it prevails in the event of any discrepancy.
Industrial Dream, inc. (the "Company") handles personal information in the application and website "U→ME" (listed in stores as U2ME, the "Service") in accordance with the Act on the Protection of Personal Information of Japan (the "APPI") and other applicable law, as set out below.
1. Company details
- 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: 7011001154488
- Telephone: +81 3-6825-2492
- Contact for personal information matters: contact@industrial-dream.com
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. Information we collect
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 (Japan or Korea), 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 external 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 whether you allowed personalized ads, and when you decided. See "9. Advertising".
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;
- race, creed, social status, medical history, criminal record, or other special care-required personal information;
- free-text evaluations of other people (all Answers are multiple choice).
5. Purposes of use
- 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 law and exercising or defending the Company's rights.
6. Provision to third parties
The Company does not provide personal data to third parties except where:
- you consent;
- it is required by law;
- it is necessary to protect life, body, or property and obtaining your consent is difficult;
- cooperation with a public authority is needed and obtaining consent would impede that work; or
- it is transferred as part of a business succession.
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.
The Company does not itself link the advertising identifier to information that identifies you, so for us it is personal-related information. Because an ad provider may link it to information that provider holds, the Company provides it only after obtaining your consent by the means described in 9.1, as required by Article 31 of the APPI. Without that consent, no interests are inferred from the advertising identifier.
7. Processors and transfers abroad
The Company entrusts processing to the providers below. All are third parties located outside Japan, and the following information is provided under Article 28 of the APPI. The Company secures ongoing safeguards for personal data through its contracts with each of them.
| Provider | Country | Purpose | Where data is stored |
|---|---|---|---|
| Supabase, Inc. | United States | Database, authentication platform | AWS Tokyo region (ap-northeast-1) |
| Vercel, Inc. | United States | Application delivery and execution | Execution in the Tokyo region; operational logs may be processed in the United States |
| Google LLC | United States | Sign-in, push notifications (Firebase Cloud Messaging), ad delivery (AdMob) | Regions determined by that provider |
| Apple Inc. | United States | Sign-in | Regions determined by that provider |
| Cloudflare, Inc. | United States | Automation checks on the web answer page | That provider's global network |
| RevenueCat, Inc. | United States | Managing entitlement status | United States |
For an overview of the data protection regimes in those countries, see the information published by the Personal Information Protection Commission (https://www.ppc.go.jp/personalinfo/legal/kaiseihogohou/). The Company will provide information about the safeguards it has taken on request.
The analytics platform (PostHog, Inc., United States) and the error-reporting platform (Functional Software, Inc. (Sentry), United States) will be added to this table 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 Personalized ads
Ads matched to your interests using the advertising identifier are shown only if you allow it.
- On iOS we follow your answer to the system tracking prompt. You can change it at any time in Settings → Privacy & Security → Tracking.
- On Android the initial state is "not allowed", and you can change it in the Service's settings screen. You can also delete the advertising ID in your device settings.
- If you do not allow it, ads are still shown, but no interests are inferred from the advertising identifier.
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 erased when the account is deleted.
9.2 External transmission
In keeping with Article 27-12 of the Telecommunications Business Act (the external transmission rules), the information the Service sends from your device to parties other than the Company is published below.
| Recipient | Information sent | Purpose | How the recipient handles it |
|---|---|---|---|
| Google LLC (AdMob) | Advertising identifier, device information, IP address | Showing ads, preventing invalid ad activity, checking that an ad was shown correctly | https://policies.google.com/technologies/partner-sites |
For how Google handles it, see that company's privacy policy (https://policies.google.com/privacy).
10. Retention
| Information | Retention |
|---|---|
| Account, profile settings, Circle membership | Until the account is deleted |
| Answers (raw), self-answers, published Profiles | Until the account is deleted; erased 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 | Erased when the account is deleted |
| Usage events | 400 days from collection, or until the account is deleted |
| Invitation records, hashes of external 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 | 7 years (statutory retention period for books and records) |
| 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. 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.
12. Your rights
You may request that the Company:
- notify you of the purpose of use;
- disclose the retained personal data (including by electronic means);
- correct, add to, or delete its content;
- cease using it, erase it, or cease providing it to third parties.
How to exercise these rights:
- Disclosure (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 data, 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. We respond within 30 days of receipt.
13. Cookies and similar technologies
The Service's web pages use no advertising cookies and no third-party behavioural tracking. For ads inside the app, see "9. Advertising". 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.
- 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.
14. People under 18
The Service is for people aged 18 or over. We do not knowingly collect information from anyone under 18, and we erase it promptly if we learn we have.
15. Changes to this Policy
The Company may amend this Policy. For an amendment that materially affects your rights or obligations, we will announce it inside the Service and on our website at least 30 days before it takes effect and, where appropriate, ask you to accept it again. Earlier versions remain available at the URL shown to you when you accepted them.
16. Enquiries and complaints
- Company contact: contact@industrial-dream.com
- If you are not satisfied with our response, you may complain to the Personal Information Protection Commission (https://www.ppc.go.jp/).
Related: Terms of Service / Account deletion
17. 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, 13); the advertising identifier therefore left the list of what we do not collect. Matching retention periods added (10) |
| v1 | 19 September 2026 | First issued |
Earlier versions remain readable at the URL shown when you consented (v1: https://u2me.industrial-dream.com/legal/jp/en/privacy/v1).
The Japanese text governs. This English rendition is provided for reference; where they differ, the Japanese text prevails.