# iViRTH Online — full content > iViRTH Online (ivirth.com) is the solutions site of iViRTH, an R&D company based in Uttar Pradesh, India (corporate site: ivirth.in). It covers digital twins, Digital Product Passports, traceability and provenance, and asset and lifecycle management, delivered as pilots, implementation services and a modular data platform. Digital twins · Digital passports · Lifecycle data # Connecting the physical and digital worlds Built for iViRTH helps organisations create structured digital representations of physical entities, establish accessible product and asset records, and connect information across lifecycles. From products and materials to industrial assets, buildings, processes, and connected systems, we turn fragmented information into useful digital infrastructure. Request a PilotExplore our solutions The challenge ## Physical things generate information. That information is often disconnected. Product, material, asset, and infrastructure information can be scattered across documents, spreadsheets, suppliers, and business systems. iViRTH helps structure and connect this information so relevant people can access it, understand its source, and use it for defined lifecycle and operational needs. ## Our core capabilities ### Digital Twin Solutions Create and manage digital representations of products, components, equipment, buildings, infrastructure, processes, and connected systems. ### Digital Passport Solutions Structured digital records for products, components, and materials, connecting identifiers with specifications, provenance, evidence, and lifecycle information. ### Traceability & Provenance Connect entities with suppliers, facilities, batches, events, and supporting evidence to improve information continuity. ### Asset & Lifecycle Management Organise asset information, service histories, maintenance records, and lifecycle events within one consistent digital framework. ### Integration & Implementation Move from fragmented data to practical digital infrastructure through data modelling, onboarding, system integration, implementation planning, and support. ## How it works Five moves from fragmented data to practical digital infrastructure. Exact capabilities depend on the use case, available data, technical feasibility, and implementation scope. - 01 ### Identify Establish an identifier for each target product, asset, component, material, or entity. - 02 ### Structure Organise attributes, relationships, documents, and events into a defined data model. - 03 ### Connect Connect records to relevant systems, suppliers, data sources, or physical data carriers. - 04 ### Access Make appropriate information available through digital records, dashboards, APIs, or QR-linked interfaces. - 05 ### Improve Use lifecycle information to support visibility, maintenance, traceability, reporting, and decisions. ## Where it applies Target application areas across eight industries — each with its own data, rules, and lifecycle. Textiles & apparelManufacturing & equipmentConstruction & built environmentEnergy & batteriesAgriculture & resourcesLogistics & distributionElectronics & consumer goodsFacilities & infrastructureTextiles & apparelManufacturing & equipmentConstruction & built environmentEnergy & batteriesAgriculture & resourcesLogistics & distributionElectronics & consumer goodsFacilities & infrastructure See industry use cases Start with a practical pilot ## You do not need to transform your entire organisation at once. Start with a defined product category, asset group, facility, or process. Establish the data model, test the workflow, measure the results, and expand based on evidence. Discuss your use caseHow we work Trust principles ## A digital record does not automatically prove every statement it contains. Trust depends on source quality, evidence, accountability, appropriate validation, and clarity about what has and has not been verified. We label what is live, delivered as a service, prototype, or planned — so you always know what you are getting. ## A modular platform, honestly labelled A shared data foundation reused across twin, passport, traceability and lifecycle use cases — each module published as live only once it exists and can be demonstrated. ### Entity & Twin Registry Identifiers, attributes, relationships and lifecycle events for defined entities. Intended capability ### Digital Passport Management Templates, QR-linked access, evidence references, completeness checks and versioning. Intended capability ### Data Integration APIs, webhooks, structured import/export and schema mapping where implemented. Intended capability ### Identity, Permissions & Trust Role-based access, audit trails and source or evidence references. Intended capability Explore the platform Pilot offer ## Start with a Digital Passport Readiness Assessment A bounded first step: understand what product data you hold, what is missing, and what a practical pilot would involve — before you build anything. - Product-data inventory and data gap analysis. - Schema and attribute mapping. - Identifier and data-carrier approach. - Implementation roadmap for a defined pilot. Process: Discover → Define → Design → Implement → Validate → Maintain. Each engagement has an agreed scope, deliverables, responsibilities, acceptance criteria and exclusions. Request a Readiness AssessmentHow we work ## Frequently asked questions What is a digital twin? - A digital twin is a digital representation of a real-world entity, such as a product, asset, building or process, connected with data so the digital record can reflect the physical state for a defined purpose. What is a Digital Product Passport? - A Digital Product Passport is a structured digital record that brings relevant product information, such as identity, materials, provenance, evidence, care and lifecycle events, into one record accessible to appropriate stakeholders, often through a QR code. What does iViRTH do? - iViRTH helps organisations create digital twins, digital passports, traceability records and asset lifecycle records, including data modelling, onboarding, integration, validation and support. Does implementation support guarantee regulatory compliance? - No. Implementation support is not certification and not a guarantee of compliance. Requirements depend on the product group and applicable law, and certification or assurance is offered only through appropriately qualified parties. How do we get started? - Start with a practical pilot: one product category, asset group, facility or process. Define the data model, test the workflow, measure the results, then expand based on evidence. Tell us what you want to connect, track, or represent. Let’s define your use case --- Home / Solutions / Digital Twins # Digital representations built around real-world entities A digital twin is a digital representation of a target entity connected with data in a way that supports an appropriate relationship between physical and digital states. Not every digital representation has every capability. Discuss a Digital Twin pilot ## Types of digital twins Depending on maturity and purpose, a twin may support integration, visualisation, monitoring, analysis, simulation, optimisation, or collaboration. ### Product twins Product identity, specifications, configurations, components, lifecycle information, and service records. ### Component & material twins Component/material properties, relationships, origin information, and changes across defined lifecycles. ### Asset & equipment twins Equipment records, technical documentation, service history, maintenance events, and connected operational data. ### Building & infrastructure twins Building, facility, spatial, asset, and operational information, including relevant BIM data. ### Process & workflow twins Process stages, activities, inputs, outputs, dependencies, and performance information. ### Supply-chain & network twins Suppliers, facilities, products, materials, logistics events, and other connected entities. ### Environmental & resource twins Relevant resource, energy, water, environmental, and performance data where suitable sources exist. ### Operational & performance twins Selected operational information, indicators, and lifecycle events for visibility and decisions. These are practical solution categories, not mutually exclusive or universally standardised classifications. ## Potential capabilities - Entity and asset registration; identifiers and structured profiles. - Data modelling and relationship mapping. - Lifecycle events and record versioning. - Data import/export and APIs. - Dashboard and visualisation integration. - Optional sensor/IoT integration. - Maintenance and performance workflows. - Simulation or analytics integration where technically supported. - Role-based access and data governance. ScopeCapabilities such as IoT connectivity, real-time monitoring, simulation, and predictive analytics are available only where the specific capability is implemented and demonstrated for your use case. ## Implementation approach - Assess the business problem, target entity, users, data, and intended outcome. - Model entities, attributes, relationships, events, and data requirements. - Connect available sources and define update frequency. - Implement records, interfaces, workflows, and integrations. - Evaluate data quality, operational usefulness, adoption, and expansion opportunities. Start with one entity type and one clear outcome. Discuss a Digital Twin pilot --- Home / Solutions / Digital Product Passports # Make product information accessible across the lifecycle A Digital Product Passport brings relevant product information into a structured digital record accessible to appropriate stakeholders. iViRTH helps you assess data readiness, structure product information, create passport experiences, and maintain records over time. Request a Readiness Assessment ## Potential data modules ### Product identity Product name, model, category, SKU, batch or item identifier, manufacturer, and data carrier. ### Materials & composition Material types, components, composition, supplier declarations, and links to related records. ### Origin & provenance Relevant manufacturer, facility, supplier, origin, and chain-of-custody information supported by evidence. ### Technical & safety Specifications, instructions, warnings, applicable documentation, and supporting reports. ### Environmental & circularity Relevant environmental attributes, durability, repairability, reuse, recycling, and end-of-life data where available and substantiated. ### Care, repair & maintenance Use instructions, care guidance, service history, repair information, and spare-part references. ### Lifecycle history Selected manufacture, inspection, repair, refurbishment, component replacement, resale, and recovery events. ### Evidence & governance Sources, responsible parties, document references, version, update history, and verification status. ImportantThis is a general data framework, not a universal mandatory checklist. Exact passport fields and obligations vary by product group and applicable law. ## Passport and record types - Digital Product Passports. - Digital Component Passports or component records. - Digital Material Records and Passports. - Battery Passport-related data implementations where applicable. - Construction product information records. - Provenance and traceability records. - Service, maintenance, reuse, repair, and circularity records. ## Implementation services - Readiness assessment and product-data inventory. - Schema and attribute mapping. - Product/component identification. - QR-linked passport pages. - Supplier data onboarding and document linking. - Lifecycle event workflows. - Completeness and consistency checks. - Integration planning and record maintenance. ## Implementation steps - Assess products, markets, stakeholders, data sources, and applicable requirements. - Define fields, identifiers, evidence, access rights, and relationships. - Build the record and access interface. - Validate completeness and consistency against the agreed scope. - Maintain records through defined update and ownership processes. Regulatory contextImplementation support is not certification and not a guarantee of compliance. Requirements for EU Digital Product Passports are introduced progressively and depend on the relevant product rules and applicable legislation. Find out how ready your product data is — before you build. Request a Readiness Assessment --- Home / Solutions / Traceability # Connect entities, events, and evidence Traceability is more than assigning a code to a product. It requires a structured way to connect identifiers, relevant parties, source information, events, and supporting evidence. Design a Traceability pilot ## What can be connected? - Products, components, materials, and batches. - Suppliers, manufacturers, and facilities. - Production, processing, inspection, and shipment events. - Supporting documents, declarations, and test reports. - Repairs, refurbishment, and other lifecycle changes. - Evidence references and record updates. ## Services - Traceability readiness and gap analysis. - Data and relationship modelling. - Provenance workflow design. - Data integration through agreed imports, exports, APIs, or other methods. - Traceability reports based on available data. Trust principleA digital record does not automatically prove every statement it contains. Trust depends on source quality, evidence, accountability, appropriate validation, and clarity about what has and has not been verified. Map one workflow end to end, then expand. Design a Traceability pilot --- Home / Solutions / Asset & Lifecycle # One consistent record for every asset’s life Organise asset information, service histories, maintenance records, operational updates, and lifecycle events within a consistent digital framework — with optional integrations where they add value. Discuss an asset pilot ## From asset register to connected record ### Asset records Identity, technical documentation, location, ownership, and structured attributes for each asset. ### Maintenance & service history Maintenance events, inspections, repairs, and service records kept against the right asset. ### Operational updates Selected operational information and indicators, with optional sensor/IoT integration where applicable. ### Optional integrations Enterprise systems, BIM or 3D data, and external services — scoped per engagement. ScopePredictive maintenance, real-time monitoring, and IoT connectivity are presented only where implemented and demonstrated for a given engagement. Turn your asset register into a living record. Discuss an asset pilot --- Home / Industries # Eight industries. One connected approach. Digital twins, passports, and traceability records apply wherever physical things carry information through a lifecycle. ### Textiles & apparel Product/material records, fibre and composition data, supplier information, care, repairability, and circularity-related information. ### Manufacturing & equipment Product configurations, component records, asset registers, service history, maintenance events, and operational data integration. ### Construction & built environment Building and asset information, material records, BIM integration, maintenance, and facility lifecycle workflows. ### Energy & batteries Asset identity, equipment records, maintenance, selected operational information, and relevant battery-passport data implementations. ### Agriculture & resources Records for defined products, lots, resources, facilities, and selected production or movement events. ### Logistics & distribution Entity identification, shipment events, custody records, and supply-network visibility. ### Electronics & consumer goods Product/component information, provenance, service, repair, and lifecycle records. ### Facilities & infrastructure Asset inventories, maintenance, service records, spatial information, and selected operational data. NoteThese are target application areas, not proof of existing customer deployments. Detailed industry pages will be added as real demand, expertise, and demonstrable work develop. Tell us which industry and which product, asset, or process. Discuss your use case --- Home / Platform # A modular foundation for digital identity, twins, and passports iViRTH’s platform approach uses a shared data foundation to support multiple digital twin, passport, traceability, and lifecycle use cases — reusing common capabilities rather than building unrelated systems for every use case. ### Entity & Twin Registry Structured registry for products, assets, components, materials, facilities, and other defined entities; identifiers, attributes, relationships, lifecycle events, and import/export. Intended capability ### Digital Passport Management Reusable templates, product/component records, QR-linked access, evidence references, completeness checks, and versioning. Intended capability ### Traceability & Lifecycle Events Supplier/facility relationships, batch/component relationships, event records, provenance references, and lifecycle history. Intended capability ### Asset & Operational Data Asset registers, maintenance and service histories, optional IoT integration, dashboards, and alerts where implemented. Intended capability ### Data Integration & Interoperability APIs, webhooks, structured import/export, external identifier mapping, schema mapping, and integration monitoring where implemented. Intended capability ### Identity, Permissions & Trust Role-based access, permissions, audit trails, source/evidence references, and identity/credential integrations where required. Intended capability ### Analytics & Simulation Integration Indicators, completeness reports, trend analysis, external simulation, and predictive/optimisation workflows where supported by suitable data and validated models. Intended capability Capability statusThese are platform modules or intended capabilities. Each is published as a live product feature only once it exists and is demonstrable; otherwise it is labelled as a service, prototype feature, or roadmap item. Tell us what your data needs to do — we’ll map it to the platform. Discuss platform requirements --- Home / Services # From digital strategy to working systems iViRTH helps organisations move from an initial concept to a scoped digital solution through discovery, data design, implementation, integration, validation, and ongoing improvement. Strategy & readiness - Digital twin readiness assessment - Digital passport readiness assessment - Use-case definition and prioritisation - Existing data and system review - Data gap analysis - Implementation roadmap Data architecture & modelling - Entity and identifier design - Data schemas and attribute mapping - Product, component, and material modelling - Asset and lifecycle data structures - Relationship and event modelling - Data governance planning Implementation & onboarding - Product and asset record creation - Passport data onboarding - QR-linked record interfaces - Document and evidence organisation - Data completeness checks - Workflow configuration Integration engineering - API integration planning - Data import and export - Enterprise-system integration - IoT and sensor integration where applicable - BIM or 3D integration where applicable - External service and identity integration Data quality & governance - Source identification - Validation rules - Versioning and change management - Permissions and access design - Auditability and record ownership - Data quality reporting Training & ongoing support - Stakeholder onboarding - User training and documentation - Record maintenance processes - Managed support options - Data updates and lifecycle administration - Roadmap reviews ## Engagement process Discover → Define → Design → Implement → Validate → Maintain Each engagement has an agreed scope, deliverables, responsibilities, acceptance criteria, dependencies, and exclusions. ScopeRegulatory assessments, laboratory testing, product certification, and independent assurance are offered only through appropriately qualified or authorised parties. Implementation support alone is not certification or a guarantee of compliance. ## Running a bounded pilot - Select one customer type and a clearly bounded use case. - Agree the number of entities or records, required data, deliverables, and exclusions. - Track implementation effort, data completeness, record usability, and feedback. - Expand based on evidence. Results are published only with permission and substantiation. ## What we measure in a pilot DeliveryOnboarding time, cost per record, data completeness, validation issues. UsageRecord retrieval, QR access, update frequency, API success and error rates where applicable. ValueTime saved finding information, reduced duplicate entry, faster evidence retrieval, improved workflow visibility. Scope a first engagement with a clear start and end. Request a Pilot --- Home / Resources # Knowledge centre Practical guides and explainers on digital twins, passports, data modelling, and traceability. ## Topics ### Digital Twin Fundamentals Core concepts and terminology. ### Digital Product Passport Guides What belongs in a passport and how to start. ### Data Modelling & Interoperability Identifiers, schemas, and exchange. ### Traceability & Provenance Events, evidence, and trust. ### Industry Implementation Guides Sector-specific approaches. ### Standards & Regulatory Updates Standards and laws in context, with sources and review dates. ### Case Studies & Demonstrations Published only with permission and substantiation. ### Glossary of Terms Plain-language definitions. ## Initial articles Planned reading list — articles are being prepared. - What Is a Digital Twin? A Practical Guide for BusinessesComing soon - Digital Twin vs Digital Passport: What Is the Difference?Coming soon - What Information Belongs in a Digital Product Passport?Coming soon - How to Start a Digital Passport PilotComing soon - Product Identity, QR Codes, and Traceability ExplainedComing soon - How Manufacturers Can Prepare Their Product DataComing soon - Digital Twins for Buildings, Equipment, and InfrastructureComing soon - Data Quality, Provenance, and Trust in Digital RecordsComing soon - Digital Passport Readiness for Small and Medium EnterprisesComing soon - From Asset Register to Connected Digital TwinComing soon ## Reference starting points Authoritative sources for terminology and regulatory context. They do not, by themselves, determine the exact requirements for every product or implementation. - ISO/IEC 30173:2023 — Digital twin concepts and terminology - ISO — Digital Product Passports explained - European Commission — Digital Product Passport - UNECE — UN Transparency Protocol Digital Product Passport specification Standards & regulationStandards and regulatory explainers will carry source links and review dates. Last reviewed: 16 October 2026. A general passport schema is not a substitute for product-specific regulatory analysis. EU Digital Product Passport requirements are introduced progressively and depend on the relevant product rules and applicable legislation. Have a question we should answer? Talk to us --- Home / Demonstrations # See what a record looks like Three illustrative demonstrations using clearly labelled, non-sensitive sample data. ## Sample digital passport Digital Product Passport ### Linen Overshirt, Model LS-24 Illustrative sample data Item identifierDEMO-0001-A CategoryApparel Composition100% linen (declared) VerificationNot verified — demo Stage 1Fibre sourced — supplier declaration linked Stage 2Garment manufactured — facility record Stage 3Inspection — report reference Stage 4Repair event — recorded in lifecycle history A QR-linked page connects a product identifier with specifications, provenance, evidence references, care guidance, and lifecycle events. - Real: the record structure and the way modules connect. - Illustrative: every value shown here is made-up sample data. - Not shown: confidential supplier, commercial, or personal data — never exposed in public passport pages. ## Asset / twin record RegisteredPump P-104 — identifier and technical documents linked MaintenanceSeal replaced — service record attached InspectionVibration check — report reference UpdateComponent swap — version history retained An asset record with a visible lifecycle history. Illustrative sample data — no live sensor feed is implied ## Traceability relationship Batch → components → supplier → facility, each link backed by an evidence reference. The network view shows how connected entities cluster around shared references. TrustA digital record does not automatically prove every statement it contains. Each demo states what is real, simulated, or illustrative. Want a demo built around your own product or asset? Request a Pilot --- Home / About iViRTH # Building connections between physical entities and digital information iViRTH focuses on technologies and implementation practices that connect physical entities with structured digital information. Our work centres on digital twins, digital passports, entity identity, traceability, lifecycle records, and data integration. MissionTo help organisations build reliable, connected digital representations and lifecycle information systems that improve visibility, information access, and decision-making. VisionA world where products, materials, assets, and systems can be represented digitally through useful, structured, and appropriately governed information. This websiteivirth.com is part of iViRTH — the focused destination for Digital Twins, Digital Passports, Traceability, and Connected Lifecycle Data. Visit ivirth.in ## How we describe our work Available nowThe feature or service exists, is tested, and can be shown or delivered. Delivered as a serviceThe outcome is delivered through a scoped consulting or implementation engagement. Prototype / demonstrationA limited demonstrator exists but is not yet a production-ready service. In developmentImplementation is actively underway and limitations are clearly disclosed. Planned / roadmapA future intention — never presented as currently available. ## Two sites, one organisation iViRTH is one organisation with two complementary web properties. This site is not a separate company: it is the focused solution and implementation destination. ivirth.inCorporate identity: company overview, broader technology vision, partnerships and organisation-wide contact. Answers: who is iViRTH and what does it do? ivirth.comDetailed solution pages, use cases, implementation services, demonstrations, resources and pilot enquiries. Answers: how can iViRTH help with my digital twin or passport problem? Corporate site — ivirth.inRequest a Pilot ## How visitors move between the sites - Corporate discovery: start on ivirth.in, then follow “Digital Twins & Digital Passports” to this site. - Solution discovery: arrive here from search or a referral, learn about a use case, and submit a pilot enquiry. - Trust check: this site links back to the corporate overview; the corporate site links here for detail. - Enquiry continuity: forms on both sites follow one enquiry process, with the source recorded where practical. Let’s define your digital use case. Get in touch --- Home / Contact # Let’s define your digital use case Tell us what you want to connect, track, or represent. Whether you are exploring digital passports, organising asset data, developing a digital twin, or connecting lifecycle information, the first step is to understand your requirements. ## Request a Pilot Name Work email Organisation Industry Digital TwinDigital PassportTraceabilityAsset LifecycleOtherProject type Approximate number of records / entities Product, asset, facility, or process involved Current data sources and systems Desired outcome and target timeline Optional message I agree to be contacted about this enquiry. See the privacy notice. Submit your enquiry Thank you. Your email app should open with your enquiry ready to send. iViRTH will review the use case, clarify requirements, and follow up. ### What happens next - iViRTH reviews the use case. - We clarify requirements. - We identify a potential scope and deliverables. - We discuss dependencies, timeline, and a commercial proposal. --- Home / Privacy notice # Privacy notice Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com This notice explains how iViRTH (“iViRTH”, “we”, “us”) handles personal information when you use ivirth.com (“the site”). We aim to collect only what we need, use it for clear purposes, and respect your choices and rights under applicable law, including India’s Digital Personal Data Protection Act, 2023 (“DPDP Act”) and, where it applies to you, the EU/UK GDPR. Contents - Who we are - Information we collect - How the enquiry form works - Why we use your information and our legal basis - Who we share it with - International transfers - How long we keep it - Security - Your rights - Children - Customer and project data - Links to other sites - Changes to this notice - Contact ## 1. Who we are iViRTH is an R&D company based in Uttar Pradesh, India. ivirth.com is the solutions site for digital twins, digital product passports, traceability and lifecycle data; our corporate site is ivirth.in. For personal information you give us through this site, iViRTH decides why and how it is used (the “data fiduciary” under the DPDP Act, or “controller” under GDPR). ## 2. Information we collect - Enquiry details you choose to provide: name, work email, organisation, industry, project type, number of records or entities, the product, asset, facility or process involved, current data sources and systems, desired outcome and timeline, and any message. - Correspondence: what you send us by email and what we reply. - Basic technical data: like most websites, our hosting provider may log IP address, browser type, pages requested and timestamps for security and reliability. - Browser storage: none. This site does not set cookies or use local or session storage (see Cookie notice). We do not ask for sensitive personal information. Please do not include confidential supplier, commercial or personal data of third parties in an enquiry; we will agree how to handle project data separately. ## 3. How the enquiry form works The form does not send data to a server on this site. When you submit it, your email app opens with your enquiry pre-filled, and nothing is sent until you press send in that app. The message is then handled by your email provider and ours. You can edit or remove any detail before sending. ## 4. Why we use your information and our legal basis PurposeBasis Responding to enquiries, clarifying requirements, scoping a pilot or assessmentYour consent (you submit and agree to be contacted); legitimate uses; steps before a contract Following up on a proposal or engagement you requestedConsent / performance of a contract Securing and maintaining the site; preventing abuseLegitimate interests / legitimate uses Meeting legal obligations and handling disputesLegal obligation / legal claims We do not sell personal information, and we do not use it for automated decisions that significantly affect you. ## 5. Who we share it with Only as needed, and only with parties bound to protect it: email, hosting and infrastructure providers that run the site and our mailboxes; professional advisers; and authorities where the law requires. If we later add analytics, scheduling or CRM tools, we will list them in this notice. We may share information within iViRTH’s corporate group so the right team can respond. ## 6. International transfers Our providers may process data outside your country, including outside India. Where required, we rely on appropriate safeguards such as contractual commitments, and we limit what is transferred. ## 7. How long we keep it We keep enquiry information only as long as needed for the purpose it was collected, to handle any resulting engagement, to meet legal, accounting or dispute requirements, and then delete or anonymise it. If you ask us to erase your information, we will do so unless the law requires us to retain it. ## 8. Security We use reasonable organisational and technical measures, including access limited to people who need it and encrypted connections (HTTPS) to this site. No method of transmission or storage is completely secure, so we cannot guarantee absolute security. See our security overview. If a personal data breach affects you, we will notify you and the relevant authority as the law requires. ## 9. Your rights - Access a summary of the personal information we hold and how it is used. - Correct or update inaccurate or incomplete information. - Erase information that is no longer needed for its purpose. - Withdraw consent at any time; this does not affect earlier lawful use. - Grievance redressal and the right to nominate another person to exercise your rights if you die or become incapacitated (DPDP Act). - If GDPR applies: also restriction, portability, objection, and the right to complain to your supervisory authority. To exercise a right, email hello@ivirth.in with “Privacy request” in the subject. We may need to verify your identity, and we aim to respond within 30 days. If you are unhappy with our response, you may complain to the Data Protection Board of India or your local authority. ## 10. Children This site is intended for business visitors and is not directed at children. We do not knowingly collect personal information from anyone under 18. If you believe a child has sent us information, contact us and we will delete it. ## 11. Customer and project data Data you provide for a pilot or implementation (such as product, material, asset or supplier records) is handled under the written agreement for that engagement, which sets ownership, access, retention and deletion. See data principles. Public passport pages never include confidential supplier, commercial, personal or operational data. ## 12. Links to other sites This site links to other sites, including ivirth.in and standards bodies. We are not responsible for their content or privacy practices; please read their notices. ## 13. Changes to this notice We may update this notice as the site or the law changes. The “last updated” date above shows the current version, and we will make material changes clear on this page. ## 14. Contact Privacy questions, requests and grievances: hello@ivirth.in (subject “Privacy request”), or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Terms of use # Terms of use Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com These terms govern your use of ivirth.com (“the site”), operated by iViRTH (“iViRTH”, “we”, “us”). By using the site you agree to them. If you do not agree, please do not use the site. Contents - About the site - Capability statements and status labels - No certification or compliance guarantee - Demonstrations and sample data - Enquiries and engagements - Acceptable use - Intellectual property - Feedback - Third-party links and standards - Availability and changes - Disclaimer - Limitation of liability - Privacy and cookies - Governing law and disputes - Changes to these terms - Contact ## 1. About the site The site provides information about iViRTH’s digital twin, digital product passport, traceability and lifecycle data capabilities. It is general information for business visitors, not an offer capable of acceptance, and not professional, legal, regulatory, engineering or financial advice. ## 2. Capability statements and status labels We label capabilities as available now, delivered as a service, prototype or demonstration, in development, or planned. Only items labelled “available now” are presented as existing, tested features; anything planned is a future intention and may change or not be delivered. Capabilities such as IoT connectivity, real-time monitoring, simulation or predictive analytics apply only where implemented and demonstrated for a specific engagement. ## 3. No certification or compliance guarantee Implementation support is not certification, verification or accredited assurance, and is not a guarantee of compliance with any law, standard or regulation (including EU Digital Product Passport rules, which are introduced progressively and depend on product-specific requirements and legislation). Regulatory assessment, laboratory testing, certification and independent assurance are offered only through appropriately qualified or authorised parties. You remain responsible for your own compliance decisions. ## 4. Demonstrations and sample data Demonstrations use clearly labelled, illustrative sample data. They show record structure and how modules connect, not real products, suppliers, results or customers, and must not be relied on as evidence of any claim. ## 5. Enquiries and engagements Submitting an enquiry does not create a contract or any obligation on either side. Any pilot, assessment or implementation is subject to a separate written agreement that defines scope, deliverables, responsibilities, acceptance criteria, dependencies, exclusions, fees and support. Information you send in an enquiry should not include confidential third-party data. ## 6. Acceptable use - Do not misuse the site, attempt unauthorised access, or probe, scan or test its security without written permission. - Do not introduce malware, overload the service, or use automated means to extract content in a way that harms the site. - Do not submit unlawful, infringing, misleading or abusive content, or someone else’s personal data without authority. - Do not misrepresent your identity or affiliation, or imply endorsement by iViRTH. ## 7. Intellectual property The site’s content, design, text, graphics, logos, software and code are owned by or licensed to iViRTH and protected by intellectual property laws. You may view the site and share links to it. You may not copy, modify, distribute or create derivative works from it without our written permission, except as the law allows. The iViRTH name and logos are our marks. Third-party names, standards and trademarks belong to their owners. ## 8. Feedback If you send ideas or suggestions, you allow us to use them without obligation or compensation, while you keep any rights in your own pre-existing materials. ## 9. Third-party links and standards Links to external sites, standards and regulatory sources are provided for convenience and context. We do not control or endorse them and are not responsible for their content or availability. They do not, by themselves, determine the requirements for your products or implementation. ## 10. Availability and changes We aim to keep the site available but do not guarantee uninterrupted or error-free access. We may change, suspend or remove content or features at any time. ## 11. Disclaimer To the fullest extent permitted by law, the site and its content are provided “as is” and “as available”, without warranties of any kind, express or implied, including accuracy, completeness, fitness for a particular purpose and non-infringement. ## 12. Limitation of liability To the fullest extent permitted by law, iViRTH is not liable for indirect, incidental, special, consequential or punitive loss, or for loss of profit, revenue, data or goodwill, arising from your use of or inability to use the site or reliance on its content. Nothing in these terms excludes liability that cannot be excluded by law, such as for fraud or fraudulent misrepresentation. Liability under any engagement is governed by its written agreement. ## 13. Privacy and cookies Our privacy notice and cookie notice explain how information is handled and form part of how we operate this site. ## 14. Governing law and disputes These terms are governed by the laws of India. Subject to any mandatory rights you have as a consumer or under local law, the courts at Uttar Pradesh, India have exclusive jurisdiction over disputes arising from them. We encourage you to contact us first so we can try to resolve concerns informally. ## 15. Changes to these terms We may update these terms. The “last updated” date shows the current version; continued use after a change means you accept it. ## 16. Contact Questions about these terms: hello@ivirth.in or the contact page. --- Home / Trust & governance # Trust is built on accurate claims A digital record does not automatically prove every statement it contains. We say what exists, what is delivered as a service, and what is still planned, and we avoid claims we cannot support. ## What we do not claim - A QR code alone is a complete digital twin, or guarantees a compliant passport. - Automatic compliance with every jurisdiction or product regulation. - Certification, independent verification or accredited assurance, unless provided by appropriately qualified parties. - Real-time monitoring, predictive maintenance, simulation or IoT connectivity, unless that specific capability is implemented and demonstrated. - Customer logos, results or case studies, without permission and substantiation. - Exposure of confidential supplier, commercial, personal or operational data in public passport pages. ## How we label capabilities Available nowExists, is tested, and can be shown or delivered. Delivered as a serviceDelivered through a scoped consulting or implementation engagement. Prototype / demonstrationA limited demonstrator, not yet production-ready. In developmentActively underway, with limitations disclosed. Planned / roadmapA future intention, never presented as available. ## Trust and policy pages ### Privacy notice How we use personal information. ### Terms of use Rules for using this site. ### Cookie notice What the site stores in your browser. ### Accessibility statement WCAG 2.2 AA target and how to report a barrier. ### Security overview How we protect information. ### Data principles Ownership, access, quality and provenance. ### Data retention and deletion How long we keep data and how it is deleted. ### Data rights Access, correct, erase, withdraw, complain. ### Service scope and support What engagements include and exclude. ### Responsible AI and analytics How we use analytics and AI responsibly. ### Acceptable use Rules for using the site and services. ### Disclaimer Limits of the information on this site. ### Children’s privacy Our approach to children’s information. ## Standards and regulatory context We explain standards and laws in context, with sources. See the reference starting points. Last reviewed 16 October 2026. ReminderA general schema is not a substitute for product-specific regulatory analysis. Questions about how we handle your data or our claims? Contact us --- Home / Security overview # Security overview Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements This page describes how iViRTH approaches information security. It states what we do and, just as importantly, what we do not claim. It is an overview, not a contractual commitment; commitments for an engagement are set in its written agreement. Contents - Our approach - This website - Client and project data - People and suppliers - Incident response - Responsible disclosure - What we do not claim - Your responsibilities - Contact ## 1. Our approach We design for least privilege, auditability and separation of public from confidential information. Controls are proportionate to the data involved and agreed per engagement. ## 2. This website - Served over encrypted connections (HTTPS) with security headers configured at the host (content-type protection, referrer policy, frame restrictions, permissions policy). - A static site: no user accounts, no database and no server-side form processing, which greatly reduces exposure. - No advertising or tracking cookies and no third-party scripts or fonts are loaded; fonts and code are self-hosted. - The enquiry form hands your message to your own email app; nothing is stored by the site. ## 3. Client and project data - Access control: role-based access, least privilege, and removal of access when no longer needed. - Audit trails: source, responsible party, version and change history for records, where the module is implemented. - Separation: confidential supplier, commercial, personal or operational data is never shown on public passport pages. - Transfer: data is exchanged by agreed secure channels, not by unprotected email, wherever practical. - Minimisation: we ask only for data needed for the agreed scope. ## 4. People and suppliers Staff and contractors with access to client data are bound by confidentiality obligations. Service providers are selected for appropriate security practices and engaged on terms that protect the data they handle. ## 5. Incident response If we detect a security incident that affects personal or client data, we investigate, contain it, and notify affected parties and authorities as the law and the engagement agreement require, without undue delay. ## 6. Responsible disclosure If you believe you have found a vulnerability, email hello@ivirth.in with “Security” in the subject. Please give enough detail to reproduce it, avoid accessing or changing data that is not yours, do not disrupt the service, and allow us a reasonable time to fix it before disclosure. We will acknowledge good-faith reports and will not pursue action against research that follows these rules. ## 7. What we do not claim Unless stated and evidenced in writing, we do not claim formal security certifications (for example ISO/IEC 27001 or SOC 2), independent penetration-test results, or that any system is immune to attack. No system can be completely secure. ## 8. Your responsibilities Protect credentials issued to you, tell us promptly of suspected misuse, and do not upload data you are not entitled to share. ## 9. Contact Email hello@ivirth.in with “Security” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Data principles # Data principles Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements These principles guide how iViRTH handles product, material, asset, supplier and lifecycle data in its work. Specific terms for an engagement are set in its written agreement, which prevails if different. Contents - Ownership - Purpose limitation and minimisation - Access and visibility - Evidence, provenance and verification - Data quality - Interoperability and portability - Personal data - Governance - Contact ## 1. Ownership You keep ownership of the data you provide and the records created from it. iViRTH uses it only to deliver and support the agreed work. We keep rights to our pre-existing methods, tools, templates and know-how. ## 2. Purpose limitation and minimisation We collect and process only the data needed for the defined scope, and do not repurpose client data for other clients or for model training without your explicit written agreement. ## 3. Access and visibility - Each record has an owner and defined access rights. - Public, partner and internal views are separated; public pages contain only information approved for publication. - Confidential supplier, commercial, personal and operational data is never exposed in public passport pages. - Sharing with third parties (for example suppliers or regulators) happens only as agreed. ## 4. Evidence, provenance and verification A digital record does not automatically prove every statement in it. We record sources, responsible parties, document references, versions and verification status, and we make clear what has and has not been verified. Self-declared supplier information is labelled as declared. ## 5. Data quality - Validation rules and completeness checks agreed per scope. - Versioning and change history for important fields. - Reporting on gaps and inconsistencies rather than silently filling them. ## 6. Interoperability and portability Where practical we use open, structured formats and documented interfaces so you can export your records and avoid lock-in. Export formats are agreed in scope. ## 7. Personal data Where a project involves personal data, roles (controller or processor), lawful basis, security and transfers are set in the agreement and in line with applicable law. See our privacy notice and retention and deletion policy. ## 8. Governance We aim to agree record ownership, update responsibilities, change management and audit expectations at the start of each engagement. ## 9. Contact Email hello@ivirth.in with “Data principles” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Service scope and support terms # Service scope and support terms Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements This page sets out the standard basis on which iViRTH scopes and delivers pilots, assessments and implementations. It is not a contract; each engagement is governed by its own written agreement, which prevails if different. Contents - How engagements work - What a scope defines - Typical services - Capability status - Client responsibilities - Acceptance - Change control - Support - Exclusions - Intellectual property and confidentiality - Fees, suspension and termination - Liability - Contact ## 1. How engagements work Discover → Define → Design → Implement → Validate → Maintain. Work begins only after a written scope or agreement is accepted by both sides. ## 2. What a scope defines - Objectives and the defined product category, asset group, facility or process. - Number of entities or records, data sources and systems involved. - Deliverables, timeline and milestones. - Responsibilities of each party, and dependencies. - Acceptance criteria and how they are tested. - Fees, expenses and payment terms. - Explicit exclusions. ## 3. Typical services Readiness assessments, data modelling and schema mapping, record creation and onboarding, QR-linked record interfaces, integration planning and engineering, data quality and governance design, training and ongoing support. See the services page. ## 4. Capability status Anything we deliver is described by its status: available now, delivered as a service, prototype, in development or planned. Roadmap items are not commitments unless written into the agreement. ## 5. Client responsibilities - Provide accurate, timely and lawfully obtained data and access. - Name a decision-maker and a day-to-day contact. - Review and accept deliverables within agreed periods. - Own your regulatory and compliance decisions. ## 6. Acceptance Deliverables are accepted when they meet the agreed criteria. Defects against the criteria are corrected within a reasonable time; acceptance is deemed if no material issues are raised within the agreed review period. ## 7. Change control Changes to scope, data volumes, timeline or fees are agreed in writing before work proceeds. Work outside the scope is quoted separately. ## 8. Support Training, record maintenance, managed support and roadmap reviews are scoped per engagement, including hours, channels, response targets and the support period. Unless agreed, support does not include new features, new data onboarding or third-party systems. ## 9. Exclusions Regulatory assessment, laboratory testing, product certification and independent assurance are provided only through appropriately qualified or authorised parties. Implementation support is not certification or a guarantee of compliance. Real-time monitoring, simulation, predictive analytics and IoT connectivity are in scope only where specifically agreed and implemented. ## 10. Intellectual property and confidentiality You keep ownership of your data and records. iViRTH keeps its pre-existing tools, methods and know-how, and grants you the rights needed to use the deliverables as agreed. Each party keeps the other’s confidential information confidential. Case studies and logos are used only with written permission. ## 11. Fees, suspension and termination Fees and payment terms are in the agreement. Either party may end an engagement on notice as agreed or for material breach; completed work is paid for and data is returned or deleted under our retention policy. ## 12. Liability Liability is limited as set out in the agreement and, to the extent permitted by law, excludes indirect and consequential loss. Nothing excludes liability that cannot lawfully be excluded. ## 13. Contact Email hello@ivirth.in with “Service scope” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Responsible AI and analytics # Responsible AI and analytics Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements iViRTH’s core work is structured data, identity and lifecycle records. Where analytics, simulation or AI-assisted features are used, they follow the principles below. We describe capabilities by status and do not present planned features as available. Contents - Scope - Principles - Use of client data - Validation and monitoring - Limits - Using this website - Raising a concern - Contact ## 1. Scope These principles apply to analytics, indicators, simulation, predictive or optimisation workflows, and any machine-learning or AI-assisted feature iViRTH builds, integrates or uses in its services. Such features are offered only where implemented and demonstrated for the engagement. ## 2. Principles - Transparency: we state what a feature does, its data sources, and its known limitations. - Human oversight: outputs support decisions and do not replace accountable human review, especially where outcomes affect people, safety or compliance. - Fitness for purpose: models and rules are used only with suitable data, and validated before being relied on. - Accuracy and honesty: we do not overstate performance, and we label estimates, simulations and predictions as such. - Privacy and security by design: minimise personal data and apply the safeguards in our security overview. - Fairness: we look for bias and unintended effects where models affect people. - Accountability: a named owner is responsible for each analytical feature in an engagement. ## 3. Use of client data We do not use client data to train general-purpose models, or share it with other clients, without explicit written agreement. Where third-party AI services are used, we tell you, and use only providers whose terms prevent your data being used for their own training unless you agree. ## 4. Validation and monitoring Analytical outputs are tested against agreed measures before use, and reviewed over time for drift, data-quality issues and errors. We document material assumptions and limitations. ## 5. Limits AI and analytics can be wrong. Outputs are not legal, engineering, medical or regulatory advice, and should not be the sole basis for high-stakes decisions. ## 6. Using this website This site does not use AI to make automated decisions about visitors, and does not profile visitors. ## 7. Raising a concern If you think an analytical output is wrong, unfair or harmful, tell us and we will review it and, where needed, correct or withdraw it. ## 8. Contact Email hello@ivirth.in with “Responsible AI” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Accessibility statement # Accessibility statement Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements iViRTH wants ivirth.com to be usable by as many people as possible, including people who use screen readers, keyboards, magnification, speech input, and people with cognitive, hearing, motor or visual differences. This statement describes our standard, what we have done, what is still imperfect, and how to tell us about a barrier. Contents - Our commitment and standard - Conformance status - Accessibility features - Known limitations - Compatibility - Alternative formats and help - How we assess - Feedback and complaints - Statement review - Contact ## 1. Our commitment and standard We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We treat accessibility as part of design and content quality, and review it whenever the site changes. ## 2. Conformance status This site is partially conformant with WCAG 2.2 Level AA, based on our own review. It has not yet been independently audited. Known exceptions are listed below, and we will update this statement after any formal audit. ## 3. Accessibility features - Keyboard access: navigation, the mobile menu, the quick-navigation palette (Ctrl/Cmd+K or “/”), accordions and forms all work without a mouse, with a visible focus outline. - Skip link: “Skip to content” is the first focusable element on every page. - Structure: one main heading per page, a logical heading order, landmarks (header, navigation, main, footer) and descriptive link text. - Contrast: dark text on a light background, with body text designed to meet the 4.5:1 minimum contrast ratio. - Reduced motion: where your device asks for reduced motion, animations, transitions and reveal effects are removed or minimised. - No-JavaScript fallback: all page content, including menu links and FAQ answers, is visible without scripts. - Forms: every field has a visible label, required fields are marked, and the consent checkbox is a native control. - Responsive and zoom-friendly: layouts adapt to phones, tablets and desktops, and content reflows at 200% and 400% zoom without horizontal scrolling. - Quiet by default: the site plays no sound or video and does not autoplay media. - Decorative graphics hidden: the animated hero graphics are marked as decorative and hidden from assistive technology. ## 4. Known limitations - Animated graphics: the hero graphics move slowly and are decorative. Turn on “reduce motion” in your operating system to stop them. - Rotating headline phrase: the hero line cycles through three phrases. All three are present in the page text; the cycling itself is decorative. - Third-party documents: standards and regulatory sources we link to are not under our control and may not be fully accessible. - Sample passport demo: the QR graphic in the demonstration is illustrative and is not scannable. We are working to reduce these limitations. ## 5. Compatibility The site is designed for current versions of Chrome, Edge, Firefox and Safari, and common screen readers such as NVDA, JAWS, VoiceOver and TalkBack. It uses HTML, CSS and a small amount of JavaScript; content remains readable without JavaScript. ## 6. Alternative formats and help If you cannot use part of the site, or need information in another format, we will help, for example by providing content as plain text or by email. A plain-text version of the site is available at llms-full.txt. ## 7. How we assess We review pages against WCAG 2.2 AA, test keyboard operation, zoom, reduced-motion settings, page structure, labels and colour contrast, and re-check whenever content or features change. ## 8. Feedback and complaints Tell us about any barrier, or ask for an accessible alternative, through the contact page or by email with “Accessibility” in the subject. Please include the page address, what you were trying to do, and the assistive technology or browser you use. We aim to acknowledge your message within five working days and send a substantive reply or fix plan promptly after. If you are not satisfied, you may contact the accessibility or consumer authority in your country. ## 9. Statement review This statement is reviewed at least once a year and after significant changes, such as the redesign of the site. ## 10. Contact Email hello@ivirth.in with “Accessibility” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Cookie notice # Cookie notice Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements This notice explains what ivirth.com stores in your browser. In short: it stores nothing, and it sets no cookies. Contents - What we store - Third-party requests - Your browser - If this changes - Contact ## 1. What we store ivirth.com does not set cookies and does not use local storage or session storage. It holds no personal information in your browser. ## 2. Third-party requests The site loads its fonts, stylesheets and scripts from its own domain. It does not load third-party trackers, social-media widgets or advertising. Links to ivirth.in and other sites are only followed when you click them. ## 3. Your browser Because nothing is stored, there is nothing for this site to clear. Your browser may keep its own cache of site files, which you can clear in your browser settings. ## 4. If this changes If we add analytics or any other non-essential technology, we will ask for your consent first where the law requires it, list it on this page, and update the date. See also our privacy notice. ## 5. Contact Email hello@ivirth.in with “Cookies” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Data retention and deletion # Data retention and deletion Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements This policy explains how long iViRTH keeps different kinds of data and how data is returned or deleted. Engagement agreements may set different periods and prevail where they do. Contents - Principles - What we keep and for how long - End of engagement - Deletion on request - Legal holds and exceptions - Public passport records - Contact ## 1. Principles - Keep data only as long as there is a clear purpose or a legal duty. - Delete or irreversibly anonymise when that purpose ends. - Make retention and deletion explicit in each engagement. ## 2. What we keep and for how long DataRetention Website enquiries and related emailWhile needed to respond and follow up; if no engagement follows, we review and delete or anonymise once the enquiry is no longer needed. Proposals, contracts and invoicesFor the period required by contract, tax, accounting and limitation law. Project data you provide (records, documents, supplier data)For the engagement and any agreed support period, then returned or deleted as agreed. Platform records and audit trails created for youAs agreed in the engagement; audit history may be retained as needed to evidence changes. Website server logsFor a short, security-focused period set by our hosting provider, then rotated. BackupsOverwritten on the provider’s normal schedule after the live data is deleted. ## 3. End of engagement - Export: on request we provide your records in an agreed structured format. - Deletion: we then delete live copies within a reasonable period and confirm in writing on request. - Backups are overwritten in the normal cycle and are not restored for other uses. ## 4. Deletion on request To ask us to erase your personal data or project data, email hello@ivirth.in with “Deletion request”. We verify your identity and authority, act on valid requests without undue delay (aiming for 30 days), and tell you if something must be kept, and why. ## 5. Legal holds and exceptions We may keep data longer where the law requires, where needed to establish, exercise or defend legal claims, or to resolve a dispute. Such data is restricted to those purposes. ## 6. Public passport records Records you choose to publish, including QR-linked passport pages, remain available until you withdraw or change them under the agreed process. Withdrawing a record does not remove copies others have already made. ## 7. Contact Email hello@ivirth.in with “Retention” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Data rights # Data rights Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements You have rights over your personal information. This page explains them, how to use them, and what to expect. It supplements our privacy notice. Contents - Your rights - How to make a request - What to expect - When we may say no - Customer project data - Complaints - Contact ## 1. Your rights - Access: a summary of the personal data we process and how. - Correction and completion: fix inaccurate or incomplete data. - Erasure: deletion when the data is no longer needed for its purpose. - Withdraw consent at any time, as easily as it was given. - Grievance redressal: a way to raise concerns and get a response. - Nominate someone to exercise your rights if you die or become incapacitated (DPDP Act). - If GDPR applies: restriction, portability, objection, and not to be subject to solely automated decisions with significant effects. ## 2. How to make a request - Email hello@ivirth.in with “Data rights request” and the right you want to use. - Tell us the email address or details you used with us, so we can find your data. - We may ask you to verify your identity before sharing or changing data. ## 3. What to expect We acknowledge requests promptly and aim to respond fully within 30 days. If a request is complex or numerous we will tell you why more time is needed. Requests are free unless clearly unfounded or excessive, in which case we may decline or charge a reasonable fee as the law permits. ## 4. When we may say no We may limit or refuse a request where the law allows or requires, for example to protect others’ rights, to comply with legal retention duties, or where we cannot verify your identity. We will explain our reasons. ## 5. Customer project data If your personal data is processed by us on behalf of a client, please contact that client first; we will help them respond. ## 6. Complaints If you are unhappy with our response, you may complain to the Data Protection Board of India or, if you are in the EU/UK, your local supervisory authority. We would welcome the chance to resolve the matter first. ## 7. Contact Email hello@ivirth.in with “Data rights request” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Acceptable use policy # Acceptable use policy Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements This policy sets the rules for using ivirth.com and any iViRTH platform, record or interface we provide. It supports our terms of use. Contents - You must not - Records and passports - Security testing - Enforcement - Reporting abuse - Contact ## 1. You must not - Break the law, infringe others’ rights, or help anyone do so. - Attempt unauthorised access, bypass security or access controls, or use someone else’s credentials. - Scan, probe or test our systems without written permission. - Upload malware, or interfere with, overload or disrupt the service. - Scrape or extract content at a scale or in a manner that harms the service. - Submit false, misleading, defamatory, abusive or discriminatory content. - Submit personal, confidential or proprietary data you are not entitled to share. - Misrepresent identity, or imply endorsement or certification by iViRTH. - Use records or passports to publish unsubstantiated compliance, sustainability or safety claims. ## 2. Records and passports Information you publish through a passport or record must be accurate, evidenced where claimed, and lawful. You are responsible for the content you publish and for not exposing confidential data. ## 3. Security testing Good-faith vulnerability reports are welcome under our responsible disclosure process. Testing beyond that needs prior written permission. ## 4. Enforcement We may remove content, suspend access or end an engagement for breaches, and report unlawful activity to the authorities. Where practical we will explain the reason and give you a chance to fix the problem. ## 5. Reporting abuse Tell us about suspected misuse so we can investigate. ## 6. Contact Email hello@ivirth.in with “Acceptable use” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Disclaimer # Disclaimer Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements Please read this disclaimer with our terms of use. It explains the limits of the information on this site. Contents - General information only - No compliance guarantee - Regulatory and standards context - Capability statements - Demonstrations - Industries and use cases - Third-party content - Limitation - Contact ## 1. General information only The content on this site is general information about digital twins, digital product passports, traceability and lifecycle data. It is not legal, regulatory, engineering, financial, tax or other professional advice. Take advice suited to your circumstances. ## 2. No compliance guarantee A QR code alone is not a complete digital twin and does not by itself produce a compliant passport. Implementation support is not certification and not a guarantee of compliance with any law, standard or regulation. Obligations vary by product group, market and applicable legislation. ## 3. Regulatory and standards context Descriptions of laws and standards (including the EU Digital Product Passport framework, which is introduced progressively) are simplified, may change, and carry a review date where shown. They are not a substitute for product-specific analysis. Check primary sources. ## 4. Capability statements Capabilities are labelled by status. Features marked in development or planned may change or not be delivered. IoT connectivity, real-time monitoring, simulation and predictive analytics apply only where implemented and demonstrated for a specific engagement. ## 5. Demonstrations Demonstrations use clearly labelled sample data and are illustrative. They are not real results, customers, products or suppliers. ## 6. Industries and use cases Industry pages describe target application areas, not proof of existing customer deployments. ## 7. Third-party content We link to external sites and standards for convenience. We do not control or endorse them and do not accept responsibility for their content. ## 8. Limitation To the fullest extent permitted by law, we are not liable for loss arising from reliance on this site’s content. Nothing limits liability that cannot lawfully be limited. ## 9. Contact Email hello@ivirth.in with “Disclaimer” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Children’s privacy # Children’s privacy Effective: 16 October 2026Last updated: 16 October 2026Applies to: ivirth.com and iViRTH engagements ivirth.com is a business site. This page explains our approach to children’s information. Contents - Who this site is for - What we collect - If we learn we hold a child’s data - For parents and guardians - Project data - Contact ## 1. Who this site is for The site is intended for professionals evaluating digital twin, passport and traceability projects. It is not directed at children, and we do not knowingly market to anyone under 18. ## 2. What we collect We do not knowingly collect personal information from anyone under 18, and we do not track or profile children, show behavioural advertising or use their data for automated decisions. We do not seek verifiable parental consent because we do not intentionally process children’s data. ## 3. If we learn we hold a child’s data We will stop using it and delete it promptly. ## 4. For parents and guardians If you believe your child has sent us information, email hello@ivirth.in with “Children” in the subject and we will act on it. See also our privacy notice and data rights. ## 5. Project data If a client project involves children’s data, special safeguards, a lawful basis and any required guardian consent are set in the agreement and applicable law before processing begins. ## 6. Contact Email hello@ivirth.in with “Children” in the subject, or use the contact page. iViRTH, Uttar Pradesh, India. --- Home / Legal # Legal and trust centre Every policy that governs this site and our engagements, in plain language. Last updated 16 October 2026. ### Privacy notice How we use personal information. ### Terms of use Rules for using this site. ### Cookie notice What the site stores in your browser. ### Accessibility statement WCAG 2.2 AA target and how to report a barrier. ### Security overview How we protect information. ### Data principles Ownership, access, quality and provenance. ### Data retention and deletion How long we keep data and how it is deleted. ### Data rights Access, correct, erase, withdraw, complain. ### Service scope and support What engagements include and exclude. ### Responsible AI and analytics How we use analytics and AI responsibly. ### Acceptable use Rules for using the site and services. ### Disclaimer Limits of the information on this site. ### Children’s privacy Our approach to children’s information. For how we label capabilities and what we do not claim, see Trust & governance. Questions about a policy? Contact us