Privacy Policy

Last updated: 8 April 2026

​

This Privacy Policy explains how CycleScreen handles information when you use the app, including when you enable location-based weather and when you choose to unlock “Live Weather” using ads or an in-app purchase.

​

1) Who we are and what this policy covers

CycleScreen is a mobile application published by RobbShift (“we”, “us”). This policy applies only to CycleScreen (the mobile app) and does not cover third-party websites or services you may access via links, ads, or external pages.

Google Play requires apps to provide a privacy policy and to disclose how user data is accessed, used, and shared, including when third-party SDKs are integrated. 

​

2) Data CycleScreen does and does not collect

No CycleScreen account is required. CycleScreen is designed without a CycleScreen-operated backend/server that collects your data.

We do not collect personal data on our own servers. In practical terms, we do not run analytics, profiles, or tracking systems on CycleScreen’s side that would allow us to identify you.

Data stored locally on your device (only):

• App preferences (for example: display settings).

• Your “Live Weather access” status (for example: whether it is currently active, and until when), to enforce the 24-hour access window after watching an ad or to remember your paid unlock.

You can remove most local app data by uninstalling the app (or by clearing the app’s storage via your device settings).

​

3) Location use for local weather

CycleScreen uses your location only to determine the local weather to display.

On Android, apps that use location services must request location permissions, and Android differentiates between approximate and precise location access. 
On Android 12+ in particular, users can control the location accuracy they grant (approximate vs. precise). 

How CycleScreen uses location (functional purpose only):

• When you enable location, CycleScreen uses it to obtain local weather conditions for your device’s area.

• CycleScreen does not use location for advertising profiling on our side.

Important note about external weather retrieval: displaying weather requires contacting weather data services over the internet. Even when CycleScreen does not collect your data, the service you contact from your phone necessarily receives network/technical information (for example, IP address) as part of providing a response.

​

4) Ads and rewarded access for Live Weather

CycleScreen offers an optional flow where you can watch ads to obtain 24 hours of Live Weather access.

CycleScreen uses Google AdMob to serve ads (including rewarded ads). Rewarded ads are specifically designed to let users view an ad in exchange for an in-app reward (here: temporary Live Weather access). 

​

5) Information processed by AdMob

Even if CycleScreen does not collect your data on its own servers, the Google Mobile Ads SDK can collect and share certain data automatically for advertising delivery, measurement, and fraud prevention. According to Google’s Play Data Disclosure documentation for the Mobile Ads SDK, this can include:

• IP address (may be used to estimate general location),

• user product interactions (such as app launch, taps, video views related to ad interactions),

• diagnostic information (performance/SDK diagnostics),

• device and account identifiers, including Android advertising ID and app set ID (and potentially other identifiers linked to signed-in accounts on the device, if applicable). 

Google’s documentation also states that data collected by the Google Mobile Ads SDK is encrypted in transit using TLS. 

​

6) Advertising ID controls

Google indicates that Android’s advertising ID can be reset or deleted by users in Android settings. 

If you reset or delete your advertising ID, ad-related behavior (including personalization) may change accordingly.

​

7) Paid option and payments

CycleScreen also offers an optional paid unlock priced at €0.99 (one-time purchase) as an alternative to watching ads to access Live Weather.

Purchases in a Google Play-distributed Android app are typically handled through Google Play’s billing system, and Google Play’s policy states that its billing system is required for in-app purchases of digital goods and services distributed on Google Play. 

​

8) Transaction-related information

For purchase operations, Google Play generates transaction identifiers (for example, order IDs) used for receipts and order management. 

In Play Console’s order management and refund tooling, Google documentation indicates orders can be searched by order ID or by the user’s full email address—meaning that, depending on the context and purchase type, the merchant/developer environment may display customer contact information for support/refund handling. 

CycleScreen does not ask you to enter payment card details inside the app’s own UI. Payments are handled through Google Play’s payment flow.

​

9) Consent, cookies, and similar technologies for ads

CycleScreen does not set “cookies” in a web-browser sense. However, advertising SDKs and mobile platforms may use device identifiers and local storage to support ads delivery, measurement, and fraud prevention.

For users in the European Economic Area, the United Kingdom, and Switzerland, Google’s requirements for AdMob publishers state that consent is needed (where legally required) for the use of cookies or other local storage and for the collection/sharing/use of personal data for ads personalization, and that a Google-certified CMP integrated with the IAB TCF is required for serving ads in those regions. 

Google also states that its User Messaging Platform (UMP) SDK is IAB-certified for TCF v2.2; and that if users do not consent for TCF Purpose 1, “Limited ads” serving applies. 
Google’s Limited ads documentation explains that Limited ads disable personalization and features that require a local identifier. 

Accordingly, where required, CycleScreen should present an in-app consent flow before requesting ads that rely on consent-dependent purposes.

​

10) Data retention, security, and international transfers

Retention

• Local app data: retained on your device until you uninstall the app or clear its storage.

• Ad-related data and purchase-related data: handled by the relevant third parties (for example, AdMob and Google Play) according to their own retention practices and policies.

Security

Google Play’s User Data policy emphasizes secure handling of personal and sensitive data, including using modern cryptography (for example, HTTPS) when transmitting such data. 
Separately, Google’s Mobile Ads SDK documentation indicates end-user data handled by the SDK is encrypted in transit using TLS. 

International transfers

If third-party partners process data outside your country/region, this can involve international transfers. Google describes mechanisms such as Standard Contractual Clauses (SCCs) as a safeguard used for certain cross-border data transfers. 
This may include transfers to countries such as the United States depending on service infrastructure and processing locations.

​

11) Your privacy rights and how to contact us

If you are in the EU/EEA (and similarly under other applicable laws), you may have rights such as the right to be informed, access, rectification, erasure, restriction, portability, objection, and rights related to automated decision-making. 

Because CycleScreen does not hold user personal data on its own servers, requests like “access” or “deletion” are generally achieved by controlling your device/app data (uninstalling the app or clearing storage) and by using platform controls (for example, resetting/deleting the advertising ID). 
For third-party processing (ads, billing), you may need to exercise rights directly with those providers under their processes.

Contact (Publisher / Developer):

• Email: robbshift@gmail.com

Changes to this policy: We may update this Privacy Policy to reflect app changes (for example, changes in ads configuration, consent flows, or legal requirements). We will update the “Last updated” date shown at the top of this document.