// Trust
How client code is handled during audit work
This page sets the default operating policy for Apple-platform audit engagements. Reviews run on a dedicated Mac Mini in a separate audit account, and if a client agreement or NDA says otherwise, the signed agreement controls.
// Defaults
Working assumptions
These defaults are meant to keep access narrow, delivery clear, and public proof redacted.
NDA available before access
- Mutual NDA can be signed before repository or archive access.
- Client-provided NDAs can also be reviewed when preferred.
Read-only access preferred
- Read-only repository access is preferred whenever practical.
- Zip or archive delivery is acceptable when repository invites are not possible.
Isolated review environments
- Audit review is performed on a dedicated Mac Mini inside a separate audit account with client work kept in scoped audit directories.
- Client code is not committed into public or product repos.
Redacted public proof
- Public samples remove identifying project details, code excerpts, and sensitive implementation specifics.
- Paid reports may include exact references, evidence excerpts, and implementation-specific guidance.
// Retention
Code retention and cleanup
Retention is kept short by default unless a written agreement requires something different.
Default retention window
- Client code is retained for 14 days after delivery by default.
- That window supports follow-up clarification and report verification.
Extended retention by agreement
- If remediation work or a follow-on engagement is booked, a different retention period can be agreed in writing.
- Absent that written agreement, the 14-day default applies.
Client-controlled access
- Clients can revoke repository access at any time after delivery.
- Read-only invites remain the preferred access model for that reason.
// Review Standards
AI assistance and human ownership
The workflow can use tooling assistance, but the deliverable is not an unreviewed machine dump.
AI-assisted review may be used
- Tooling may assist with pattern detection, evidence gathering, and issue triage.
- Use of those tools does not change the scope boundary or client ownership terms.
Final findings are human-reviewed
- Paid findings are reviewed and owned by Pixelwright Digital before delivery.
- The report is curated for accuracy, prioritization, and practical implementation value before anything is shared externally.
Not a certification service
- The deliverable is an Apple-platform code audit report, not a certification, formal penetration test, or compliance attestation.
- Clients needing those services should engage the appropriate specialist provider.
What clients should expect in paid audit reports
- Written findings with severity or urgency framing
- Exact file and line references where appropriate
- Evidence-backed explanations written for founders and engineers
- A clean boundary between audit work and separately scoped remediation work
// Next step
Review the sample, then decide whether you need triage or a full audit.
The trust layer should be visible before you share code, not hidden after you book.