Privacy Policy
NeoArc is security-first. Collecting personal data is not part of our business model. This policy covers the marketing website and the three application editions (Connected, Enterprise, Sovereign), explaining exactly what is and is not collected in each context.
NeoArc is a security-first company. Collecting personal data is not part of our business model and never will be. We build architecture tooling for professionals working in sensitive environments, and we designed our products accordingly: your data stays on your machine, under your control.
This policy explains, in plain language, what NeoArc collects, where it is collected, and why. It covers two distinct contexts: the NeoArc marketing website and the NeoArc Studio desktop application. The application ships in three editions with different network capabilities, and data collection varies accordingly.
Scope
This policy covers two separate contexts with different data collection behaviours.
| Context | What It Is | Data Collection |
|---|---|---|
| Marketing Website | The public NeoArc website (neoarc.io) | Anonymous analytics via Google Analytics and Azure Application Insights |
| NeoArc Studio Application | The desktop application installed on your machine | Varies by edition (see below) |
Part 1: Marketing Website
The NeoArc marketing website collects anonymous visitor statistics to help us understand how the site is used, which pages are visited most, and where visitors encounter problems. This data is collected through two services:
What the marketing website does not collect
Cookies
The marketing website uses cookies as part of the analytics services described above. These cookies are used solely for anonymous usage measurement and site improvement. You can control or block cookies using your browser settings.
Part 2: NeoArc Studio Application
NeoArc Studio is a desktop application that runs on your machine. Your architecture content (pages, diagrams, schemas, models, ADRs, and all other workspace files) is stored locally on your filesystem. The application ships in three editions, each with different network capabilities and data collection behaviour.
| Edition | Network Capability | Telemetry |
|---|---|---|
| Connected | Outbound internet access, Azure publishing, external Git remotes, remote LLM integration (future) | Opt-in only (off by default) |
| Enterprise | Internal network only. Connects to on-premises Git servers and DevOps infrastructure behind firewall controls. No outbound internet. | None |
| Sovereign | Fully air-gapped. Zero network capability. No external or internal network calls. Single executable installer with all resources bundled. | None |
Connected Edition Telemetry
The Connected Edition includes an optional telemetry setting that is off by default. When a user explicitly opts in, the application may send:
Enterprise Edition
The Enterprise Edition operates on internal networks only. It has no outbound internet access and does not send telemetry, usage data, or error reports to NeoArc or any external service. All network activity is confined to on-premises infrastructure (Git servers, DevOps tooling) behind your organisation's firewall controls.
Sovereign Edition
The Sovereign Edition is fully air-gapped. It makes zero network calls of any kind, neither to external services nor to internal network infrastructure. The application is distributed as a single executable installer with all resources bundled. There is no telemetry, no update mechanism, and no network capability. This edition is built for defence, classified, and critical infrastructure environments where network isolation is a hard requirement.
What We Never Collect (All Editions)
Regardless of edition, NeoArc Studio never collects the following:
| Category | Details |
|---|---|
| Architecture Content | Pages, diagrams, schemas, models, ADRs, endpoints, or any workspace content |
| Personal Identifiers | Names, email addresses, IP addresses, or contact details |
| Keystrokes or Inputs | Passwords, credentials, or text entered into the application |
| Project Metadata | Project names, file names, folder structures, or repository URLs |
| Advertising Data | NeoArc does not display ads, use ad networks, or build marketing profiles |
Data Ownership
Your work belongs to you. NeoArc Studio does not claim ownership over your content. We do not inspect, process, or transmit your architecture content for analytics, training, marketing, or any other purpose. Your workspace files remain on your filesystem under your control.
This is not a concession. It is the design. NeoArc is built for environments where data sovereignty is non-negotiable, and that principle applies to every edition.
Data Sharing
We do not sell, rent, or trade data. Anonymous analytics data from the marketing website and from opted-in Connected Edition users may be processed by trusted third-party services (Google Analytics, Azure Application Insights) solely for the purposes described in this policy.
Changes to This Policy
If we change how data is collected or used, we will update this policy clearly and openly. Material changes will be communicated through the application release notes and the NeoArc website.
Questions or Concerns
If you have any questions about privacy, data usage, or anything in this policy, we encourage you to reach out. Transparency matters to us, and we are happy to explain how things work.