Privacy Policy

1. Scope of this policy

This policy applies to every product developed and published by the Developer, whatever the operating system, the device or the distribution channel:

• Mobile apps for iOS, iPadOS and Android, distributed through the App Store, Google Play or other authorized stores.
• Desktop apps for macOS, Windows and Linux, distributed through the App Store, the Microsoft Store, third-party platforms or direct download from valladares.org.
• Games for mobile, PC and browser, distributed through app stores, gaming platforms (such as Steam or itch.io) or direct download.
• Browser extensions for Chrome and compatible browsers.
• The valladares.org website and its subpages.

Some products may publish a product-specific privacy addendum on their store listing or on their page within this site (for example, when a feature requires an account or an online connection). In that case, the addendum prevails over this policy only as to what it expressly governs; in every other respect, this document applies.

2. General principle

The Service is built around data minimization: it collects as little information as possible, ideally nothing that could identify you. Contact form submissions are processed as described in section 8. When a product needs to save information in order to work, it does so locally on your device or, if you enable it, in a syncing service under your own account (iCloud, Google, Steam Cloud or an equivalent), which you control and to which the Developer has no access.

This principle is universal: it applies equally on an iPhone, an Android phone, a Windows PC, a Mac, a Linux machine or a game running in the browser.

3. Platform summary

As a general guide, and without prejudice to the detail in the sections below:

