Privacy notice

How the portal handles data.

Billed via Microsoft Marketplace
Last updated: 2026-05-10
This portal is designed to collect only the minimum inputs required to produce an assessment run and its output files.
Back to portal
Quick links
FAQ
Common questions
Support
Ask Fop
Architecture
Deployment paths
RFS
Request a scenario
Security
Report concerns
Privacy
Data handling
Terms
Usage conditions
Accessibility
Feedback channel
Partners
CSP marketing
Legal
Policies & agreements
Data you provide
  • Scenario selection and assessment parameters (e.g., target domain).
  • Contact details when required to generate an assessment.
  • Optional notes you enter (avoid secrets).
Personal data categories can include business contact details (such as work email), organization identifiers, and operational request metadata needed to deliver your requested assessment.
Generated data
  • Run status/progress metadata.
  • Generated report/result files made available for download.
How we use and share data
  • We use data to operate the portal, run requested assessments, generate deliverables, and provide support.
  • Access is limited to authorized personnel and approved subprocessors required to provide the service.
  • We do not sell customer personal data.
  • Where required by law, we may disclose limited data to competent authorities.
See Subprocessors and Data Processing Agreementfor processing roles and commitments.
Evidence uploads
When enabled for a scenario, evidence uploads are performed directly from your browser to your designated storage workspace. The portal UI does not store uploaded evidence files in the application backend. Generated output files and the operational metadata needed to deliver the service are handled separately under the retention window below.
Cookies and browser storage
  • This portal uses browser storage (localStorage/sessionStorage) for functional settings such as UI preferences and run continuity.
  • We do not use browser cookies for advertising purposes in this portal experience.
  • If operational cookies are introduced in future releases, this page will be updated with their purpose and lifetime.
Retention
  • Request metadata: 365 days.
  • Audit trail: 730 days.
  • Generated output files created for your request: up to 365 days.
These windows apply to run metadata, audit records, and generated output files. They do not mean the portal stores uploaded evidence files in the application backend. The windows mirror the retention commitments in the Data Processing Agreement. If you need earlier removal or an account-level data deletion review, use the support contact referenced by your engagement.
Security safeguards
  • Encryption in transit and at rest for service data.
  • Role-based access controls and least-privilege operational access.
  • Logging and audit trail controls for security and support operations.
Additional details are available on the Security page.
Your rights and requests
You can request access, correction, deletion, or export of applicable personal data through the engagement support channel.
See Data subject requests for request handling guidance.
Payment data
Billing for this service is performed by Microsoft through the Microsoft Commercial Marketplace. Microsoft, not MSC/LuiT, processes payment instruments, taxes, invoices, and refunds for the subscription. The portal receives only the subscription identifier and metering events required to operate your plan.
Contact
For privacy questions or data requests, use the support contact referenced by your engagement or the support channel on Support.
2026 LuiT || ₷©®•Modern Support Consult•Hosted on Microsoft Azure + GitHub Enterprise
FAQSupportArchitectureRFSSecurityPrivacyTermsAccessibilityPartnersLegalTRIX
Support details(version & routing)
APImsc-portal-api-d7g5fudfa7eufufa.westeurope-01.azurewebsites.net
Builda30883e1@20260812T141507Z
LaneMicrosoft Commercial Marketplace (ISV Success)
Billing & licensing(public summary)
This portal provides structured assessments and actionable guidance. Results depend on what is observable and what changes are implemented in your environment.
Results depend on inputs
  • Online scenarios measure available signals (for example: public DNS records) and report what is observable at the time of the run.
  • Guidance describes recommended steps; applying them may require configuration changes, permissions, vendor behavior, and timing.
  • Outcomes are influenced by multiple moving parts; we focus on measurable improvements, defensible choices, and clear evidence you can act on.
How costs are calculated (customer view)
  • Microsoft Commercial Marketplace: Microsoft is the merchant of record. Microsoft handles billing, taxes, invoicing, refunds, plan changes, and cancellation under your Microsoft Customer Agreement. Manage the subscription from Azure Portal → SaaS subscriptions.
  • Plans & metering: per-plan price and any metered dimensions are visible in the Marketplace offer at checkout. Charges appear on your Microsoft invoice.
  • Customization-supported scenarios: scope and pricing are confirmed with you (in writing) before work begins, and only change if scope assumptions materially change.
  • Taxes are calculated and collected by Microsoft. Marketplace invoices are the source of truth.
Fairness & exceptions
Reconciliation is based on the agreed deliverables and the available inputs. If customer-side deliverables (access, approvals, change windows) are delayed after being identified as blockers, we may pause measurement or re-baseline the delivery window. We prefer fast, transparent review and adjust when the facts support it.
License scope
Some scenarios and deeper artifacts are intentionally restricted in public mode. For customization-supported engagements, licensing/procurement and exact deliverables are confirmed before work begins. If you need enterprise-wide terms or invoicing, use Support.
Why Modern Support Consult
Microsoft-first, on-prem friendly
MSC is built around Microsoft infrastructure and cloud operations, with on-premises realities treated as first-class. Built by an Exchange-focused specialist (~30 years IT; ~20 years Microsoft messaging & integration).
Curated, regulated guidance
Not random tips: curated and cross-compared to reduce noise and keep actions defensible.
Benchmarking + checklist outputs
Scenarios benchmark posture and produce checklist-style remediation aligned with mainstream security/ops methods.
Quadral method (Codex / Metaflow-ready)
Evidence → traceable outcomes: signals, checks, decisions, guidance, exceptions. Designed for consistent benchmarking and audit-friendly reasoning.
Use Close to return to the portal.