Privacy Policy
Alarmmate explains the differences between information processed by function and data on the device and server data.
- Operator
- 더리얼그룹(The Real Group Co., Ltd.)
- Operating region
- Operation and service data storage for South Korea: Northern Virginia, USA (us-east-1)
- Support and privacy contact
- tech@realry.com
- Effective date
- 2026-11-12
Account and login
- If you choose to sign in with Apple or Google, the provider identifier, the email confirmed by the provider (if provided), the app's display name, and sign-up time will be used for account identification, login, and customer support. If you use Apple private email, a corresponding forwarding address may be provided.
- We process the provider's identity token, one-time authentication value and authorization code during sign-in verification. Our server stores session-token hashes and their creation and expiry times.
- iOS account sessions are stored in this device's Keychain. Android account sessions, installation identifiers and deletion-recovery tickets are stored in app-private storage protected by Android Keystore. These Android records are excluded from operating-system backups and device transfers. An app-stored access flag is not accepted as proof of purchase.
Back up cloud settings
- After encrypting the alarm/routine settings selected by the user to upload on the device, the encrypted data and update time are stored on the server. Backup passwords and pre-encryption settings are not sent to this backup API.
- The original photo, journal, small room decoration, and wake-up and manual sleep records are not included in this settings backup. Alarms restored to another device are added as off, so you must check and turn them on directly.
Wake-up flow events
- When the server is connected and logged in with an account, function events such as saving an alarm, starting and completing a mission, reconfirming, reminding again, emergency termination, and completion can be sent to the server. Events are used for condition diagnosis and operational reporting.
- Events include event, alarm, and wake-up session identifiers, time of occurrence, progress, practice status, platform, and alarm type. The production server distinguishes device events by a combined value of the account and installation identifier. This event does not include the alarm name, photo, and microphone source.
- If you log out or don't have a connection, unsent events may remain on the device and later be sent from a valid account connection. You can check the transmission connection status and turn it off on the data and diagnostic screens.
View the morning weather
- If you use Apple WeatherKit Weather on iOS, the device sends fixed representative coordinates for the selected city directly to Apple. This request does not go through the Alarmmate production server. Responses are cached on the device for up to 30 minutes and displayed from the weather source and instructions provided by Apple.
- In other environments that use the production server's weather proxy, the fixed representative coordinates of the selected city are transmitted to the production server, and the server queries the weather provider with those coordinates. If the supplier and authority configuration is not ready, the weather will not be displayed.
- Choosing a city does not require location permission. On iOS and Android, the app checks location once while in use only when you select current location. Android requests approximate location permission only. You can choose a city if permission is denied, location services are off, or the lookup fails.
- Current coordinates are rounded to two decimal places. iOS requests Apple WeatherKit directly from the device. Android temporarily sends the rounded coordinates and device time zone in an HTTPS request body to the Alarmmate server to query Apple WeatherKit. Coordinates are not linked to account or installation identifiers or saved in preferences, databases or logs, and no background tracking occurs. The server keeps a bounded in-memory cache of location-specific lookup keys and weather responses and does not reuse entries older than 10 minutes. The device caches only the weather response; Android forecast times follow the device time zone. Services receiving internet requests may process connection information such as IP addresses.
Purchases and customer support
- We process account identifiers, signed purchase transactions, transaction identifiers, product IDs, purchase environment, expiration and withdrawal times, and verification times to confirm ownership of App Store purchases and reflect usage rights. If you have connected RevenueCat, the subscription management provider, an Apple purchase transaction signed with the same account identifier is sent to confirm the purchase and subscription. Purchases from different login accounts are not automatically merged. We do not collect all App Store payment information or payment card numbers as purchase verification data on this server.
- On Android, the RevenueCat SDK and Google Play verify purchases and restores. Device access does not require an Alarmmate account. When you choose to link purchases to an account, we send Google Play purchase tokens and an installation-specific anonymous customer ID to our server over HTTPS. Our server checks Google Play and RevenueCat transaction, product and subscription records. Alarmmate processes raw purchase tokens only for verification and does not store them in its database or logs. We store token hashes, original transaction and product IDs, linked account and installation IDs, purchase environment, and relevant purchase, expiry, revocation and verification timestamps.
- If you choose to submit an inquiry, the account identifier, inquiry type, text, processing status, and submission time will be saved. The app/OS version, permission status, number of alarms, and whether errors have occurred are saved together only if you select Attach Device Diagnostics. Personal information written directly in the text of the inquiry will also be processed, so please enter only the necessary information.
group and sharing
- When a group is created, joined, and invited, the group name, owner, participation relationship, invitation code, expiration time, and display name within the group are processed. If you press the wake-up check in directly, the account identifier and date/time will be saved to the group and displayed to other participants.
- If you select Report or Block, the reporting person, target group, reason, explanation, and processing status and time, and the target identifier, display name, and time will be processed. The person in charge authorized to operate queries, reports, and queries will search and process the data necessary for the operation of the function, and leave a processing history.
Data and sensors left on the device
- This function stores and processes alarms, weather records, and manual sleep records, personal journals, mood, and promises, small room decoration, weather points, and prop exchange records, and photo, microphone, and motion sensor inputs used in sensor missions. It does not provide a function to upload the original photo, recording, and motion sensor source of the mission to the above operation API. Use the camera/microphone according to the relevant functions and permissions.
- According to Google's SDK disclosure, Google ML Kit used for Android barcode recognition may send device and app information, per-installation identifiers, performance metrics and error diagnostics over HTTPS for diagnostics and usage analytics. This is separate from sending original barcode photos to Alarmmate servers. Google's SDK privacy information applies.
- This is not a release that provides automatic sleep and snoring analysis. Manual sleep recording and sound playback for sleep are different from automatic health measurements. Device backup, photo access, and sharing operations provided by the OS can be handled separately according to the user's device settings and choices.
- Local export files can include alarms, wake-up and manual sleep records, journals, and decoration settings. The original photo and authentication token are excluded. When sending a file to the app/storage location selected by the user on the shared sheet, check the processing method of that destination as well.
- The function for selecting dates to exclude alarms from the calendar reads the calendar allowed by the user from the device. The event name, time, and calendar information required on the selection screen are read and the selected date is reflected in the alarm settings, and no new schedule is written to the calendar. The original schedule and the entire calendar list are not uploaded to the operation API. Since the selected and saved exclusion dates are alarm settings, they can be included in the backup of the encryption settings selected by the user.
Purpose of processing and storage/deletion
Account information, session, encryption settings, backup, purchase verification, inquiries, and selected group materials are stored during account maintenance to provide these functions. Once the app has verified the identity, disconnected the required Apple connection, confirmed the remote deletion of the connected RevenueCat customer, and saved the deletion processing ledger, the relevant account data and connection event/group participation data from the current operating database are deleted. If remote verification or saving fails, the deletion is not marked as complete and the state remains in process. Wake-up feature events are periodically deleted 90 days after server reception, consumer related operation processing history 90 days after recording, and employee security and permission audit records 365 days old. Cleanup runs at server startup and approximately every 15 minutes, and actual cleanup may be delayed during a failure or while waiting for processing. A copy of the service database for disaster recovery is stored daily on a dedicated, access-restricted, encrypted S3 in us-east-1 in the US. The copy is processed as an expiration date 7 days after creation, and there may be a delay in S3's actual deletion time. The local copy of the server is up to 2 copies of the latest and previous ones, and files older than 7 days are cleaned up during the next maintenance session. Immediate destruction during a failure is not guaranteed, and copies more than 7 days after creation are not accepted for general recovery. A separate deletion ledger containing only the UUID and processing time of the deleted account is processed as expiring after 14 days, and is used to reapply the account deletion when recovering a valid copy. The deleted account's data on the previous copy reflects the deletion ledger prior to restoration, and account deletion does not mean that all past copies are immediately physically destroyed. Set up production API and proxy error logs to be kept in AWS CloudWatch for 14 days. The dedicated host's system journal is organized at the upper limit of 14 days, 128 MiB on disk, and 32 MiB during execution, and may be cleaned up earlier due to capacity limitations. We do not guarantee immediate destruction during host failure or maintenance delays. The applicable processing standards below also apply to external provider materials. Local alarm, wake-up and manual sleep records are separate from account deletion and can be managed through the device's data controls. App Store and Google Play subscriptions must be managed separately in the store where they were purchased. The Android remote deletion recovery ticket stores the account UUID hash, installation identifier, and confirmation status, and is deleted in the next request/cleanup session 14 days after issuance. The device's deletion and recovery records are protected by Keystore and cleaned after recovering confirmed deletion/license. You can request to view or delete unlinked guest purchase materials using the personal information contact information.
- If RevenueCat customer data is linked, we also request deletion by that provider. If remote deletion is not configured or fails, we do not mark account deletion as complete. When account deletion is completed, we delete the account, sessions, encrypted backups, support requests and purchase-verification data from the current service database, along with that account's wake-up event associations and group-membership data. If other members remain in a group, ownership of the group may be transferred.
- An Android installation's RevenueCat customer record can be linked to only one Alarmmate account. After confirming deletion of the RevenueCat customer data, we delete the account, session and purchase-link records. We do not report account deletion as complete while processing or provider confirmation is pending or unsuccessful. To request access to or deletion of unlinked guest purchase data, use our privacy contact. Anonymous identifiers used to verify purchases are also treated as personal data.
- To confirm completion when a device misses an account-deletion response, we may retain hashes of secret recovery tickets, pseudonymous account and installation identifiers, and processing status. Tickets are valid for 14 days. Expired server records are removed on the next relevant deletion-status request or server startup. The raw ticket is not stored on the server; it is kept in protected device storage. Once deletion of the RevenueCat customer data is confirmed, the device may use a new anonymous identifier to restore Google Play purchases. Network or store verification failures can require a separate retry of purchase restoration.
- For server operation processing history, separate operation backup, and the scope and storage standards of data stored by the App Store/Login Provider, please also check the operation storage guide above and the processing outsourcing/external provision guide below. The deletion completion screen does not mean that all external provider data has been deleted.
Outsourced processing/external provision
In order to provide authentication, purchase, and weather functions selected by users, necessary information is exchanged with the relevant provider. The actual operating configuration and storage instructions of Alarmmate are as follows.
AWS: Hosts operational APIs, restricted access databases, encrypted disaster recovery copies, and operational logs. The service storage region is Northern Virginia (us-east-1), USA. Account identification, authentication, encrypted backup, wake-up feature events, subscription verification, inquiries, and group data are sent and processed via HTTPS when using this function. ALB access and connection logs in S3 and app proxy's explicit HTTP access logs are not used, and operational error logs are stored in CloudWatch for 14 days. Cloudflare only uses DNS, not the HTTP proxy for this service. RevenueCat, Inc.: Verifies purchase and renewal status by sending a consumer UUID, signed Apple purchase transaction, anonymous customer identifier for each iOS and Android installation, and Google Play purchase, product, transaction environment, and subscription status when linking purchases to an account. The provider discloses that it stores customer data in an AWS data center in the US. Personal information inquiries can be made to compliance@revenuecat.com. When deleting an Alarmmate account, we request deletion of the associated RevenueCat customer record and verify that this record can no longer be retrieved. This does not mean that the provider's own legally or security-retained data and backups are immediately destroyed. Apple: Apple processes the Apple sign-in and App Store payment/purchase verification you choose. Choosing a city does not require location permission. On iOS and Android, the app checks location once while in use only when you select current location. Android requests approximate location permission only. You can choose a city if permission is denied, location services are off, or the lookup fails. Current coordinates are rounded to two decimal places. iOS requests Apple WeatherKit directly from the device. Android temporarily sends the rounded coordinates and device time zone in an HTTPS request body to the Alarmmate server to query Apple WeatherKit. Coordinates are not linked to account or installation identifiers or saved in preferences, databases or logs, and no background tracking occurs. The server keeps a bounded in-memory cache of location-specific lookup keys and weather responses and does not reuse entries older than 10 minutes. The device caches only the weather response; Android forecast times follow the device time zone. Services receiving internet requests may process connection information such as IP addresses. Google: Processes the Google Sign-in selected by the user only if the feature is configured and provided. Android purchases, restores, and subscriptions are handled by Google Play, and the server temporarily processes the original purchase token during purchase verification and does not store it in its own database/log. The Google ML Kit Barcode SDK for Android can send device/app information, installation-specific identifiers, and performance/error diagnosis information via HTTPS. This is separate from uploading the photo source to the production server. Administrator Google authentication for employees is separate from consumer accounts. Each provider's privacy policy applies to account and service information directly processed by Apple and Google. This guidance does not arbitrarily determine a separate contract or provider storage period.
- The production API and service databases are handled by the AWS US Virginia Northern Region (us-east-1). Inquiries about the operator and requests for access and deletion can be submitted using the contact information above.
- RevenueCat receives account identifiers linked to iOS purchases, signed Apple transactions, installation-specific anonymous identifiers for iOS and Android, and Google Play purchase, product, environment and subscription information to verify access. Android purchase tokens, anonymous identifiers and transaction data can be personal data. We do not send names, email addresses or raw sensor data as RevenueCat customer attributes. RevenueCat states that it stores customer data in US AWS data centres. Provider backups and legal retention are separate from deletion of records under our control.
- Apple Sign In, the App Store and WeatherKit process information needed for authentication, purchase verification and weather. Google Play processes information needed for Android purchases, restores, subscriptions and transaction verification. Google authentication is used when you choose Google Sign In. Employee administrator sign-in is separate from consumer accounts.
Operating region/overseas processing
Using the service account, backup, event, inquiry, group, and purchase status functions, necessary data is delivered to the US operating infrastructure (AWS us-east-1) via an encrypted connection to the Internet for processing and storage. The items, purposes, and periods are the same as the above instructions for each function and storage/deletion. If a subscription is linked, we send the account UUID, signed purchase transactions, installation-specific anonymous customer identifiers, and Google Play purchase, product and subscription status to RevenueCat, Inc. (US, contact compliance@revenuecat.com). The recipient's deletion of customer data is requested and confirmed during the account deletion process, and the provider's standards may be applied to the provider's own backup and legal storage. Apple and Google's authentication, payment, and weather services are services operated by each provider, and the provider discloses that data can be processed in various countries, including the United States. Alarmmate does not select or guarantee a specific processing country or separate storage period for these services, and also provides each provider's official personal information, transfer, and deletion instructions. If you don't want external processing, you can use the guest alarm on your device without using the corresponding selection features for account, cloud backup, groups, subscription connections, and weather. Inquiries about confirmation, correction, deletion, and suspension of processing of relevant materials and overseas processing can be submitted at tech@realry.com. Stopping processing may limit the functionality that requires that data. Google's official privacy policy also applies to the processing of diagnostic information in Android Google ML Kit, and anonymous identifiers for purchase confirmation are also treated as personal data.
Safeguards and options
- Service connections use HTTPS, and account session tokens are stored as hashes on the server. It separates access rights for each employee and leaves a history of operational processing. The configuration backup is encrypted by the device to AES-256-GCM, and the backup password is not sent to the server.
- Camera, microphone, motion and calendar permissions are requested when needed and can be changed in your device's system settings. If you decline a permission, you can use missions or alternatives that do not need it. We do not automatically record sleep or snoring.
- You can check the connection status and turn off the transmission of wake-up events from Settings → Data and Diagnostics in the app. If turned off, transmission to that server will stop, and the alarm will continue to be available on the device. groups, inquiries, and sharing are handled by actions selected by the user. We do not provide customized advertising or data sales functions using advertising identifiers.
Request to check, export, or delete information
- Delete account and server data: Double check your identity as the current login provider in App Settings → Account · Cloud Backup → My Account → Delete Account. The Apple account deletes the server account data after the provider disconnection is complete. If verification or disconnection fails, it is not marked as complete.
- Deleting your account does not delete this device's alarms, wake-up records or manual sleep records. In My Account → Device Data, you can export local data or select alarms, wake-up records and manual sleep records for deletion. Finish any active wake-up session before continuing.
- Account deletion does not cancel subscriptions. Use the app's subscription management link to open the purchasing store, or manage subscriptions in iPhone Settings → Apple Account → Subscriptions, or Google Play → Payments and subscriptions → Subscriptions. Deleting the app or your account does not cancel an App Store or Google Play subscription.
- My Account Data Export provides a file with account information, inquiries, encrypted backups, and purchase confirmation records of the logged-in account. Guests can also use the export in My Device Data Manager. We don't automatically send a destination to others before selecting it on a shared sheet.
- If the account deletion is displayed as being processed, confirmation of the deletion of remote subscription management materials has not yet been completed. You can check the deletion status on the same account and try again until it is marked as complete. Save only the processing state so as not to require reuse of an Apple Verification Code that has already been completed.
For inquiries regarding access, correction, deletion, suspension of processing, and overseas processing, please contact us using the personal information contact information above. You can request the range of information necessary to identify the requester. If you do not want external processing of the optional function, you may not use the relevant login, purchase connection, or weather check, and you can also request deletion of account data from the app. If data required for processing purposes is deleted or external processing is stopped, the corresponding account, backup, group, and license verification functions may be restricted.