Robot Navigation Academy privacy policy

Robot Navigation Academy (the App) is an offline-first educational robot-navigation simulator for teens aged 13 and older and adults. It is not a certified safety system, a production robot controller, or an authorization to operate a real robot.

Who we are

Robot Navigation Academy is provided by Academy4Tech, developed by Muhammed Nabeel. The primary privacy and support contact is [email protected]. The alternative contact is [email protected]. Website: academy4tech.com.

This policy applies to Android package com.academy4tech.robotnavigationacademy, app version 1.2.0 (versionCode 3). It was last updated on 18 September 2026.

Information handled by the App

Learning and simulator information stored on your device

The App stores its core learning and simulation records locally on your Android device. Depending on the features you use, these records can include:

your preferred certificate name; lesson completion; bookmarks; quiz attempts; flashcard review timing; achievements; persisted capstone stage and evidence-check selections; and the issued certificate ID, date, score breakdown, performance band, and course version;
app preferences such as theme, high-contrast mode, reduced-motion preference, language-related display choices, and whether the advertising placement is hidden for the current app session;
scenarios you create, including maps, obstacles, terrain, goals, sensor settings, simulated pedestrians, fault settings, seeds, and experiment names or notes;
recorded simulation results, such as collisions, elapsed time, path length, minimum clearance, pose error, coverage, scenario hashes, and simulator version information; and
learner-entered code-exercise text and locally generated teacher or evidence summaries.

The App uses local Android storage, including Room and DataStore, for these records. Academy4Tech does not receive this local course or simulator information through an Academy4Tech account or Academy4Tech cloud service in this release. The App does not require an account, and it does not include active classroom sync, cloud backup, remote code execution, AR, or real-robot/HIL connectivity.

Android or a device vendor may offer system-level backup, transfer, or device-management features. The App disables Android application backup in its manifest, but users should review the settings and policies of their device, school, employer, or operating-system provider because those services are outside Academy4Tech’s control.

Code exercises

Code exercises use a restricted, non-executing validator. The App checks entered text for expected learning patterns; it does not run that text as a process, grant it file access, or send it to a remote execution service. Do not enter secrets, credentials, or personal information in an exercise.

Information you choose to include

On first launch, the App optionally asks for the preferred name to display on a course certificate. You can choose Not now and use the rest of the App without providing a name; a name is required only before the certificate can unlock. It does not need to be a legal name, can be added or edited later in Settings or the Certificate section, and remains in local DataStore unless you explicitly export or share a certificate. Scenario names, experiment notes, code-exercise text, and exported files can also contain whatever you type into them. You control that content. Avoid adding student identifiers, confidential material, or other personal information that is not needed for the learning activity.

The App includes Google Mobile Ads SDK 25.5.0 and Google’s User Messaging Platform (UMP) SDK 4.0.0. When the App asks Google for consent information or is permitted to request an ad, Google and its advertising partners may automatically process information such as:

Internet Protocol (IP) address, which can be used to derive general location;
device, app, browser, operating-system, language, and network information;
interactions with the advertising placement, including views, clicks, and other product-interaction events;
diagnostic, performance, security, and fraud-prevention information; and
identifiers that are available and permitted under the device, account, consent, regional, and SDK configuration in effect.

Google’s precise collection, purposes, sharing, retention, and available controls can vary by region, ad response, user choice, device setting, and changes to Google’s services. Google’s current disclosure for its Mobile Ads SDK describes collection of IP-derived general location, user product interactions, diagnostic information, and device or account identifiers for advertising, analytics, and fraud-prevention purposes. See Google Mobile Ads SDK data disclosure and Google’s Privacy & Terms.

The App does not attach lesson progress, scenario content, experiment names, notes, code text, or simulation results to an ad request. The App’s manifest removes the Google advertising ID permission and Android Privacy Sandbox ad-services permissions for ad ID, attribution, and topics. Removing those permissions limits access to those Android facilities; it does not mean that Google processes no data or that no other permitted identifier or network information can be used.

Reports and user-directed exports

The App can create reports, comma-separated value (CSV) files, and a PNG course certificate from local records when you deliberately choose an export or share action. An export may contain the scenario or experiment name, seed, scenario hash, simulator version, run date or time, metrics, completion evidence, learner-entered notes, your preferred certificate name, certificate ID and issue date, course version, measured score and performance band, and the displayed score breakdown.

