Skip to main content

What AIS does not do - boundaries

Clear boundaries protect both the bank and AIS. This page states typical splits; your contract and deployment may differ.

AIS does not typically​

  • Replace your core banking system of record for customers and accounts.
  • Act as your legal entity in front of regulators-your bank remains accountable.
  • Run your HR, procurement, or enterprise ITSM-unless explicitly scoped (rare).
  • Publish customer PII in documentation portals-never paste real customer data into tickets or docs.

The bank still owns​

  • Regulatory filings and licence obligations.
  • Customer consent and privacy notices for how data is used.
  • Credit policy content and committee decisions.
  • Third-party vendor relationships outside AIS.

AIS typically operates (platform)​

  • Service availability of the AIS components you purchased.
  • Model deployment pipelines as contracted (who pushes approved models to production).
  • Product behavior shared across customers at the platform layer.

When the split is unclear​

Use this phrase with your internal stakeholders and with AIS:

“Confirm with your AIS account team.”

Examples of common gray areas: data residency, subprocessors, incident notification timelines, and custom scoring fields for niche products.

:::caution Unknown until contracted

Anything not explicitly in your order form, DPA, or technical schedule should be treated as unknown here-not as a promise.

:::

Next: Data handling · Bank and AIS roles