PRIVACY DEBRIEF · EFFECTIVE AUGUST 26, 2026
Eighteen questions, answered in the open.
This policy describes the Baywise Android app in this package and this two-route website. It distinguishes device-only rehearsal state from ordinary requests a future website host may process.
01 · Which surfaces are in this debrief?
What this covers
This policy covers the Baywise Android app delivered in this package and the Baywise introduction and policy pages. It does not automatically cover a different product, organization system, store account, or third-party site.
02 · Who makes public commitments?
Who controls publication
This is a local publication package. The future publisher controls public hosting, store publication, contact details, and any later service changes. The package does not prove authorization from Life Support System Training or a live deployment.
03 · What is the app built to do?
What Baywise does
Baywise presents app-authored fictional communication rehearsals. A person turns among eight situations, moves through ten frames, chooses selected branches, sees a local consequence, and may queue up to three situations for a future pass.
04 · What do you give the app?
What you enter
You tap built-in scenarios, navigation controls, branch choices, queue markers, and clear controls. There is no free-text field, form, account profile, camera input, contact import, precise location prompt, or file upload.
05 · Which rehearsal marks remain?
What is saved locally
The app stores the current scenario, current frame, current result state, whether a scenario is open, and up to three built-in scenario keys in the local queue. These values are app preferences on the device.
06 · Is there a place for private details?
Sensitive information
No. Baywise is not designed to receive names, health information, student records, case notes, emergency details, passwords, financial data, or other sensitive personal information. Do not treat its built-in rehearsal choices as a record system.
07 · Which device doors are requested?
Device permissions
The packaged app does not request camera, microphone, contacts, location, photos, notifications, Bluetooth, calendar, storage, or similar runtime permissions.
08 · Does rehearsal state leave the device?
Network behavior
The packaged Android app has no Internet permission and contains no app feature that transmits rehearsal state to a server. This statement describes this build; a publisher must reassess the policy before adding connected behavior.
09 · Is identity required?
Accounts
No sign-in, registration, profile, social login, or identity verification exists in the packaged app.
10 · Who measures your taps?
Analytics
No analytics or behavioral measurement SDK is included in this app build. The app does not create an analytics identifier or send event telemetry.
11 · Is attention being sold?
Advertising
Baywise contains no advertising SDK, sponsored placement, behavioral advertising, or in-app billing feature.
12 · Who receives app data?
Sharing
Because the app does not collect or transmit personal data, it does not sell, rent, or share app data with data brokers, advertisers, analytics companies, or the supplied organization profile.
13 · How long do local marks stay?
Retention
The small local preference state remains until you use the in-app clear control, clear app data in Android settings, or uninstall the app. The app does not impose a server retention schedule because it has no server store.
14 · How can you clear the bay?
Erase controls
Open Method Note and choose the clear-local-state action. Android's clear-storage control or uninstalling the app also removes its local preference state.
16 · What changes when these pages are hosted?
Website hosting
If a publisher places these static pages on a web host, that host may process ordinary technical request information such as IP address, request time, requested path, browser data, and security logs under its own terms. This package itself contains no form, analytics script, account, cookie banner, or advertising tracker.
17 · Where does this policy stop?
External links and security
A future publisher may add store or organization links. External destinations follow their own practices. Reasonable local and hosting safeguards reduce risk but cannot promise absolute security; verify the destination before sending information elsewhere.
18 · What happens when the product changes?
Changes and contact
The publisher should revise this notice before adding data collection, permissions, connected features, or a new provider, and should update the effective date. A public release must also provide an accurate, monitored publisher contact; none is invented in this local package.
