As we expand support for publishing to non-US Autodesk Construction Cloud (ACC) accounts, our users based outside the US have asked important questions about where data is stored, when it’s processed, and what regional implications that might have. This article outlines how Informed Design stores and processes product-related data, what role ACC plays in access control, and why no building project data ever leaves your region — even when publishing or using products linked to non-US based ACC accounts.
All Product Data Is Stored and Processed in the US
All product-related data in Informed Design is stored in our US-based Informed Design service and processed using our US-based APS Automation services. This includes:
CAD files or model references
Parameters and rules
Product variations (configurations and model state representations)
Output file definitions (such as Revit Families and bills of materials)
At the time of publishing a new product or a product update, users of the Informed Design Add-in for Inventor are shown a clear notice:
By using Informed Design, your project data may be processed and stored in the US.
The notice also mentions the following limitation:
Currently, Bridge functionality is supported for Informed Design products published in US-based accounts only.
This means that as of now, ACC Bridge folder automations between non-US based ACC projects will omit Informed Design products. All other files will sync as expected.
What About Non-US ACC Accounts?
Informed Design integrates with ACC — the Files tool in Autodesk Docs — to manage access permissions, not for file storage or data regionalization. This lets your team use the familiar ACC environment to control who can work with your published products in the Informed Design Add-in for Revit and the Informed Design Web Portal.
You can now publish to any Docs project folder, regardless of the ACC account's regional data storage.
⚠️ Important: Publishing to an ACC account based in the EU, Australia, UK, Germany, Canada, India, or Japan does NOT mean product data is stored or processed in that region.
When Does Data Enter the US?
New user-defined data is submitted to our US-based service only at a few specific points.
When the user publishes a Product or Release:
Creating a Product (POST /products)
Updating a Product (PATCH /products/{productId})
Creating a Release (POST /releases)
Updating a Release (PATCH /releases/{releaseId})
These publish-related actions send and persist your product definition, CAD files or model references, input parameters, and output types to our Informed Design service, hosted in the US.
When the user submits a Variant:
Create Variant (POST /variants)
This action sends and persists your specified parameter values as constrained by the published product release, and in some cases, your chosen variant name.
Our US-based APS Automation services use this information to build your requested variant on-demand using the CAD dataset. Variant creation submits no new user-defined data to US-based services other than your request parameters, and variants contain no reference to specific building models or Revit files.
When a user requests Output creation based on a Variant :
Create Outputs (POST /outputs)
This action sends and persists the alphanumeric identifier of the variant you've specified, and your choice of output types (such as a Revit Family or shop drawings) to be created from that variant.
Our US-based APS Automation services use this information to create your requested output file on-demand using the previously-generated variant. As you'll see in the payload schema, output requests submit no user defined-data to US-based services other than your choice of variant and output file types.
When a user requests file upload based on an Output :
Create Upload Request (POST /uploads)
This action sends and persists the alphanumeric identifiers of the outputs you've specified, and your choice of upload location for the resulting files.
Our US-based Informed Design service uses this information to create files using your previously-generated outputs and place them into your selected ACC or Fusion Team folder. Upload requests submit no user-defined data to US-based services other than your choice of outputs and folder for the uploads.
What Happens in Downstream Workflows?
Once a product and its releases are published, the additional workflows described above use our US-based services, but do NOT introduce any building design or project-specific data to our system.
Instead:
Variants are created by modifying parameters and model states of the already-published release; no building-specific context is involved.
Outputs (Revit Families, shop drawings, etc.) are generated from those variants using our APS Automation engine, based on already-published product and release data.
Uploads refer to our service placing generated output files into your selected ACC or Fusion Team folder; no incoming files are transferred from your building project.
No Revit models, building geometry, or project-specific design context are ever uploaded to or processed by the Informed Design or APS Automation services.
What This Means for Data Privacy and Sovereignty
Even when publishing to a non-US ACC account:
Your building project files stay in your region by design, thanks to ACC Regional Data Storage.
Your published product data is stored and processed in the US.
After publish time, all downstream activity is driven by users acting upon the already-published product and release data.
With this architecture, your building project-specific information remains within your chosen ACC data region.
For Developers and Partners
If you want to dive deeper into exactly what data is transmitted, when it’s sent, and how each request is structured, our full API documentation provides a complete technical reference — including endpoints, payload schemas, and response formats.
Explore the Informed Design API Reference.
We hope this helps you and your team make legally and operationally compliant decisions when working with Informed Design across international projects. Still have questions? Leave a comment below or visit the Informed Design Forum.
View full article