Skip to main content

Compliance / Engineered into the system

Obligations become
operating controls.

Valueye helps teams turn privacy, security, sector, and contractual requirements into architecture, workflows, ownership, verification, and evidence.

Read our posture

CURRENT POSTURE / 04 SEP 2026

Precise claims.
Real scope.

01

Valueye maps controls to the product, data, jurisdiction, contract, infrastructure, and responsibility model in scope.

02

We do not claim a certification, attestation, audit outcome, penetration-test result, or universal legal compliance unless current evidence supports that exact statement.

03

This page describes an engineering and assurance approach. It is not legal advice, and customer counsel or compliance owners determine applicable obligations.

01 / REGULATORY LANDSCAPE

Designed for obligations that have consequences.

These are common reference points—not a complete legal inventory. Every engagement begins by confirming the entity, product, processing activity, jurisdiction, and current effective requirement.

INDIA / DATA

DPDP Act & Rules

We can support purpose-aware collection, notices and consent journeys, data-principal requests, retention, deletion, security safeguards, breach workflows, and processor responsibilities where applicable.

The Digital Personal Data Protection Act, 2023 and notified 2025 Rules use phased commencement. Applicability and implementation dates must be assessed for each organisation.

Official source

INDIA / CYBER

CERT-In directions

Systems can be designed to support incident identification, time-aware escalation, evidence preservation, log availability, clock synchronisation, and accountable reporting workflows.

The 2022 directions and related FAQs apply according to entity, incident, service, and legal scope; operational procedures must reflect the applicable requirement.

Official source

INDIA / BFSI

RBI technology obligations

For regulated customers, we can support outsourcing governance, due diligence, audit access, monitoring, data protection, business continuity, cloud controls, and exit planning through explicit technical and contractual inputs.

The regulated entity retains its regulatory obligations and must determine which RBI directions apply to its business and arrangement.

Official source

EU / PRIVACY

GDPR

Where the GDPR applies, architecture can support controller-processor boundaries, data-subject rights, minimisation, privacy by design, processing records, security, retention, and international-transfer decisions.

Roles, lawful basis, territorial scope, transfer mechanisms, notices, and legal conclusions belong in a customer-led legal and privacy assessment.

Official source

WEB / ACCESSIBILITY

WCAG 2.2

We use the Web Content Accessibility Guidelines as the technical reference for perceivable content, keyboard operation, understandable interactions, and robust implementation.

Automated checks are useful but do not establish conformance by themselves; representative browsers, devices, keyboards, and assistive technologies still require human testing.

Official source

02 / COMPLIANCE BY ARCHITECTURE

Make the right action the natural action.

Controls work best when they live inside the product and operating model—not in a document nobody opens.

01

Data inventory and classification

Know what information exists, why it is processed, where it travels, who can reach it, and how sensitive it is before selecting controls.

02

Purpose, notice, and consent

Translate product intent into understandable collection points, permissions, revocation paths, and durable records where consent or notice is required.

03

Identity and least privilege

Use role-based access, strong authentication, administrative separation, periodic review, and explicit service identities appropriate to the risk.

04

Auditability and evidence

Preserve useful, access-controlled records of sensitive actions, approvals, changes, and events so reviews can reconstruct what happened.

05

Retention and deletion

Define lifecycle rules for live data, exports, logs, backups, and third-party systems, with exceptions and verification where the product requires them.

06

Incident and recovery readiness

Connect detection, severity, escalation, customer coordination, regulatory decision points, restoration, and post-incident improvement before an event occurs.

07

Third-party governance

Make provider purpose, data access, location, contractual controls, monitoring, change, and exit requirements visible throughout the engagement.

08

Shared responsibility

Document which controls belong to Valueye, the customer, cloud or model providers, and end users—then keep those boundaries current.

03 / BFSI READINESS

Controls a regulated business can operate.

For banking, financial services, wealth, lending, distribution, trading, and insurance-adjacent systems, we design for oversight—not just feature completion.

01

Maker-checker and approval paths

02

Role and entitlement governance

03

Consent and transaction evidence

04

Traceable administrative action

05

Environment and tenant separation

06

Vendor and cloud visibility

07

Continuity and recovery inputs

08

Exit and data-return planning

A regulated entity remains accountable for its obligations, governance, approvals, supervision, and customer outcomes. Valueye supplies engineering, documentation, and operating inputs within the agreed responsibility boundary.

04 / ASSURANCE WITHOUT THEATRE

Frameworks guide. Evidence proves.

Standards and assurance frameworks are useful when their scope, control ownership, operating period, exceptions, and evidence are understood.

01

CONTROL SYSTEM REFERENCE

ISO/IEC 27001

Useful for structuring an information security management system and its risk-based controls. Referencing the standard is not a claim of certification.

02

ASSURANCE REFERENCE

SOC 2

Useful when customers need independent assurance mapped to applicable Trust Services Criteria. A framework reference is not a claim that a current SOC report exists.

03

ENGAGEMENT CONTROL SET

Customer requirements

Contractual, procurement, architecture, data-residency, recovery, and sector requirements are mapped to the exact product and operating model.

05 / EVIDENCE LIFECYCLE

A control is a living system.

01

Discover

Identify law, contract, data, business process, system boundaries, vendors, and accountable owners.

02

Map

Translate obligations and risks into controls, responsibility, evidence, exceptions, and acceptance criteria.

03

Engineer

Build the necessary product, identity, infrastructure, workflow, logging, privacy, and recovery mechanisms.

04

Verify

Review design and implementation, exercise important paths, address findings, and record the result.

05

Operate

Retain evidence, monitor change, revisit access and vendors, rehearse response, and improve the control set.

06 / COMPLIANCE QUESTIONS

Ask what is true now.

We would rather give a qualified, useful answer than a broad statement that fails under scrutiny.

01Is Valueye certified to ISO 27001 or audited against SOC 2?+

Valueye does not represent a certification, attestation, audit result, or report as current unless it can provide the applicable evidence and scope. ISO/IEC 27001 and SOC 2 may be used as useful control and assurance references when a customer engagement requires them.

02Can Valueye support DPDP Act and GDPR obligations?+

Valueye can design product, data, identity, retention, consent, and operational controls to support obligations identified for an engagement. The customer and its advisers remain responsible for determining applicable law, roles, lawful grounds, notices, and final compliance requirements.

03How does Valueye support regulated BFSI teams?+

For relevant BFSI systems, Valueye can engineer role-based access, maker-checker workflows, audit trails, consent evidence, environment segregation, monitoring, resilience, vendor-risk inputs, and exit considerations. Final regulatory applicability and approval remain with the regulated entity.

04Who owns compliance responsibility?+

Responsibility is shared and documented. Valueye is responsible for the controls and services assigned to it under the engagement; customers retain responsibility for their business processes, data-controller or data-fiduciary decisions, user administration, legal interpretation, and regulatory obligations unless an agreement expressly says otherwise.

05How are third parties and subprocessors handled?+

Relevant providers should be identified, assessed, contractually governed, granted only necessary access, and monitored in proportion to risk. Provider selection, data location, exit needs, and customer approval requirements are established for the engagement.

06Can a customer request security and compliance evidence?+

Yes. Subject to confidentiality, contractual scope, and the sensitivity of the material, customers can request relevant policies, architecture information, control ownership, testing scope, recovery information, and other available evidence through Valueye's review process.

CONTROL REVIEW

Your requirement deserves an exact answer.

Share the product, data, jurisdiction, customer role, regulatory context, and assurance request. We will map what exists, what is customer-owned, and what needs to be engineered or independently verified.

Request a control review Visit the Trust Center