Turn service commitments
into clear arrangements.

Record availability and incidents for specified services as agreed. Review model, endpoint, contract and dependency changes, and deliver incident records, change lists and periodic reports. Monitoring targets, frequency, alerts and response scope are agreed in advance.

For changes affecting cover, record notification and acceptance separately; a reported change is not automatically insured. After an incident, organize timelines and required information within the engagement scope. The insurer or its authorized representative determines the payout.

Monitoring alerts do not replace claim notification. Continuous recording does not mean round-the-clock human support or guaranteed recovery.

Notify promptly: Contact the designated claims channel within policy deadlines, retain original records and take reasonable steps to reduce loss.

Verify the event: Check the agreed subjects, timing and rules, and submit the required declarations and evidence. aimam provides information support within its engagement scope.

Assessment & payment: Handled by the insurer or its authorized representative. Check the payment timing for customer compensation, backup procurement and insurance proceeds separately.

Request review through the agreed channel, checking source information, measurement rules and processing versions. If the error is in our work, we assess its impact, make agreed corrections and retain a change record. Where delivered information is affected, we assist with authorized corrections and handover.

The service agreement specifies scope, review procedures and responsibilities. Insurance decisions rest with authorized institutions and do not replace aimam's responsibility for its own commissioned work.

Service termination and insurance expiry are confirmed separately. Hand over delivered reports, available incident records and open matters as agreed. Specify further assistance, fees, withdrawal of access, and data retention and deletion arrangements.

Past incidents, open claims and subsequent recoveries remain subject to their respective documents. Ending a paid service does not mean all records are immediately deleted or that further support is free indefinitely.

One incident does not automatically trigger all three covers. First assess the outage and customer compensation. Valid credits reduce receivables; only the remaining eligible debt enters the credit loss assessment. GPU residual value is assessed separately at the agreed end date, subject to equipment condition and disposal requirements.

Record backup costs, contractual compensation, parametric payouts and recoveries separately. Coordination with other cover follows applicable law and policy terms; do not assume all payments are added or all deducted. The same actual loss is not reimbursed twice.

Buyer advance payments, unpaid rent and loan defaults are not automatically included in these covers. Multiple policies do not necessarily diversify risk; shared failure points and funding pressures still need review.

With authorization, we can work with your existing broker and monitoring team to review contracts, coverage and records. aimam provides agreed technical facts and information support. Recovery and backup procurement remain with the client's authorized decision-makers and technical providers; appropriately qualified and authorized institutions handle insurance arrangements and claim decisions.

Institutions can commission underwriting information packs, risk concentration maps and loss scenario reports. These review shared failure points, relevant revenue or liability amounts, customer concentrations and maturity profiles, stating data coverage, sources and unconfirmed items.

Related suppliers or fees for arranging transactions, if involved, are disclosed in advance along with relevant authority. Reports are not insurance quotations, credit ratings or financing guarantees.

Start with your entity's role, project region, service or asset scope, contractual commitments and existing cover. Detailed contracts, operational and financial information are exchanged after confidentiality, purpose and authorization are agreed. User conversations with models are not required by default.

Agreements specify recipients, access rights, retention, cross-border processing and deletion rules. Insurance-related data use does not automatically include investment analysis, transaction introductions or other purposes. Additional uses require separate authorization.

aimam focuses on compute risk analysis, coverage design and monitoring support. Appropriately qualified and authorized institutions handle insurance placement, underwriting and payment. The formal documents define the specific scope.

Coverage regions, insurance products and applicant entities require individual confirmation. Website languages are for readability, not an indication of local availability. Website information is not coverage in force.