Every Wolfix scan is worked by six specialists at once. Each one owns a distinct slice of what stands between a working app and a business you can charge for — and each finding in your report carries the badge of the department that reviewed it. The departments are roles, not people: Wolfix narrates all of them, and the badge simply tells you whose expertise the gap falls under. This article is the single place to see what each specialist checks.
The six departments at a glance
Legal
Wolfix reviews legal coverage by checking for a published privacy policy, terms of service, and cookie policy, then maps them against the jurisdictions and data practices detected in your stack. It flags GDPR consent gaps, missing data-retention language, and — when user-generated content is detected — an absent DMCA section. Where a document is missing, Wolfix can generate one tailored to what the scan found.
Security
Drawing only on the code scan, Wolfix inspects security posture: hardcoded secrets or credentials, authentication and session handling, rate limiting on sensitive endpoints, and common vulnerability patterns. It has no live-URL or DNS signal, so a security finding always traces back to something in the source. Each issue is ranked by launch impact rather than by how hard it is to fix.
Technology
Wolfix checks the technical foundations that keep an app reachable and well-described: DNS records, hosting configuration, error tracking, meta tags, and robots.txt. Many of these are observable from the live URL and DNS lookups, so they surface even on a URL-only scan. For broken or missing items, Wolfix produces a ready-to-paste code fix.
Brand
Wolfix evaluates the visual identity a customer or app store sees first: logo, favicon, Open Graph image, and App Store screenshots and metadata. Gaps here rarely block a launch, but they read as unfinished to the people deciding whether to trust you. Wolfix can generate a full brand kit sized for every surface the scan detected.
Growth
Wolfix looks at whether the app can actually be found and understood: tagline clarity, SEO and AIO signals, analytics events, and referral infrastructure. These checks combine live-URL observations with deterministic rules about what a discoverable product needs. Findings are framed as the difference between shipping and being noticed.
Operations
Wolfix reviews the operating scaffolding a real business needs: a registered entity, a business bank account, insurance, support pages, and a cancellation flow. Because much of this lives outside the codebase, operations findings often route to a vetted referral partner rather than a generated asset. Operations also owns cross-cutting findings that span more than one department.
How the badges show up in your report
In the report, every finding sits under one department badge, and the department summary strip shows coverage across all six at a glance. A grey column means that area was not scanned — for example, security stays grey on a URL-only scan because it has no signal without source access. A coloured column tells you how many findings the scan routed to that department.
Use the badge to delegate
The department badge is a shortcut for who should act. A blocker under Legal likely needs a lawyer's sign-off; a risk under Security is a conversation with whoever owns your infrastructure. You don't have to fix everything yourself — the badge tells you who.
Departments are coverage, not characters
It helps to read the six departments as six lenses Wolfix scans through, not as six voices. Wolfix never speaks as a department in the first person, and a department never "decides" anything on its own — Wolfix checks an area as part of, say, legal coverage, and reports what it found. This keeps the report consistent: one narrator, one severity model, six areas of expertise applied in parallel.
Which department owns a finding is deterministic
Routing isn't a judgment call. Wolfix maps each finding to its owning department by a fixed set of rules — DNS findings go to Technology, exposed secrets to Security, privacy gaps to Legal, and so on. If you want the mechanics, see how Wolfix routes findings to departments.
When a specialist doesn't fit
Sometimes an area genuinely doesn't apply to your project — a brand kit for an internal-only tool, or operations checks for something you never intend to charge for. You can exclude a specialist from a scan so its findings don't clutter the report. That's a per-scan setting, not a permanent change; see excluding a specialist from a scan for the steps.