68/100

Moderate evidence

GainPublished recordBusinessGood Space

Privacy and empathy in AI chatbots: A dual-route analysis of cognitive and emotional trust in financial services

Truvace record
TRV-2026-2687raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
256c44ac1ef2…check it

Trust remains a critical barrier to the adoption of artificial intelligence (AI) chatbots in financial services, yet extant research has not systematically examined how distinct communication strategies differentially shape cognitive and emotional trust. Grounded in Dual Process Theory and enriched by Theory of Mind, this study investigates how privacy communication and empathetic language influence users’ trust formation through complementary cognitive (System 2) and affective (System 1) pathways. Privacy commu…

The gain

In a 163-participant experiment with a GPT-based investment chatbot in a simulated banking scenario, privacy communication raised cognitive trust and empathetic language raised emotional trust.

What this doesn’t fix

The experiment ran in a simulated banking scenario with 163 participants, so the results do not show how trust would change with real customers and real money.

Sources

1 on file
  1. Peer-reviewed2026-06-03

Cite this record

v1

Truvace Impact Record TRV-2026-2687, v1: “Privacy and empathy in AI chatbots: A dual-route analysis of cognitive and emotional trust in financial services.” Truvace, 2026-11-12. /record/TRV-2026-2687 (accessed on the day you copy it). sha256 256c44ac1ef251ab…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1256c44ac1ef2…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2687 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.