Privacy
What we collect, and what we do with it.
This site sets no cookies, runs no analytics and makes no third-party requests. The personal data that reaches us is what you put in an email, and what we see while doing the work.
This website
The site itself collects nothing.
It is static HTML, CSS, fonts, images and one script, all served from this domain. No cookies are set, no local storage is written, and no analytics, tag manager, advertising pixel or third-party font runs here. The content security policy blocks requests to other origins, so a tracker cannot be added by accident.
The one script is the assistant in the corner of the page. It answers from a fixed set of answers written into the file itself, not from a language model, and it makes no network request. Nothing you type into it is sent anywhere or stored, and the conversation is gone when you close the page. With scripts blocked, the rest of the site works exactly the same.
There is no form that submits to a server. Every way of contacting us is a mail link that opens your own email app.
The site is served by Cloudflare, which keeps standard request logs (IP address, time, address requested, browser) for delivery and abuse prevention. We do not build profiles from them.
Enquiries
When you email us.
We receive what you put in the message: usually your name, your email address, your business and a description of the problem. We use it to reply, to work out whether and how we can help, and to quote for the work. You are not added to a mailing list.
If you would rather we deleted the thread once the conversation is over, say so and we will.
During the work
What we see while doing the job.
Technology work often means access to other people's data. The rule is the same everywhere: use it only for the job, and do not keep it.
Code and repositories
Building or changing software means read (and sometimes write) access to your repository. We work in the code you asked us to work in, and access is removed when the project ends.
Databases and the data in them
A system we build or extend usually holds real records: customers, orders, documents. We use production data only where the job genuinely requires it, prefer a copy with the personal details removed, and never take a copy away with us.
Credentials and provider accounts
Deployment means access to your hosting, domain and provider accounts. Wherever possible those accounts are yours and we are given our own logins rather than sharing yours, so access can be revoked without changing anything you rely on.
Application security reviews
A review is agreed in writing first, including what is in scope. Testing can expose real user data; anything we see is used to write the finding and nothing else, and the report goes to you alone.
Penetration testing is carried out by SkullSploit, which publishes its own policy for testing data at skullsploit.com/privacy.
Sharing
Who else sees any of it.
Nobody buys data from us. The suppliers that necessarily handle some of it are the ones any company uses: our email provider and the hosting for this website. Where we source equipment or services for you, the supplier receives what they need to fulfil the order, and we tell you who they are.
We disclose information only where the law requires it, and we will tell you if that happens unless we are prohibited from doing so.
Your rights
Asking what we hold.
Email contact@skullsolutions.com and ask. We will tell you what we have about you, correct it if it is wrong, or delete it where we are not required to keep it. You do not need to cite a law to ask.
Skull Solutions Pvt Ltd is a company registered in the Maldives, and is the controller responsible for the data described on this page.
If this policy changes, the date at the top of the page changes with it.