Know where the information goes.

Separate the workspace from its connected services.

Your DataRoom

A room is a folder on your machine with its own memory. The local workspace holds the project context and records created through MindrianOS. Review what you choose to connect, publish or export.

Theo

Theo reads problem shapes, not content. The method service uses problem types and method references, with a random installation identifier. This boundary describes the Theo connection; it is not a promise about every other provider. See Theo’s role and connection.

Claude and other providers

MindrianOS runs within a Claude surface. Information used in that session may be processed by your AI provider under your account settings and its terms. Review those settings and any institutional requirements before adding sensitive material.

Exports and other destinations

Review the destination and content before sharing a report, publishing material or connecting an external service. A local source file does not make a published copy private.

Accounts, requests and website activity.

Sign-in and account information

Supabase handles account authentication. You can use Google sign-in or an emailed access link. The website uses session cookies to keep you signed in. It stores account information such as your email and may record the account that invited you.

Letter subscriptions

If you choose to subscribe, the subscription record includes your account, email, the consent wording, when you consented and any recorded inviter. Unsubscribing marks that subscription as unsubscribed; it does not delete your account.

Pilot inquiries

The pilot form stores your email, role and any institution or message you provide in Supabase so we can respond about a pilot. Sending a pilot request does not subscribe you to the letter.

Analytics

The website loads Microsoft Clarity for usage analytics. PostHog is also used when configured. Website navigation and interaction data can include page addresses and query parameters. These services are separate from the local DataRoom.

Earlier assistant integrations

The previous website assistant is no longer part of the page interface. Its older service endpoints remain in the application. If an older client calls them, submitted messages and supported attachments can be processed by Google Gemini. The older homepage endpoint can also send a generic problem label to Theo. Those endpoints are distinct from the account and documentation flows.

Choose the email you want to receive.

Sign-in links and account confirmations serve the account flow. Product updates and the letter require a separate choice. The subscription checkbox starts unchecked.

The consent text shown when you subscribe: “Yes, m:os may email me product updates and the m:os letter. Unsubscribe in every email.”

Account confirmation email may be sent through SendGrid when email delivery is configured. Authentication links are handled through the sign-in service.

Use the unsubscribe link in an email, or request an unsubscribe link. Unsubscribing from updates does not prevent account emails you request, such as a new sign-in link.

Ask about your particular situation.

For questions about information held by this website, account records or an institutional evaluation, contact jsagir@gmail.com.

For an institutional deployment, review the intended data, the connected providers and the applicable requirements before agreeing the scope.