Privacy Policy
How Rotelo stores your schedules and memos, what information the advertising and usage statistics services process, and what to keep in mind when sharing and backing up.
1. Scope and basic principles
This policy applies to the Rotelo Android app (package name: com.ardi.rotelo). Rotelo can be used without signing in or creating an account.
Schedules and memos are managed in the app's local storage; there is no feature that sends them to a server run by the developer. However, the Google advertising SDK and the usage statistics tool (Google Analytics for Firebase) included in the app process separate information to serve ads and to measure usage. If you choose another app or a cloud service through the sharing or backup features, information may also be passed to that service.
2. Information stored in the app and how it is used
- Schedule information: shift schedules, shift types, start and end times, break times and repeating patterns are stored to show the calendar, apply patterns and calculate work-hour statistics.
- Personalisation: memos for each date, colours and per-memo reminder settings are stored to tell schedules apart and to show what you wrote.
- Settings: app settings such as the theme, notifications and time zone are stored for the screen, local notifications and widgets.
- Memo search: recent search terms are stored on the device and can be deleted one by one or all at once on the search screen. Search terms are not included in share codes or backup files.
- Change and import history: a change history for undo and a record that prevents duplicate imports are stored on the device. The change history may contain schedules and memos as they were before a change.
- Backup settings: the URI of the chosen backup folder and a backup origin identifier are stored on the device to manage where backups go and where they came from. These settings are not sent to the developer.
The app does not pass the contents of schedules or memos to the Google advertising SDK or to the usage statistics tool. There is no analytics server run by the developer; the advertising SDK and Google Analytics for Firebase process usage and diagnostic information as described below.
3. Information processed by the advertising and usage statistics services
Rotelo shows banner and interstitial ads through the Google Mobile Ads SDK (AdMob) and provides the required consent flow through the Google User Messaging Platform (UMP).
According to Google's SDK disclosures, the advertising SDK may automatically collect or share the IP address (used to estimate an approximate location), device or account identifiers such as the advertising ID and the app set ID, interaction information such as app launches, ad views and taps, and diagnostic information. The actual processing depends on the device, its settings and other factors, and is used to serve and measure ads and to prevent fraud. An approximate location derived from the IP address is different from precise location collected through a GPS permission. Google states that information is encrypted with TLS in transit.
Google's processing follows Google's policies and may take place outside your country. Please also check those policies and Google's privacy controls for retention periods and deletion options. Clearing the app's data does not delete information that Google has processed.
Usage statistics (Google Analytics for Firebase)
Rotelo uses Google Analytics for Firebase (Firebase Analytics), provided by Google, to understand how the app is used and to improve its features and the way ads are shown. This tool is included only in the app distributed through the store.
Information collected: according to Google's disclosures, the app instance ID, the advertising ID (which may not be collected depending on device settings), an approximate location estimated from a masked IP address, app lifecycle information such as app launches, screen views and sessions, and device and app version information are collected automatically. In addition, the app sends feature usage counts (saving a shift assignment, applying a pattern, saving a memo, creating and importing share codes, restoring a backup, adding a widget, ad display opportunities) and the type of a failed action as events that do not identify you.
Information not sent: dates, shift type names, work hours, memo contents, the text of share codes, the backup folder location, search terms and personally identifying information such as names, email addresses or phone numbers are never put into any event. Events contain predefined category values only.
Consent and encryption: in regions where user consent is required, the choices you make in the UMP consent prompt also apply to usage statistics and ad measurement through Google's Consent Mode. Usage statistics are processed under Google's policies and encrypted with TLS in transit. Regardless of consent, turning off the Send usage statistics switch in the app's settings stops further usage statistics from being sent (section 4).
4. Ad consent and privacy choices
UMP shows a consent prompt before ads are displayed where your region and the SDK require it. If the SDK determines that privacy options must be offered, you can review or change your choices in the app under Settings → Ad privacy settings. This menu is not shown in every region or situation.
You can manage advertising ID settings in Android settings; depending on the OS version, the options may include resetting or deleting the ID. Choosing non-personalised ads does not stop all processing needed to serve and measure ads and to prevent fraud.
You can turn usage statistics off or back on in the app under Settings → Privacy → Send usage statistics. The switch is on by default; once turned off, no further usage statistics events are sent from that moment, and the choice is kept when the app is restarted. This setting is stored only on the device and is not included in backup files or share codes.
The same advertising ID settings also apply to usage statistics, and clearing the app's data or reinstalling the app creates a new app instance ID and returns the switch above to its default. Uninstalling the app stops any further collection. Retention and deletion of information that has already been sent follow Google's policies described in section 3.
5. App permissions and device features
- Internet and network state: used to request and show ads.
- Notifications: on supported Android versions and with your permission, the app shows schedule and memo notifications. Memo notifications can be set to hide their contents on the lock screen. The notification permission is optional and can be changed in Android settings.
- Exact alarms and restoring notifications after a reboot: used to schedule and keep schedule notifications on the device; not a feature for the developer to track you.
- Folder access: accesses the backup folder you chose with the system folder picker, within the scope you granted.
Rotelo does not request precise GPS location, contacts, camera or microphone permissions.
7. Backup files and storage location
A backup is an unencrypted JSON file that contains your schedules, settings and all of your memos. Unlike share codes, where including memos is your choice, backups also contain memos and per-memo reminder settings. Share codes do not include reminder settings.
- Default location on Android 10 and later: the shared Documents/rotelo folder.
- Default location on Android 8 and 9: the Documents/rotelo folder inside the app's own storage; files there are deleted together with the app when it is uninstalled.
- Custom location: in Settings you can choose a folder on the device or at a cloud provider with the system folder picker. If you choose a cloud folder, the files may be transferred to or synchronised with that provider, and the provider's policies apply.
Regular backups automatically clean up older files so that recent versions are kept, but safety copies and similar files may remain. Not every backup is deleted after a fixed number of days. Please check the folder you chose and delete the files you no longer need.
8. Retention and deletion
Information you enter in the app is kept in local storage. Even after you edit or delete an item, its earlier contents may remain in the undo history or in backups. To erase all data inside the app, use Android Settings → Apps → Rotelo → Storage → Clear data, or uninstall the app. Menu names may differ by device.
Backups in a shared folder or in a folder you chose may remain after the app's data is cleared or the app is uninstalled. Delete them separately in a files app or at your cloud provider. The default app-private backups on Android 8 and 9 are deleted when the app is uninstalled. Codes copied into other apps, files saved elsewhere and copies kept by recipients also need to be managed separately.
Retention and deletion of information processed by the advertising and usage statistics services follow Google's policies and the related settings.
9. Your controls and security
You can view, edit and delete schedules and memos directly in the app. Notifications and app permissions are managed in Android settings. Ad-related choices are managed under Settings → Ad privacy settings where that menu is offered, sending usage statistics under Settings → Privacy → Send usage statistics, and the remaining choices through Google's and Android's privacy controls (such as resetting or deleting the advertising ID).
Please manage your device lock and access permissions, and check the contents before passing on codes or backup files that contain memos. No separate encryption is guaranteed for the app's local storage or for every exported file. Access to the backup folder and to sharing destinations depends on the device and service settings you chose.
10. Changes to this policy and this web page
When app features or the way information is processed change, this page is updated and the last-updated date changes. This page is an English translation of the Korean policy, which is updated at the same time.
This page itself is a static document that contains no external scripts, ads, analytics tools or cookies. The processing of access logs by the hosting service that serves the page may follow that service's policies.