Consent at LenderLink

No consent, no query.

You sign off on data risk, so here is the short version. Every check on our network starts with a borrower saying yes. Here is how that works, and how it lines up with Open Finance.

verified_user
Consent comes firstA lender can only ask about a borrower who agreed to the check.
handshake
Contracts back it upEvery member signs a Data Sharing Agreement. Same rule for everyone.
route
Built for what is nextOpen Finance adds a digital consent artefact. We are ready to carry it.
How it works

Two routes. Same rule.

Consent first, then data. Press Next and follow the flow.

On LenderLink today

Consent by contract

Live

The borrower says yes to the lender. Data Sharing Agreements carry that yes to every member on the network.

Borrowerapplies for a loanT&C +PRIVACY POLICYData Consumerinquiring lendercaptures consentLenderLinkexchange · routes queryrelies on member consentContributor 1Tier 1 · bankContributor 2Tier 1 · lenderContributor nTier 1 · fintechinquiry · resultDSA · CONSUMERDSA · CONTRIBUTOR1234

Back-to-back Data Sharing Agreements bind every member to the same consent standard. A query is only ever made about a borrower who gave consent.

VS
Where the industry is heading

Consent by artefact

Open Finance

The borrower says yes at the source. The source issues a digital consent artefact that can cover one recipient or many.

RECIPIENT ASKS · BORROWER GOES TO THE SOURCEBorrowerauthenticates at sourceConsent dashboardview · amend · revokeData Holderbank / lender / telcocaptures consent at sourceCONSENT ARTEFACTscope · purpose · recipientsexpiry · signature · logStandard APItoken checkedRecipient 1lenderRecipient 2BNPL / fintechRecipient 3insurerRecipient nany accredited partyissueschecks every call1234

Consent lives in a registry at the data holder, mirrored on a dashboard the borrower controls. Each release is checked against the artefact and logged.

Our commitments

Six things we hold ourselves to

verified_user

Consent before data

No bulk pulls. No browsing. A lender only asks about a borrower who agreed.

target

One purpose

Credit evaluation, fraud prevention and account management. Nothing else.

handshake

Everyone under contract

Members who ask and members who answer both sign a Data Sharing Agreement, with audit rights.

auto_delete

Keep only what we need

Personal data goes once the query is done. The audit trail stays, without the personal detail.

gavel

Philippine law first

Built around the Data Privacy Act of 2012 and the principles of BSP Circular 1122.

extension

Ready for the artefact

When data holders issue digital consent artefacts, the network can carry them.

Side by side

Two routes, one principle

Both put the borrower first. They differ in where consent is recorded.

LenderLink networkOpen Finance model
Who captures consentThe lender, in the applicationThe data holder, at sign-in
Form of consentAccepted terms, with proof kept per applicantA signed consent artefact
What binds the partiesData Sharing AgreementsCommon APIs and accreditation
Borrower experienceNo extra stepA short redirect to confirm consent
Reach of one consentOne lender, one purpose, one inquiryOne consent, many recipients
Status in the PhilippinesLive todayFramework set by BSP Circular 1122, rails still being built
Common questions

What partners ask us

Who collects the borrower's consent?

The lender, as part of the application. They are closest to the borrower, so that is where consent belongs.

What if a borrower says no?

Then no query is made. No consent, no query.

Can the data be used for anything else?

No. Only credit evaluation, fraud prevention and account management.

How long do you keep personal data?

Only as long as it takes to complete and evidence the query. Then it is removed. The audit record stays, without the personal detail.

This page explains consent on the LenderLink network in general terms. The Data Sharing Agreement and each member's privacy notice govern the detail. Last updated September 2026.