Privacy policy
Shift Alarm — Scheduled Alarm
Updated 20 October 2026.
1. Who is responsible
The developer and seller of the paid feature is Individual Entrepreneur Efremov Sergey Olegovich (Ефремов Сергей Олегович), INN 471905964680, OGRNIP 326470400141351. Send questions and requests concerning access, correction or deletion to sergey_efremov.dev@mail.ru. This policy covers the Android application and alarm.efreitor2001.ru.
2. Information stored on your device
The application stores alarm time, work and rest days, cycle start date, label, enabled state, melody, volume and gradual volume settings. Technical scheduling, ongoing alarm, snooze and recovery information is also stored to support reliable local operation.
When you select a custom audio file, the application stores a local reference and Android's permission to read that selected file. Selecting one melody does not by itself give access to all your documents. The audio file is not uploaded to Google Drive.
A verified purchase is stored locally with an integrity check protected by Android Keystore. This confirmation is excluded from ordinary application backup. Clearing application data or uninstalling removes local settings and confirmation; clearing the cache alone does not delete all application data.
3. Optional Google Drive synchronization
Communication with Google begins after you explicitly connect an account and grant permission. The application requests access only to its hidden appDataFolder, rather than all Drive files. Your settings are stored directly in the chosen Google account; the developer has no separate server for storing your alarms.
The cloud copy contains work and rest days, calendar start date, time, enabled state, alarm label, volume and gradual volume, and a built-in melody key or a custom-melody marker. Random installation and record identifiers, change versions and deletion records allow changes from devices to be merged.
If a purchase exists, the copy also contains its Robokassa invoice number, merchant and product identifiers, amount of 14900 kopecks, RUB currency, payment mode flag and a random verification value. These are used to restore and reverify payment. The receipt email, card data, payment passwords, local integrity signature, audio files and their URIs or names, ongoing alarm and snooze state are not uploaded.
The selected account's email and identifier are stored locally to associate synchronization with that account; the access token is used in memory. Google data is not used for advertising, profiling or sale. Its use is limited to synchronization and restoration and complies with the Google API Services User Data Policy, including Limited Use.
The application merges device changes and keeps deletion records so that old copies do not automatically bring deleted alarms back. Background synchronization runs after changes and periodically when a network is available; Android may delay it. Restored alarms are scheduled again using the device's local time. Unavailable custom audio is replaced with a built-in melody and a warning.
Drive requires Google services. It may be unavailable on devices without them, including some Huawei devices. Local alarms and a purchase already verified on the device do not require a permanent Google connection.
4. Payments and restoration
At checkout Robokassa receives the receipt email, invoice number, product amount and description, receipt information and technical order-verification values. Payment details are handled by the payment provider and relevant banks; the application's own code does not store card details.
Until a transaction is resolved, the device stores the pending invoice, email, date and accepted offer version so that the original transaction can be checked after closing the payment form or restarting. During restoration the application queries that invoice's status with Robokassa. A cloud “ad-free” flag alone never grants the feature.
The seller receives payment and refund information through Robokassa to fulfil the agreement, meet record-keeping duties and provide support. It does not include alarm settings unless you voluntarily send them with a support request. See Robokassa's privacy policy.
5. Advertising and third-party technology
The free version uses the unified Yandex Mediation build. It includes the SDK and partner-network adapters; actual participation depends on Yandex Advertising Network settings, availability and region. Supported sources include Yandex, Google, VK/myTarget, AppLovin, Appnext, BIGO Ads, Chartboost, Digital Turbine, InMobi, ironSource/Unity, Mintegral, Moloco, Pangle, Start.io, Liftoff/Vungle, Zmaticoo, BidMachine and Tapjoy.
Advertising services may process the advertising identifier, IP address, device, OS and network information, approximate region inferred from network data, impressions, interactions and diagnostic information. The application's own code does not send alarm settings or labels, purchase data or Google Drive content to advertising services. Setting alarms does not require a precise-location permission.
After purchase verification the application stops requesting and displaying ads, removes loaded banners and does not initiate its ad SDK for advertising on subsequent launches. A purchase does not erase information previously received by advertising operators.
Further information: Yandex privacy policy, Yandex Mediation information, and Google privacy policy. Independent providers can be contacted through the channels in their own policies.
6. Android permissions
Exact alarms support scheduling; notification and full-screen intent permissions support the alert and ringing screen; foreground service, wake and vibration capabilities support playback; boot events restore schedules after restart. Internet and network-state access support advertising, payments and optional synchronization. Access to selected audio is granted through Android's file picker. A full-screen notification is not permission to draw over all other applications.
7. Retention, disconnection and deletion
- Delete individual alarms in the application. To remove all local data, use Android's “Clear storage/data” option or uninstall. System backup of some settings depends on Android version, device settings and the application's backup rules.
- Disconnecting Google in the application stops synchronization and revokes access, but leaves an existing cloud copy. To delete it, open Google Drive in a browser: Settings → Manage apps → Shift Alarm → Delete hidden app data. First disconnect synchronization on your devices to prevent a new upload.
- Deleting the cloud copy also removes the information needed for automatic purchase restoration; it does not cancel the acquired licence. If restoration fails, contact support with payment evidence.
- Payment and accounting records that the seller, Robokassa or a bank must retain are kept for legally required periods. Support messages are used to reply, resolve claims and meet legal obligations, and are deleted once no retention ground remains.
8. Grounds, security and rights
Processing supports user-selected functionality and performance of the agreement, legal duties, and separate consent where required. Google authorization is requested separately and can be revoked. You may request information about processing, correction, restriction or deletion where applicable by law, and contact the competent authority.
Google and Robokassa connections use HTTPS. Device and account security also depend on their protection settings. Google and other independent providers may process information on infrastructure outside your country under their own terms. Absolute security of transmission and storage cannot be promised.
The website has no payment form, developer-operated analytics counter or advertising scripts. GitHub Pages hosting may process request logs, including IP addresses: see the GitHub privacy statement. Email requests pass through your email provider and the support mailbox.
The application is not specifically directed at children. Purchases by minors require involvement of a legal representative where required by law. Contact support if a child has accidentally submitted personal information.
Updates are published with a new revision date. Contact: sergey_efremov.dev@mail.ru.