English
1. Who is responsible
Uyoung.Inc (주식회사 유영) operates JAMEN, a contact-free sleep tracking service. Privacy contact: Ho-young Oh (오호영), uyoung.st@gmail.com. This policy covers the JAMEN app, its analysis service and these privacy and account-deletion pages.
2. What we process and why
- Audio you record or select: breathing and other nighttime sounds, which may include speech or other people's voices. We process audio to estimate sleep stages and, after the updated in-app audio notice is accepted, regions containing possible snoring. This is not a sleep apnea assessment. Recording starts through your action and microphone permission; screen-off recording can continue until stopped or interrupted. Upload begins when you choose to start analysis. Please do not record other people without appropriate permission.
- Sleep and analysis information: Wake, REM and NREM estimates, stage probabilities, estimated snoring regions and probabilities, assessed and unassessed durations, timestamps, processing status and errors. We also retain diagnostic information with the report, including audio fingerprints (hashes), signal statistics, model outputs and model version, to check the analysis path and troubleshoot errors. These are associated with your service connection and are not treated as anonymous data. Temporary decoded audio, mel-spectrograms and audio feature representations are used during analysis and removed with the analysis scratch files.
- Access information: hashes of connection/recovery credentials, invitation hashes and access counts, creation and revocation times. These authorize access to your reports and limit abuse. Your recovery code is stored in the device's secure storage; protect it like a password.
- Device-only settings: language, appearance, audio consent version/time, age confirmation and recording metadata. We store an age-eligibility confirmation rather than a birth date. These settings are not uploaded as part of the analysis request.
- Technical and support information: request time, network/request metadata and error information can be processed by hosting infrastructure for delivery, security and troubleshooting. If you email us, we receive your email address and the contents you send. Do not email audio or recovery codes unless a specific secure support process has been agreed.
Google sign-in is not currently enabled on the production service. If enabled in a later version, we will update the relevant notice before use. The current version does not collect payment details, use an advertising SDK, sell personal information, share it for cross-context behavioral advertising, or use audio/reports for model training. Cloud storage of original audio is not offered.
2a. Reminders, feedback and optional diagnostics
Bedtime reminders are scheduled locally at a time you choose. Notification permission is optional; turning reminders off cancels their schedule. The selected time stays on your phone. This version does not register the device for remote marketing messages.
When you submit feedback with consent, we receive the category, message, optional reply email, app version, platform and language, associated with your service connection. We use it to answer and improve the app. Recordings and reports are not attached. Feedback is stored with our Railway service in Singapore and deleted after 180 days by hourly cleanup (or after service recovery during an outage). You can delete your submitted feedback in Settings; deleting your account also deletes it. Email sent outside the app follows the support correspondence retention below. Withholding feedback or an email does not affect sleep analysis.
With your separate optional choice in Settings, Google Firebase Crashlytics receives crash traces, app/device/OS information and installation identifiers for reliability diagnosis. Processing can take place in the United States and other Google processing locations; it is not limited to our Singapore analysis server. We do not attach recordings, reports, feedback, email or account credentials. Firebase Analytics and advertising collection are disabled. Under Firebase’s privacy documentation, Crashlytics begins removal from live and backup systems after 90 days. Turning the option off stops future report uploads and deletes unsent reports on the device; it does not recall reports already uploaded. Contact our privacy address about rights requests; Google’s privacy contact information is at Google Privacy Policy. Refusing diagnostics has no effect on analysis or reminders.
2b. Optional product improvement signals
With a separate, default-off choice in Settings, JAMEN sends recording-start/save, upload-start/failure and report-open event names, a random event ID, your private connection identifier, app version and receipt time to the existing Railway service in Singapore. These signals contain no audio, report values, filenames or message text. We use them to understand reliability and repeat use. Events are best effort and are not queued on your phone when offline. You may separately choose to submit whether a report was helpful, associated with that report and connection; this is not an assessment of medical accuracy. Both event data and helpfulness answers are retained for up to 90 days, with hourly cleanup or cleanup after service recovery. Turning sharing off stops new events and requests deletion of existing events and helpfulness answers. If deletion fails, the app explains how to retry; account deletion also removes them. Reports and recordings are unaffected by deleting usage data. Refusing these optional choices does not affect analysis.
For recordings made with the app, we also receive the recording start time and time-zone name to label the correct night. Imported and older recordings may have an unknown recording date, which is labeled separately from the analysis date. Bounded analysis jobs may resume after a restart only while their temporary input is still available. Queued jobs expire after two hours before processing; audio is deleted after completion or failure and is not retained for training.
3. Permission and choice
You can decline microphone access and audio processing, or withdraw audio consent in Settings. This stops new recording and upload through the app, but does not automatically cancel an already-started analysis or delete saved information. Use the deletion controls below. The privacy policy itself is not a substitute for any separate consent required for health-related information or international transfers. Refusing server processing means cloud analysis cannot be provided.
4. Storage and deletion
- Uploaded audio and temporary analysis files
- Deleted after analysis finishes or fails. If a process is forcibly interrupted, remaining files are cleaned up when the service next starts. During an outage cleanup may be delayed until recovery; contact us for assistance. Raw audio uses temporary working storage, not the report database. We do not operate an original-audio archive.
- Reports and diagnostics
- Retained until you delete an individual report, delete all reports, or delete your service connection/account. Account deletion removes reports and linked identities from the active database. An analysis in progress must finish before those deletion operations can complete.
- Recordings on your phone
- Remain until you delete them using the app or remove the app's local data. Deleting server reports does not delete local audio. Files originally imported from another folder or app remain under your control outside JAMEN.
- Access and security records
- Active credential hashes are kept while your connection is active. Revoked credential hashes and revocation timestamps remain to reject reuse, until the corresponding authentication system is retired. They do not include your audio or deleted sleep reports. Invitation records have a validity of up to seven days; expired hashes and aggregate attempt counters may remain in the access database for security administration. There is currently no scheduled purge for those records. You may request review of retained security information through our privacy contact.
- Infrastructure logs and copies
- Application HTTP access logging is disabled. Operational/error logs may contain session identifiers and technical details. Railway Pro documents a 30-day log retention window; this is not a promise that every infrastructure copy is erased within 30 days. We do not intentionally include audio or authentication secrets in logs. Provider-managed security records and infrastructure copies are governed by Railway's processing terms. Active-database deletion does not constitute certified physical erasure of every underlying storage copy.
- Support correspondence
- We use correspondence to handle your request and delete it when no longer needed for that request or an associated dispute. Where a specific legal obligation requires retention, we restrict its use to that purpose and explain the basis and period in response to a rights request.
5. Service providers and international processing
We use Railway Corporation, a US provider, for hosting, temporary audio processing and report storage. The JAMEN application server and report volume are configured in Singapore. When you start analysis, audio is sent over HTTPS; reports, access hashes and technical metadata are processed as necessary to provide, retrieve and protect the service. The retention periods above apply to JAMEN-controlled data.
Railway's infrastructure administration, security and support may involve processing in the United States; selecting Singapore does not mean every provider operation occurs only there. Railway privacy contact: privacy@railway.com. See its Data Processing Addendum, privacy policy and subprocessor information. We use this provider to deliver the analysis service you request. You can refuse further transfers by not uploading, withdrawing audio consent, or contacting us; cloud analysis will then be unavailable. We do not give audio or sleep reports to advertisers. Disclosure may also occur if required by applicable law.
6. Your rights and account deletion
You can view and delete reports in the app, remove device recordings separately, withdraw audio consent, and delete your connection/account in Settings. You can also use our web account-deletion page with your recovery code. Deletion revokes account access and removes associated reports; limited security records described above remain.
Email our privacy contact to request access, a copy, correction, deletion, restriction of processing, or to raise a complaint or appeal our response. Depending on applicable law, you may exercise these rights through an authorized representative. We verify ownership without asking for unnecessary identity documents. If recovery information is lost, we may be unable to identify your records safely; we will explain available options. We do not penalize you for exercising privacy rights. Automated stage estimates can be inaccurate; you can challenge a result or delete it. They are not used by JAMEN to make employment, insurance or eligibility decisions.
7. Security and age
We use HTTPS for server transport, hashed server credentials, device secure storage for access secrets and owner-specific access controls. Access to operational systems is restricted. Electronic records are deleted from active storage using application and database deletion controls; no system can guarantee absolute security or immediate physical erasure of provider-managed media.
JAMEN is for people aged 14 and older. We do not offer the service to children under 14. Contact us if such a child's information has been submitted so we can investigate and remove it. Eligibility to use the app does not establish medical suitability: adolescent prediction performance has not been validated. JAMEN is not a diagnostic or treatment service.
8. Cookies and changes
These policy and deletion pages do not use advertising or analytics cookies. Hosting infrastructure still processes requests needed to serve the pages. Material changes to this policy will be announced through the app or this page with an updated effective date. New uses such as audio archiving, model training, advertisements or account integrations will require updated notices and, where required, separate consent before starting.