WIDE MARGIN

Privacy information

A clear court for what the product does.

The Android app holds only the current walk in memory while it is open. It does not ask for an account, a narrative, an image, a location, or a person description.

Two adjacent architectural courts representing app and website scope

This page separates the Android app from the static introduction website. The app is designed around built-in scenes and choices. The website publishes information; a future web host may necessarily process ordinary request metadata to deliver files. No public host or authorized publisher contact is claimed in this local edition.

A calm entrance marking the intended-reader route
Separate surfaces, literal behavior

App and website scope

This notice covers the Wide Margin Android app and the static pages served at the introduction and privacy routes. The app and website are separate surfaces: opening a web page is not an in-app feature, and using the app does not send a record to this site.

An open architectural seam representing an educational boundary
An entrance with room to choose

Intended audience

Wide Margin is written for adults and older teens exploring observation, uncertainty, access, and respectful requests in fictional shared spaces. It is not designed as a child-directed game, a social service intake tool, or a way to monitor another person.

A bright outward threshold with no simulated service desk
Learning stays distinct from authority

Educational purpose and authority boundary

The prompts are original educational material. They do not represent law-enforcement guidance, legal advice, venue rules, dispatch instructions, official training, or a statement of Air 95 Foundation programs. The app cannot verify events, people, places, or risk.

A temporary sunline trace crossing an unobstructed outward path
Urgent situations move outward

Emergency and real-world service boundary

Wide Margin is not an emergency service and cannot contact responders. If immediate danger exists, use the real emergency channel available where you are. For non-urgent route, venue, transit, or building questions, choose the relevant real-world information source. The app does not choose a jurisdiction or place a call.

An empty wall with no persistent history marks
The current sunline exists only on screen

Walk gestures and rehearsal choices

You can change a built-in scene, shift its visual margin, move among walks, select a type of handoff, and reveal a built-in rehearsal sentence. These actions manipulate app state only. The app provides no free-text field, camera surface, audio recorder, or incident form.

Clear architectural space where a notebook would otherwise appear
No walk history is built

Volatile state and persistent storage

The current walk number, sunline position, viewing margin, and selected built-in phrase are held in volatile interface memory while the visit is active. The released build does not write a walk history, report, observation, or rehearsal sentence to persistent app storage.

Sensitive details the app does not request

Do not enter personal details because the product has nowhere to enter them. Wide Margin does not request a name, address, phone number, email, exact location, person description, allegation, health detail, protected characteristic, photo, recording, credential, or emergency narrative.

A sealed camera-like opening rendered as plain architectureAn architectural court with no location mechanism
An unbuilt gate representing the absence of account permissions
No device sensor passage

Device permissions

The release does not request camera, microphone, location, contacts, phone, notification, nearby-device, calendar, file, photo-library, or accessibility-service permission. Android may provide ordinary operating-system controls that are outside the app's own feature set.

An unmeasured open court with no analytics markers
The Android route ends on the device

App network behavior

The Android manifest does not request internet access and the app includes no account, sync, upload, messaging, remote content, advertising, billing, or cloud feature. The website is a separate web publication and needs a network connection to visit once publicly hosted.

An empty commercial frontage with no identity gate
No sign-in threshold

Accounts and identity

There is no registration, sign-in, profile, user ID, password, social login, membership check, or identity verification. The app does not recognize the same user across visits or devices.

A sharing route that visibly ends within the local court
No audience measurement passage

Analytics and diagnostics

The app includes no analytics SDK, advertising measurement, session replay, attribution service, behavior profile, crash-reporting network client, or experiment framework. Android and the device maker may maintain their own system diagnostics under their policies; those are not sent by a Wide Margin analytics feature.

A temporary trace fading across a white wall
No commercial frontage

Advertising, purchases, and billing

The app has no advertisements, sponsorship placements, donation flow, marketplace, subscription, paywall, in-app product, or billing SDK. It does not collect payment information.

A cleared promenade after reset
Nothing is prepared for disclosure

Sharing, sale, and disclosure

Because the app does not collect or persist user content, it has no app-held personal narrative to sell, rent, publish, transfer, or disclose. It provides no export or share control. This does not make claims about data independently handled by an app store, device platform, browser, or future website host.

A shared-device shadow crossing an otherwise clear plane
The visit has a short shadow

Temporary-state lifetime

Walk state exists only for the active in-memory visit. Clear returns to the opening wall; leaving or the operating system ending the process removes that volatile state. There is no retained history period because no history database is created.

Reset, exit, uninstall, and shared devices

Use Clear to remove the visible visit state immediately. Exiting or ending the app process also removes it. Uninstalling removes the app itself. On a shared device, someone looking at the screen during an active visit may see the current built-in scene and phrase, so clear the wall before handing over the device if desired.

A supported route intended for an older reader without depicting a childA boundary between local app space and future website hosting
A calm external-link colonnade with a visible boundary
Supported use stays contextual

Children and supported use

The experience is written for adults and older teens, not directed to young children. A parent, guardian, educator, or other trusted adult may choose to discuss the fictional scenes with a younger person. The app does not request age, school, guardian identity, or child account information.

A closing contact court under a finite architectural shadow
Publication has real boundaries

Website hosting, external destinations, and security limits

The static site itself contains no form, account, ad tag, analytics script, or embedded social feed. A future host may process IP address, request time, browser details, and requested path as ordinary delivery metadata under that host's own terms. External destinations have their own practices. No device or transmission can be promised absolute security.

Policy changes and publisher contact

If the released app's behavior or public website changes, this notice should be updated before the change is represented as current. The local edition has no verified public effective date or authorized publisher contact, so it does not invent one. The publisher must add an authorized contact and publication date before public release.

Local build boundary: this page documents the prepared app and site; it does not establish publication, Play approval, or organizational endorsement.

Return to the topic index