Enterprise 3D AI in Japan: data residency and compliance considerations

For many Japanese enterprises, the first question about any cloud AI tool is not about features. It is about where the data goes. This is a reasonable question, and it has a specific answer in the context of Marble Voyage.

Data residency on Tokyo-region infrastructure ¶

All processing and storage for Marble Voyage runs on infrastructure in the AWS Tokyo region (ap-northeast-1). Project files, generated meshes, texture maps, and prompt history are stored in Tokyo-region S3 buckets. Data does not leave Japan's borders as part of normal platform operation.

This matters for companies whose client contracts include data localisation requirements, and for industries where intellectual property protection is a primary concern. A product design that exists only as a 3D file is still intellectual property, and knowing where that file is stored is a reasonable requirement.

Access controls and audit logging ¶

On Enterprise plans, project access is controlled at the folder level. Administrators can restrict which team members can view, edit, or export specific projects. Access changes are logged with a timestamp and a user identifier.

Marble Voyage staff do not access customer project files except to investigate a support ticket that the customer has opened. This is stated in the Terms of Service and is enforced through access controls on the infrastructure side, not just as a policy.

Procurement and contract considerations ¶

Enterprise contracts include a Data Processing Agreement (DPA) that specifies the categories of data processed, the legal basis for processing, and the sub-processors involved. The DPA is available for review before signing. If your procurement team requires specific clauses, the enterprise sales team can discuss amendments.

SLA-backed uptime at 99.9% is included in Enterprise contracts. Planned maintenance windows are announced at least 72 hours in advance via the status page and by email to the account administrator. Unplanned downtime is reported on the status page within 15 minutes of detection.

Starting an enterprise evaluation ¶

The typical enterprise evaluation runs over four weeks. The first week is a scoping call to understand the use case, team size, and compliance requirements. Weeks two and three are a supervised trial with a dedicated account manager. Week four is a review call and contract discussion.

To start an evaluation, use the contact form on the site or call 092-306-9418 during business hours (Monday to Friday, 10:00-18:00 JST). The enterprise sales team is based in Fukuoka and responds to all enquiries within one business day.

Data residency is not a differentiating feature. It is a baseline requirement for serious enterprise adoption in Japan, and it should be verifiable, not just claimed.