This Policy applies to Bluetooth device connection and related services provided by CloudMind, operated by KEIAN CORPORATION.
1. Basic information: Nickname, gender, mobile phone number, and email address.
You acknowledge and agree that when you register an account or use our services, we will record personal information you provide, such as your password and mobile number. Such information is necessary for us to provide the services.
2. Core feature: Bluetooth device control
Types of information collected:
Processing rules:
We do not create direct user profiles based on your personal information.
To follow data minimization and transparency, we describe in this section and in the “Business functions” parts of this Policy the business purposes, use scenarios, and handling of sensitive system permissions so you can review them before you consent. If you decline a permission, usually only the feature that depends on it is affected, and you may still use other basic services that do not require it (unless otherwise required by law).
How we request permissions and when: We do not bundle permission requests with cold start when you have not used the related feature. When you use a relevant feature, the app will ask for authorization at the appropriate time through the standard system permission dialog. The microphone (audio recording) permission is requested only when you use voice input, voice intercom, speech recognition, voice assistant, or similar features; details are set out in this Privacy Policy.
Other main permissions (summary): READ_PHONE_STATE helps keep audio/voice sessions stable; storage and gallery access are requested when you take photos, pick from the gallery, or upload/download media; location is requested for Bluetooth/Wi‑Fi assistance or writing location to photos (e.g., EXIF); the camera is requested for photography or scanning.
Purpose: Used to establish and maintain push/real-time messaging channels (e.g., Ably), verify consistency of device–account binding, and identify devices for LAN pairing. When you sign out or end a session, it is used to unsubscribe from real-time messaging and close message listeners—a necessary teardown step for the real-time channel service described above.
How obtained: Automatically via the Android system API (Settings.Secure.ANDROID_ID).
Scope: Only the device’s Android ID—we do not read IMEI, IMSI, the phone’s WLAN MAC, Bluetooth MAC, or other device identifiers.
Use scenarios: After you agree to this Privacy Policy and complete first-run consent; when signed in and using real-time messaging, device binding, or LAN pairing; when you actively sign out to end your account session and unsubscribe from messaging.
Storage and transfer: Used to connect and manage sessions with real-time messaging services such as Ably; not read before you consent; not used for ad tracking, targeted marketing, or user profiling.
[We do not collect your phone MAC] We do not read, collect, or upload the WLAN MAC address or Bluetooth MAC address of your mobile device (phone/tablet).
Purpose: Used as the unique identifier of smart photo frame / hardware devices you actively add, for account–device binding, photo and media sync, reminders and messaging, multi-device management, and security validation.
How obtained: From QR codes on the frame you scan, LAN discovery broadcasts from the frame, or your account’s bound-device list; we do not silently read your phone’s network interface MAC in the background.
Scope: Only WiFi MAC addresses of smart photo frames you actively add or have bound—not unrelated third-party devices, and not your phone’s own MAC.
Use scenarios: Adding/binding a frame, switching the current device, syncing photos/reminders/calendar to a specific frame, voice intercom, and online status queries.
Storage and transfer: Frame MAC and binding records are cached locally and synced to our servers for cross-device management; you may delete binding data when unbinding or deleting your account.
Purpose: When you use third-party payment (Alipay), WeChat sharing/payment, or similar features, to check whether the required client app is installed so we can launch it or prompt you to install it.
How obtained: Through Android package visibility, querying whether specific package names are installed (e.g., com.eg.android.AlipayGphone, com.tencent.mm); we do not enumerate or upload your full installed-app list.
Scope: Only a few apps directly related to the current feature (mainly Alipay, WeChat, and similar payment/sharing clients)—not other unrelated installed apps.
Use scenarios: When you initiate payment, sharing, or features that need to open a third-party app; such queries occur only after you agree to this Privacy Policy and complete first-run consent.
Third-party SDKs: We may integrate DCloud uni-app / uniMP, Tencent X5, Tuya / Thing (if you use related hardware), Google Firebase (e.g., push), Ably (realtime messaging), Alipay (payments), and similar SDKs. They may process identifiers, network data, push tokens, install-list signals, etc., as needed for their features. We integrate them on a minimum-necessary basis; please also read their privacy policies.
1. Disclosure required by law
We may provide relevant information when required by law by judicial authorities or government agencies acting within their lawful powers.
Despite reasonable safeguards, transmission over the internet cannot be guaranteed to be 100% secure.
Deleting an account requires verification of your bound mobile number or email.
Feedback: keiankabu@gmail.com
Office address: 4-6-10 Higashi-Ikebukuro, Runa Osumi Bldg. 4F, Toshima-ku, Tokyo 170-0013, Japan
Dispute resolution: If consultation fails, the Tokyo District Court shall have exclusive jurisdiction as the court of first instance.