How MAIC handles project data.

Overview

MAIC helps mining, manufacturing, materials, semiconductor, battery, laboratory, and technical teams organize uploaded project files and ask grounded questions over those files. This policy explains what we collect, why we collect it, and how we handle project content.

Information we collect

• Account information: name, email address, authentication identifiers, and organization membership details.
• Project content: files, notes, observations, protocols, results, papers, metadata, labels, chat prompts, answers, citations, and project activity created in MAIC.
• Technical information: device, browser, log, usage, diagnostic, rate-limit, and security information needed to run and protect the service.

How we use information

We use information to provide the MAIC workspace, authenticate users, create searchable project corpora, retrieve relevant chunks, generate grounded answers, maintain chat history, improve reliability, prevent abuse, and support users.

AI processing

MAIC extracts text from supported files, chunks it, creates embeddings, and retrieves relevant excerpts when a user asks a question. Retrieved context and user prompts may be sent to configured AI model providers through the MAIC AI layer. MAIC is designed so answers are grounded in retrieved source text and can cite the documents used.

Model training

MAIC does not use customer project content to train MAIC-owned foundation models. Handling by external model providers depends on the provider and deployment configuration selected for the workspace or environment.

Storage and security

MAIC supports local filesystem storage and Supabase-backed storage. We use access controls, authentication, project scoping, and operational safeguards appropriate to the deployment. No system can guarantee perfect security, so teams should avoid uploading content they are not authorized to process in MAIC.

Sharing

We share information with service providers only as needed to operate MAIC, such as authentication, storage, hosting, email, analytics, and AI model processing. We may disclose information when required by law, to protect MAIC or users, or as part of a business transaction.

Retention

We keep account, project, artifact, chunk, and chat records for as long as needed to provide the service, meet legal obligations, resolve disputes, maintain security, and support backups. Deleting projects or documents removes them from the active workspace according to the product workflow and deployment configuration.

Your choices

Users may update account details, delete documents or projects where the product permits it, and request help with account or data questions. Organization administrators may control member access according to the workspace configuration.

Contact

For privacy questions, contact the MAIC team through your workspace owner or support contact.