Local-first runtime
Avaryn is designed to run locally on the operator’s own machine. Inputs, intermediate computation, and exported artifacts are intended to stay local unless a workflow explicitly uses connected third-party systems.
Connected systems
When a workflow uses connected tools such as email, calendars, issue trackers, or other external services, the relevant requests and resulting records necessarily interact with those systems. Their own privacy and data-handling rules still apply.
Contact information
If you email [email protected], we receive the information you choose to send so we can respond, coordinate access, and support the private alpha.
Private-alpha changes
Avaryn is still in an internal testing phase. The product surface, deployment options, and privacy language may evolve as we expand testing and move toward broader distribution.