Public use
Informational site
The site explains modules, review method, and trust framing, but it does not itself open a case.
Legal / Terms
The public site is informational. A binding mandate begins only after mandate boundaries, commercial terms, and the governance path are explicitly confirmed.
Use boundary
The terms separate the informational layer of the site from the point at which binding obligations arise between the client and FIRST CLASS HOLDING s.r.o.
What matters
The terms summarise the public baseline; concrete obligations are confirmed in proposal and onboarding documents.
No public advice
Public pages explain capability and review method; they do not answer a client’s specific investment, legal, or compliance position.
Written confirmation
Scope, timeline, deliverables, and commercial terms are confirmed in writing before the engagement starts.
Input responsibility
Clients may send only materials they are authorized to access, without hiding critical usage restrictions.
Operational terms
The page explains what is expected from the user, when the formal handoff begins, and where special contractual requirements are handled.
Terms in practice
The terms define the boundary between the public site, proposal, and onboarding.
Using the public site does not create an advisory relationship or an entitlement to a specific output.
The proposal stage aligns mandate boundaries, timeline, billing, and governance expectations before launch.
DPAs, confidentiality addenda, and procurement-specific requirements belong here, not in public copy.
Users may not attempt to bypass technical controls, extract content outside its intended use, or disrupt operations.
Mandate boundary
This protects both the buyer and the operator: it stays clear when this is informational browsing and when it becomes a real service commitment.
Protected content
The institutional framing, copy, and structure remain part of the protected brand and product layer.
Special terms
Procurement, invoice-later, DPA, or confidentiality addenda are confirmed against the actual mandate boundaries and billing context.
Contact and escalation
The legal operator and contact route remain visible for policy review, procurement, and mandate preparation.
Contact points
Sensitive mandates keep legal, privacy, and procurement follow-up on one named contact path.
Privacy policy
The matching document stays available for the same legal, privacy, and procurement review.
OpenTerms of use
This document is the active reference in the current language.
Current documentCookies
The matching document stays available for the same legal, privacy, and procurement review.
OpenDPA and privacy contact
The matching document stays available for the same legal, privacy, and procurement review.
OpenLegal documents
All legal pages remain separately accessible so legal, procurement, or security teams can open them directly from the public site.
Privacy
The matching document stays available for the same legal, privacy, and procurement review.
Open privacy policyTerms
This document is the active reference in the current language.
Current documentCookies
The matching document stays available for the same legal, privacy, and procurement review.
Open cookie policyRelated review pages
Use these pages when published legal text needs to be matched against operating controls, commercial framing, or the next contact step.
Contact
The contact page keeps the operator, introduction lead, and next-step path visible when the published documents do not resolve the review.
Open contactNext step
The public web remains a briefing layer. Request access and, once approved, the detailed workflow, intake paths, and next steps become available inside the member area.
Access frame