How We Protect Your Data
Last Updated: October 18, 2026
We advise businesses on keeping customer data safe while they use AI, so here is exactly what we do with yours. Everything on this page describes how the site and client portal work today.
Encryption and Browser Protections
- Every page is served over HTTPS, and browsers are told never to connect over plain HTTP.
- Pages send security headers that stop other sites from embedding them (which prevents clickjacking), stop browsers from guessing file types, limit what a link passes to the next site, and switch off the camera, microphone, location, payment, and USB features, which no page needs.
Forms
- Every form that sends us information is checked with Cloudflare Turnstile on our server before anything is passed on, so automated submissions are stopped at the door.
- Verified submissions are forwarded to our automation platform with a shared secret, so the platform can refuse anything that did not pass that check.
- We collect only the fields each form asks for. The Privacy Policy lists them.
The Client Portal
- Individual accounts. Each person has their own account; there are no shared passwords. Passwords are stored only as salted scrypt hashes, and must be at least 12 characters.
- Short sessions. Sign-ins are signed, HttpOnly, secure cookies that expire after 12 hours. Changing a password signs out every other device, and a deactivated account loses access on its very next request.
- Guessing is slowed. Repeated failed sign-ins lock that address for 15 minutes.
- Each client sees only their own reports. Every request is checked against the account’s company before anything is served, and stored reports are checked against the company that owns them in the database.
- Reports live in a database, not in public files. Client reports are stored in a managed PostgreSQL database in the United States and served only through that check.
- Reports are sandboxed. Each report opens in an isolated browser sandbox, so nothing inside a document can act with the viewer’s account.
- No tracking. Analytics and session recording do not run anywhere in the portal, on its sign-in page, or on the Chief AI Officer page.
AI and Your Data
- We use OpenAI and Anthropic through their business APIs, under terms that do not use API data to train their models by default.
- We send a model only the data a task needs, and a person reviews every client deliverable.
- We never use your data to train AI models. The AI Use Policy has the full rules, including how we handle client data during engagements.
Keeping Only What We Need
Form and lead records are deleted within 3 years of our last contact, failed sign-in records after 15 minutes, and portal sessions expire after 12 hours. The Privacy Policy lists every retention period.
If Something Goes Wrong
If we learn of a security incident that affects your information, we will contain it, investigate it, and notify you as the law requires. Clients are notified as their engagement agreement provides.
Report a Vulnerability
If you believe you have found a security problem on this site, email hello@larrycollett.com with “Security report” in the subject and enough detail for us to reproduce it. We will acknowledge your report within 3 business days. Please give us reasonable time to fix the problem before you disclose it publicly, test only against your own account, and do not access, change, or delete other people’s data. We will not pursue legal action against good-faith research that follows these rules. Our contact details are also published at /.well-known/security.txt.
Questions
Email hello@larrycollett.com. We are happy to answer security questionnaires from clients and prospective clients.