Android’s system document picker or share sheet lets you choose where the file goes. The selected destination could be another app, a school-managed service, cloud storage, email, messaging, removable storage, or a local folder. Once you send a file to another provider or person, their privacy and retention practices apply. Review the preview, remove unnecessary personal information, and confirm the recipient before sharing.

To open Android’s share sheet, the App writes the current certificate PNG to its private cache and grants the selected receiving app temporary read access. A later share removes older certificate-cache copies; Android may also clear cache, and clearing App storage or uninstalling removes it.

The capstone export and certificate require all lessons, at least two locally recorded runs, all eight capstone-stage confirmations, and all manual evidence checks. The certificate score is calculated deterministically from the best lesson-quiz average (70%), saved-run success rate (15%), collision-free rate (10%), and average path efficiency (5%); it is not an AI judgment. Neither artifact establishes professional qualification, safety certification, field-test eligibility, independent review, or permission to operate hardware. A qualified person must independently review the evidence, hardware, site, procedures, and applicable rules.

How the placement works

The dashboard contains one inline native-ad placement. A Google-served advertisement is identified as an ad and includes Google’s AdChoices presentation when supplied. The App does not implement custom ad-click handling. You can dismiss the whole placement for the current process/app session.

If an ad cannot be requested or displayed—for example while consent is unavailable or loading, the device is offline, or Google returns an error or no fill—the App displays a packaged Academy4Tech house message instead. That local fallback does not contact an ad network. The App does not continuously retry an unsuccessful ad request.

The App does not include advertising mediation, an Academy4Tech analytics service, or a third-party crash-reporting SDK in this release.

Once per cold/process launch in the App’s single Activity, UMP asks Google for current consent information and calls Google’s method to load and show a consent form when required. The App does not initialize Google Mobile Ads or request a Google ad until UMP reports that ads may be requested through canRequestAds().

When Google reports that a privacy-options entry point is required, Settings displays Manage ad privacy choices. You can use it to revisit available advertising privacy choices. Availability and the form shown depend on Google’s determination for your region and configuration. Device- or account-level advertising controls may also be available through Android or Google settings.

Hiding the in-app ad placement controls its visibility only for the current app session. It is not the same as withdrawing or changing a consent choice. Use Manage ad privacy choices when that option is available, or contact us if you need help.

Conservative advertising configuration

The intended audience is teens aged 13 and older and adults, not children under 13. Until a reviewed neutral age screen and final policy configuration exist, the App applies these conservative settings to every UMP or Mobile Ads request:

UMP’s under-age-of-consent flag is set to true;
Google Mobile Ads age-restricted treatment is set to TEEN;
the maximum ad content rating is G; and
publisher-requested ad personalization is disabled.

These publisher settings are designed to limit advertising. They do not replace a user’s privacy rights, a parent or school’s responsibilities, or Google’s own processing rules. They also do not, by themselves, make the App appropriate for children or establish compliance with every child-directed or education law.

Debug builds use Google’s test native-ad unit. Release builds are configured to use Academy4Tech’s production AdMob unit. Testers must not click live production ads.

Permissions and network access

The Android manifest includes Internet and network-state access so the App can request Google consent information, load an advertisement when permitted, and open a user-selected external web page. Google Mobile Ads may merge operational permissions such as wake-lock and foreground-service permissions into the final manifest. The App does not request camera, microphone, precise location, contacts, storage, Bluetooth, or nearby-device permission in this release.

The simulator’s lidar, camera cone, motion, localization, and map data are generated inside the simulation. They do not read a physical camera, microphone, location sensor, or robot. Cards describing cloud, AR, code-execution, and real-robot/HIL integrations are informational placeholders; those integrations are not active.

An external-link action can open your browser or another installed app. That provider receives data normally associated with a web request and is governed by its own privacy policy.

Academy4Tech does not sell locally stored lesson or simulation records, and the App does not upload those records to an Academy4Tech backend. Academy4Tech does not use them for cross-context behavioral advertising.

Information may nevertheless be processed by or disclosed to:

Google, for UMP consent services and Google Mobile Ads when a request is allowed;
a destination you select, when you export, save, or share a report;
your device, school, employer, or operating-system administrator, if they manage the device or destination; and
authorities or other parties when legally required, or when reasonably necessary to protect users, the public, Academy4Tech, or the integrity of the service.

Relevant third-party information includes:

Google and a user-selected export destination may process information in countries other than the one where you live. Their policies describe their legal bases, safeguards, retention, and transfer practices.

Retention, deletion, and controls

Local records

Local learning progress, preferences, scenarios, and run history remain on the device until you delete them through an available App control, clear the App’s storage in Android settings, or uninstall the App. Individual App screens may provide more targeted reset or delete controls. A session-only ad-placement dismissal is reset when the app process ends.

Before clearing storage or uninstalling, save any evidence file you want to keep. The App cannot recover local records after Android removes them. Files you previously exported are separate; delete them from their destination and from any recipient or backup as needed.

Google and other providers

Academy4Tech does not control Google’s retention of consent, ad, diagnostic, security, or fraud-prevention information, or the retention practices of a destination you selected for an export. Use the relevant provider’s controls or contact that provider for deletion requests involving its systems. You may also contact Academy4Tech; we will explain what we control and, where applicable, act on a valid request.

Because this release has no Academy4Tech account or cloud database for learner records, we normally cannot locate or remotely delete data stored only on your device. Do not email us a full evidence package unless support specifically requires it and you have removed information that is not needed.

Children, students, and education

Robot Navigation Academy is intended for teens aged 13 and older and adults. It is not directed to children under 13, and Academy4Tech does not knowingly ask a child under 13 to create an account or submit personal information. The App’s conservative ad-request settings do not change this intended audience.

If you are under the age at which you can independently consent to data processing in your location, use the App only with a parent, guardian, teacher, or school’s authorization as applicable. Schools and educators should avoid entering student names or identifiers into scenarios, notes, code exercises, or exported files, and should review their legal obligations, device-management settings, destination policies, parental-consent requirements, and procurement rules.

If you believe a child has provided personal information to Academy4Tech, contact us. Include enough information to investigate, but do not send additional sensitive data. If information exists only in local App storage, it must be removed on that device.

Security

The App reduces exposure by keeping core curriculum, preferences, scenarios, and simulation results on the device; disabling Android application backup; restricting the code validator; not enabling dormant cloud, AR, or hardware integrations; and not adding learner records to advertising requests.

No application, device, transmission, or storage method is completely secure. Keep Android updated, use a device lock, protect exported files, review sharing destinations, and avoid entering unnecessary personal or confidential information. Report a suspected security or privacy issue to [email protected].

Your choices and regional rights

Depending on where you live, applicable law may provide rights to know, access, correct, delete, restrict, object to, or obtain a copy of certain personal information, or to withdraw consent. These rights can be subject to exceptions and identity-verification requirements.

Available practical controls include:

using core learning and simulation features offline;
declining to add personal information to free-text fields;
deleting local records, clearing App storage, or uninstalling;
choosing whether, where, and with whom to export a file;
dismissing the ad placement for the current app session;
using Manage ad privacy choices when Google requires that option to be available; and
using Android, Google, browser, or destination-provider privacy controls.

To make a privacy request about information controlled by Academy4Tech, email [email protected] or [email protected]. State your country or region, the nature of your request, and how we can respond. Do not send passwords, government identifiers, or an unredacted student report. We may need reasonable verification and will respond as required by applicable law.

Changes

We may update this policy when the App, advertising configuration, third-party services, or legal requirements change. The effective date will identify the latest version. A material change should be reflected in the hosted policy and, where required, in the App, Google Play, AdMob, or a new consent notice before the changed processing begins.

New cloud sync, accounts, analytics, remote execution, camera/AR, Bluetooth, nearby-device, location, or real-robot features would require a fresh privacy and safety review and an updated policy before release.

Start a conversation

For learning questions, collaborations, application support, privacy questions, data-deletion requests, and project enquiries, write to the Academy4Tech inbox.

Academy4Tech — Muhammed Nabeel
Email Academy4Tech: [email protected]
Alternative email: [email protected]
Website: academy4tech.com

Robot Navigation Academy privacy policy.