Privacy Policy

Applicable version: Rucoy Calculator 0.6.0 (build 10)
Android package: com.apollo.rucoy_calculator
Effective date: July 17, 2026
Last updated: July 17, 2026

Version-specific scope. This Privacy Policy is valid only for Rucoy Calculator version 0.6.0 (build 10). It does not automatically apply to earlier versions, later versions, modified builds, forks, unofficial distributions, websites, or other products. A different version may use different features, permissions, software development kits, data practices, or privacy notices.

1. Who We Are

Rucoy Calculator is an independent calculator and reference application developed by Apollo Daniel (“Developer,” “we,” “us,” or “our”).

For privacy questions or requests, contact:

• Email: developer.apollo.mail@gmail.com

For purposes of applicable privacy laws, including Brazil’s Lei Geral de Proteção de Dados Pessoais (“LGPD”), the Developer is responsible for decisions concerning the limited data processing performed directly by this version of the App. Third-party services identified in this Policy may separately determine how they process data under their own terms and privacy policies.

2. About the App

Rucoy Calculator provides calculators and informational tools related to levels, skills, experience, training, weapons, monsters, potions, and other gameplay-related values associated with Rucoy Online.

The App is an independent, unofficial fan-made tool. It is not operated, sponsored, endorsed, or approved by Rucoy Online or its respective rights holders.

3. Summary of Version 0.6.0 Data Practices

In version 0.6.0:

• The App does not require a user account.
• The App does not provide a Developer-operated cloud account or synchronization service.
• Calculator inputs are generally processed on the device.
• Saved calculator templates and preferences are stored locally on the device.
• The App uses Google Mobile Ads and Google’s User Messaging Platform (“UMP”) for advertising and privacy choices.
• The App asks users to select an age range, rather than provide an exact date of birth, to configure advertising protections.
• The App checks Google Play for available updates.
• The App can open third-party websites and applications for donations, community links, social media, the game listing, and updates.
• The App does not intentionally request access to the camera, microphone, contacts, SMS messages, call logs, or precise GPS location.
• The App writes a Pix code or Pix key to the clipboard only when the user taps the corresponding copy button. It does not intentionally read clipboard contents.

The Google Mobile Ads SDK may process information such as IP address, approximate location inferred from IP, app interactions, diagnostic information, and device or advertising identifiers, as described in Section 7.

4. Information Processed Directly by the App

4.1 Age-range selection

The App asks the user to select one of the following technical age categories:

• Under 13;
• 13 to 17; or
• 18 or older.

The App does not ask for an exact birth date. The selected category is stored locally under an application preference and is used to configure Google advertising settings.

The categories are used as technical advertising and safety settings. They are not intended to determine a person’s legal age, contractual capacity, or status under every country’s laws.

Version 0.6.0 applies the following safeguards:

• Users under 13 are treated as children for Google advertising configuration.
• Users aged 13 to 17 are treated as under the age of consent for Google advertising configuration.
• Both under-18 categories receive non-personalized advertising and a maximum G ad content rating.
• Personalized advertising is not enabled for under-18 users.
• Changing the selected age range blocks existing ad requests, resets the prior Google UMP consent state, and starts the privacy flow again.

A parent or legal guardian should select or confirm the age range when required by applicable law.

4.2 App language and device locale

The App may process:

• The language selected by the user;
• The device’s system language and locale;
• A country or region code derived from the device locale.

The selected language is stored locally. The country or region code derived from the locale is used in memory to help apply advertising privacy settings. The App does not use this locale-derived value as precise geolocation.

4.3 Calculator templates and preferences

Users may create and save local calculator templates. Depending on what the user enters, a template may contain:

• Template name;
• Character level;
• Skill value;
• Buff or debuff value;
• Number of monsters;
• Character class;
• Attack type;
• Selected weapon; and
• Default-template preference.

These values are gameplay inputs, not account credentials. They are stored locally using the device’s application preferences. The Developer does not receive these templates through a Developer-operated server in version 0.6.0.

Users should not place real names, passwords, financial information, private messages, or other sensitive personal information in template names or calculator fields.

4.4 Onboarding and interface preferences

The App stores limited local flags and preferences, including:

• Whether first-time setup was completed;
• Whether an experimental or AI-assisted translation warning was already shown for a language;
• The selected language;
• The selected default template; and
• Other settings necessary to restore the user’s chosen App configuration.

4.5 Calculator inputs not saved as templates

