Service page improvements
Trust & security at Harborflow
A plain compliance record: what we hold, when it was attested, who processes data, how to request the report.
Critical priorityIn progress/security700–1,000 wordsTom Brennan
Production status
Move the brief from idea to published and verified.
- ✓Pending
- ✓Needs approval
- 3In progressCurrent state
- 4Verification required
- 5Completed
Drafting started Oct 30, 2026.
Demand targeted
1,450
Monthly searches across target prompts
Target prompts
1
Prompts this page is written to win
Competing pages
1
Currently cited for those prompts
Length
700–1,000
Owned by Tom Brennan
The gap
Why this page needs to exist
We hold SOC 2 Type II and publish nothing an engine can confirm it from.
Angle
How to treat the subject so engines can quote it
A plain compliance record: what we hold, when it was attested, who processes data, how to request the report.
Suggested structure
Sections in order, with what each one needs to contain
- 1CertificationsSOC 2 Type II with attestation date and auditor.
- 2Data handlingEncryption at rest and in transit, retention, residency options.
- 3SubprocessorsNamed list with purpose and region.
- 4Access controlsSSO, SCIM, role model, audit log retention.
- 5Request the reportUnganted path with NDA step described.
Must include to be citable
Without these the page will not be quoted
- Attestation date
- Named auditor
- Subprocessor list
- Organization schema
Brief detail
- Id
- c-06
- Type
- Service page improvements
- Target path
- /security
- Owner
- Tom Brennan
- Length
- 700–1,000
- Started
- Oct 30, 2026
- Published
- —
Audience
Security reviewers and controllers running vendor due diligence
Target prompts
What this page is written to win
- Is AP automation software SOC 2 compliant and how is payment data protected?Not mentioned1,450/mo
Pages you are competing with
Currently cited for these prompts
- Nexora Paynexorapay.com/trust