Inemuri Guard

1. About this policy

Inemuri Guard ("the app") is provided by Studio Toriumi ("we"). It watches your eyelids with the camera and, if your eyes stay closed for a set time, wakes you with sound, vibration and the screen. It was designed for dozing off at a desk. If you use it in a car, it is only an aid: it is not a driver-assistance system, a safety device or a medical device, and it does not replace the driver's duty to pay attention.

Using the app while driving
The app can miss signs of drowsiness, and it can go off when you are not asleep. We accept no liability for accidents or damage arising from relying on how the app behaves, fails to behave, or what it displays. Do not operate your phone while driving. Mount it securely where it doesn't block your view or controls, and follow the traffic laws where you are. If you feel sleepy, pull over somewhere safe and rest, whatever the app says.

This policy covers both the Android app (distributed on Google Play) and the browser version. The Android app is free to use (see sections 6 and 7 for ads and in-app purchases). By using the app, you agree to this policy.

2. What we don't collect

The app doesn't ask for your name, email address or any other personal details, and there's no account to create. Camera video, microphone sound and your drowsiness history are processed and stored only on your device. None of it is sent to us or to anyone else.

The Android app talks to an ad network (Google AdMob) to show ads (section 6). In car mode, speed limit alerts (on by default) send the rough area you're in to a map server (section 5). The browser version has neither ads nor speed limits, and the page doesn't talk to any server.

3. Camera

The app uses the camera to detect when you're falling asleep. Here's how:

• It finds landmarks on your face, turns how open each eye is into a number from 0 to 1, and looks at how long both eyes stay shut and what share of the recent past they were mostly closed (PERCLOS). It doesn't count blinks.
• Video used for drowsiness detection is processed in real time on your device only. It is never recorded, saved or sent. (The only recording is the dashcam below, and only when you open it yourself.)
• On Android, detection runs with Google ML Kit, a machine-learning library that works entirely on the device.
• The camera turns off when you close the app (or tab) or stop monitoring.
• If no face is found, the alarm doesn't sound, and nothing about the video is sent anywhere.

If you don't allow camera access, drowsiness detection won't work. You can withdraw the permission at any time in your system or browser settings.

3-2. Dashcam (Android app, experimental)

