Security & data
What happens to your information.
A plain description of how we handle the information you share with us, and how access is agreed when we work together.
Website inquiries
How your inquiry is handled.
What you share
Your name, work email, an optional company name, the topic you choose and the message you write.
Where it is kept
We use HubSpot to manage inquiries, so your details and your message are saved there as a contact record and a dated note.
Who reads it
Fahad Mubiru reads inquiries and replies personally.
Booking a call
Scheduling is separate. Sending an inquiry never books an appointment, and booking a call never requires the form.
Read the privacy page for retention and your options, or email fahad@oldoaklabs.com.
Client implementations
How access and approvals are agreed.
Least access that works
We ask for the narrowest access that lets the workflow function, and we write down which systems and data are in scope.
Named human approvals
Consequential actions — anything that commits money, sends something externally or changes a record of truth — route to a named person.
Credentials stay with you
Keys and connections live in your environment or in server-side configuration. They are never placed in browser code.
Ending an engagement
Access is removed when work ends, and we document what was connected so you can verify it.
Working with your requirements
Tell us what your organisation needs.
- We use established providers for CRM and scheduling, and their terms apply to information held in those systems.
- Where a workflow touches sensitive or regulated data, we agree the handling rules and approval points in writing before any build work.
- If your organisation has security, procurement or documentation requirements, share them early and we will tell you plainly how we can meet them.
Old Oak Labs