Security questionnaire answers (IceShore)
https://iceshore.ai/en/blog/a-p6-1/
On this page
- Answers to the questions security reviews most often ask before you start using IceShore
- Storage location and cross-border transfer
- Subcontractors
- Encryption
- Access control
- Audit logs
- Retention and deletion
- Incidents and vulnerabilities
- How AI is handled
- After your contract ends
- For fields not on this page, see our legal documents
- You can view a sample architecture without signing up
Answers to the questions security reviews most often ask before you start using IceShore
This page is for the person filling in your company's security questionnaire. It covers seven areas: storage location and cross-border transfer, subcontractors, encryption, access control, audit logs, retention and deletion, and incidents and vulnerabilities.
IceShore is provided by Launchers Co., Ltd. (10F Shibadaimon Center Building, 1-10-11 Shibadaimon, Minato-ku, Tokyo, Japan). Our Japanese qualified invoice issuer registration number is T7010001137750.
Storage location and cross-border transfer
| Item | Answer |
|---|---|
| Data center | AWS Tokyo region (ap-northeast-1) |
| Location of primary data | Japan |
| Location of backups and logs | Japan (ap-northeast-1), except for the CDN access logs for the API and MCP (kept 90 days) and inquiry emails, which are in the US (us-east-1) |
| What leaves Japan | Some information goes to providers outside Japan for payments, outgoing email, inquiry emails, and analytics. The providers and their countries are listed in our Privacy Statement |
We hold architectures (ADL data, which describes a system's use cases, dependencies, and external integrations), account information for the IceShore service, and audit logs of operations in IceShore.
There are two things we do not hold. One is credit card information, which our partner payment provider keeps. The other is credentials. Anything that looks like the value of an access key, JWT, private key, connection string, password, or token is masked automatically before it is stored.
Please do not include sensitive information in what you write in architecture descriptions, comments, and similar fields. Nothing is masked other than the parts detected as credentials above, so customer names, business partner names, and internal system names are not hidden. Masking is also not guaranteed to catch everything.
Subcontractors
Our subcontractors, what each one is used for, and where each is located are listed in our Privacy Statement and in Annex 3 of our Data Processing Agreement.
Encryption
| Area | Answer |
|---|---|
| In transit (from users) | TLS 1.2 or later |
| In transit (app to database) | TLS required. The database rejects plaintext connections, and the app verifies the server certificate |
| At rest (database) | AES-256. Keys are customer-managed keys in AWS KMS, with automatic annual rotation enabled |
| At rest (backups) | Encrypted with the same key |
| At rest (files) | AES-256 |
| At rest (share link tokens) | Stored with reversible encryption |
Passwords are hashed with PBKDF2-HMAC-SHA-256 before they are stored. Each user has a unique salt, and the iteration count is set at or above the OWASP recommendation. Password hashes cannot be reversed.
The cryptographic techniques used for password storage are HMAC and SHA-256, both listed in the CRYPTREC Ciphers List (the Japanese e-Government Recommended Ciphers List). PBKDF2 is built only from these two.
Access control
| Item | Answer |
|---|---|
| Authentication | Email address and password. Connections from AI clients use OAuth 2.1 with PKCE |
| Roles | Four levels: owner, admin, editor, and reader |
| Sharing outside the company | Share links (view only, expire after 14 days) and guest invitations |
| Guest permissions | Guests cannot edit. They can view, and on the Team plan and above they can comment |
| Multi-factor authentication | Each user can set up multi-factor authentication with an authenticator app (TOTP) |
| Failed sign-ins | 10 consecutive failures lock the account for 1 hour |
| IP address restrictions | Available on the Business plan. You can restrict where access comes from by IP address (IPv4 and IPv6 CIDR) |
| SSO, SAML, and SCIM | Not supported |
IP restrictions can be set separately for three paths: the IceShore app, share links, and connections from AI clients. Owners and admins can configure them. The audit log records each time a restriction is turned on or off and each time an IP address is added, changed, or removed. Workspaces and architectures cannot be opened from IP addresses outside the allowed list, but summary information such as the workspace name is still shown.
Only the owner can change admin roles or remove an admin from a workspace.
Share links have no password. Anyone with the URL can open them, but only to view. Comments cannot be posted through them. Only admins and editors of that architecture can issue them. They expire after 14 days and can be disabled at any time. Disabling a link is recorded in the audit log.
Audit logs
| Type | Retention |
|---|---|
| In-product activity history (viewable period) | The last 30 days on Free and Team, 12 months on Business |
| CSV export | Business |
| Database audit log | 7 years |
The records themselves accumulate with no time limit on every plan. What changes by plan is how far back you can view. The database audit log is separate from the in-product activity history. It records connections and queries.
Consent and connection records do not store IP addresses.
Operations that our operations staff perform on the production database stay in the database audit log for 7 years.
Retention and deletion
| Data | Period |
|---|---|
| Account information | Until the account is closed; anonymized at closure |
| Consent and connection records | 12 months. Deleted automatically by a daily job |
| Architectures and version history | For as long as the workspace exists. Version history keeps the latest 50 versions |
| How long data remains in backups | 7 days, the retention period of automated backups |
| Text input limit in the app | Up to 2,000 characters (including comments) |
Closing an account anonymizes it rather than deleting it. The name and email address are removed, and the account is anonymized. Architectures that person created stay in the workspace.
Send deletion requests to legal@iceshore.ai. We respond after verifying your identity.
Incidents and vulnerabilities
| Item | Answer |
|---|---|
| Contact | support@iceshore.ai (product) / legal@iceshore.ai (legal) |
| Incident notification | Without undue delay after we become aware of it, we notify the workspace owner and admins by email |
| Vulnerability reports | security@iceshore.ai |
| Vulnerability response | Initial assessment within 5 business days |
We do not commit to a deadline for completing a fix, because it depends on severity.
How AI is handled
Inference is done by the AI you already subscribe to and use. IceShore does not perform inference. IceShore's role is to prepare the material your AI reasons over and hand it to that AI.
What reaches the AI is the architecture (ADL). Credentials do not.
We do not operate any machine learning models. The “AI understanding” shown on screen is a number calculated from how much is written in the architecture. It allocates 40 points to the share of fields filled in, 30 points to the share of processes with a business description, and 15 points to the share of actors with a defined head count, then subtracts up to 15 points for the share of empty use cases. No estimation or training is involved.
Adopting IceShore does not add another AI service to the ones you use. The assessment you already made of your current AI under your internal AI usage policy still applies.
For our own work, we use Claude (Anthropic, US) to handle inquiries and for operations.
After your contract ends
An architecture's content is in a text format called ADL (Architecture Description Language). Reindeer Technology Pte. Ltd. publishes the language specification and schema under the Apache License 2.0. Exported files can be read outside IceShore, and reading them does not require a contract with IceShore. The specification is published on GitHub. https://github.com/reindeer-project/ArchitectureDescriptionLanguage
Ending a paid plan does not delete the workspace or its architectures. They remain on the Free plan, but you can no longer edit architectures, add new ones, or invite new members. Share links you have given out also stop working.
For fields not on this page, see our legal documents
| Questionnaire field | Source |
|---|---|
| Personal information collected and purposes of use | Privacy statement |
| Details of outsourcing and subcontracting | Privacy statement |
| Governing law and jurisdiction | Terms of Service |
| Name, address, and person responsible for the contracting party | Act on Specified Commercial Transactions disclosure |
Please check the recommended environment first. It assumes the latest stable version of Google Chrome and a screen resolution of 1920x1080px or higher. Below 960px wide, some features are limited.
You can view a sample architecture without signing up
Before you decide, take a look at a sample architecture in the app. No email address is needed.
https://app.iceshore.ai/workspace/sample/
We can also help if you need a more detailed questionnaire filled in. Send review questions to support@iceshore.ai.