Overview
In this article, you will learn how the App collects, stores, and transfers data.
Before You Start
Not all users will have access to the RecDesk Engage App cockpit. User access is determined by your original agreement upon purchase.
What data is stored or processed in the keychain/secure enclave on the user's mobile device?
- Personal identifiable information such as RecDesk Member unique IDs, First/Last name
- Recdesk Username & Password for authenticating to RecDesk with API
- Token for authenticating with the API
Who has access to data in the keychain/secure enclave?
Data stored in personal devices in the keychain/secure enclave is only accessible by the locally installed App. This is not accessible by any party other than the locally installed App.
What data is stored or processed on AWS hosted Innovatise servers?
- Personally identifiable information such as RecDesk Member unique IDs, First/Last name
- Usage statistics such as app opens, app navigation
- Push notification content and notification user engagement statistics (view, open, action)
- Cockpit CMS configuration data
- System Logs, including personally identifiable information such as RecTrac Member unique IDs, IP addresses
Who has access to the data stored on AWS hosted Innovatise servers?
Data stored on AWS hosted Innovatise servers is accessible to key Innovatise and RecDesk personnel that perform the following roles:
- DevOps, for the management of the platform
- Support, for supporting the solution
- CEO/Head of Product, for escalation purposes
- Key senior members of the engineering team for support and maintenance of the platform
- Users will only be given the minimum access required to perform their role, and access will be revoked as soon as it is no longer needed.
Statistical data and basic personally identifiable information, such as RecDesk Member unique IDs, First/Lastname, is available to configured municipal RecDesk Engage App Admin users via the Cockpit CMS. Users and roles are managed by the RecDesk Engage App Admin.
How does the App transfer data?
- App/Cockpit CMS to RecDesk APIs using an authenticated HTTPS communication
- App to AWS hosted Innovatise servers using AWS Identity and Access Management (IAM) HTTPS communication
- Cockpit CMS to AWS hosted Innovatise servers using AWS OAuth HTTPS communication
Is cardholder data stored or processed by the Native App or Innovatise?
No, cardholder data is not stored or processed by the local app or Innovatise.
How are payments processed?
Payments are processed by the RecDesk Engage App using URL redirection to a third-party hosted payment page exactly as they are processed for a customer browsing the RecDesk site on a desktop computer. For more information, consult the payment processor documentation for your deployed RecDesk payment integration.