Transaction data never reaches persistent storage
Finarkein processes consented bank data in memory, returns a structured answer, and keeps only the audit trail. Borrower transaction data does not persist on Finarkein infrastructure.
Borrower consent governs every data access
Finarkein does not access a borrower's financial data without a valid, active consent token from an RBI-regulated Account Aggregator. The borrower may revoke consent at any time.
Signed consent token needed
Before each query, Finarkein validates the digitally signed consent artifact from the Account Aggregator before requesting data from a bank FIP. Without consent, analysts cannot access data.
Defined consent windows
Consent covers a specified period and data window. Finarkein enforces both limits, preventing queries beyond the window approved by the borrower, even when the FIP holds more data.
Instant revocation
After a borrower revokes consent through the Account Aggregator, Finarkein receives notice and immediately stops further queries under that consent reference.
How data passes through Finarkein
Raw transaction data follows a controlled route from the FIP through the AA to Finarkein's processing layer, where it is used and then discarded.
Bank FIP
The bank FIP holds raw transaction data. It is not copied or stored outside the FIP without active consent.
AA Consent Layer
The RBI-regulated Account Aggregator verifies the consent artifact and routes the request.
Finarkein Processing
Data is processed only in encrypted memory. Raw transactions never enter disk or persistent storage.
Audit Record Only
The audit log stores the structured answer and reasoning trace. Raw data is discarded after each query.
Aligned to RBI AA framework requirements
Finarkein operates as a Financial Information User (FIU) under the RBI Account Aggregator framework. Accordingly, the regulator defines the data access model, consent requirements, and audit duties, rather than Finarkein's internal policies.
The framework requires purpose-limited access, data minimisation, and borrower consent throughout. Finarkein's architecture enforces these controls at the infrastructure level, not only through policy.
- Access limited to the consented purpose
- Data minimised: only query outputs retained
- Complete audit trail for each access event
- TLS 1.3 encryption in transit and in memory
- Access restricted to authorised analyst roles
- Immutable query log for regulatory review
Questions about borrower data handling?
Book a session to review the complete data flow.