Data flow and provider connections
This is the honest split between what stays on your phone and what can leave it when you choose to use cloud AI.
| Topic | What typically stays on your device | What may leave your device | Authoritative detail |
|---|---|---|---|
| Cases and work in progress | Case records, intake, analysis results, and optional outcome notes stored in the app (local database) on your device. | Nothing is uploaded to a Situ8-operated “cloud case sync” today—there is no team sync product shipped. | App UI and disclosures; Privacy. |
| AI provider keys / credentials | Keys you enter are stored using on-device secure storage as described in Privacy—not displayed on this marketing page as engineering fact. | Keys are not sent to us as “passwords you type in chat”; the provider you connect receives prompts you send through that connection. | Privacy, Contact. |
| Prompts and context to a provider | — | When you run analysis, the content required for that provider’s API (prompts and related context) is sent per that provider’s terms and routing. | Provider’s policies; in-app provider settings. |
| Sign-in (Google) | Session handled by platform sign-in flows on the device. | Identity and authentication are subject to Google’s terms for Sign-In. | Google account terms; Play listing. |
| Diagnostics / analytics | Developer diagnostics (when enabled) produce information you can copy or share from the device. | Product analytics in current builds are designed as on-device logging (e.g. Logcat)—not a shipped enterprise analytics pipeline. If that changes, it should show up in app notices and Privacy. | In-app diagnostics; future Privacy updates. |
If this page, the app, and the Play listing disagree, treat the app and store as the source of truth for live behavior.
Human oversight
Situ8 does not make decisions for you. It produces structured reads, summaries, and suggestions you can use—or reject.
- You interpret outputs and choose what to act on.
- You are responsible for how analysis is used in the real world, including who else sees it.
- The product is not an autonomous agent with goals of its own; it runs when you invoke it, on your case and your settings.
This is operational posture—not a substitute for professional advice where licensing or regulation applies (see Boundaries).
AI limitations
Models can be useful and still be wrong.
- Outputs may be incorrect, incomplete, out of date, or biased.
- Analysis is draft reasoning to pressure-test against what you know—not a verdict.
- Do not rely on Situ8 as the sole basis for legal, medical, emergency, safety-critical, or other regulated decisions. Use qualified people and proper channels when stakes require it.
If something reads plausible but you would not bet a career or a safety outcome on it, that instinct is correct.
Reporting problematic outputs
We want a clear path—not “prefer in-app when available.”
Current channels (Android app today)
- Help & feedback — From the profile menu, Help & feedback opens your email app with a message to support@forgesdlc.com (subject preset for Situ8 feedback). Use this for offensive or unsafe output, misleading analysis you relied on in a serious context, broken flows, and general product feedback.
- Google Play — Use the Play listing’s developer contact and store feedback for install, account, and distribution issues, and as an additional channel for serious reports.
On the analysis screen, you can optionally save a short outcome reflection (helpful or not, what you tried, what happened next). That reflection is stored on the device with the case—it is not the same as a real-time abuse queue to our team. It helps you and future product design; it does not replace email or Play when you need a human response.
What to include when you write in
- What you were trying to do, what the app showed, and why it was harmful or wrong.
- Screenshots if safe to share (redact secrets).
- Build/channel if you know it (Play internal vs production).
Not for emergencies. Situ8 is not an emergency service. If someone is at immediate risk, contact your local emergency number or appropriate crisis services—not the app or this inbox.
Where Situ8 is not the right tool
- Emergency response — use emergency services.
- Licensed professional advice — legal, medical, mental health, and other regulated domains need qualified humans.
- Safety-critical decisions by itself — operational, physical, or financial harm if wrong: do not treat model output as sufficient.
- Enterprise governance today — no org-wide admin, SSO, audit logs, or compliance program is sold as part of the shipped consumer app.
Trust posture today
Today
Solo Android case work, user-controlled provider setup, clear judgment and boundary copy, Help & feedback email and Play channels, Privacy/Terms as legal layers.
Next
Sharper in-product reporting UX if we add a dedicated flow, tighter alignment between app notices and public pages, clearer pilot guidance for teams—without claiming enterprise certifications we do not have.
Later
Admin controls, org governance, SSO, and auditability only when they are actually shipped and described in product—not on this page as vapor.
Pilots & direction
Team workspaces and enterprise controls are not shipped today.