IceShoreHelp
JA EN
Data & trust

Your AI answers. IceShore only holds the materials

Your own AI is what answers. IceShore holds the materials for that judgment — your configuration data (the ADL) — and passes them only when needed, within your own permissions.

Your own AI is what answers

What assesses the impact of a change is the AI you connected. IceShore never hands that judgment to a black-box model, whether its own or someone else's. Its role is to prepare and pass the materials for that judgment.

How your AI provider handles what you give your AI, including architecture data it reads from IceShore, is governed by your agreement with that provider.

What IceShore stores

What IceShore stores is your configuration data — the ADL (Architecture Description Language), a description of business meaning, processing flows, dependencies and similar details. Your AI creates the ADL locally by reading your source and documents. IceShore also stores the infrastructure-as-code files the ADL refers to (CloudFormation, Terraform, and similar). In those files, values that look like access keys, private keys, connection strings, passwords, or tokens are replaced with ***MASKED*** before they are saved. Because this works by matching known patterns, it is not guaranteed to catch every secret.

Data you store in IceShore is stored and processed in the AWS Tokyo region.

Don't put personal data, credentials, or confidential real data into the ADL. The ADL captures business meaning (a description of the configuration); it is not a place to store real data.

Encryption

Traffic between your browser or your AI and IceShore (iceshore.ai) is encrypted with TLS 1.2 or later. The connection between the app and its database also requires TLS, and the database rejects unencrypted connections.

The database and its backups are encrypted with a key that IceShore manages in AWS KMS. All file storage (Amazon S3) is also encrypted with AES-256. Passwords are stored in a form that cannot be turned back into the original.

Authentication & access scope

MCP connections authenticate with OAuth2.1 (PKCE). Authentication is required only to read your own workspace's data, and access is limited to the permissions you already hold — it never grants more. Only the official samples can be read without authentication.

Per-workspace isolation

Data is completely isolated per workspace (tenant isolation) and cannot be seen from other workspaces. When used in an organization, it is not shown to members without permission either.

Connected AI

Any AI you have authorized can be reviewed and revoked at any time from “Connected AI” in the app.

Materials for evaluating IceShore in your organization

If you are assessing IceShore for your organization, these two articles answer the usual questions.

IceShore Adoption Checklist for IT Departments: what data reaches IceShore and what does not, where AI inference happens, how to disconnect, how deleting architectures and closing accounts works, and how your architectures stay with you after the contract ends.

Security questionnaire answers (IceShore): answers to items security questionnaires usually ask about, such as data location, subcontractors, encryption, access control, audit logs, and retention and deletion.

Terms & privacy

Details such as data retention, deletion, and storage region are set out in the Data Processing Agreement, the Privacy Statement and the Terms of Service: