Product and intended use
Define the configuration, people, information and tasks being assessed.
Self-host versus hosted demo
Public claim only
Home: start in the cloud or clone the repo. Privacy: the policy covers mikeoss.com and app.mikeoss.com only; self-hosted deployments are outside maintainer collection. GitHub: GNU AGPL v3.0. Hosted demo must not receive confidential or privileged material.
Ask: Will we self-host under AGPL, or is any paid hosted tenancy offered under a DPA?
Self-hostable by design
Public claim only
Home: documents never leave your perimeter when self-hosted. README describes Next.js, Express, Supabase Auth/Postgres and Docker Compose with object storage. Hosted demo region is not stated.
Ask: If we self-host, which regions will our Supabase/storage/model endpoints use? If we use the demo, where is it hosted?
Assistant, tabular review, workflows
Public claim only
Home: chat over documents with citations, case research, spreadsheet-style tabular review, reusable workflows, matter-scoped projects. Blog notes MFA, MCP connectors, Word add-in in the repo, CourtListener in v0.3.0.
Ask: Which features are stable in the tagged release we would run, versus demo-only?
CourtListener, not Australian corpus
Public claim only
v0.3.0 article on the home page names CourtListener integration. No licensed Australian case-law or legislation corpus is described.
Ask: What jurisdictions does CourtListener cover in our build, and can we point the citation engine at Australian sources?
Data, controls and requirements
Compare the actual configuration with firm, client and jurisdiction requirements, supported by evidence.
Client disclosure for open-source stack
Not confirmed
No client-consent template. Self-host still sends prompts to whichever model provider the firm configures, unless a local model is used. Hosted demo is expressly unsuitable for client material.
Ask: Provide (or we will draft) a client-disclosure describing self-host, model provider and AGPL.
Customer-chosen keys
Public claim only
README: add an Anthropic, Gemini or OpenAI API key unless using another configured endpoint. Changelog: OpenAI-compatible registry for self-hosted or third-party endpoints. Privacy: inputs go to the provider selected for that deployment.
Ask: Which providers and regions will we configure, and will we use local models for matter data?
Operator-chosen stack
Public claim only
Self-host: subprocessors are the firm's Supabase, storage and model providers. Hosted demo: privacy allows sharing with infrastructure, hosting, storage, auth, email, analytics or model providers; no named dated list.
Ask: For the hosted demo, name every processor and region. For self-host, we will inventory our own.
No foundation-model training by MikeOSS
Public claim only
Privacy: MikeOSS does not train foundation models on prompts, documents, chats or outputs. Third-party model handling, retention, logging and training follow that provider's API terms and settings. Local models stay local unless telemetry is configured.
Ask: Confirm ZDR/no-train on every API key we will use, including the hosted demo if anyone evaluates it.
Hosted usage may improve the product
Public claim only
Privacy (hosted): information may be used to understand usage and improve the product. Self-host: maintainers do not collect usage data. No separate feedback-toggle was described.
Ask: Does hosted telemetry include prompt text, and can it be disabled?
No numbered hosted schedule
Public claim only
Hosted: retain as long as needed to provide the service, maintain records, resolve disputes, enforce agreements and comply with law. Self-host: operator's own retention. Model-provider logs are outside MikeOSS control.
Ask: State hosted retention for chats, uploads and logs, or confirm we must self-host to control it.
Rights listed, process not numbered
Not confirmed
Privacy lists access, correction, deletion, restriction, portability depending on location. No 30-day certified deletion for the hosted demo was stated. Self-host deletion is the operator's.
Ask: How do we delete a hosted-demo account and provider logs, and will you certify?
Maintainers do not see self-host data
Public claim only
Privacy: self-host means maintainers do not collect account data, documents, prompts, chats, search history or usage. Hosted: maintainers may use information to operate, secure and troubleshoot. No named access log for the demo.
Ask: Who can access hosted-demo content, and is that access logged?
MFA claimed; org walls in code
Public claim only
Home: v0.3.0 adds MFA. GitHub history discusses organisation-admin deny overrides on matters. Hosted access-control documentation was not a separate admin guide in this pass.
Ask: Is SSO available on hosted, and how are ethical walls configured in self-host?
Not specified in privacy
Not confirmed
Privacy: technical and organisational measures are used; no TLS/at-rest algorithm statement. Self-host encryption depends on the operator's Supabase/storage/TLS configuration.
Ask: Document TLS and at-rest encryption for the hosted demo, and the defaults in docker-compose.
No SOC 2 or ISO claim found
Not confirmed
No SOC 2, ISO 27001 or ISO 42001 claim was found on the home page, privacy notice or GitHub README extract. SECURITY.md exists in the repo; this pass did not treat it as a certification.
Ask: Is any independent assurance offered for the hosted demo, or must we rely on self-host controls?
AGPL plus privacy; no public DPA
Not confirmed
No public terms of service or DPA for the hosted demo were found (privacy only). Self-host is AGPL-3.0. Contracting entity, governing law and liability cap are unpublished.
Ask: Name the contracting entity, provide Terms/DPA for any hosted use, and confirm AGPL obligations for internal self-host.
Depends on deployment
Public claim only
Self-host transfers are those of the firm's chosen providers. Hosted demo hosting country is not stated; model providers (OpenAI/Anthropic/Google) typically process outside Australia.
Ask: Where is app.mikeoss.com hosted, and which countries will our model traffic enter?
No published notification SLA
Not confirmed
Privacy does not state a customer-notification period for a personal-data breach. SECURITY.md exists in the repository.
Ask: What is the incident-notification period for the hosted demo, and who is the security contact?
Open-source changelog
Public claim only
Home lists version posts (v0.1.0 April 2026 through v0.4.0 July 2026). Privacy may be updated by posting. No contractual change-notice for a hosted service.
Ask: How do we pin a release for production self-host, and how is hosted-demo change communicated?
Self-host data stays with operator
Public claim only
Self-host: data is in the firm's database/storage; exit is ordinary backup/export. Hosted: deletion/export process is not numbered beyond general privacy rights.
Ask: What export format exists for hosted-demo workspaces, and when is it purged after we leave?
MCP and Slack
Public claim only
Changelog on the home page and GitHub: Slack plus any MCP server, with two self-host setup pathways. Connectors can send matter text to third systems if configured.
Ask: Which connectors are enabled by default, and how do we require per-action approval?
Case research via CourtListener
Public claim only
CourtListener integration is named for legal research. Open-web browsing is not separately described. Self-host could add other tools.
Ask: Does the assistant browse the open web, or only CourtListener and uploaded documents?
Workflows and MCP tools
Not confirmed
Reusable workflows and MCP connectors can run multi-step actions. Guardrails and human-approval defaults for consequential actions were not documented on the privacy page. Hosted demo should not be used for client actions.
Ask: Which actions can run unattended, and how do we require a human step before any external write?
Citations claimed; no mandatory gate
Public claim only
Tabular review is described as every cell cited to a page and quote. No contractual requirement that a lawyer accept output before export. Professional responsibility remains with the firm.
Ask: Is there an in-product review acknowledgement, or do we rely on firm policy?