Security & sensitive information
We would rather hold less of your information than more.
Taking on a technology partner means letting someone near the keys to your business. Here is exactly what we hold, what we deliberately do not, and what we are not going to claim.
Credentials
We do not run a password database of our clients' secrets.
It would be convenient for us, and it would make Buki one of the most attractive targets a small business could accidentally create. So we separate two things that are usually confused.
Knowledge about access — who owns an account, who administers it, where the credential is kept, and what the recovery process is — lives in your technology record. That is the part that disappears when people leave, and the part we exist to preserve.
The secret itself stays wherever it belongs: your password manager, your own administrators, your recovery contacts. Where we genuinely need standing access to do the work, we hold our own named account on your system rather than your password.
The principle
Controls
What we actually do.
Least necessary access
We hold the minimum access required to do the work, and no more. Where your own password manager can hold a credential, it holds it. We record where access lives and how it is recovered, rather than becoming the sole holder of the secret.
Named, not shared
Access is tied to a named person at Buki, not to a shared login. When one of our people leaves, their access is revoked as part of offboarding — and we can tell you exactly what they had.
Multi-factor everywhere it is offered
On our own systems and, wherever we administer them, on yours. Where a system does not support it, that fact is recorded as a known weakness rather than quietly accepted.
Auditable changes
Consequential changes carry a record of who requested them, who approved them, who performed them and what the result was. The trail is created as the work happens, not reconstructed afterwards.
Separation between clients
Your record is isolated from every other client's. Access by our staff is explicit, granted per client, and logged.
Encryption and backups
Data is encrypted in transit and at rest, backed up on a schedule, and restoration is tested rather than assumed. A backup nobody has restored is a hope, not a control.
Access reviews
We periodically review who has access to what — ours and yours — and remove what is no longer needed. Stale access from a departed contractor is one of the most common real risks we find.
Export on demand
You can ask for everything we hold about your technology at any time, without giving a reason, in a form another provider can use.
Standards
What we are not going to claim.
Buki is not ISO 27001 certified, and is not SOC 2 audited. Plenty of firms our size imply otherwise by putting the logos on a page. We are not going to do that.
What is true is that we design our systems and operating procedures toward those frameworks — ISO/IEC 27001 and 20000, SOC 2, ITIL service management, and the NIST Cybersecurity Framework — because they encode decades of hard-won practice. If certification later becomes useful to our clients, the groundwork will already be done.
Our philosophy is to build it correctly first and certify later, rather than to buy a badge and work backwards from it.
A certification you cannot verify is a marketing claim. Ask us specific questions instead — we will answer them.
Continuity
What happens if something happens to us.
We plan for our own failure. Client records are backed up and encrypted, restoration is tested, and recovery procedures are written down rather than held by whoever happened to build the system.
More importantly, the design means our failure is survivable for you. Your domains, cloud accounts and subscriptions are in your company’s name. Your technology record is maintained so that another competent provider could read it and continue. The cost of losing us should be the inconvenience of replacing us — nothing more.
If we ever cease operating, our commitment is to get every client a complete handover package before we go.
Questions
About ownership and information.
Do I still own my accounts?
Yes — and where you do not yet, we will usually recommend fixing it. Domains, cloud accounts, software subscriptions and data should be registered in your company's name.
We may administer these systems for you, hold appropriate access, and renew things on your behalf. That is different from owning them. You should never be in a position where leaving us means losing something.
What happens if Buki disappears?
You keep operating. That is a design requirement, not a reassurance.
Because your accounts are in your name and your technology record is maintained to a standard another provider could pick up, the practical cost of losing us is finding a replacement — not reconstructing your technology from scratch. You can ask for a complete export at any time, without explaining why.
How does Buki handle sensitive information?
We deliberately do not run a password database of our clients' secrets. Wherever possible we record where a credential lives and how access is recovered, and let your own password manager hold the secret itself.
Where we do hold access, we hold the minimum required, it is tied to a named person, and consequential changes are logged with who requested, approved and performed them.
Getting started
Ask us the hard questions.
Bring your worst-case scenario to the first conversation. If we cannot answer it clearly, you should not hire us.
Or email us directly at yarsahimalaya@gmail.com.