Calculator values entered during ordinary use are processed on the device to generate results. Unless the user saves them in a template or a specific preference, version 0.6.0 does not intentionally transmit those values to a Developer-operated server.

4.6 Clipboard use

When the user chooses to copy a Pix key or Pix payment code, the App writes that selected value to the system clipboard. Version 0.6.0 does not intentionally inspect or read unrelated clipboard contents.

The operating system and other applications may be able to access clipboard contents according to their own permissions and platform behavior. Users should clear the clipboard after use if they consider the copied value sensitive.

5. Information We Do Not Directly Request

Version 0.6.0 does not intentionally ask users to provide:

• Name;
• Email address inside the App;
• Password;
• Rucoy Online account credentials;
• Exact date of birth;
• Government identification number;
• Home address;
• Contact list;
• Photos or media library;
• Camera or microphone recordings;
• SMS or call-log data;
• Precise GPS location; or
• Credit-card, debit-card, or online-banking credentials.

This does not mean that third-party services opened by the user or integrated for advertising process no personal data. Their practices are described below and governed by their own privacy notices.

6. Local Storage and Device Security

The App stores preferences and templates in standard application storage on the user’s device. This local storage is intended for ordinary App settings and gameplay values and should not be treated as a secure vault for confidential information.

The Android application configuration for version 0.6.0 disables ordinary Android application backup through android:allowBackup="false". However, no device or software can be guaranteed completely secure.

Local App data normally remains until one of the following occurs:

• The user deletes a template or changes a setting;
• The user clears the App’s storage through Android settings;
• The user uninstalls the App;
• The operating system removes the data; or
• A later App version changes the storage format or retention behavior.

7. Advertising, Google Mobile Ads, and Google UMP

7.1 Advertising services used

Version 0.6.0 integrates:

• Google Mobile Ads SDK / Google AdMob for banner and interstitial advertisements; and
• Google User Messaging Platform (UMP) for consent messages and privacy choices.

The App displays a banner ad when ads are permitted. It may also attempt to display one interstitial ad per App session when the user chooses to calculate again, provided an ad is loaded and the applicable consent state permits the request.

7.2 Data that Google Mobile Ads may process

According to Google’s disclosure for the Google Mobile Ads SDK, the SDK may automatically collect and share data for advertising, analytics, and fraud-prevention purposes, including:

• IP address, which may be used to estimate general or approximate location;
• User interactions with the App or advertisements, such as App launches, taps, and video views;
• Diagnostic and performance information, such as launch time, hang rate, and energy usage; and
• Device or account identifiers, such as the Android advertising ID, App Set ID, and other applicable identifiers.

The exact data processed can depend on the device, Android version, Google services, consent choices, advertising configuration, region, and changes made by Google. Google states that data collected by its Mobile Ads SDK is encrypted in transit using TLS.

Google may use advertising partners or other recipients within its advertising ecosystem. Their involvement and processing are controlled by Google’s systems, the advertising configuration, applicable law, and the user’s privacy choices.

7.3 Consent and personalized advertising

Version 0.6.0 requests updated consent information through Google UMP before allowing advertising requests.

Personalized advertising is allowed by the App only when:

• Google UMP indicates that ads may be requested;
• The user is in the 18-or-older category;
• The applicable consent signals permit personalized advertising; and
• Restricted-data-processing signals do not require a more limited mode.

When personalized advertising is not permitted but ads may still be requested, the App requests non-personalized advertisements. In certain United States privacy regions, the App applies restricted data processing or limited-data-use behavior when indicated by the available privacy signals.

If a required consent flow cannot establish that ads may be requested, the App blocks its advertising requests until an eligible state is available.

7.4 Privacy options

For eligible adult users and regions where Google indicates that a privacy-options entry point is required, version 0.6.0 displays a privacy settings option inside the App’s settings. That option opens Google’s UMP privacy form and re-evaluates ad requests after the form is closed.

Under-18 users do not receive personalized ads through the App and do not receive the adult UMP privacy-options entry point in version 0.6.0.

Users may also be able to reset or delete the Android advertising ID through Android’s privacy or ads settings, depending on the device and Android version.

7.5 Google policies

Google’s handling of data is governed by Google’s own notices, including:

• Google Privacy Policy: https://policies.google.com/privacy
• Google advertising technologies: https://policies.google.com/technologies/ads

The Developer does not control Google’s independent retention periods, advertising profiles, security systems, or responses to requests concerning data held directly by Google.

8. Google Play Update Check

After first-time setup and the consent flow, version 0.6.0 may contact Google Play to compare the installed App version with the version available in the store.

