DataSchutz Home Page
Sections
Why DataSchutz

Controls built around the transaction decision itself.

DataSchutz combines fraud-prevention research with practical cybersecurity and infrastructure experience, supporting evaluation from sandbox design through integration planning.

Inside the authorisation window

Risk is evaluated while the transaction can still be approved, challenged or stopped.

Contextual risk signals

Device, session, location, behaviour, transaction and merchant context inform decisions.

Low-friction decisions

The architecture is intended to avoid unnecessary steps for legitimate users.

API-oriented integration

CELT-UV is designed for integration with payment and digital-banking decision flows.

Privacy-conscious telemetry

Contextual risk evaluation is designed around purpose-limited signals rather than broad identity collection.

Auditable outcomes

Decision factors can support explainable review and institution-specific governance.

Pilot and sandbox support

Evaluation can begin in controlled environments before any production decision is considered.

Security beyond the API

Cybersecurity, network and infrastructure services support the wider control environment.

Privacy-conscious architecture

Strict purpose limitation — telemetry, not identity.

CELT-UV is designed around purpose-limited telemetry for transaction risk scoring and security evaluation. DART - Dynamic Authorization and Risk Tokenisation (an API for fraud prevention in instant payment systems like UPI, Payshap, Wero, Pix and Fedpay) remains under development.

Data-minimisation intent

The architecture is designed not to require names, national identity numbers or bank account numbers for its contextual risk models. Final data handling depends on the agreed integration and the customer’s operating environment.

What we ingest

  • User app behaviour
  • Device integrity signals
  • Location
  • Merchant / POS score
  • Transaction patterns

Telemetry separation, retention and access controls can be defined during integration to support the customer’s applicable privacy and governance obligations.