MAG OptiAI

MAG OptiAI Policies

Subprocessors & Service Providers

MAG OptiAI uses third-party providers to operate the website, Pro Console, billing, authentication, AI workflows, infrastructure, hosting, vector retrieval, support, analytics, and reliability.

This list reflects the current launch/beta architecture and should be reviewed before enterprise contracting. Provider terms may change, and customers should review each vendor's current terms directly. This page is informational and is not itself a signed DPA.

Provider list

Purpose

Supported AI processing, generation, embeddings, extraction assistance, explanations, and comparisons.

Typical data categories

Prompts, user questions, retrieved context, document text, structured inputs, summaries, AI outputs, and metadata needed to deliver the AI feature.

Notes / verification status

OpenAI's current business/API terms say customer content is not used to develop or improve services unless the customer explicitly agrees. Customers should review the linked current terms directly.

Purpose

Backend infrastructure, storage, compute, and artifact storage where configured.

Typical data categories

Account, project, and workspace metadata; uploaded files; generated artifacts; logs; result artifacts; operational metadata; and backend records where configured.

Notes / verification status

Region and storage behavior depends on MAG OptiAI's deployed configuration.

Purpose

Authentication, user management, sessions, and account identity workflows.

Typical data categories

Name, email, phone where configured, authentication identifiers, session/auth metadata, and device/IP/usage metadata depending on configuration.

Notes / verification status

Clerk's role depends on Clerk terms and the data category; this page does not classify Clerk as only a processor in every context.

Purpose

Payments, subscriptions, billing, invoices, payment status, and tax/payment support where configured.

Typical data categories

Billing identifiers, customer profile, payment metadata, subscription state, invoice records, and transaction metadata.

Notes / verification status

Payment method handling is processed through Stripe. MAG OptiAI does not intentionally collect or store full payment card numbers in its own application systems.

Purpose

Frontend hosting, deployment, edge/runtime hosting, frontend request processing, and analytics where configured.

Typical data categories

Request metadata, IP/device/browser metadata, logs, and analytics depending on configuration.

Notes / verification status

Analytics and request logging depend on the deployed Vercel configuration.

Purpose

Vector retrieval, document chunk indexing, embedding/vector metadata, and retrieval support for DocAI or similar workflows.

Typical data categories

Embeddings/vectors, document chunks or references where configured, retrieval metadata, and project/document identifiers.

Notes / verification status

Qdrant publishes a Qdrant Cloud DPA. MAG OptiAI should confirm which deployed Qdrant mode, account, and terms apply before enterprise contracting.

Purpose

Website and Pro Console analytics where configured.

Typical data categories

Page-view events, marketing-event metadata, product or workspace event categories, device/browser information, approximate traffic data, and timestamps.

Notes / verification status

Included because the codebase contains Google Analytics / gtag integration. Analytics behavior depends on measurement configuration.

Enterprise review

Customers evaluating procurement, vendor security review, custom terms, or a signed DPA should contact MAG OptiAI before relying on this launch/beta list as a contracting exhibit.

Additional data-flow, retention, and request-path details are described in the Privacy Policy and Data Processing & Retention policy.

Related policies