1. Overview
This policy applies to mobile applications for Android, iOS, and other supported platforms that identify Rintronic or Inversiones Rintronic C.A. as the developer or publisher and link to this page. Each app may provide an app-specific notice below or inside the app. If an app-specific notice differs from this general policy, the more specific notice controls for that app.
2. App-specific privacy notices
Petals Logic
Petals Logic is an offline casual logic game published by Inversiones Rintronic C.A. The current version does not require an account and does not collect, transmit, sell, or share personal information. It does not use personal information for advertising or tracking.
- On-device information: game progress, settings, accuracy, and level history may be stored locally on the device.
- Permissions: the game does not request access to location, contacts, camera, microphone, health information, or advertising identifiers for its normal operation.
- Reports: PDF reports are created only when requested by the user and remain under the user’s control through the device’s normal save or share functions.
- Deletion: users can remove locally stored app information by clearing the app’s storage or uninstalling the app, subject to the device platform’s behavior.
- Children: the game is suitable for a general audience but is not designed to collect information from children.
FPGA Foundation
FPGA Foundation is an educational app published by Inversiones Rintronic C.A. It teaches digital logic, Verilog, RTL simulation, and FPGA design concepts. The app uses Google or Apple sign-in through Firebase Authentication to establish the learner’s account; the selected provider may supply an account identifier and profile details such as a name or email address. Rintronic does not receive or store the learner’s Google or Apple password.
- Learning progress in the cloud: when signed in and online, the app synchronizes lesson completion, scores, attempts, exercise variants, learning streak, and the current resume lesson to Firebase Cloud Firestore under the signed-in Firebase user ID. A Google account and an Apple account are separate identities in this release; progress is not automatically merged between them. Use the same provider account to retrieve that account’s cloud progress.
- Information kept on the device: learning progress, app preferences, the remembered learner name, biometric-unlock preference, and Verilog editor drafts are stored locally using the device’s app storage. Verilog drafts are not included in the cloud progress snapshot. Signing out does not itself delete local or cloud learning records.
- Biometrics: optional biometric unlock uses the device operating system’s local authentication prompt. The app stores the user’s enablement preference, not fingerprint or face templates; biometric data remains under the platform’s control.
- Purchases: billing, if enabled for the relevant release, is handled by Apple App Store or Google Play. Premium access and purchase restoration are platform-specific. The current app build does not unlock a purchase unless secure receipt verification is configured; no payment-card details are collected by Rintronic.
- Deletion and account requests: users may request deletion of their account and associated cloud learning data by emailing mobile.apps@rintronic.com. Include “FPGA Foundation” and the sign-in provider in the request so the account can be identified. Local app data can be removed through the device’s app-storage controls or by uninstalling the app.
- Third-party services: Firebase Authentication and Cloud Firestore provide sign-in and progress synchronization; Google Play or Apple App Store provides platform billing when available. Their own privacy terms also apply.
This page is intentionally stable so it can be referenced from Apple App Store Connect, Google Play Console, and from privacy links inside Rintronic apps.
3. Data, device access, and permissions
Depending on an app’s function, it may request access to Bluetooth, nearby devices, network connectivity, notifications, sensors, files, camera, location, health or fitness information, or other device capabilities. An app-specific notice will identify the actual permissions and purposes before that app is published.
Rintronic will not represent an app as collecting no data unless the app and all integrated third-party SDKs have been verified accordingly. Information processed only on the user’s device will be distinguished from information transmitted off-device.
4. Health, wellness, and sensor information
Some Rintronic apps may connect to wearable, bio-sensing, or remote-monitoring devices. Where applicable, an app-specific notice will describe the measurements handled, whether they are stored or transmitted, who can access them, and what security and deletion controls apply. Unless an app explicitly states otherwise, it is not intended to provide medical diagnosis, treatment, or emergency services.
5. Purposes of processing
App information may be processed only for purposes disclosed for that app, such as providing requested functionality, connecting to devices, synchronizing user-authorized information, maintaining accounts, supporting users, securing services, diagnosing failures, improving reliability, or complying with law.
6. Service providers and third-party SDKs
An app may rely on platform services, cloud infrastructure, crash reporting, authentication, device manufacturers, healthcare integration providers, or other SDKs. Every published app notice should identify material third-party categories and link to relevant provider policies where appropriate. Rintronic does not sell mobile-app personal information or permit undisclosed cross-app advertising tracking.
7. Security
We use safeguards appropriate to the data and app function, which may include encrypted transport, access controls, authentication, data minimization, and limited retention. No system is completely secure, and app-specific security requirements will be reviewed in proportion to the sensitivity of the information handled.
8. Retention, account closure, and deletion
App-specific notices will state retention periods or the criteria used to determine them. Where Rintronic maintains an account or server-side personal information, users may request deletion through the controls identified in the app or by emailing mobile.apps@rintronic.com. We may verify identity and may retain limited records where legally required or necessary for security and dispute resolution.
9. User choices
Users can manage many permissions through device settings, stop future app data transmission by disabling relevant permissions, disconnect devices, or uninstall the app. Disabling a required permission may prevent related features from functioning. Additional access, correction, portability, consent, objection, or deletion rights may apply depending on jurisdiction.
10. Children
Unless an individual app and its store listing expressly state otherwise, Rintronic apps are not directed to children. Apps intended for children will receive a dedicated notice and age-appropriate protections before publication.
11. Changes
We may update this policy and app-specific notices when features, SDKs, or data practices change. Material changes will be communicated as appropriate through this page, the app, or the relevant store listing.
12. Privacy contact
For questions, privacy requests, or deletion requests, email mobile.apps@rintronic.com and include the app name, platform, and the nature of the request.
Inversiones Rintronic C.A.RIF J-30983081-3
Rintronic®