GyoDal Privacy Policy

Effective Date: August 24, 2026

Information entered into the App is stored on the user's device by default. Information leaves the device only when the user explicitly uses features such as cloud backup or sharing, or when third-party services process the limited information described in this policy.

This Privacy Policy explains what information the App processes, why it is processed, which third-party services are involved, and what choices are available to users.

1. Information Stored on Your Device

The following information is stored only on your device — and, when you turn cloud backup on, in your own cloud account — and is never sent to the developer or to any third-party server without your permission:

• Shift patterns, presets, team configurations, shift schedules, and attendance records
• Per-day notes and personal events
• Anniversaries and display settings, including themes, colours, language, lunar-calendar display, and widget configuration
• The e-mail address of the Google account linked for cloud backup, stored locally for display purposes

The database containing this information is encrypted using a key protected by the device keystore. Uninstalling the App deletes the data stored locally by the App.

2. Permissions Requested by the App

The App directly requests only the following two runtime permissions:

The App does not request general access to your photos or files. Loading a QR image, opening a backup file, and exporting an image or PDF are handled through the system picker or save dialog provided by the operating system. The App receives access only to the specific file selected by the user and cannot browse the user's entire photo library or file storage.

Internet access, network-state access, and vibration are normal permissions granted by the operating system. They are used for public-holiday lookups, advertising, purchase verification, cloud backup, sharing features, and haptic feedback.

3. Third-Party Services

3.1 RevenueCat — Purchases and Subscriptions

RevenueCat, Inc. is a third-party platform that helps app developers verify and manage in-app purchases and subscriptions made through the app stores. Purchases and subscription status in this App are handled through its service.

• Data processed: purchase history, including product, purchase and expiry times, renewal status, and refunds; store-issued transaction identifiers; and basic device or App information such as platform, App version, and country
• Because the App has no account system, RevenueCat uses an automatically generated anonymous identifier. The App does not send the user's name, e-mail address, or other identity information to RevenueCat.
• The App does not enable RevenueCat's device-identifier collection option and does not send an advertising identifier to RevenueCat.
• The App passes the randomly generated Firebase app-instance identifier described in section 3.3 to RevenueCat as a subscriber attribute, so that purchase events reported by RevenueCat's servers can be attributed to the same analytics record. This identifier belongs to an App installation and does not identify a person, a device, or a Google account.
• Payments are processed by Google Play or the Apple App Store. Neither the App nor RevenueCat receives card numbers or other payment-instrument details.
• RevenueCat Privacy Policy: https://www.revenuecat.com/privacy

3.2 Google AdMob — Advertising

Advertisements may be shown to users of the free version of the App.

• Data processed: advertising identifiers, including the Advertising ID; IP address, which may be used to estimate an approximate location; advertising and App interaction data; and diagnostic information
• Purposes: serving and measuring advertisements, analytics, and fraud prevention
• In the European Economic Area, the United Kingdom, and other regions where consent is required, the user's choices are collected through Google's User Messaging Platform consent form. The form can be reopened under Settings › Add-ons › Ad Privacy Options.
• If the user has purchased ad removal or has an active Premium subscription, the advertising SDK is not initialised and the advertising data described above is not collected through the App.
• Google advertising policies: https://policies.google.com/technologies/partner-sites

3.3 Firebase — Usage Analytics and Crash Diagnostics

Firebase is Google's platform for app analytics and error diagnostics. The App uses two of its services, Firebase Analytics and Firebase Crashlytics, primarily to diagnose and fix abnormal behaviour such as crashes and app-not-responding (ANR) errors, and to measure basic usage as well as purchase and advertising performance.

