JP Morgan Chase 2015 Annual Report Download - page 23

Download and view the complete annual report

Please find page 23 of the 2015 JP Morgan Chase annual report below. You can navigate through the pages in the report by either clicking on the pages listed below, or by using the keyword search tool below to find specific information within the annual report.

Page out of 332

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332

2121
We need to protect our customers, their data and
our company.
We necessarily have a huge amount of data
about our customers because of under-
writing, credit card transactions and other
activities, and we use some of this data to
help serve our customers better (I’ll speak
more about big data later in this letter).
And we do extensive work to protect our
customers and their data – think cyber-
security, fraud protection, etc. We always
start from the position that we want to be
customer friendly. One item that I think
warrants special attention is when our
customers want to allow outside parties to
have access to their bank accounts and their
bank account information. Our customers
have done this with payment companies,
aggregators, financial planners and others.
We want to be helpful, but we have a respon-
sibility to each of our customers, and we are
extremely concerned. Let me explain why:
• When we all readily click “I agree” online
or on our mobile devices, allowing third-
party access to our bank accounts and
financial information, it is fairly clear
that most of us have no idea what we
are agreeing to or how that informa-
tion might be used by a third party. We
have analyzed many of the contracts of
these third parties and have come to the
following conclusions:
Far more information is taken than the
third party needs in order to do its job.
Many third parties sell or trade infor-
mation in a way customers may not
understand, and the third parties,
quite often, are doing it for their own
economic benefit – not for the custom-
er’s benefit.
Often this is being done on a daily basis
for years after the customer signed up
for the services, which they may no
longer be using.
We simply are asking third parties to limit
themselves to what they need in order to
serve the customer and to let the customer
know exactly what information is being used
and why and how. In the future, instead
of giving a third party unlimited access to
information in any bank account, we hope to
build systems that allow us to “push” infor-
mation – and only that information agreed to
by the customer – to that third party.
• Pushing specific information has another
benefit: Customers do not need to provide
their bank passcode. When customers
give out their bank passcode, they may
not realize that if a rogue employee at
an aggregator uses this passcode to steal
money from the customer’s account, the
customer, not the bank, is responsible for
any loss. You can rest assured that when
the bank is responsible for the loss, the
customer will be fully reimbursed. That
is not quite clear with many third parties.
This lack of clarity and transparency isn’t
fair or right.
Privacy is of the utmost importance. We
need to protect our customers and their data.
We are now actively working with all third
parties who are willing to work with us to set
up data sharing the right way.
Why are you making such a big deal about protecting customers’ data in your bank?