Privacy Policy

Private by structure, not by promise alone.

This policy describes the exact intended behavior of All Hands, Shared Play version 1.0.0 and these matching static support pages.

Effective July 31, 2026Publisher: SOJO UNITED, INC.Android package: org.sojounited.allhandssharedplay

Plain summary: no account, no Internet permission, no ads, no analytics, no tracking, no participant records, and no server collection by the app. The app keeps only a Role Lens, up to five module IDs and their order, and optional considered-today markers in private on-device storage.

Section 01

Responsible entity and scope

SOJO UNITED, INC. is identified as the publisher of All Hands, Shared Play. This policy covers the Android app and the matching public app-support pages. The app is an original adult-facing educational edition about supporting youth and community recreation; it is not a team, league, school, city, medical, or emergency service.

Section 02

App purpose and editorial boundary

The app provides 35 educational modules, fictional scenario slips, general safety boundaries, source annotations, and a private Session Thread. These materials do not document or promise a current SOJO UNITED program, grant, event, recipient, schedule, eligibility rule, registration service, or outcome.

Section 03

Information stored locally

The app may store a selected Role Lens, up to five selected module identifiers, their order, and whether a module was marked considered on the current date. This limited state remains in the app's private storage on the device.

Section 04

Information the app does not request

The app does not request a name, email address, phone number, account, password, date of birth, roster, attendance record, precise or approximate location, photo, audio, contacts, calendar, payment details, health information, incident report, pickup record, or free-text personal note.

Section 05

Processing purposes

Local state is used only to display the chosen adult perspective, maintain the private Session Thread, and show a considered-today marker. It is not used to evaluate a person, infer a condition, target content, rank participation, create a streak, or make an eligibility decision.

Section 06

Permissions

The app requests no Internet, location, camera, microphone, contacts, calendar, phone, SMS, storage, nearby-device, notification, biometric, or sensor permission. The installed binary should be reviewed again before each release so this statement continues to match the exact build.

Section 07

SDKs, advertising, analytics, and tracking

The app includes no advertising SDK, analytics SDK, crash-reporting service, social SDK, attribution SDK, remote configuration, cloud database, push service, or behavioral tracking. It does not display ads or create an advertising identifier.

Section 08

Sharing, selling, and third parties

Because the app does not transmit app-use or personal data to the publisher, it does not sell, rent, or share such data. General source publishers are referenced for education but receive no app data from the app.

Section 09

External links and email applications

A source button may ask Android to open a public web address in the user's chosen browser. A future contact button may ask an external email app to start a message after a monitored publisher address is confirmed. Those external apps and sites operate under their own terms and privacy practices.

Section 10

Children, families, and intended use

The app is written for responsible adults such as guardians, coaches, volunteers, and participant-support adults. It does not provide child accounts, child profiles, direct messaging, matchmaking, social discovery, public posting, behavioral advertising, or independent youth registration.

Section 11

Safeguarding and communications boundaries

The app discourages private adult-minor messaging, isolated transport, hidden one-to-one access, public child profiles, and storage of youth records. Users must follow the responsible organization's current screening, supervision, consent, reporting, pickup, and communication requirements.

Section 12

Sports, health, injury, and emergency limitations

The app is general education, not coaching certification, medical advice, diagnosis, treatment, concussion assessment, fitness prescription, return-to-play clearance, crisis care, or emergency response. Stop activity and use responsible adults, qualified professionals, current official sources, and local emergency services when appropriate.

Section 13

Retention

Local selections remain until the user changes them, clears local app data inside the Privacy Center, clears the app through Android settings, or uninstalls the app. A considered-today value may remain locally but is shown as current only when its stored date matches the device's current date.

Section 14

Deletion and no-account status

No account or server copy exists, so there is no remote account-deletion workflow. The Clear Local Data control removes the Role Lens, Session Thread, order, and considered markers from the app's private preferences. Uninstalling the app also removes its local app data under Android behavior.

Section 15

Device backup and security

Android backup and device-transfer participation are disabled for the app's private state. The small amount of local data is protected by Android's application sandbox. No device or software can be guaranteed completely secure, so users should not place personal, medical, incident, roster, or transport information in the app.

Section 16

User choices and accessibility

Users may use the modules without selecting a Role Lens or building a Session Thread, may clear local data at any time, and may choose whether to open external sources. The interface is designed for scalable text, semantic labels, strong contrast, reduced motion, and screen-reader navigation; device settings and implementation quality can affect the experience.

Section 17

Policy changes

This policy may be updated when app behavior, law, platform requirements, or the public support surface changes. The effective date will be revised and material changes should be reflected consistently in the app, public policy, listing, and Play declarations before a new release.

Section 18

Privacy contact

Privacy questions may be sent through the verified developer contact published with the app's current Google Play listing or through the public support page linked from that listing. Users should not include medical, incident, roster, pickup, or other sensitive participant information in an initial inquiry.

Policy integrity

The public page must match the exact uploaded AAB.

If permissions, SDKs, local storage, links, support contact, audience, or app behavior changes, update and republish this policy, the in-app Privacy Center, Play listing, and Data Safety answers before release.