• The rear camera records the road only after you open the dashcam screen and start recording. No audio is recorded.
• Clips are saved as one-minute files only on your device (in the app's private storage). The newest 10 are kept and older ones are overwritten automatically. Clips around a detected jolt, or when you tap Protect, are kept.
• Clips leave your device only if you choose Share / save. We never receive them.
• Clips may show other cars' number plates or people walking by. Please respect their privacy if you publish anything.
• While recording, on-device object detection finds cars, people and traffic lights ahead and speaks up about closing in fast, following too closely and the car ahead moving off. Detection results never leave the device either.
• After a hard impact, a screen appears with buttons to call emergency services and to send your location. Nothing is called or sent automatically. Your location is shared, as a message through the app you choose, only when you tap Send my location.

3-3. Driver emergency response (Android app, off by default)

• In car mode, if the drowsiness alarm keeps ringing for 20 seconds, the app shows a "No response" screen. Only if you have saved a phone number (for example a family member's) and turned this feature on, the app waits 15 more seconds and then calls that number. Without phone permission, it opens the dialer with the number filled in instead.
• The app never calls emergency services on its own.
• The number you save is stored only on your device and never sent to us or anyone else.

3-4. Walking mode (Android app, experimental)

• The rear camera image is analyzed on the device only to tell you, by voice and vibration, about cars coming up behind you or the color of a traffic light. Nothing is recorded, saved or sent.
• Spoken alerts use your device's text-to-speech.

4. Microphone (Android app)

The Android app uses the microphone for two optional features. If you don't allow microphone access, everything else, including camera-based detection, still works.

4-1. Stop the alarm by voice (v1.4.0 and later)

While the alarm is ringing, you can stop it by saying things like "I'm up" or "stop". This uses your device's speech recognition (on most devices, Google's).

• Speech recognition runs only while the alarm is ringing (up to 90 seconds). The app never listens while monitoring or idle.
• Because it calls your device's speech service, depending on your settings, that audio may be processed by an off-device service such as Google's, under that service's privacy policy. We never receive or store the audio or the transcript.
• The app keeps only the last short phrase it recognized (so the settings screen can show that it heard you), and that is cleared the next time the app starts.
• Turn off Settings → Detection → Stop by voice and the feature won't use the microphone.

4-2. Breathing detection (in development)

The app uses the microphone to notice the steady rhythm of sleep breathing and sound the alarm.

• Only changes in loudness (the envelope) are analyzed, on the device, to estimate breathing rhythm.
• Nothing is recorded, saved or sent. The sound itself is never kept.

5. Location (Android app)

In car mode, speed limit alerts (on by default) use your location to show the speed limit of the road you're on and let you know when you go over it.

• Location is used only while monitoring in car mode with the app on screen. The app does not collect location in the background.
• Speed limits come from OpenStreetMap, an open map dataset, via public servers (the Overpass API at overpass-api.de and others). What's sent is only the bounds of a square about 2 km across that contains you. Your exact position, speed, heading, the time and device identifiers are not sent. Once an area has been fetched, it's kept on the device and not requested again. The same request also returns the speed cameras mapped on OpenStreetMap in that area, so the app can warn you when one is ahead.
• As with any internet request, the map server can see your connection's IP address. Those servers are run by others, not us, and handle data under their own policies. Nothing goes through our servers, and we never receive your location.
• Your current speed is worked out from the phone's GPS and never leaves the device. No location history is stored.
• Turn off Monitor → Sensitivity and placement → Speed limit alerts, or don't grant location permission, and the feature uses no location and makes no requests.

Map data © OpenStreetMap contributors (ODbL). Roads without data show no limit, and the data can differ from the actual signs. Always follow the road signs.

6. Ads (Android app)

The Android app shows banner and interstitial ads through a third-party ad service, Google AdMob. In serving ads, the ad provider may automatically collect your device's advertising ID, device details such as OS and app version, and approximate location. That information is handled under each provider's privacy policy. The browser version has no ads.

Opting out of personalized ads

• Google ad settings: https://adssettings.google.com/
• On your device, go to Settings → Google → Ads to reset your advertising ID or opt out of personalized ads.

Related links

• Google Privacy Policy: https://policies.google.com/privacy

7. In-app purchases (Android app)

The Android app sells ad removal and extra features through Google Play in-app purchases. Payment details such as your name and card number are handled by Google; we never receive or hold them.

8. Permissions and why they're needed

The Android app asks for these permissions:

Permission	Why
Camera	To detect closed eyelids (video is processed on the device only), and to record with the dashcam when you open it (saved on the device)
Microphone	To detect sleep breathing and stop the alarm by voice (no recording is saved)
Location	To alert on speed limits and speed cameras in car mode and the dashcam (section 5; only while the app is on screen), and to send your location from the crash screen (only when you tap it)
Phone	To call the number you saved when you don't respond, if you turned on driver emergency response (section 3-3; off by default)
Notifications	To wake you when drowsiness is detected or a nap timer ends
Vibration	To vibrate as part of the alarm

The browser version uses only the camera, notifications and vibration. It doesn't use the microphone in normal use.

9. What's stored on your device

The Android app stores your drowsiness history, symptom check history, settings (including the driver emergency phone number) and dashcam clips only in your device's storage. History is deleted automatically after about 90 days, and we can't see or access any of it.

The browser version stores (in local storage) only your display mode, language and "use in car" settings, the fact that you accepted the terms, and any sleep times you entered yourself. Sleep times are deleted automatically after about 90 days. All of this is erased when you uninstall the app or clear the site's data in your browser.

10. Sharing with third parties

We don't hold your personal data on any server, so we have nothing to share with third parties. Data collected by ad providers in the Android app is covered in section 6. The area bounds and IP address that reach the map server when fetching speed limits are covered in section 5.

11. Children's privacy

The app isn't intended for children under 13 (or the minimum age set by the laws where you live), and we don't knowingly collect personal data from children.

12. How long data is kept, and deletion

History and settings stored on your device are erased when you uninstall the app or clear the site's data in your browser (Android history is also deleted automatically after about 90 days). We don't hold any of your personal data on a server.

13. Changes to this policy

We may update this policy when laws or the app change. Changes take effect when posted on this page, and we'll announce significant changes here.

14. Contact

For questions about this policy or how the app handles your information, contact:

• Operator: Studio Toriumi (https://toriumis.com/)
• Email: info@toriumis.com

For the privacy policy of the toriumis.com website as a whole, see https://toriumis.com/privacy/.