Usage Policy

COMPASS ONE — last reviewed 20 September 2026 · plain-language draft

Status: this is an acceptable-use draft that matches what the product is built for and what it already refuses. It is not lawyer-reviewed. There is no automated “acceptable use” monitor and no click-through at login — the gates below are the enforcement that exists in code today.

Who operates this pilot. COMPASS ONE is a private pilot operated by Szymanski Consulting. It is not an official product of any service-club organization. The operator is responsible for the pilot service.

Who may use COMPASS ONE

Invited adult leaders and administrators of a participating service-club organization. You may use only the account and assignment you were given. The product is not for children and not for public registration.

Intended use

Prepare and rehearse an LTG → Governor style briefing on clubs in your scope.
See which clubs need attention, using membership and club-health signals.
Record commitments, projects, and this-week follow-ups.
Capture affirming notes about people: strengths, growth, mentorship, future leaders.
Talk or type. Ask COMPASS to keep a note when you want it remembered.
Export your assignment’s workbook for your own leadership work when your role allows it.

People notes — positive only

Do not use COMPASS as a grievance, gossip, or performance-punishment file. Person-scoped notes must be about development and potential. The software will refuse many complaint and smear phrases, and it will not put that text back into a briefing or export. If the real issue is a vacancy, process, or club result, record it on the club, not as a character judgment of a person.

This filter is not perfect. Novel wording can slip through. You are still responsible for what you ask COMPASS to save.

Do not

Try to read another organization’s data, another leader’s conversations, or clubs outside your assignment.
Share a 6-digit sign-in code or a live session token. Those are your credentials.
Forward exported workbooks with member names more widely than your role requires.
Use the assistant to generate attacks on people, or to bypass the people-note rules by rephrasing.
Probe sign-in to discover whether an email has an account. The page is built not to tell you.
Overwhelm the service (scripted request floods). Sign-in, invites, and paid AI routes are rate-limited.
Treat at-risk ranks or assistant replies as an official finding or as a forecast that a club will close. The watch list is a rule-based attention index. You remain responsible for leadership decisions.

Voice and chat

Speak or type only what you are willing to have stored as text. Voice audio goes to the AI provider for that call and is not kept as a recording in COMPASS; the transcript and any saved notes are kept. If you void a note, it is hidden, not erased.

What the software already enforces

Invite-only accounts; 6-digit email-code sign-in; assignment-scoped API access.
Organization isolation (application checks plus database row-level security).
Positive-people write and read gates; future-leader notes need a real name and club.
Soft-void with an audit row for insights and commitments.
Export limited to field / admin roles and to the caller’s geography; transcripts omitted.
Field-length limits on tool writes; email-to-self cannot be redirected to someone else.

The product does not run a general acceptable-use classifier, does not record that you accepted this page, and does not watch every prompt for policy violations beyond the gates above.

If access is misused

The operator may suspend or remove an assignment (is_active — access is turned off, the row is kept). Contact the administrator who invited you, or david@szy.com for the reference pilot.