This Trust & Transparency page explains who is responsible for this site, how information is presented, and how visitors can challenge or correct a claim. It is a practical editorial commitment—not a certification or claim that every project has been independently audited.
1. Who is behind this site?
AR. Abhinav Ranjan maintains this personal portfolio to document technology learning, cybersecurity education, research interests, publications, projects, and the Luminary Technicals ecosystem. “AR.” is an organizational honorific used within Luminary Technicals, meaning “Authority Representative”; it is not a government-issued or regulated professional qualification. See the About page, biography, and ecosystem glossary.
2. How project status is communicated
- Operational / available: use only when the page provides a functioning public destination or current evidence of availability.
- Prototype / experimental: work has been built or explored, but should not be treated as a certified or production-ready service.
- Planned / inactive: a future intention, not a live capability. AgroScan is currently described as inactive with a planned 2027 revival.
- First-person account: a historical statement based on Abhinav's account; add independent documentation when it is available.
3. How awards and institutional relationships are described
Where possible, award or credential claims should link to a primary issuer source, public record, certificate, event page, or other dated evidence. A personal archive or certificate image is useful context but is not always proof of a publicly verifiable record. Where a primary source could not be found, the site aims to label the claim as reported or not independently verified. Reference to Tata, DRDO, IITs, or another institution must not be read as a partnership or endorsement unless an appropriate source explicitly confirms it.
4. Sources, authorship, and AI assistance
Personal experiences are attributed to the person recounting them. Technical or legal claims should cite primary documents or reputable technical sources where practical. The site may use AI-enabled tools for drafting, organisation, coding assistance, or editing; any material claims still require human review, and AI assistance is not presented as independent verification. Not every code example is externally audited or tested in every environment, so examples should be reviewed before production use.
5. Corrections, updates, and security reports
For a factual correction, send the URL, the specific claim, the proposed correction, and a primary source or other supporting evidence to legal@abhinavranjan.qzz.io. We may amend, annotate, or remove content after review. For website security issues, contact help@abhinavranjan.qzz.io with a concise description and safe reproduction steps. Do not access, alter, or extract data from systems without explicit authorisation. No bounty or response time is promised unless separately published.
6. Relationships and independence
Luminary Technicals and related projects are described as part of Abhinav's own ecosystem. Project and organisational names do not imply registration, government status, institutional endorsement, commercial availability, or independent verification unless the relevant page provides evidence.
7. Limitations
This site is a personal portfolio. It is not a standards body, certification authority, government portal, or substitute for independent technical, legal, or professional review. For policies governing the site, read the Privacy Policy, Cookie Policy, Terms & Conditions, Disclaimer, Editorial Policy, and Domain Licence & Issuance Notice for the publisher’s domain-namespace disclosure.