Code, cloud, and website evidence
Detect personal-data signals, form fields, request bodies, storage hints, logging exposure, cookies, scripts, and third-party tools.
Svikruti scans repositories, cloud-facing product surfaces, websites, privacy notices, and consent journeys, then turns engineering evidence into RoPA starters, vendor registers, fix tickets, SARIF, and an offline evidence workbench.
git clone https://github.com/chevauxenbois/svikruti.git cd svikruti python3 -m venv .venv source .venv/bin/activate python -m pip install -e '.[parsers]' svikruti scan \ --repo . \ --url https://example.com \ --privacy-url https://example.com/privacy \ --out svikruti-report.html \ --sarif-out svikruti.sarif \ --ropa-out ropa.csv \ --actions-out actions.csv \ --vendors-out vendors.csv
Notice gaps, sensitive data, logging exposure, vendor review, and CI evidence in one place.
Svikruti does not pretend to certify compliance. It creates a transparent evidence pack that privacy, security, engineering, cloud, and legal teams can verify quickly.
Detect personal-data signals, form fields, request bodies, storage hints, logging exposure, cookies, scripts, and third-party tools.
Connect findings to notice coverage, consent and withdrawal, data minimization, vendor governance, RoPA readiness, and children-data review.
Each finding can carry detector ID, confidence, file or URL evidence, language, framework hints, and fields that require human confirmation.
DPDPA teams need more than a questionnaire. They need proof of what is collected, where notices are weak, which processors appear, and what engineering can fix before launch.
Compare detected data categories, vendors, cookies, forms, and consent copy against privacy notice coverage and missing purpose language.
Export structured inventories with evidence references, review fields, and confirmation gaps for legal, procurement, and security teams.
Turn findings into prioritized actions and copy-ready tickets with acceptance criteria, so review ends with fixes instead of screenshots.
The HTML workbench is for humans. The JSON, SARIF, CSV, and Markdown files are for CI, GRC, procurement, legal review, and engineering tickets. The Scan Quality view shows what was inspected, what was not proven, and what humans should verify.
Executive posture, control board, evidence explorer, action tracker, and flow map.
GitHub code scanning output for pull-request review.
Schema-versioned privacy inventory starter with evidence references.
Processor register starter with DPA, transfer, security, and review fields.
Copy-ready GitHub, Jira, or Linear issue bodies with acceptance criteria.
Optional AI-assisted synthesis grounded in scanner evidence.
Run it locally, attach it to CI, or use it as the evidence layer for a future hosted PrivacyOps workflow.
Repository, website URL, privacy notice, and optional browser consent journey.
Personal-data categories, vendors, logging, storage, forms, cookies, and notices.
Evidence to DPDPA control areas and launch-readiness concerns.
RoPA, action tracker, vendor register, notice patch, SARIF, JSON, and fix pack.
Use GitHub Actions to block risky privacy changes before release.
The priority is a useful open-source tool for India's privacy community. If teams need continuous PrivacyOps across products and releases, the hosted direction will be shaped with early users.
For founders, privacy practitioners, and engineering teams that want DPDPA evidence quickly.
For teams that need continuous PrivacyOps across products and releases, if there is enough demand.
Use the GitHub repo today, follow the build, and help shape India-first PrivacyOps tooling for DPDPA.
The vision is to simplify DPDPA compliance through code, cloud evidence, technical controls, open-source workflows, and practical artifacts that teams can actually use.
Svikruti is an independent open-source effort to make DPDPA readiness more practical for Indian startups, security teams, privacy teams, and engineers.
It is not legal advice and it does not replace counsel. It is a technical evidence layer that helps teams find, discuss, and fix privacy gaps faster.
If you are figuring out DPDPA readiness for a product, cloud setup, website, consent flow, vendor process, or engineering release, reach out. I am happy to have a practical conversation and see where Svikruti or hands-on assistance can help.