Flow Commons

Privacy policy Effective August 28, 2026

A plain-language lifecycle map

What stays on your device,
what the website may expose,
and what you control.

This policy describes the current Flow Commons Android release and the static website files packaged with it. The app's learning state is local. The website is a separate public surface whose hosting environment may create ordinary delivery records.

Source

Privacy at a Glance

Flow Commons does not require an account. Scenario choices, progress, reflection tokens, and an optional note remain in the app's private local storage unless you erase them or remove the app. The Android app contains no advertising or analytics SDK and does not send this learning state to a remote service.

A clear headgate dividing a calm blue channel into visible paths

Boundary

Scope of This Policy

This notice applies to the Flow Commons Android app with package name org.boothorchardwaterassociation.flowcommons and to the pages at this website's root and /privacy-policy/. It does not control the privacy practices of an app store, operating-system vendor, web host, browser, or external site you choose to visit.

A bounded clay basin set apart from surrounding channels

Entry

Information You Enter in the App

You may select scenarios, allocate symbolic flow tiles, mark scenarios complete, choose a reflection token, and type an optional short field note. These are learning interactions, not account details. Flow Commons does not ask for your name, email address, precise location, payment information, contacts, photographs, microphone recordings, or health information.

Small clay tokens entering a clearly bounded local basin

Local channel

On-Device Processing

The app calculates route totals, chooses consequence text, updates completion state, and restores your last scene on the device. Bundled images and educational text are read from the installed app. No server is needed to process a scenario or generate a comparison.

A closed-loop translucent channel moving through a local relief model

Basin

Local Storage

Flow Commons stores its state in app-private preferences managed by Android. This includes the current scene, selected scenario, tile allocations, completed scenario identifiers, reflection choices, and optional note text. The app does not intentionally write these items to shared media storage or cloud backup.

A small sealed reservoir holding colored local-state pieces

Holding time

Retention

Local state remains until you use the in-app clear action, clear the app's storage through Android settings, or uninstall the app. Flow Commons does not operate a remote retention schedule for app state because it does not receive that state. A web host may retain delivery logs according to the publisher's hosting configuration and the host's own terms.

Layered seasonal sediment accumulating in a contained channel

Release

Erase Local Data

Open the Season Ledger and choose Clear my ledger to remove scenario progress, allocations, reflections, and optional notes created in the app. You can also clear storage in Android settings or uninstall the app. This action cannot remove records held independently by an app store, browser, web host, or external site.

A lifted clay gate releasing pieces from a local reservoir

Web delivery

Website Delivery Logs

The packaged website contains static HTML, CSS, JavaScript, and local images. The site itself does not send form submissions to Flow Commons. When a public host delivers a page, that host may process ordinary connection data such as IP address, timestamp, requested path, user agent, and security events. The exact retention and access rules depend on the publisher's selected host.

Brief surface ripples marking delivery events before fading downstream

Browser state

Cookies and Similar Technologies

These two static pages do not set a Flow Commons cookie, use browser local storage, fingerprint visitors, or embed a consent manager. A hosting or security provider may use its own essential technologies at the delivery layer; those technologies are outside the packaged page code and should be described by the publisher if enabled.

An unmarked channel bed with no retained browser tokens

Measurement

Analytics

The Android app contains no analytics SDK. The packaged website contains no analytics script, tracking pixel, tag manager, or session replay code. Hosting-level aggregate traffic or security reporting may still be available to the publisher through the chosen web host.

A quiet measuring reach with no collection vessels attached

Commercial boundary

Advertising

Flow Commons does not display ads, include an advertising SDK, sell audience segments, or use app activity for behavioral advertising. The packaged website contains no ad slot or affiliate tracker.

An uninterrupted tactile landscape without commercial markers

Identity

Accounts and Authentication

The app has no sign-in screen and does not create a Flow Commons account. It does not request a password, social login, email verification, or profile. Any app-store account used to download the app is managed by the store provider under its own terms.

An open commons with no identity gate or credential vessel

Device access

Permissions and Device Features

Flow Commons does not request access to location, camera, microphone, contacts, calendar, notifications, Bluetooth, nearby devices, phone state, or shared photos and files. Standard operating-system access needed to render the interface and use app-private storage is handled by Android without a runtime permission prompt.

Closed clay gates around unused device-feature channels

Families

Children

Flow Commons is a general-audience educational experience and is not directed specifically to children under 13. It does not knowingly collect personal information from children. Because optional notes stay local, families and educators can decide whether note-taking fits their setting and can erase app state at any time.

A calm shared learning basin with differently sized neutral tokens

Protection

Security Boundaries

Local state is kept in the app's private storage and excluded from the app's configured backup and device-transfer rules. Device security still depends on Android, screen-lock choices, operating-system updates, and physical access. No software or hosting environment can promise absolute security.

Nested limestone contours protecting a small inner reservoir

Course correction

Changes and Effective Date

This policy is effective August 28, 2026. If app behavior or the packaged website changes, the notice should be revised before the changed release is distributed, and the effective date should be updated. Continued availability of an older page does not by itself describe a newer app release.

A movable canal joint showing a deliberate course correction

Return channel

Questions and Publisher Contact

For privacy questions about a published release, use the verified developer contact shown on the Google Play listing where you obtained Flow Commons. This page does not publish or invent an email address, telephone number, or response-time commitment.

A final blue return channel arriving at a simple clay marker