This process may disclose ordinary network and technical information to Google, such as:

• IP address;
• App package identifier;
• Installed or requested version information;
• Device and network metadata ordinarily included in a connection to Google Play.

The Developer does not use this check to create a user profile. Google processes the request according to its own terms and privacy policy.

9. Donations and Payment Providers

The App offers optional donation methods. Donations are voluntary and are not required to use the calculators.

9.1 Pix

For users viewing the Portuguese interface, the App can generate a static Pix QR code and copy-and-paste code locally using a fixed Pix key.

The App itself does not ask for or receive the user’s banking password, card number, or bank-account credentials. The transaction is completed in the user’s banking or payment application.

The payment institution and the recipient’s financial institution may process transaction data. The recipient may receive transaction-related information made available by the payment system, such as the amount, transaction identifier, payer identification, or other details required to complete and document the payment.

9.2 Ko-fi, Patreon, and PayPal

Buttons for Ko-fi, Patreon, and PayPal open services operated by those providers. Those providers may collect account, payment, device, fraud-prevention, tax, and transaction information under their own terms and privacy policies.

The Developer does not receive the user’s full card or banking credentials through the App. The Developer may receive donation-related information that the selected provider makes available to a recipient or creator.

Users should review the applicable provider’s privacy notice before completing a transaction.

10. External Links and Third-Party Services

Version 0.6.0 can open external links, including links to:

• Google Play;
• Rucoy Online’s store listing;
• GitHub;
• WhatsApp;
• Discord;
• YouTube;
• Ko-fi;
• Patreon;
• PayPal; and
• The published privacy-policy page.

These destinations are not controlled by the App. When the user opens them, the destination, browser, operating system, or external application may process IP address, device information, account information, cookies, identifiers, referrer information, and user interactions under its own rules.

This Privacy Policy does not govern third-party websites, applications, payment services, social networks, advertising networks, or the Rucoy Online service.

11. Purposes and Legal Bases

Depending on the user’s location and applicable law, version 0.6.0 processes data for the following purposes and legal bases:

Where processing relies on consent, the user may refuse or withdraw consent. Refusing personalized-ad consent does not remove the core calculator functions, although it may result in non-personalized ads or no ad request, depending on Google’s eligibility decision and applicable law.

12. Children and Teenagers

The App may be used by different age groups and therefore requests a neutral age-range selection for advertising configuration.

Version 0.6.0 is designed so that:

• It does not request a child’s real name, email address, exact birth date, game credentials, or direct contact information;
• Under-18 users do not receive personalized ads through the App;
• Under-13 users receive child-directed advertising treatment;
• Users aged 13 to 17 receive under-age-of-consent advertising treatment; and
• Under-18 ad content is limited to a G rating in the App’s Google Mobile Ads request configuration.

A parent or guardian should supervise use by a minor and should make or verify the age selection when required. The App should not be used by a child in a way that conflicts with applicable law, parental instructions, Google Play rules, or the terms of any linked service.

The Developer does not knowingly maintain a Developer-operated database of children’s direct identifiers in version 0.6.0. If a parent or guardian believes that a child sent personal information to the Developer by email or another external channel, they may request deletion by contacting the email listed in Section 1.

13. Sharing and Disclosure

The App or Developer may disclose or enable processing of information in the following circumstances:

1. Google advertising and consent services. As described in Section 7.
2. Google Play. For update checking and store-related functions.
3. Payment and donation providers. Only when the user chooses to use those services.
4. External applications and websites. When the user chooses to open an external link.
5. Legal compliance and protection. When reasonably necessary to comply with law, lawful requests, court orders, protect rights or safety, investigate abuse, or defend legal claims.
6. Business or project transfer. If responsibility for the App is transferred, relevant records may be transferred subject to applicable law and an appropriate notice. Version 0.6.0 does not maintain a user-account database to transfer.

The Developer does not directly sell a user-account database because version 0.6.0 has no user accounts or Developer-operated user-profile database. Advertising-related processing by Google may be considered “sharing,” “targeted advertising,” or a similar regulated activity under certain jurisdictions. Eligible users should use the UMP privacy options and device advertising controls described in this Policy.

14. International Data Transfers

The App is developed in Brazil. Google, payment providers, social networks, and other linked services may process data in Brazil, the United States, the European Economic Area, or other countries where they or their service providers operate.

Those countries may have different data-protection rules. Transfers performed by third parties are governed by their own legal mechanisms, contracts, and privacy notices.

15. Retention

15.1 Local App data

