AssembleJS privacy policy

Revision 1

AssembleJS is a framework and development tool, not an application data service operated by Ayers Electronics Inc. The application you build and the services you connect decide what data they receive, keep, and send.

Application requests

An application's AssembleJS API code can read the request data delivered to it, including query values, a request body, headers, and cookies. The application author controls that code, its responses, and whether any of that data is stored or sent elsewhere. Pages and services do not receive the full request as a hidden second path.

Remote assemblies

A project can compose an assembly from another server only after its configuration declares that remote origin. For each remote, the project can name the visitor-request headers to forward and separately decide whether that remote is trusted with the page's query. Those destinations and forwarding choices belong to the application configuration; AssembleJS does not silently forward all incoming headers, cookies, or credentials to a remote.

The MCP development tool

The optional AssembleJS MCP server runs over standard input and output for an AI agent you already use. It carries no language model and no credential, and calls no inference API. It can inspect and change the project through the tools it exposes. While the project's development server runs, it may ask that server to render an assembly or page with the data the project's own services returned. The AI agent and MCP client handle what you give them under their own terms and settings.

Packages and services you choose

Installing packages contacts the registry selected by your package manager. Running or deploying an application can contact the origins and services its author configured. Those services receive ordinary connection information and whatever the application sends to them under their own privacy terms.

Contact

Questions about this policy may be sent through the Ayers Electronics Inc contact page.