One device. A small shelf of practice state.

The Android app keeps practice state locally. A saved Ready Strip consists of a scenario ID, a response ID, and three step IDs. The app also remembers the last selected portal and scenario so the practice can resume in context.

The website is a static introduction and privacy route. The included page code does not submit a form, build a visitor profile, serve ads, or run an analytics package.

This policy covers the Returnlight Android application identified by package name org.bouldercountylostpetrescue.returnlight and this two-route Returnlight website package.

It does not describe the independent websites, services, forms, or privacy practices reached through external source links. Those destinations provide their own terms and notices.

Returnlight receives taps on built-in chapter portals, scenario frames, signal cues, response options, and Ready Strip steps. These are selected from a fixed editorial catalog.

The app does not provide a field for entering a pet name, person name, address, coordinates, phone number, email address, case report, photograph, message, or free-form note.

Scene selection, rationale display, step ordering, archive display, and reset are handled by code and content bundled with the app. These actions do not require a server response.

Returnlight does not use the selected practice state to infer identity, location, health, behavior, or an outcome for a real animal.

The app uses Android shared preferences in its private application storage. The values are short preset IDs for saved strips and the last portal or scenario position.

Because the stored values are catalog IDs, the shelf can reopen the selected scenario, response, and three-step order without creating a separate pet or person profile.

A saved Ready Strip remains until the user removes that strip, erases all local practice state, clears application storage through Android, or uninstalls the app.

The application backup and device-transfer configuration excludes its shared-preference state, reducing unintended movement of the archive to another device.

The replay shelf provides a remove action for one saved strip. The ready room provides an erase action for all Returnlight practice state and asks for confirmation before clearing it.

Android's application-storage controls and uninstall process provide additional device-level ways to remove the same local data.

Delivering any public website normally requires a hosting provider to receive network information such as an IP address, request time, requested path, user-agent string, and delivery or security status. The exact retention and access rules depend on the publisher's chosen host.

The Returnlight page code does not read those server logs or copy them into the Android app. The chosen host's own privacy information governs its log retention and access.

The included Returnlight HTML, CSS, and JavaScript do not set cookies, local-storage values, advertising identifiers, or cross-site tracking pixels.

A final host, consent layer, security product, or publisher-added integration could change that behavior. If one is added, the published policy should identify the tool and its purpose.

The Android project and website package include no analytics SDK, analytics tag, event collector, session-replay script, heatmap, attribution library, or measurement pixel.

If a future version adds measurement, its published policy will identify the service and the behavior that changed.

Returnlight includes no ad SDK, ad slot, sponsored placement, behavioral-advertising profile, or advertising identifier access.

Source links and organization references are editorial context, not paid endorsements inside the delivered product.

Returnlight has no registration, sign-in, password, social login, cloud profile, subscription, purchase, or account-recovery flow.

Saved practice state belongs to the local app installation rather than to a portable Returnlight identity.

The Android manifest does not request the Internet permission. Organization and source names appear in its reading bay as bundled text.

The website contains ordinary links to the organization and source publishers. Following one leaves Returnlight and sends a normal web request to that destination under its privacy practices.

The app does not request location, camera, microphone, contacts, phone, nearby-device, notification, calendar, biometric, motion, or user-selected media permissions.

Its launcher activity uses ordinary Android application lifecycle and private storage capabilities.

Returnlight is a general educational practice experience and is not designed to collect information from a child or create a child account. Its fixed-choice interaction does not ask for a child's name, contact details, photo, precise location, or message.

Families can erase the local practice shelf from the app or use Android's storage controls at any time.

Local practice state uses Android private application storage and is excluded from the app's configured backup and device-transfer paths. The product also minimizes the stored values to preset IDs.

No local software or storage design can promise absolute security. Device access, operating-system compromise, modified builds, publisher-added integrations, and the final website host remain separate security boundaries.

This policy describes Returnlight version 1.0 app behavior and its static website. A published revision will identify its effective date and the product behavior it describes.

Material changes to collection, permissions, network behavior, accounts, analytics, advertising, or hosting integrations require corresponding policy language before the changed version is distributed.

Use the publisher contact shown with the official Returnlight distribution for privacy or app-support questions.

The Boulder County Lost Pet Rescue website remains the source for questions about that organization; this policy does not designate its public channels as Returnlight publisher support.