Open tmancey opened 3 years ago
@tmancey we discussed this in the privacy confab and it sounds fine, but just a reminder that for new features/things that expose user info it's best to go through a security/privacy review.
@ShivanKaul once the work is complete a security/privacy review will be requested before we merge. Thanks
Startup
Database
Locale
GET /v1/getstate
Account
Wallet
Issuers
Unblinded tokens
Failed confirmations
Unblinded payment tokens
Past transactions
Notification ads
New tab page ads
Inline content ads
Promoted content ads
Resources
Contextual
Text classification
Behavioral
Conversions
Epsilon greedy bandit
Purchase intent
Anti targeting
Catalog
Notification ads
New tab page ads
Inline content ads
Promoted content ads
User interaction
Idle detection
User activity
Classification
Contextual
Text
Behavioral
Epsilon greedy bandit
Purchase intent
Permission rules
--enable-features
command-line args on productionAds
Notification ads
New tab page ads
Inline content ads
Promoted content ads
History
Transfer (aka Landed)
Conversions
Server
responses
Issuers
GET /v1/issuers/
endpointRedeem unblinded payment tokens
PUT /v2/confirmation/payment/{payment_id}
endpointRedeem unblinded token
Create confirmation
POST /v2/confirmation/{confirmation_id}/{credential}
endpointFetch payment token
GET /v2/confirmation/{confirmation_id}/paymentToken
endpointRefill unblinded tokens
POST /v2/confirmation/token/{payment_id}
endpointRefill unblinded tokens
GET /v2/confirmation/token/{payment_id}?nonce={nonce}
endpointCatalog
GET /v9/catalog
endpointSubdivision targeting
GET /v1/getstate
endpoint