Security & continuity
Who can reach your data, how long we keep it, what you own at the end, and what happens when the power goes.
- Accounts
- MFA
- Erasure
- On request
- NDA
- Standard
- IP
- Yours
Security and continuity controls
- Your accountsRegistered in your name
- CredentialsPer client, never shared
- Working copiesOnly what the task needs
- DeletedFrom every machine that held it
- ConfirmedIn writing, to you
Accounts and access
We are a small team on ordinary laptops. What protects your data is not our hardware, it is which accounts exist, who holds them, and how fast they are taken away.
- Multi-factor authentication on every account that reaches a client system
- Credentials never sit in a repository, a chat thread or an email
- Access granted per engagement, and only to the people working on it
- Access revoked the day a person leaves the engagement, not at the end of the month
Your data
We hold as little of it as the work allows, for as long as the work needs, and we delete it the day you tell us to.
- Sample or anonymised records for development wherever the task allows
- Where the real records are needed, the copy is deleted once that work is done
- Anything you ask us to erase is erased, and you get that in writing
- Separate accounts, repositories and credentials per client, with nothing shared between engagements
- Data returned or destroyed at the end of an engagement, confirmed in writing
Legal and ownership
A registered Pakistani company. An NDA is the starting position, and the intellectual property is yours on payment.
- Incorporated with the Securities and Exchange Commission of Pakistan (CUIN 0357912) and registered with the Pakistan Software Export Board, Ministry of IT & Telecom (Reg. No. Z-25-22478/26)
- Mutual NDA signed as standard, before the first technical conversation
- Intellectual property transfers to the client on payment, written into the contract
- Code, cloud accounts and domains registered in your name from day one
- Third-party licences and their terms listed before a dependency is adopted
- Named subcontractors disclosed, and bound by the same terms
Continuity
Power cuts and dropped lines are ordinary in Lahore. Nothing that matters lives in our office, which is what makes them a nuisance rather than an incident.
- Work held in cloud repositories and cloud environments, never only on a local disk
- Environments rebuildable from source, so a dead machine costs a day and not the project
- Laptops and mobile data, so an outage moves us rather than stops us
- Overlap hours published, and a named lead reachable inside them
When something goes wrong
You hear it from us, the same day, with what we know and what we do not.
- Incidents affecting client data or availability reported the day they are identified
- A written account of what happened, what was affected, and what changed afterwards
- The engagement lead owns the communication, not a support queue
Lahore, and the hours we overlap with you.
We are based in Lahore, Pakistan, and work with clients worldwide. What a buyer needs to know is when they can reach a person.
- Base
- Lahore, Pakistan (UTC+5)
- Europe
- Four hours of overlap with Central European working hours, every day
- North America
- Four hours of overlap with North American mornings, every day
Need this in a vendor questionnaire?
Send the form. We will fill it in properly, and tell you where the honest answer is no rather than writing what you want to read.
We respond within one business day. If we are not the right fit, we will tell you.