Authentication
Clerk
Clerk supports sign-in, user identity, and browser session management for Pro Console access.
Policies & Trust
MAG OptiAI handles uploaded files, operational datasets, saved scenarios, model artifacts, document indexes, billing state, and AI-assisted outputs. This hub brings the main policy documents together for customers, buyers, and Pro Console users.
Launch posture
Policy map
These policies remain available in the footer and are also collected here for quick review before using the Pro Console or evaluating a paid workspace.
Service scope, account responsibilities, subscriptions, acceptable use, AI-assisted outputs, cancellations, and support boundaries.
How website, account, billing, support, product-use, and workspace information is collected and used.
Uploaded files, datasets, scenarios, model artifacts, AI processing, storage controls, retention windows, and deletion behavior.
Google Analytics / gtag usage, analytics event categories, cookies, similar technologies, and user choices.
Self-serve plan coverage, billing actions, AI credit top-ups, active access, and manual billing support.
How cancellation timing works and what remains available through an already-paid billing period.
How refund requests are reviewed through support instead of automated in-product refund flows.
Data lifecycle
Product workspaces may store project setup, scenarios, uploaded files, extracted text, vector indexes, model versions, result artifacts, and usage records. Retention depends on workspace status, account type, active product use, and applicable operational or legal requirements.
Free workspaces
Active unused saved work may be archived after 30 days; archived saved work may be deleted after 7 days.
Paid or test workspaces
Active unused saved work may be archived after 90 days; archived saved work may be deleted after 30 days.
Active workspace records
Current projects, active models, and protected records may remain available while they are needed for workspace functionality.
Administrative records
Billing, security, support, audit, legal, and service-integrity records may be retained longer when required or appropriate.
Subprocessors and services
MAG OptiAI uses service providers and internal operational systems for authentication, billing, cloud infrastructure, AI processing, vector retrieval, app hosting, analytics, support, logs, and backups. Some providers are used only where a feature is enabled or configured.
Authentication
Clerk supports sign-in, user identity, and browser session management for Pro Console access.
Billing
Stripe supports checkout, subscriptions, payment method handling, and billing portal actions.
Cloud infrastructure
MAG OptiAI uses Google Cloud-backed services for backend infrastructure, product artifact storage, logs, and backups where configured.
AI processing
Supported AI workflows may use OpenAI for generation, extraction assistance, embeddings, or explanations.
Vector retrieval
DocAI document retrieval uses Qdrant-backed vector storage for indexed document chunks and grounded answer retrieval.
Public app hosting
MAG OptiAI public website and Pro Console frontends are deployed through Vercel.
Marketing analytics
The public website may use Google Analytics for page-view and marketing-event analytics when analytics is enabled.
Contact and support
Contact, privacy, security, support, and billing email aliases may route to MAG OptiAI's operational contact mailbox.
Logging and monitoring
Operational logs and diagnostics may be used for reliability, debugging, abuse prevention, and security review.
Backups and recovery
Backups or restore points may retain product or operational data for continuity, recovery, and incident response.
Provider/category
Purpose
Data involved
Clerk
Authentication and session management
Account identifiers, sign-in details, browser session information, and related authentication metadata.
Stripe
Payments, subscriptions, billing portal, invoices, and payment method handling
Billing identifiers, subscription status, payment metadata, invoice details, and related account information. MAG OptiAI does not need to store full card numbers.
Google Cloud
Backend infrastructure, artifact storage, logs, and backups where configured
Product metadata, uploaded or generated artifacts, operational logs, backup data, and service infrastructure metadata.
OpenAI
Supported AI generation, embeddings, extraction assistance, explanations, and other AI-assisted workflows
Prompts, retrieved context, document text, structured inputs, and generated outputs needed to provide the requested AI feature.
Qdrant
Vector retrieval and document index storage for DocAI where used
Indexed document chunks, vector metadata, retrieval context, and document-reference metadata.
Vercel
Public website and Pro Console frontend hosting
Frontend hosting metadata, deployment data, routing data, and platform logs.
Google Analytics / gtag
Public-site analytics when enabled
Page-view events, marketing-event metadata, device/browser information, and approximate traffic data.
Email/contact systems
Contact, privacy, security, support, and billing communications
Names, email addresses, message content, request details, and related correspondence metadata.
Logging, monitoring, and backups
Reliability, debugging, security, service integrity, continuity, and recovery
Operational events, diagnostics, identifiers, timestamps, errors, backup copies, and restore data where configured.
Pro Console acceptance
The Pro Console records the accepted Terms, Privacy, and Data Processing & Retention versions for the authenticated user and workspace account.
Acceptance record
User, account, policy versions, and accepted timestamp.
Decline path
The decline screen links to policy review, support, and sign-out.
Version control
Updated policy versions can require a new acceptance.