Robot Navigation Visual Guide privacy policy

This policy describes Robot Navigation Visual Guide, package com.academy4tech.movebaseguide, developed and published by Academy4Tech. It covers locally stored ROS 1 and move_base learning features, Google Mobile Ads, and Google’s User Messaging Platform (UMP).

The App does not currently implement cloud accounts, synchronization, remote classrooms, augmented reality, remote code execution, or live robot-control services.

At a glance

The App has no Academy4Tech account, sign-in, cloud profile, or synchronization backend. On first launch, the learner chooses a local display name before entering the learning App. The name is used for the on-device certificate and can be changed later in Settings.
Lessons, search, quizzes, simulations, glossary content, and diagrams are packaged with or generated locally by the App.
Learning progress, assessment attempts, troubleshooting and capstone results, bookmarks, flashcard scheduling, settings, saved workspace content, local assignments, and the certificate record stay in the App’s private storage. Academy4Tech does not receive them.
A performance-based educational Certificate of Completion is generated as a PDF in App cache only after the learner chooses Create and share PDF, Reissue with updated name, or Share certificate PDF. It is not accredited, externally verified, or an Open Robotics credential.
android:allowBackup="false" excludes App data from Android Auto Backup and Android device-to-device transfer.
The App contains Google Mobile Ads. When UMP permits an ad request, Google’s SDK may automatically collect and share the advertising-related data described below, even though Academy4Tech does not operate a learning-data backend.
The App has no Academy4Tech analytics or crash-reporting SDK beyond diagnostics and measurement associated with the Google advertising SDK.
The App has no AR or camera session, remote code execution, live ROS or robot connection, teacher roster, or cloud sync.

1. Information kept locally

Room database

The App stores the following in its app-private Room database:

lesson identifiers, last-opened timestamps, progress, and completion state;
best lesson-checkpoint scores and final-assessment attempts;
troubleshooting results and warehouse-capstone results, including attempt counts and pass evidence;
issued certificate snapshots containing the learner’s chosen name, local record ID, issue date, content version, and score breakdown;
lesson bookmarks and their creation timestamps;
flashcard review ratings and scheduling data, including due time, interval, ease, repetitions, and lapses;
one user-saved workspace project, including title, notes or observations, YAML draft, status, summary, and update time; and
locally created assignment titles and local metadata.

Bundled lessons, questions, glossary terms, flashcards, project briefs, assignments, and architecture records are also seeded into Room. They are publisher-supplied App content, not personal information received from the user.

Preferences DataStore

The App stores the learner-entered display name, whether first-run onboarding is complete, theme, learning mode, language tag, high-contrast choice, large-learning-text choice, reading-friendly-spacing choice, reduced-motion preference, and sound preference. The display name is used only in the local profile and certificate unless the learner explicitly shares that certificate.

Session-only simulation state

Simulation timelines, individual in-progress quiz answers, capstone selections before submission, coding-lab text or results, unsaved workspace edits, experiment-log additions made during the current session, and the captions toggle can reset when a screen or App process is recreated. Passed lesson checkpoints, submitted final-assessment summaries, capstone and troubleshooting results, and an issued certificate snapshot are persisted locally.

The App does not send these Room, DataStore, or session values to Academy4Tech. They are not used by the Google ad request assembled in the App code.

The App integrates Google Mobile Ads SDK 25.5.0 and Google UMP SDK 4.0.0. Development builds use Google’s official sample AdMob App ID and Native Advanced ad-unit ID. Public release builds use Academy4Tech’s production App ID and Native Advanced ad unit with the applicable AdMob Privacy & messaging configuration.

Before requesting a Native Advanced ad in the Home feed, the App:

asks UMP to update consent information;
loads and shows a consent form when UMP says one is required;
checks UMP’s canRequestAds() result; and
initializes Google Mobile Ads and requests one Native Advanced ad for the Home feed only when that result permits it.

If a consent-information refresh fails, a previous valid UMP decision can still permit an ad request. The ad appears at a natural break in the scrollable Home feed and is marked with localized ad attribution and AdChoices. Where UMP reports that privacy options are required, a Privacy choices control is shown with the placement. The About screen also has a persistent Manage ad privacy choices entry point; UMP decides whether a form is available.

The Hide ad control hides the native ad card only for the current App session. It does not withdraw consent, erase Google’s data, buy an ad-free entitlement, or persist after the App is relaunched.

Depending on the user’s region, choices, Google’s messages, and Academy4Tech’s AdMob configuration, ads may be personalized, non-personalized, limited, or unavailable. Consent is not the only possible legal basis, and the privacy options available can vary by region.

Google states that the Mobile Ads SDK automatically collects and shares the following categories when it operates:

Data category	Examples described by Google	Purposes described by Google
Approximate location	IP address, which may be used to estimate general location	Advertising or marketing, analytics, fraud prevention, security, and compliance
App activity	App launch and user interactions such as ad views or taps	Advertising or marketing, analytics, fraud prevention, security, and compliance
App information and performance	App launch time, hang rate, energy use, and other SDK diagnostic or performance data	Advertising or marketing, analytics, fraud prevention, security, and compliance
Device or other identifiers	Device, advertising, or account-related identifiers available to the SDK	Advertising or marketing, analytics, fraud prevention, security, and compliance

Google says SDK transmissions are encrypted in transit using TLS. Google’s disclosure guidance reviewed on September 19, 2026 describes Mobile Ads SDK 25.5.0, the version used by this App. Exact collection, sharing, retention, ad personalization, regional controls, and user rights depend on the Google services, publisher configuration, device settings, and user choices. See Google’s Mobile Ads Play data-disclosure guide, Android privacy guide for ads, Google Privacy Policy, and partner-site explanation.

