DODDLE DOCUMENTATION
Acceptable usage policy
Name of Sub-processor | Processing Activity |
---|---|
AWS | Hosting of the Platform and all data (including Personal Data) uploaded to the Platform. |
Crashlytics | Crashlytics is used to capture information when one of our mobile applications crashes. |
Okta | Okta is our repository for managing user accounts. We have separate repositories for internal and external users. |
NAV | NAV is our financial reporting system. It is hosted on Microsoft Azure. |
Zendesk | Zendesk is our ticket management system for both internal and external support requests. |
Flurry | Google Analytics is used to capture information about usage of our mobile applications. |
Sparkpost | Sparkpost is used to send transactional emails. |
Dropbox | Doddle uses Dropbox to provide file sharing and collaborative working. |
Slack | Doddle uses Slack to facilitate topic-based online chat, calls and collaboration. |
Twilio | Doddle uses Twilio to send SMS text messages to customers when a parcel is ready for collection. |
Urban Airship | Doddle uses Urban Airship to send push notifications and interact with mobile wallets. |
Pingdom | Doddle uses Pingdom to monitor the health of web-based services and APIs. |
OpsGenie | Doddle uses OpsGenie to send system alerts to on-call staff by push notification, text or phone call. |
Loqate | Doddle uses Postcode Anywhere to provide postcode lookup and geospatial services. |
Loggly | Doddle uses Loggly to hold technical logs for analysis and problem diagnosis. |
We use Google Vision API to run OCR on photos of parcels which we have not been able to reconcile to information from an integrated retailer partner. | |
Metapack | Doddle integrates with Metapack to receive manifest data. In some cases, Doddle uses the Metapack platform to create labels. |
Doddle uses Facebook Messenger to support the DoddleBot Facebook Chat Bot, which allows customers to setup a return to an integrated retailer via Doddle. |