Age range, language, templates, default-template choices, and onboarding flags are retained locally until deleted, changed, cleared with App storage, removed by the operating system, or removed through uninstallation.

15.2 Advertising and consent data

Google controls retention of data processed through Google Mobile Ads and UMP. Retention may depend on consent, advertising settings, legal requirements, account settings, fraud-prevention needs, and Google’s policies.

15.3 Donation data

Banks and payment providers retain transaction data according to their own policies and legal obligations. The Developer may retain donation records received from those providers when necessary for accounting, tax, fraud prevention, legal compliance, or the exercise of rights.

15.4 Support communications

If a user contacts the Developer by email or another external channel, the Developer may retain the communication for as long as reasonably necessary to answer the request, maintain support records, prevent abuse, comply with law, or defend rights.

16. Security

The Developer uses reasonable measures appropriate to the limited nature of the App, including:

• Processing calculator values locally;
• Avoiding a Developer-operated user-account database in version 0.6.0;
• Disabling ordinary Android application backup in the App manifest;
• Using Google’s official consent and advertising interfaces;
• Blocking ad requests when the App does not have an eligible consent state; and
• Relying on encrypted network transport provided by third-party services where supported.

No storage or transmission method is completely secure. Users are responsible for maintaining device security, installing the App from a trusted source, keeping Android updated, and avoiding sensitive information in template names or calculator fields.

17. User Privacy Rights

Depending on applicable law, including the LGPD, a user may have rights to:

• Confirm whether personal data is processed;
• Access personal data;
• Correct incomplete, inaccurate, or outdated data;
• Request anonymization, blocking, or deletion of unnecessary, excessive, or unlawfully processed data;
• Request deletion of data processed on the basis of consent, subject to legal exceptions;
• Obtain information about sharing;
• Obtain information about the consequences of refusing consent;
• Revoke consent;
• Object to unlawful processing;
• Request portability where applicable and technically feasible; and
• Request review of certain automated decisions where applicable.

Because version 0.6.0 keeps most App preferences locally and does not have a user account, many rights can be exercised directly:

• Change the language or age range in App settings;
• Delete individual templates;
• Clear the App’s storage in Android settings;
• Uninstall the App;
• Use the in-App UMP privacy-options form when it is displayed;
• Reset or delete the Android advertising ID through Android settings, where available; or
• Contact Google or another third party concerning data that it controls.

To submit a request to the Developer, email developer.apollo.mail@gmail.com with enough information to understand the request. Do not send passwords, banking credentials, government identifiers, or unnecessary sensitive information.

The Developer may need to verify the requester’s identity when required to prevent unauthorized access or deletion. Because the App has no account system, the Developer may be unable to identify or retrieve data stored only on the user’s own device.

Brazilian users may also contact the Autoridade Nacional de Proteção de Dados (“ANPD”) where legally available, particularly after first attempting to resolve the matter with the controller.

18. Automated Processing and Advertising Profiles

The App itself performs mathematical calculations based on user inputs and does not make decisions that produce legal or similarly significant effects.

When an eligible adult consents to personalized advertising, Google and its advertising ecosystem may use automated systems and profiles to select, measure, limit, or personalize ads. Users may refuse or withdraw eligible advertising consent through the available privacy controls.

19. Do Not Track and Global Privacy Controls

Mobile applications do not consistently receive browser “Do Not Track” signals. Version 0.6.0 does not implement a separate browser Do Not Track mechanism.

Where Google UMP or platform privacy signals provide an applicable opt-out or restricted-processing indication, version 0.6.0 uses those signals to request non-personalized advertising, restricted data processing, or limited data use as described in Section 7.

20. Changes and Version Limitation

This Policy describes only the code and integrations reviewed for version 0.6.0 (build 10).

It will not automatically govern:

• Version 0.5.0 or earlier;
• Version 0.6.1 or later;
• Development or debug builds;
• Modified APKs or bundles;
• Forks or third-party builds;
• A web version of the calculator;
• Other applications by the Developer; or
• Third-party services linked from the App.

A later App version may publish a separate policy with a different effective date. Users should review the policy presented with the exact version they install or use.

Third-party services may change their practices independently, even while the user remains on version 0.6.0. Their current privacy notices control their processing.

21. Contact

Questions, complaints, or privacy requests concerning Rucoy Calculator version 0.6.0 may be sent to:

Apollo Daniel
Email: developer.apollo.mail@gmail.com

When contacting the Developer, identify that the request concerns Rucoy Calculator version 0.6.0 (build 10).