Academy4Tech does not receive the locally stored learning database through the advertising integration. Google nevertheless processes the advertising SDK data described above.

3. Permissions and device access

The App directly declares:

INTERNET, used by Google advertising and consent services; and
ACCESS_NETWORK_STATE, used to observe connectivity for network-dependent SDK behavior.

The merged release manifest can also contain advertising-related permissions contributed by Google SDK dependencies, including the advertising ID and Android Privacy Sandbox ad-services permissions, plus library implementation permissions.

The App does not request camera, microphone, precise or coarse device location, contacts, calendar, phone, SMS, media-library, nearby-device, or Bluetooth permission. Its AR-labelled preview does not start ARCore or a camera. Its disabled robot bridge does not discover or control robots.

User-selected website and social links are handed to external apps or browsers; those destinations use their own network access and privacy practices.

Workspace and capstone export actions assemble plain text only after the user chooses Share. A certificate action generates a PDF inside the App’s cache, then supplies it to Android’s system share chooser through a temporary, read-only FileProvider URI permission.

Academy4Tech does not receive the selected destination or exported content unless the user deliberately chooses an Academy4Tech-controlled destination. The selected app or service processes the export under its own privacy terms. Users should inspect drafts and avoid putting secrets, credentials, personal data, or unsafe robot configurations into an export.

Website, email, LinkedIn, GitHub, and YouTube actions open external apps or sites. Those third parties can process information under their own notices. Simply displaying a bundled lesson or running a simulation does not open an external service.

5. Disclosure, sale, and service providers

Academy4Tech does not sell the local learning, project, or settings data described in this policy and does not upload it to a publisher backend. Google is the advertising and consent service provider and independently processes the categories described above. A user-selected share destination becomes another recipient only when the user chooses it.

No teacher, school, employer, or other learner receives data from the classroom-demonstration screen. It has no roster or remote reporting channel.

Information may be disclosed if Academy4Tech later receives information and is legally required to preserve or disclose it, or when reasonably necessary to protect users and services. In the current architecture, Academy4Tech does not hold the app-private learning database.

6. Retention and deletion

Local Room and DataStore records remain until they are overwritten, App storage is cleared, or the App is uninstalled. Generated certificate PDFs can remain in the App cache until Android evicts them, the user clears cache or storage, or the App is uninstalled. Android Auto Backup and device-to-device transfer are disabled for this App, so those local records are not included in those Android migration mechanisms. Device-level forensic copies or manufacturer behavior outside the App’s control cannot be guaranteed absent.

To delete local App data, use Android Settings > Apps > Robot Navigation Visual Guide > Storage > Clear storage, or uninstall the App. Reset buttons clear only the named session simulation; they are not a whole-App deletion control.

Because the App has no Academy4Tech account or server-side profile, there is no Academy4Tech account record to delete and no server deletion request flow. If accounts are added later, account and associated-data deletion options will be provided before that feature is released.

Google and any user-selected share destination apply their own retention and deletion rules to data they process. Use the UMP privacy-options form when available, Android or Google advertising settings, the destination service’s controls, or the contact mechanisms in Google’s policy for those records.

7. Security

Local records are held in Android app-private storage protected by the operating-system sandbox. Android backup and transfer are disabled. Google reports encryption in transit for Mobile Ads SDK transmissions. Exporting moves plain text or a certificate PDF to a destination the user chooses; users are responsible for that destination and should not export confidential data.

No storage or transmission method is completely secure. The current database is not separately end-to-end encrypted by the App, and rooted, compromised, debug-enabled, or physically accessible devices can weaken platform protections.

8. Children, students, and Families

The current ad-supported App is designed for general robotics learners and is not configured as a child-directed service. The classroom dashboard and friendly visual guides do not establish a teacher account or child profile.

Academy4Tech selects Google Play target-age groups based on the actual audience, store listing, design, and marketing. If a child age group is included in the future, the distribution will be reviewed against Google Play Families requirements, eligible advertising SDK and serving rules, identifier restrictions, age-screen requirements, and applicable child-privacy law. The App, policy, consent flow, and Data safety disclosures will be updated before that distribution model is used. See the Google Play Families policy and target-audience guidance.

Parents, guardians, schools, or users with concerns may contact Academy4Tech using the details below.

9. International processing

Google and a user-selected share destination may process information in countries other than the user’s country. Their privacy notices describe their transfer mechanisms and regional rights. Academy4Tech does not operate an international synchronization system for the local learning data in the App.

10. User choices and rights

Depending on location, users may have privacy rights concerning information processed by Academy4Tech or Google. For app-private learning data, clearing storage or uninstalling is the direct deletion method because Academy4Tech cannot access or identify those records. For questions or a request concerning information Academy4Tech actually holds, email the privacy contacts below. Academy4Tech may need reasonable information to verify and respond to a request, and legal exceptions can apply.

Users can revisit available advertising choices through About > Manage ad privacy choices. A privacy form may not be required or available in every region. Hiding the native ad card is not an advertising-data opt-out.

11. Changes and future features

Academy4Tech will update this policy and its effective date when the App’s data behavior, SDKs, operator, or services materially change. A policy and Google Play Data safety review will be completed before enabling any currently absent capability such as accounts, cloud sync, remote classroom reporting, analytics or crash reporting, camera-based AR, live-robot networking, or remote code execution.

The public policy will remain accessible and will reflect the behavior users receive.

12. Contact

Privacy questions or complaints may be sent to:

Academy4Tech
Website: academy4tech.com
Privacy: [email protected]
Alternative: [email protected]

For Google advertising privacy questions, use the controls and contact information in the Google Privacy Policy.

Robot Navigation Visual Guide privacy policy.