Postbox

img_postbox04

The technology behind Private Sharing

Our client apps for mobile, desktop and web applications all use the underlying digi.me cloud services to do 3 things

Securely collect user data

Move user data to their personal cloud storage

Share personal data with full user consent

img_postbox04
img_postbox01

Application partners using the digi.me SDK

We provide ultra-light sample apps with the SDK built in. You can build your apps around the SDK quickly The SDK has the benefit of:

 Simplifies and hides the connections to the digi.me cloud

Wraps up all the security and encryption libraries

Manages the requests to the digi.me app for user approvals

img_postbox02

SDK supports Private Sharing give and get

The SDK supports user consent for each Private Sharing function in 2 specific ways

GET DATA | Private Sharing (Consent Access) request - Requests the user to consent for data to be shared according to the Private Sharing Contract. Data is pulled to your app

GIVE DATA | Postbox request - Requests the user to consent for an application partner to push data to their Postbox

img_postbox02
img_postbox03

Data exporters Give data back to users

Digi.me cloud services support 2 methods for companies holding user data to return it to them:

API | from data sources that support API, where the user has an access credential and authenticates to access their data via digi.me

GIVE | from data sources that integrate with the digi.me cloud services via our Postbox SDK

Sample app showing SDK functions

Here you see the sample app offering each option, the implementation allows developers to see the two different functional modes for giving and getting user data with consent

img_sampleappsdk
postbox0
STEP 1
Select Give vs Get data path

Select the runtime option

postbox1
STEP 2
Give data = Postbox mode

Ask the user to select the action to send a “demo” receipt to their digi.me library via the SDK and digi.me cloud service

postbox2
STEP 3
SDK calls the digi.me app

Passing the private sharing contract details setup in the SDK initiation

postbox3
STEP 4i
Digi.me app Consent Request

The digi.me app has fetched the secure copy of the sharing contract and shown to the user in readable form with access to the T&C and data sharing details

postbox4
STEP 4ii
User Approves

Once the user approves the data push request there is a short delay while the digi.me cloud creates a secure crypto postbox to receive user data

postbox5
STEP 5
Partner App regains flow control

The digi.me cloud service, via the SDK returns a secret key for your partner app to use in the data push, and to retain for future use in the same way as an Oauth class Access Token.

postbox6
STEP 6
Digi.me app user refresh

In the digi.me app the user can trigger a refresh with a soft scroll down

postbox7
STEP 7
Digi.me app sees new data

The digi.me app can now see and display the data receipt pushed by the partner app

postbox8
STEP 8
Pushed data collection

In the digi.me app the user see all data from each partner pushing to them, in this case just the recent demo item

postbox9
STEP 9
Looking at the data itself

The digi.me app support an object inspector that displays the object attributes. It will not render image or pdf class docs natively for security protection reasons, but allows export to other viewers