LEGAL · MAREA
Marea Privacy Policy
Marea Timer: Visual Countdown · Last updated: 1 November 2026
Marea is a visual timer for Android. You do not need to create an account. Timer titles, durations and preferences are stored on your device and are not sent to CYBERACE LTD or included in advertising requests.
This policy distinguishes the ad-free timer from versions that include advertising services. Currently, release version 1.3.1 does not include advertising or purchases; development versions include an optional Google AdMob test. Test ads may also transmit data to Google. The advertising sections apply when you use that integration.
1. Who is responsible
The controller responsible for Marea is CYBERACE LTD, whose registered address is Digeni Akrita 54, Office 303, 1061, Nicosia, Cyprus, and whose tax identification number is CY60116122N.
For privacy enquiries and support: support@cyberace.tech. Website: cyberace.tech.
2. Data stored on your device
Marea stores the timer duration and title, custom durations and colours, visual style, language, theme, and sound, vibration and screen preferences. It also saves the state of the active session so it can be restored when you return to the app, including pauses and overtime.
This data enables us to provide the service you request and remember your preferences. We do not maintain a remote session history or have remote access to this data. Automatic backups and transfers of Marea data are disabled in the app’s Android configuration.
3. Advertising and Google services
Versions with advertising integration use Google AdMob and Google User Messaging Platform (UMP) for consent management. The banner appears on the timer setup screen; it is not shown during the countdown, pauses or overtime.
When you use these services, Google may collect and share your IP address, approximate location derived from it, interactions with the app and ads, diagnostics, and device or account identifiers where applicable, including the Android advertising ID. These are used to serve and measure advertising, analyse service performance and prevent fraud. The availability of identifiers also depends on the device, its settings and the applicable configuration.
The advertising SDK transmits its data encrypted using TLS. It may use local storage and identifiers to perform its functions. Testing ads is not equivalent to an anonymous connection or a simulation without data transmission.
Google and participating advertising providers receive data in accordance with the applicable configuration and privacy choices. You can review the providers and their purposes in the consent message. See also Google’s privacy policy, how Google uses data from apps that use its services and information about SDK data.
4. Your advertising choices
In regions where applicable, the privacy form allows you to give or refuse consent, or manage choices by purpose and provider. Personalised advertising and access to storage or identifiers that require consent are based on your consent. When a provider relies on legitimate interests for a permitted purpose, the form explains this and allows you to manage your objection.
Refusing consent does not prevent you from using the timer. Nor does it necessarily mean that no ads can be shown: depending on the applicable choices and requirements, limited ads may be shown or no advertising may appear. A non-personalised ad does not, in itself, mean that no data is processed.
When required by the form, the integration provides access to privacy options so you can review your choices and withdraw consent. In the development version, this access is available in the advertising test controls on the setup screen. Withdrawing consent does not affect the lawfulness of earlier processing.
During development testing, you must explicitly start the test. A banner is only requested if UMP permits ad requests. “Stop test” removes the banner, but does not withdraw consent or delete data already received by Google. You can also manage the advertising ID in Android’s privacy settings, depending on the system version.
5. Statistics and purchases
Marea does not include Firebase Analytics, Google Analytics or a service of its own that records your countdowns. This does not exclude the advertising SDK measurements and diagnostics described above.
Where distribution and data volume allow, CYBERACE LTD may consult Google Play Console, Android vitals and AdMob reports on installations, stability and advertising. These reports come from Google’s services; Marea does not send them the titles or content of your timers.
There are currently no active charges or subscriptions. The menu presenting the option to remove ads is a preview. Before purchases are enabled, this policy will be updated to describe the relevant processing.
6. Android permissions
Notifications, alarms, sound and vibration allow the app to alert you when time runs out. You can manage their permissions in Android. Denying notifications does not prevent you from using the visual timer, although background alerts may be affected.
Marea does not request access to contacts, the camera, microphone, precise location or personal files. Versions with advertising require Internet access and access to network state. Their SDKs may declare permissions for the advertising ID and basic phone-state data, such as network type; these are not permissions to read your messages or contacts. The version without the advertising SDK does not declare Internet access.
7. Support and legal bases for processing
If you contact support, we receive your email address and the information you choose to send. The app opens your email application without automatically attaching timer titles, files or usage logs.
We use this information to handle your request. The legal basis is the provision of the service when the enquiry relates to it, and our legitimate interest in responding to other enquiries and maintaining service security. We may also retain information necessary to comply with legal obligations. We do not use support messages to send you advertising.
8. Retention and deletion
Local timer data is retained until you change or delete it. You can use “Clear local data” in Marea’s settings, clear the app’s data in Android or uninstall it. Clearing timer settings does not delete consent preferences stored by the SDKs. There is no Marea account whose deletion you need to request.
We retain support correspondence for as long as necessary to resolve the enquiry and meet applicable responsibilities or legal obligations. You can request its deletion; if there is a legal reason to retain part of it, we will explain this to you.
Google services apply their own retention periods depending on the data and purpose, as described in their retention information. Deleting Marea or its local data does not automatically delete information already sent to Google or other providers. You can exercise your rights with those controllers and ask us for help identifying the appropriate channel.
9. Recipients and international transfers
In addition to the advertising providers described above, providers that enable us to manage our email and support may process communications to deliver those services. We may disclose information to authorities when legally required. We do not sell local timer titles, preferences or sessions.
Google may process data outside the European Economic Area. It explains the safeguards it uses, including adequacy decisions and standard contractual clauses where applicable, in its international data transfer frameworks. Other providers explain their practices in the policies linked from the privacy form.
10. Your rights
Where applicable, you can request access to, rectification, erasure, restriction of processing and portability of your data, object to processing and withdraw your consent. Write to support@cyberace.tech. We may request the minimum information necessary to verify your request. Data stored only on your device is deleted using local controls, because we do not have a remote copy.
You can lodge a complaint with the data protection authority where you live or with the Office of the Commissioner for Personal Data Protection in Cyprus. CYBERACE LTD does not make decisions about you based solely on automated processing that have legal or similarly significant effects. Advertising personalisation, if authorised, may use interest profiles in accordance with the providers’ practices.
11. Children
Marea does not request dates of birth or create its own profiles of children. If a child needs authorisation from their legal representative to consent to processing, they must have it. The timer can be used without activating the advertising test. If you believe a child has improperly provided us with personal data, contact support so we can review it.
12. This page and changes to the policy
When you open external links, the browser and destination website may process technical data necessary for the visit. This policy describes Marea; browsing cyberace.tech is also subject to that website’s privacy information. Marea does not add timer titles or sessions to links.
We will update this policy when the processing described changes, indicating the revision date and requesting new choices where appropriate. The public reference URL is https://cyberace.tech/marea-privacy.
CYBERACE LTD · support@cyberace.tech