68/100

Moderate evidence

GainPublished recordBusinessGood Space

Different Strokes for Different Folks: Exploring Algorithmic Fairness and Trust in Generative Artificial Intelligence

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

ABSTRACT Generative artificial intelligence (GenAI) is widely used to personalize recommendations, yet questions remain about the representativeness of algorithmic recommendations to recognize diverse consumer needs. This research integrates the stimulus‐organism‐response model and social identity theory to inform how personalization influences recommendation acceptance through algorithmic fairness and trust and how communication style affects these processes, which may differ between ethnic groups. Using a sequ…

The gain

In a 136-person experiment, highly personalised generative AI recommendations increased recommendation acceptance, perceived algorithmic fairness and trust compared with low personalisation.

What this doesn’t fix

The ethnic-group comparison came from a quasi-experiment rather than a randomised design, and the interview study had only 14 participants.

Sources

1 on file
  1. Psychology & Marketingdoi:10.1002/mar.70306
    Peer-reviewed2026-11-17

Cite this record

v1

Truvace Impact Record TRV-2026-3042, v1: “Different Strokes for Different Folks: Exploring Algorithmic Fairness and Trust in Generative Artificial Intelligence.” Truvace, 2026-11-19. /record/TRV-2026-3042 (accessed on the day you copy it). sha256 b42c666fc0abfcbc…

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. Publishedv1b42c666fc0ab…

    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-3042 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.