Security
How I keep your code and data safe
This page describes what I do, on my machines and in your projects, and how this website is built. It is not an audit service. It is the answer to the questionnaire your IT team sends before they let anyone near the repository.
Last updated:
My devices and accounts
Encrypted and locked
Full‑disk encryption on every machine, automatic lock when I step away, a work machine that nobody else uses. No client code on shared or personal devices.
Updated as they ship
Operating system, browsers, runtimes and tools take updates when they are released.
Password manager, MFA everywhere
Unique generated passwords, multi-factor authentication on every account that offers it, hardware keys where supported.
One browser profile per client
Sessions, extensions and cookies stay separate. A client’s admin panel never shares a profile with anything else.
Encrypted backups
Backups of my own work are encrypted at rest. Your code is never backed up outside your repository unless we agree on it.
Nobody else
No subcontractors, no assistants, no shared logins. The person with access is the person you talked to.
Secrets and access
Secrets live in the platform
Environment stores and secret managers, never in code, never in a chat with a model, never in a screenshot. Local secrets sit in files outside version control.
Least privilege, your accounts
I use accounts you create and control, scoped to the job, separate from anyone else’s. You can revoke them in one click and you should when we are done.
Production is not a workstation
No production access from development machines. Migrations, configuration and fixes go through code and review, never by hand on a live system.
Offboarding
At the end: access handed back, local copies deleted, confirmation in writing. If you want a list of what I had access to, you get one.
How I build
- Gates the agents cannot skip. Lint, tests and security checks run in CI on every change. A human reviews every pull request, including the ones an agent opened.
- Security headers by default. Content Security Policy without inline scripts, nosniff, referrer and permissions policies. This website is built that way; you can check its headers in your browser.
- Staging before production. Every change is seen running somewhere that is not production first. Migrations are rehearsed on a clone, then repeated with the same steps.
- Same‑day response to advisories. When a vulnerability in a dependency becomes public, the patch ships the same day. One example: the React2Shell response in work I can show.
- Caps and kill switches. Rate limits, cost budgets with an atomic gate and an emergency stop on every paid service. An abandoned request should not cost you money or data.
- Minimal logging, masked data. Logs hold what debugging needs and nothing personal. Analytics gets anonymized or masked data. Backups and point‑in‑time recovery are set up and tested, never assumed.
- Email that cannot be spoofed. My domain publishes SPF with a hard fail, DKIM and DMARC with a reject policy. The free SPF, DKIM and DMARC checker shows how yours looks.
This website
Runs on Cloudflare Workers with a Content Security Policy that forbids inline scripts, no third-party scripts and no CDNs. Analytics is PostHog in the EU, loaded through a first-party proxy, with no cookies and with every input masked in session replays. Admin panels sit behind Cloudflare Access. The source of the main site and of the agent skills is public on GitHub. What is collected and why is on the privacy page.
Report a vulnerability
Found something in a page or tool under ciunkos.com? Email me, or use the security.txt file (RFC 9116). You get a reply within 24 hours on working days and a fix as fast as the issue deserves. There is no bug bounty. Please do not test systems that are not mine and do not touch other people’s data; a proof of concept against your own account is plenty. Credit in public if you want it.
Compliance experience
CASA Tier 2
I led Google’s Cloud Application Security Assessment (based on OWASP ASVS) for Patriot Mail (built at Sanddev), an email client with Gmail access. It passed in January 2026, findings from a third-party pentest were fixed, every control became a Playwright test on each pull request, and I led the yearly reassessment, validated in October 2026.
GDPR in practice
Data processing agreements, records of processing, data minimization, retention limits and deletion flows, shipped in products I built.
Platform and buyer reviews
Yahoo’s OAuth review passed; SSO and multi-tenant routing shipped. Sandtime.io (built at Sanddev) runs a vulnerability disclosure program with a public Hall of Fame. The facts a questionnaire asks about me are in the trust center.
FAQ
Questions from security questionnaires
Do you have an ISO 27001 or SOC 2 certificate?
Where is my data processed?
Do you use AI tools on my code?
What happens to my code and data when we finish?
Can I run a security review of your work?
In 30 minutes you will know if we are a fit
You bring the problem, I bring the questions. Want a number first? The configurator shows hours, a price range and the start date.
or write to ciunkos@gmail.com
After you book you get a calendar invite. Nothing else to fill in.
My pledge
- Reply within 24 hours. I reply within 24 hours on working days, personally, not a bot. Weekend messages: by Monday noon.
- Late means free. If I am late, the first hour of work is free. You do not have to ask.
- Scope in writing within 24 hours. A free 30‑minute call with no company deck, then the scope and the price in writing within 24 hours. You decide.
- The person who does the work. You talk to the person who does the work. No sales layer, no handoff.
- Follow‑up only with news. I follow up only when I have something new for you. Never a “did you see my offer”.
- Honest “not a fit”. If I am not the right person, I say so on the call and point you to someone who is.
Calls this week · work can start now · B2B contract · Wrocław, Poland (CET), remote
You own the code, domain and accounts from day one. Nothing is held hostage.