• Purposes: diagnosing and improving abnormal behaviour such as crashes and ANRs; improving the App through basic usage figures such as which screens are opened; and measuring purchase and advertising performance.
• Content entered by the user — company or team names, preset names, shifts, schedules, notes, and anniversaries — is never included in any of these records.
• Information processed automatically by these SDKs: a randomly generated App-installation identifier, App version, device model, operating-system version, language and country settings, and an IP address that may be used to estimate an approximate region, together with records of which screens were opened and of completed in-app purchases. Crashlytics additionally processes crash and error diagnostics such as stack traces, the state of the App at the time of the crash, and a Crashlytics installation identifier.
• Analytics storage, ad storage, ad user data and ad personalisation may be granted.
• In the European Economic Area, the United Kingdom, and other regions where consent is required, analytics storage stays disabled until the user completes the consent form described in section 3.2. The choice can be revisited at any time under Settings › Add-ons › Ad Privacy Options.
• Crash diagnostics are collected only in published release versions of the App.
• Firebase privacy information: https://firebase.google.com/support/privacy
  Google Privacy Policy: https://policies.google.com/privacy

3.4 Google Account and Google Drive — Optional Cloud Backup

Google account sign-in and Google Drive access are used only when the user voluntarily enables cloud backup.

• Sign-in is handled by the operating system's credential manager. The App receives identification information for the account the user selects, including its e-mail address, and consent for the Drive permission scope below is obtained at the same time.
• Backup files are stored in the user's own Google Drive account. The developer cannot access those files.
• The App uses only the drive.file permission scope. This limited scope allows access only to files created by the App and does not allow the App to browse the user's existing Drive files.
• Backup contents are encrypted on the device before being uploaded.
• The e-mail address of the linked Google account is stored only on the device so that it can be displayed in the App.
• The account can be disconnected and backup files can be deleted at any time through the App's cloud-backup settings or the user's Google account and Drive settings.

3.5 Public Holidays — Bundled Data and the Google Calendar API

Public holidays are shown primarily from the calendrical dataset bundled with the App (Thereki Almanac), which requires no network access. The Google Calendar API is used only as a supplementary lookup, to pick up holidays that have been newly designated or changed.

Such a lookup contains only the selected country and date range. It does not contain the user's personal information or calendar-event contents.

3.6 Google Play — In-App Review

The App may display the review dialog provided by Google Play. That dialog, and any rating or comment submitted through it, is handled entirely by Google Play. The App is not told whether a review was written or what it said, and it sends no user information to Google Play for this purpose.

3.7 Share-Link Hosting — gyodalshare.web.app

If the user shares a shift schedule or preset as a link, ordinary web access logs such as an IP address, access time, and requested address may be recorded by the hosting service when the recipient opens that link.

The shift or schedule contents carried by a share link are encrypted. However, anyone who possesses the link may be able to open and import its contents in the App. Users should therefore share links only with intended recipients and protect them from unauthorised access.

4. Retention and Deletion

• On-device data: deleted when the App is uninstalled. Individual deletion and data-reset functions are also available in the App.
• Cloud backup files: retained in the user's Google Drive until the user deletes them.
• Purchase records: retained by RevenueCat and the applicable app store for as long as necessary to provide the service and comply with transaction record-keeping obligations.
• Advertising, analytics, and crash-diagnostic data: retained according to Google's applicable retention policies and settings.

5. Your Rights and Choices

• Advertising and analytics consent: where consent is required, revisit the consent choice under Settings › Add-ons › Ad Privacy Options. The advertising ID can also be reset or deleted in the device settings.
• Permission withdrawal: revoke camera or calendar access at any time through the device settings.
• Cloud disconnection: disconnect the linked Google account and delete backup files through the App settings or Google Drive.
• Subscription management: manage or cancel subscriptions through Google Play or the Apple App Store.
• Deletion requests: contact the developer using the address below to request deletion of purchase-related records or of analytics records associated with your App installation. Transaction records retained by an app store remain subject to that store's policies and legal obligations.

6. Children's Privacy

The App is not directed to children under the age of 14 and does not knowingly collect personal information from children.

7. Security Measures

The App applies the following measures to protect information:

• Encryption of the on-device database, with encryption keys protected by the operating-system keystore
• Password-based encryption of backup files
• TLS encryption for external network communications

No method of storage or transmission can provide absolute security. Users are responsible for protecting their devices, Google accounts, backup passwords, and sharing links from unauthorised access.

8. Changes to This Privacy Policy

This Privacy Policy may be revised when applicable laws, App features, data-processing practices, or third-party service providers change. The updated contents and effective date will be posted on this page.

9. Contact

For questions, requests, or concerns regarding this Privacy Policy or the App's processing of information, please contact: