Your demo request.
When you request a demo, Mat3 stores the contact details, company information, plan preference and message you submit. The Mat3 team uses these details to respond about the demo. These requests are held privately, separately from project documents, and cannot be read by other companies through the workspace.
Sending a demo request does not subscribe you to marketing, take a payment or book a meeting automatically. Please keep confidential project details out of the message; you can add private project files after signing in.
Private files and team access.
Original files are stored privately with a checksum. Access requires a signed-in company member with access to the project. Cloud authentication uses verified email and server sessions. In local development, the workspace and files are saved on the computer running the app.
The hosted pilot uses Amazon Cognito for company sign-in and AWS private storage and a database in the United States (Northern Virginia). Vercel serves the public website and workspace interface. Files are available through authorised workspace requests; the file bucket is not public.
Services that process documents.
For live processing, relevant document pages and images are sent to Google Cloud Document AI for OCR, and extracted text with source references is sent to Gemini on Vertex AI for structured extraction and interpretation. The processing locations and model version are recorded in deployment configuration and review history.
The current pilot sends OCR requests to Google Cloud's EU location and Gemini requests to its EU endpoint. Only the selected document scope is used for the review. Please upload project documents that your company is authorised to process.
Processing logs use identifiers, states and timings. Document contents and credentials are excluded from routine application logs.
Records kept for the project.
Approved requirements, reviewed submissions, machine findings, reviewer corrections, decisions and exported report snapshots are preserved as versioned records. Removing a member revokes access while keeping their past decisions attached to their identity.
Use company settings to manage staff access and processing allowances. Archive a project when it is no longer active; its existing review history remains available to authorised members.