Privacy Policy
AllSenseLab Co., Ltd. processes personal information from the myinstay app under this policy. Inquiries on the company website and registrations and orders on the online shop are covered by the policies on those sites.
In short
You can use every feature of myinstay without signing in. If you consent to usage statistics, it collects app usage information linked to an install ID for product improvement and usage statistics: your saved spray schedule and the estimated daily spray time calculated from it. On Android, it also collects a hash of an app-scoped device value. If you sign in with a Kakao, Google or Apple account, it keeps the user ID, email and name provided by that service, and your diffuser names and schedules, in your account to identify the account and store your schedules. If you allow notifications, you are notified when a refill you recorded has about 15% left and when there is an announcement such as an app update. Both arrive through Firebase Cloud Messaging. While refill alerts are on, the app registers each diffuser's refill record (date, amount and schedule rate) and the notification token with our server, which estimates what is left and sends the alert. Refill alerts can be turned off on the Scent screen and announcements in More › Announcements. We do not send advertising notifications.
Usage collection is off by default. We collect usage data only after you consent in More › Privacy, where the data, purpose, retention and processing locations are shown. You can decline or withdraw and continue controlling the diffuser. If you explicitly request deletion, we process the information needed to authenticate and receive that request.
Signing in is optional too. The sign-in screen shows what is collected, why, how long it is kept and your right to decline; tapping the Kakao, Google or Apple button is your consent. Without signing in you can still use every feature, including connecting the diffuser and using schedules.
1. Information we collect
What we collect — install identifiers and usage information (if you consent to usage statistics)
| Item | Details |
|---|---|
| Install ID | An ID automatically generated through Firebase Anonymous Authentication. Usage records are stored under this ID. If you delete the app and reinstall it on the same phone, the ID may carry over through iOS secure storage or Google backup restoration on Android. Restoring an Android backup onto a new phone may also carry the ID over. Anonymous Authentication describes the authentication method; it does not mean the records cannot be linked to a device. When you sign in, the install ID becomes your account ID and usage records are linked to that account; signing out starts a new install ID. |
| Android device-value hash | We store a hash derived from ANDROID_ID, which is scoped to the app-signing key, device, and Android user, alongside the install ID. It can distinguish a device under the same conditions; the original ANDROID_ID and advertising ID are not transmitted. The value may change after a factory reset or a change of signing key, among other circumstances. We do not collect this value on iOS. |
| App and environment | App version, operating system (iOS or Android), language, country |
| Usage | Spray schedule settings (start and end time, days of the week, spray and pause duration), the daily spray time estimated from them, the scent you selected, the last connection time, and when you opened the app, connected, or saved a schedule, and when you recorded a refill or changed the amount put in, together with the refill date and amount put in |
What we collect — if you sign in (optional)
| Item | Details |
|---|---|
| Account ID | The Firebase Authentication account ID. If you sign in from an installation that consented to usage statistics, the install ID becomes the account ID. |
| Sign-in records | The service you signed in with (Kakao, Google or Apple), your user ID at that service, the email and name the service provides, and the time of sign-in. A new record is kept for each sign-in. From Kakao we receive your member number and, if you agree, your nickname, but not your email. Apple provides your name only on the first sign-in, and if you choose Hide My Email, Apple's relay address is kept. |
| Consent record | When you agreed to the notice on the sign-in screen, and the app version at that time |
| Schedules kept in your account | Account schedule storage turns on when you sign in and can be turned off in More › Account. While it is on, we keep your diffuser names, four schedules (including their names), and a hash of the device identifier used to find the same diffuser after you reinstall the app or switch phones. On Android that identifier is the diffuser's Bluetooth address, so we treat the hash as a value that points to the diffuser. |
What we collect — if you receive notifications (optional)
| Item | Details |
|---|---|
| Notification registration | The information needed to deliver announcements: a per-installation identifier created by Firebase (the Firebase installation ID) and a notification token (on iOS, including the Apple push notification token), plus the app version, language, time zone and device information (such as model and OS version) sent along when registering for notifications and subscribing to announcement topics (all users, platform, language). We register this information while Announcements or refill alerts are turned on, and delete it when both are turned off. Announcements can be turned off in More › Announcements. myinstay does not keep a separate copy of the notification token or the Firebase installation ID. Announcements are sent by topic; we do not pick out individual users. |
| Refill alert registration | For each diffuser with refill alerts turned on, we register the refill date, the amount put in, the selected scent, the schedule rate history (the time of each change and the number of seconds the pump runs per day) and whether the alert is turned on with our server, together with the notification registration information above (Firebase installation ID, notification token, app version, language and time zone). It is used only to estimate what is left and send the alert at about 15%. Diffuser names (nicknames) and device identifiers are not sent; diffusers are told apart by a hash value. |
What we do not collect
- Phone number or address — the email and name received at sign-in are kept only as account information above and are not included in usage statistics
- Location (GPS)
- Passwords — Kakao, Google and Apple handle sign-in; myinstay never receives your password
- Advertising identifiers (neither Apple IDFA nor the Android advertising ID)
- Contacts, photos, microphone
- Crash reports
2. Why we collect it
- Product improvement — understanding which schedules people use, and how much, so we can refine the app and the product.
- Usage statistics — aggregating usage patterns from records stored under install IDs. Estimated daily spray time is not measured cumulative usage.
- Account identification and schedule storage — confirming the account you signed in with, and keeping your diffuser names and schedules in your account so they carry over when you reinstall the app or use another phone.
- Announcements — sending news such as app updates and service changes or interruptions as notifications. We do not send advertising.
- Refill alerts — estimating what is left from the registered refill record and sending an alert at about 15%.
We do not use this information for advertising and do not sell it to third parties.
3. Permissions the app uses
| Permission | Purpose |
|---|---|
| Bluetooth | BLE communication with the AllSenseLab MUSE diffuser (AJBLE100). This communication happens only between your device and the diffuser. |
| Internet access | (1) sending the install identifiers and usage information above, (2) fetching a static JSON file to check for app updates, (3) showing help pages and opening external links, (4) signing in and exchanging the schedules kept in your account, (5) registering for and receiving announcements, (6) registering for and receiving refill alerts |
| Notifications | Showing refill alerts and announcements. The app asks for this permission after you first save a schedule, when you first record a refill, or when you turn on refill alerts or announcements. If you do not allow notifications, every feature other than notifications still works. |
4. Data exchanged with the diffuser
Over BLE, myinstay exchanges the following with the diffuser:
- Spray schedule (start and end time, days of the week, spray and pause duration)
- Power on/off
- Clock synchronization (current time)
That exchange itself happens only between your device and the diffuser. The schedule settings listed above are, however, stored on our server as part of the usage information.
5. Data stored on your device
myinstay stores the following on your device:
- The identifier of each diffuser you connected to, along with the schedule, scent, and nickname you set for it
- The anonymous install ID
- Your sign-in state, and the pairing between the diffusers this phone has connected to and the diffusers kept in your account
- The refill dates, amounts and schedule rate history you recorded, and your notification settings — also registered with our server while refill alerts are on
Deleting the app or clearing its storage removes all of the above from your device. The anonymous install ID, however, may remain in the device's secure storage (iOS) or Google backup (Android) and carry over if you reinstall on the same phone. On iOS, deleting the app ends your sign-in and you need to sign in again; on Android, restoring a Google backup may carry your sign-in over as well. The diffusers and schedules kept in your account come back when you sign in again.
6. Third-party services
myinstay uses the following external services:
- Google Firebase (Google LLC) — authentication (anonymous authentication and linking Kakao, Google and Apple sign-in), storage of usage and account information (Cloud Firestore), receiving Kakao unlink notifications (Cloud Functions), registering for and delivering announcements and refill alerts (Cloud Messaging and Firebase installation IDs, if you receive notifications), and storing refill alert registrations and estimating what is left (Cloud Firestore and Cloud Functions). Firestore and Cloud Functions run in the South Korea (Seoul) region; Cloud Messaging is a global service whose processing location cannot be chosen. Firebase privacy information
- Kakao Login (Kakao Corp.) — when you sign in with a Kakao account, Kakao verifies your identity and provides myinstay with your member number and, if you agree, your nickname. Kakao privacy policy
- Google Sign-In (Google LLC) — when you sign in with a Google account, Google verifies your identity and provides your user ID, email and name. Google privacy policy
- Sign in with Apple (Apple Inc.) — when you sign in with an Apple account, Apple verifies your identity and provides your user ID, your email (a relay address if you choose Hide My Email) and your name (first sign-in only). Apple privacy policy
- App update manifest hosting — requests a static JSON file for update notices. This request does not include the telemetry install ID or diffuser settings.
No advertising SDKs and no tracking SDKs are used.
Where the data goes — usage and account information is stored in the South Korea (Seoul) region, but anonymous authentication and sign-in are processed in Google's data centers in the United States, where the authentication account (the account ID and the user ID, email and name from the sign-in service) is also stored. If you receive notifications, the notification registration information may be processed in the United States and other countries where Google has data centers, and refill alert registrations are stored in the South Korea (Seoul) region. The usage-statistics consent screen shows the processing locations; declining statistics or not signing in leaves every feature available. If you explicitly request deletion, we process authentication for the existing install ID.
| What is transferred | The install ID, Android device-value hash, app and environment information, and usage information listed in section 1. If you sign in, also the account ID and the user ID, email and name from the sign-in service. If you receive notifications, also the notification registration information (Firebase installation ID, notification token, app version, language, time zone and device information), and if refill alerts are on, the refill alert registration. Processing locations for the Firebase services are listed below. |
| Where | United States (anonymous authentication, sign-in, and storage of the authentication account); South Korea, Seoul region (usage and account information, refill alert registrations); and the United States and other countries where Google has data centers (notification registration, because Cloud Messaging is a global service whose processing location cannot be chosen) |
| When and how | Over an encrypted connection when usage is recorded after consent, when you sign in, when you turn on Announcements or a refill alert, when a refill record or schedule changes, and whenever the app updates the notification registration while either is on (for example, when you open the app), or when you explicitly request deletion |
| Who receives it | Google LLC — firebase.google.com/support/privacy |
| Purpose | As set out in section 2 (product improvement, usage statistics, account identification and schedule storage, announcements, refill alerts) |
| Retention | As set out in section 7 |
| How to refuse | Turn off usage statistics consent in More › Privacy to stop new usage-statistics uploads and cancel pending requests. Requests already received by the server cannot be recalled. You can keep using the diffuser controls without deleting the app, and request deletion of stored records on the same screen. If you do not sign in, no account information is transferred; after signing in, you can stop by deleting your account. Turning off a refill alert on the Scent screen deletes that diffuser's refill alert registration. Turning off More › Announcements stops announcements only; when both announcements and refill alerts are off, the notification registration information (notification token and Firebase installation ID) is deleted. Turning off notifications in your phone settings stops notifications from being shown. |
7. Retention and deletion
- Install records are kept for two years after their last usage-data update; individual events for two years after creation. Using the app with collection off does not renew these periods.
- More › Privacy › Request data deletion lets you request deletion of server records using authentication for the current installation. While you are signed in, this menu is replaced by account deletion, which also deletes your usage statistics. Collection stops immediately. Receipt is shown only after server confirmation and does not mean deletion is complete. An operator deletes the usage events, install record and Firebase authentication account in that order.
- The request record contains the install ID (the account ID if you signed in), platform, where the request came from (the app, an operator or Kakao), request time, status and completion time. It is retained for two years after completion to record processing and block further uploads by the old ID, then deleted. Local diffuser settings remain unchanged. Opting in again starts collection under a new install ID.
- For records from an older installation that this app can no longer access, contact service@allsenselab.com. Other installation records are not automatically deleted based on a matching install ID or Android device value. If a request fails, you can retry on the same screen.
If you signed in
- Account information (account ID, sign-in records, consent record) and the diffusers and schedules kept in your account are retained until you delete your account.
- Requesting deletion in More › Account › Delete account deletes the account and everything linked to it (sign-in records, diffusers and schedules, and that account's usage statistics) within 30 days. For Kakao sign-in we also unlink the Kakao connection; for Apple sign-in we revoke the Sign in with Apple authorization. Settings on the diffuser and on this phone are not deleted.
- If you disconnect myinstay in your Kakao account settings (connected services) or close your Kakao account, we treat it as a request to delete your account once Kakao notifies us.
- Turning off account schedule storage deletes the diffusers and schedules kept in your account right away; the settings on this phone and the diffuser remain. Signing out only ends the sign-in on this phone; the account and the records kept in it remain.
- If you have deleted the app or cannot use it, you can request account deletion by emailing service@allsenselab.com with the service you signed in with and the email at that service (your nickname for Kakao). After verifying your identity, we delete the account within 30 days.
If you receive notifications
- Refill alert registrations are kept while refill alerts are on and deleted when you turn the alert off on the Scent screen. Firebase keeps the notification registration information (notification token and Firebase installation ID) while announcements or a refill alert is on; when both are off, the app deletes it, and Firebase then removes it from its live and backup systems within 180 days.
- If you delete the app without turning notifications off, the notification token stops working and our server deletes the refill alert registration once sending fails for that reason. The notification registration information may remain under Firebase's own rules (on Android, a notification token expires after 270 days without use). Because myinstay does not keep a separate copy of the notification token or the Firebase installation ID, we cannot find and delete it later. To have it deleted, turn notifications off before deleting the app.
8. Children
myinstay does not knowingly collect information from children under 13.
9. Changes
This policy may change. Any change will be announced on this page.
10. Privacy officer and your rights
You can request access, correction, deletion or suspension of processing of your personal information using the contact details below. A legal or authorized representative may also make a request. We will explain the verification needed to confirm your identity or the representative's authority. In-app data deletion requests follow section 7.
Contact details and request content you provide are used for identity verification, handling your request and communicating the result, not for marketing. Please do not send unnecessary copies of identity documents or sensitive information.
- Operator: AllSenseLab Co., Ltd. (주식회사 올센스랩)
- Privacy officer: 김민기 (CEO)
- Privacy inquiries: service@allsenselab.com
- Phone: +82-2-2138-3421
- Address: Room 508, The Space Tower, 144 Gwangnaru-ro, Seongdong-gu, Seoul, South Korea