No sensitive data in the first check; start with data classes, sources and responsibilities.
Security & Procurement
Clarify security and procurement before the AI pilot.
For US and international teams that do not want a useful AI initiative to stall in security review, procurement or privacy review. Tirion surfaces data classes, roles, review points and buyer material early.
Available for procurement and privacy review after scope.
Microsoft 365/Azure-first; Azure OpenAI only after review.
No customer data needed in forms, score or early review.
Business lead, IT/security lead and approval boundaries are named.
Human review before sensitive processing, exceptions or pilot expansion.
Scope, sample SOW, FAQ, data handling notes and responsibilities.
Safe sequence
Clarify first, deepen later.
This overview keeps the entry small: public check, triage, scope review and only then project work with documented approvals.
Website, resource or AI check captures minimal context only.
Tirion classifies use case, data class, responsible people and review need.
Roles, data access, DPA/SCCs and tooling are confirmed before deeper work.
Customer-specific material, pilot scope or buyer material is created only after review.
Which data does Tirion need?
The first check does not require sensitive data. Tirion starts with patterns, data classes, system assumptions and responsibility context.
- No customer data in the AI check
- Data classes before access
- Sources and responsibilities before ingest
- Review before sensitive processing
When are DPA/SCCs available?
Tirion prepares typical procurement questions early: scope, data handling, responsibilities, DPA/SCCs, SOW and security review.
- Send a procurement or security question via contact, 30-minute call or one-pager.
- Tirion clarifies scope, data classes, roles and affected systems.
- DPA/SCC and buyer material are prepared for the agreed scope.
- Approval, SOW and review points are documented before project work.
Which tools are used?
The work is Microsoft-first: Microsoft 365, Azure, identity, access, logging and operations are reviewed before tool or model decisions.
- Microsoft 365 and Azure context
- Azure OpenAI only after scope
- Identity and permissions as baseline
- No tool lock-in in the first check
Who is the contracting party?
Security, privacy and procurement questions go to kevin.geiger@tirion.cloud or through the contact form. They move into a review path, not a generic sales queue.
- Tirion LLC, a US-registered limited liability company.
- Registered office: 30 N Gould St, Sheridan, WY 82801, United States.
- Buyer material covers scope, roles, data handling notes, DPA/SCC questions and sample SOW structure.
- Final contracting, venue and review details are confirmed in the customer agreement.
What does Tirion not need before scope?
- No customer data, patient data or confidential documents.
- No admin access, tenant dumps or production data.
- No internal policy files in the first check if data classes and responsible people can be described.
- No tool or model decision before data class, approval and responsibilities.
Is Tirion legal counsel?
No. Tirion structures technical, operational and management decisions. Legal or privacy counsel remains responsible for legal assessment.
How are roles and review points handled?
AI may prepare, sort or summarize. Risk-relevant decisions need human review, clear responsibilities and traceable approvals.
- Business lead
- IT/security lead
- Approval boundaries
- Evidence vault and review cadence