ALARMMATE

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

Back up cloud settings

Wake-up flow events

View the morning weather

Purchases and customer support

group and sharing

Data and sensors left on the device

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.

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.

Google ML Kit SDK data disclosure

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

Request to check, export, or delete information

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.