The current execution boundary
You prepare the build snapshot outside Swift Analyzer, keep its manifest and compiler-produced Index Store in an environment you control, and point the CLI at those local inputs. The analyzer does not build the project or send it to this website.
Validation, scan, and explanation share one immutable snapshot identity. That makes the operating boundary inspectable: the evidence used for a result stays attached to the same manifest and exact subject.
Treat analysis evidence as sensitive
Local does not mean harmless. Build artifacts and analyzer output can reveal sensitive project metadata even when they do not contain every source file. Keep them within your normal repository and build-data controls, and review exported JSON before sharing it.
Manifest and build identity
Repository revisions, products, targets, source membership, paths, toolchain, and build-profile details can expose project structure.
Compiler Index Store
Compiler records can carry symbol names, relationships, source locations, module boundaries, and other sensitive project metadata.
Analysis results
Human and canonical JSON output can reveal declarations, reachability, evidence gaps, and exact identifiers. Inspect it before sharing.
What this website does today
The published source candidate contains no analytics, advertising, cookies, accounts, or forms. It has no source-upload surface and does not receive manifests, Index Stores, or analysis output.
Production hosting, provider access logs, operator identity, retention, and request handling are still undecided. Those facts must be added before this candidate can become a production privacy or security statement.
Read-only content
The current routes publish static product guidance and documentation links; they do not expose an analysis API.
No account surface
There is no signup, login, organization, billing, dashboard, or customer project state in this publication.
Hosting still pending
A local preview cannot establish how a future public host will process IP addresses, request metadata, or security reports.
A hosted service would be a different boundary
A future team or hosted workflow cannot inherit the local security story by implication. Before launch it would need a separately reviewed contract for every data flow from collection through deletion.
Until that contract and its implementation exist, hosted analysis remains planned and unavailable. No source, manifest, compiler evidence, or finding should be sent to an example.invalid destination.
Collection and purpose
Define exactly which source, build metadata, identities, and diagnostics enter the service—and why each category is required.
Access and isolation
Define authentication, authorization, tenant separation, operator access, encryption, auditability, and incident boundaries.
Retention and deletion
Define storage locations, retention windows, backups, deletion behavior, export handling, and customer-request procedures.
Report a vulnerability
No production security recipient is defined. The contact page links to the author’s public profiles, which are not approved channels for security reports. Do not send vulnerability details, credentials, source code, manifests, or compiler artifacts to an example.invalid address.
A launch-ready version of this page must name a real monitored route, who receives reports, what not to include initially, and how acknowledgement and handling actually work.
Claims we do not make
This candidate does not claim security certifications, independent audits, penetration-test coverage, compliance status, production availability, or a vulnerability-response SLA.
The useful claim is narrower: the documented analyzer workflow is local, evidence boundaries remain explicit, this site has no upload or account surface, and every future hosted data flow requires a new reviewed boundary.