Enterprise procurement · provider transparency
A code-backed inventory of third-party services MIRMC relies on or can use when specific features are enabled.
cloudflare
Canonical production runtime, edge delivery and deployment boundary.
Data classes that may be involved
supabase
Authentication, database authorization, storage and server-side application data services.
Data classes that may be involved
stripe
Agency SaaS subscription checkout, portal management and verified billing state convergence when Stripe billing is configured.
Data classes that may be involved
MIRMC's Agency flow delegates card entry to Stripe-hosted payment surfaces; this register does not claim Stripe availability for every commercial account or country.
resend
Transactional and operational email delivery when server email credentials are configured.
Data classes that may be involved
calcom
Consultation booking and booking webhook synchronization when configured.
Data classes that may be involved
lovable
AI-assisted application workflows and a secondary trusted application origin where explicitly configured.
Data classes that may be involved
openai
AI-assisted website delivery and image/content workflows when an OpenAI key and relevant feature are configured.
Data classes that may be involved
google-ai
Optional AI and external quality/intelligence services when configured.
Data classes that may be involved
groq
Optional AI model execution for configured server-side workflows.
Data classes that may be involved
firecrawl
Public-web crawling and prospect/website intelligence when the feature is configured and invoked.
Data classes that may be involved
Trust Center
Review implemented, controlled and planned enterprise controls.
Security policy
Responsible disclosure and reporting boundaries.
Privacy policy
Public privacy terms remain the legal-facing reference.
