Operator
FIRST CLASS HOLDING s.r.o.
The legal and operating carrier of the public web and the subsequent mandate entry.
Legal / Privacy
The privacy policy defines the processing basis, mandate boundaries, and retention discipline for EX AI HUB.
EX AI HUB operates in a due diligence context where personal and corporate data may enter a mandate. This page explains the privacy boundaries that apply before and during mandate intake.
- Each processing activity follows a defined decision context, not an open-ended research grab.
- Minimisation, redaction, and retention classes are part of case discipline, not an afterthought.
- Privacy questions move through a named contact and a mandate-specific review path.
Privacy boundaries
Privacy framing stays tied to a concrete decision, not to open-ended signal accumulation.
In due diligence, the legitimacy of processing depends on a clear purpose, limited boundaries, and a disciplined review process.
What this page covers
Core privacy guardrails
This summary outlines the privacy baseline for the public site and mandate intake.
- Purpose framing
- Each processing activity is tied to an appointment, transaction, onboarding, or governance review.
- Data categories
- Collected data stays limited to what is needed for a decision-grade review.
- Retention discipline
- Review windows, legal hold, and cleanup steps remain separated and readable.
- Request handling
- Privacy questions are routed through a named contact and a mandate-specific review path.
Decision context
The site does not support open-ended surveillance
Personal and corporate review are framed as risk-based due diligence tied to an explicit business decision.
Sensitive subjects
Sensitive categories and higher risk require a narrower review frame
If a mandate raises special-category or jurisdictional risk, the review boundary is calibrated before intake proceeds.
Export discipline
The final delivery carries only the identifiers needed for the decision
Redaction and do-not-include discipline remain part of the review layer, not a last-minute manual improvisation.
Operational privacy
The privacy policy stays readable from intake through case delivery.
The page explains what is typically processed, why, and for how long, without making promises the operating model cannot keep.
Practical translation
How privacy guardrails apply in practice
Policy text matters, but privacy boundaries also need to hold in day-to-day case handling.
Collected inputs
Typical inputs include submitted subject context, supporting materials, and operational metadata needed for case intake and delivery.
Processing basis
The legal basis and safeguards are assessed against the actual decision context, not only the module name.
Access boundaries
Access follows tenant, role, and review need; sensitive materials do not circulate without a named owner.
Retention and deletion
Retention follows review windows, legal necessity, and the cleanup discipline confirmed for the mandate.
Minimisation
Collecting “just in case” is not an acceptable baseline
If a data point cannot support the review or the final decision, it does not stay in the active review set.
Human review
Person-related inferences do not reach the final delivery without a review checkpoint
AI-assisted throughput may accelerate extraction, but privacy-sensitive final statements remain under analyst control.
Client requests
Privacy requests need a named owner and route
Questions about mandate boundaries, retention, or safeguards are captured in a named review path, not as a side note.
Contact and escalation
Legal, privacy, and procurement questions have a named contact path.
The legal operator and contact route remain visible for policy review, procurement, and mandate preparation.
Contact points
Who leads legal review and next steps
Sensitive mandates keep legal, privacy, and procurement follow-up on one named contact path.
- Legal operator
- FIRST CLASS HOLDING s.r.o.
- Contact lead
- Mgr. Karol Szekely handles the initial contact and coordinates the next mandate-specific step for privacy or procurement questions.
- Recommended route
- Use the contact or proposal path to confirm mandate context first, then finalize DPA or contractual addenda where required.
Privacy policy
Current legal document
This document is the active reference in the current language.
Current documentTerms of use
Open the related legal document
The matching document stays available for the same legal, privacy, and procurement review.
OpenCookies
Open the related legal document
The matching document stays available for the same legal, privacy, and procurement review.
OpenDPA and privacy contact
Open the related legal document
The matching document stays available for the same legal, privacy, and procurement review.
OpenLegal documents
Related legal pages
All legal pages remain separately accessible so legal, procurement, or security teams can open them directly from the public site.
Privacy
Current legal document
This document is the active reference in the current language.
Current documentTerms
Related legal document
The matching document stays available for the same legal, privacy, and procurement review.
Open terms of useCookies
Related legal document
The matching document stays available for the same legal, privacy, and procurement review.
Open cookie policyRelated review pages
Legal review stays connected to security, pricing, and the contact path.
Use these pages when published legal text needs to be matched against operating controls, commercial framing, or the next contact step.
Contact
Use the contact path for mandate-specific legal or procurement questions
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
If the legal documents raise open questions, resolve them before the mandate moves forward.
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.
- The public layer stays free of intake workflow and detailed commercial branching.
- The next step is confirmed only after access approval and portal registration.
Access frame
- Invite-only entry
- Detailed workflow inside the member area