Status: under repair. Feature surface is incomplete and not currently available for evaluation. No work has landed on the backing service since 2026-06-17, and its CI has failed on every run since 2026-06-10 (the last green run was 2026-06-05). The entry exists so the project is visible in the portfolio’s working set; verifiable claims and a working surface will return together.
Claims about analytics behavior — particularly anything stated about cookies, identifiers, or PII handling — will only appear here when they are independently verifiable end-to-end against the deployed code, not just the design intent.
For inquiries, contact us via the SUMequities contact page.
When This Entry Becomes Substantive
The privacy-positioned framing will only return when at least one of these holds:
- A reproducible, automated test suite enforces the privacy claims (no high-entropy identifiers, no full URLs / referrers / UA strings in tracked events) end-to-end on the deployed worker, and the test results are linkable, and/or
- A third-party privacy audit covers the deployed configuration and the audit is referenceable.
Until either is met, no privacy-positioned claim about this project will appear on the portfolio.
Verification
Full proof report → All claims, all projects →- In progress
Reproducible automated test suite enforcing privacy claims (no high-entropy identifiers, no full URLs / referrers / UA strings in tracked events) end-to-end on the deployed worker, with linkable results — or a referenceable third-party privacy audit. A privacy-attestation test file (test/privacy.attestation.test.js) exists in the private backing repo, but its CI has not had a green run since 2026-06-05 and the repo is not publicly readable, so the results are not linkable