• iOS / iPadOS: data on the device; optional iCloud syncing; purchases and diagnostics handled by Apple.
• Android: data in the app's private storage; optional backup through Android Backup / Google Drive; purchases and diagnostics handled by Google.
• macOS: data in the user's application support folder; optional iCloud syncing where the app offers it.
• Windows / Linux: data in local user or configuration folders (for example, AppData or the user's configuration directory); no content is sent to the Developer.
• PC games on distribution platforms: saves and progress stored locally and, where the platform offers it and you enable it, in its cloud service; play statistics handled by the platform.
• Browser extensions: processing happens in your browser; your history and page content are never sent to the Developer.
• Web: informational site, no accounts; browsing statistics using Google Analytics.

4. Mobile apps (iOS/iPadOS and Android)

As a general rule, mobile apps require no sign-up, ask for no account and collect no personal data such as name, email, phone number or location, unless a specific feature expressly states otherwise within the app itself. Anything you enter (notes, amounts, calculations, preferences or settings) is stored only on your device and is not transmitted to the Developer.

• The Developer has no access to the data you enter or to your activity inside the apps.
• If an app uses system features (notifications, calendar, camera, etc.), it does so only with your permission and for the stated purpose, processing the information on your device.
• On iOS/iPadOS, data is stored in the app's private container (“sandbox”) and, if you enable it, in your iCloud. The app does not access the advertising identifier (IDFA) and does not track you across third-party apps and websites (App Tracking Transparency), unless the App Store listing expressly states otherwise.
• On Android, data is stored in the app's private storage and, where the system has it enabled, may be included in Android's automatic backup tied to your Google account. The app does not collect the advertising identifier (AAID) or persistent device identifiers for tracking purposes, unless expressly declared in the Google Play “Data safety” section.
• The privacy disclosure published on each store listing (App Store “App Privacy” and Google Play “Data safety”) is the official, up-to-date summary of what each individual app handles.

5. Desktop apps (macOS, Windows and Linux)

Desktop apps run locally on your computer and, unless their documentation says otherwise, work offline and without a user account. The files, projects, settings and output you create stay on your machine, under your control and in the operating system's standard locations.

• Files you open, edit or process with a desktop app are never uploaded to any server operated by the Developer; processing happens on your machine.
• Some desktop apps may occasionally check online whether a new version is available. That request transmits only the minimal technical data inherent to any web request (IP address, product version and operating system); it is not used to identify you and is not combined with any other information.
• If an app requires a license key or activation, it will be validated as described in its documentation; the Developer does not tie that key to a user profile or to your activity within the product.
• Apps that use the camera, microphone, screen or video devices (for example, virtual camera utilities) process the signal in real time and locally: they do not record, store or relay it to the Developer. What you do with that signal in other applications is outside our control.
• On Windows, configuration data typically lives in the user folder or in AppData; on macOS, in the application's container or support folder; on Linux, in the user's configuration directories. You can inspect or delete it at any time.

6. Games (mobile, PC and web)

Games store your progress, scores, settings and preferences locally on the device. In the browser, this information may be kept using the browser's own mechanisms (localStorage or similar), which you can clear from its settings.

• If a game offers cloud saves, leaderboards or achievements through a platform (Game Center, Google Play Games, Steam or another), that data is handled by said platform under its own policies and within your account, not on the Developer's servers.
• Casino-style or slot-machine games are social games with no real money: no financial data is processed and no betting activity is recorded, because no real-money wagering exists.
• If a game were to include online or multiplayer features, its listing or its specific addendum will detail what data is exchanged (for example, a nickname you choose) before you use them.
• Gaming platforms may record playtime, achievements and aggregated statistics under their own terms; the Developer only accesses the anonymous, aggregated reports those platforms make available.

7. Browser extensions

Extensions run inside your browser and operate only on the pages and permissions declared on their store listing. They do not collect your browsing history, your credentials or the content of the pages you visit, and they never send any of it to the Developer. Extension settings are stored in the browser's local storage or, if you have browser sync enabled, in your own account.

8. Website, cookies and analytics

The valladares.org website is primarily informational. It does not require you to create an account or provide personal data in order to browse it. If you choose to get in touch by email, you voluntarily share whatever information you include in your message, which will be used solely to answer your query and is not added to any database for commercial purposes.

The site uses Google Analytics 4 to measure visits, navigation, clicks to app stores and successfully submitted contact requests. Google Analytics uses cookies or identifiers to produce usage reports. Contact events include only the request category: we do not send your name, email, company or message to Analytics. A click to an app store does not mean an app was installed. You can block or delete cookies in your browser without affecting the essential site content.

Contact form and spam protection

Contact requests are managed at support.valladares.org. When you submit the form, you share your name, email, reason, related company or application, subject and message so we can handle your request. These details remain pending until you confirm your email through a link valid for 24 hours. Confirmation creates a ticket and, if one does not exist, a customer profile associated with your email, without an initial password. This information is not used for marketing subscriptions.

The portal uses necessary cookies to protect forms and, when you sign in, maintain your session. It includes a CAPTCHA generated and validated on the server, without sending the challenge to external providers. An identifier derived from your IP and request timestamps are stored to limit abuse. Temporary contact records older than two days are removed when a new valid submission is processed. Confirmed tickets are retained separately to manage the conversation.

Confirmations, replies and ticket changes are sent by email through the delivery provider. Messages remain in the portal and the mailboxes receiving notifications. You can request information or deletion by emailing diego@valladares.org. Do not include passwords or sensitive information.

9. Storage and syncing

The data generated by the products resides in your device's local storage. If you enable a syncing or backup feature, it uses your own account with the relevant provider — iCloud in the Apple ecosystem, Google backup on Android, the cloud save service of the relevant gaming platform — managed by that third party and under your control; the Developer has no access to that content.

When you uninstall an app, the associated local data is removed according to the operating system's behavior. On desktop, some uninstallers leave the user configuration folder behind: you can delete it manually if you want to erase every trace of the product.

10. System permissions

When a product needs a permission (camera, microphone, notifications, location, storage, calendar, screen recording, local network access or others), the operating system will ask you for it explicitly, and you can grant or revoke it at any time from your device settings. Each permission is used solely for the feature that justifies it, and the information is processed on the device. Denying a permission may disable the associated feature but does not prevent you from using the rest of the product, unless it is essential to its purpose.

11. Purchases and payments

If you make an optional purchase, the transaction is processed exclusively by the store or platform you obtained the product from — Apple (App Store), Google (Google Play), Microsoft (Microsoft Store), the relevant gaming platform or the payment processor indicated during checkout. The Developer does not receive, see or store payment data (card numbers, bank accounts or otherwise). Processing of that data is governed by the privacy policy of the respective store or processor, and refund policies are those of that channel.

12. Diagnostics, crashes and telemetry

The Developer embeds no trackers and no first-party telemetry that identifies you. Distribution platforms may, however, provide aggregated and anonymous information about performance, installs and crashes:

• Apple provides crash reports and usage metrics if you have agreed to share them with developers in your device settings.
• Google Play provides error reports (ANRs/crashes) and aggregated install and performance statistics.
• Gaming platforms and desktop stores may provide aggregated statistics on sales, sessions and hardware configurations.
• If a desktop product lets you send an error report manually, that submission is always voluntary and you will be able to review what it includes beforehand; nothing is sent automatically without your action.

In every case, this information reaches the Developer without identifying you and is used only to fix bugs and improve compatibility.

13. Advertising and profiling

The products display no third-party advertising and integrate no ad networks, and no profiling is performed for advertising purposes, nor any automated decision-making producing legal effects concerning you. Should any specific product incorporate advertising in the future, this will be stated expressly and in advance on its store listing, on its product page and in an addendum to this policy, before you install or update that product.

14. Third-party services

The Service relies on providers that operate under their own privacy policies: chiefly Apple (distribution, purchases, iCloud, Game Center), Google (Google Play distribution, site analytics, Android backup), Microsoft, and the gaming distribution platforms and the site's hosting provider. The Developer neither controls those platforms nor the processing they carry out independently. We recommend reviewing their respective policies.

15. No sale of data

The Developer does not sell, rent or trade personal information to third parties, and does not build profiles for advertising purposes from identifiable data. There is no exchange of personal data with advertisers or with data brokers.

16. Children

The Service is not directed at collecting data from children and does not knowingly request personal information from them. Apps or games with an age rating (App Store, Google Play, PEGI, ESRB or whichever rating applies on each platform) must be used in accordance with that rating and under the supervision of parents or guardians where appropriate. We encourage parents and guardians to use the parental controls and purchase restrictions offered by operating systems and distribution platforms. If you believe a child has inadvertently provided data, please contact us so we can address it.

17. Security

By keeping data on your device rather than on our own servers, the exposure surface is significantly reduced. Products are distributed signed and verified through the relevant official channels; always download from official stores or from valladares.org, since copies hosted elsewhere may be altered or contain malicious software unrelated to the Developer. Even so, no system is completely secure; you are responsible for protecting your device, your accounts and your credentials, and for keeping your operating system up to date. The Developer is not liable for unauthorized access resulting from the loss or compromise of your device or your accounts.

18. Retention and deletion

As a rule we retain no data about you, because we never receive it: the information lives on your device and you decide how long it stays there. You can delete it by clearing the content inside the product, uninstalling it, removing its configuration folder on desktop, or deleting the cloud copy from your provider account. Emails you send us are kept only for as long as needed to handle your query and any reasonable follow-up. The site's technical logs and the platforms' aggregated statistics are retained according to each provider's periods.

19. Your rights

Under the data protection rules applicable in Chile (including Law No. 19,628 and, once in force, Law No. 21,719), you may exercise the rights of access, rectification, erasure, objection and portability in respect of any personal data that might be processed. If you are in the European Union, the United Kingdom or another jurisdiction with equivalent legislation, you may exercise the rights that legislation grants you on comparable terms.

Since the Developer generally stores none of your data, you exercise most of these rights directly on your device (by editing or deleting the content) or with Apple, Google, Microsoft or the distribution platform in respect of the data they hold under your account. For any question, write to us at the contact address.

20. International transfers

The technology providers involved (Apple, Google, Microsoft, distribution platforms and the site's hosting provider) may process information on servers located outside Chile, in accordance with their own policies and safeguards. By using the Service, you accept that such processing may take place under the conditions established by those third parties.

21. Changes to this policy

This policy may be updated to reflect new products, new platforms or regulatory changes. The version in force is the one published on this page, bearing its update date. Where a change is material — for example, if a product were to start requiring an account, an online connection or advertising — it will be highlighted. We recommend reviewing it periodically.