Solutions
About Us
Need help? Here's the guide for you
It depends on your use case.
These are few common examples from our clients:
A. Trigger the SDK during the “submit application” action to collect data for the registered customer.
B. Trigger the SDK at landing/log-in page to collect data for all users.
After the SDK is successfully integrated, you need to push an app update for it to start collecting data.
Reference number is used as a dataset identifier in the credolab server. Client will use this reference number to retrieve insights (score & fragment).
The reference number is generated during data collection process by SDK.
It depends on your use case.
Most of our clients is using the combination of the Loan ID or User ID + Timestamp.
If specified reference number isn’t unique, the data collection is terminated with an error message.
No, credolab SDK does not track location because it does not run in the background and it does not process personal data.
We update the SDK at least once per year to ensure that our clients have the latest technology compatible with the newest Operating Systems being announced (or released) and also have access to all the new data points we find during our R&D investigations. As soon as a new Android OS version is available, we test the current SDK first and implement changes only if needed. It is our commitment to inform you of the latest changes and guide you through the implementation options whenever required.
The average datasets is about 117 Kb. Having said this, it is important to notice that the size of a dataset depends on the SDK version and on the permissions that are enabled. The more permissions the SDK has access to, the bigger the amount of data collected and the bigger the size of the dataset.
Yes, although the average size of a dataset is about 117Kb, the maximum dataset size is 30MB.
According to the Google Play policy, some permissions are classified as "dangerous" and some are not. Below find the list of the dangerous permissions that you can enable via our SDK:
- Media (READ_EXTERNAL_STORAGE)
- Contacts (READ_CONTACTS)
- Calendar (READ_CALENDAR)
- Registered Account (GET_ACCOUNTS)
- SMS (READ_SMS)
And below find the list of all other permissions that are considered as "non dangerous" and that you can enable via our SDK:
- Application (QUERY_ALL_PACKAGES)
- Bluetooth
- Wifi (ACCESS_WIFI_STATE)
- Fingerprint (USE_FINGERPRINT)
- Internet
Yes, on top of the permissions described above, we offer the additional ones listed below:
- Usage Statistics (USAGE_STATS_SERVICE)
Do note that, since these permissions are considered as very sensitive by Google, they can only be integrated in your app if your app has already been approved by Google. Although we might assist Paid Subscribers along the approval process, credolab is not responsible for the outcome.
In case of error while uploading a dataset from the device to credolab's server, the SDK returns the appropriate error code with the message. Do note that, in such a case, the upload action doesn't repeat automatically and, to avoid data loss, you need to call the upload data action manually.
No, credolab SDK does not run in the background and works/collects data only when triggered by the hosting app.
Dangerous permission is the permission that can potentially affect the user’s privacy or the device’s operation. Despite the fact that credolab does not collect or process any personal data or personally identifiable information (P.I.I.), declaring a dangerous permission in the app manifest is required when integrating the SDK. Furthermore, the app user must be allowed allow/deny such permission.
Yes. Credolab's SDK can be easily integrated in a React Native environment. The guide for Android available here and iOS module is described here. Please speak to our Sales Representative here to learn more.
Normal or non-dangerous permissions are those permission that do not require any action by the app user.
Yes. Credolab's SDK can be easily integrated in a Flutter environment. The guide for Android available here and the project example is described here. Please speak to our Sales Representative here to learn more.
Yes, credolab's Android multi-modular SDK allows you to easily select which module(s) to enable/declare based on your business, existing permissions, use case, or requirements.
Yes, credolab's SDK can be easily integrated in Ionic environment. However, we do not offer such plugin to the free-trial user. Please speak to our Sales Representative here to learn more.
The credolab SDK supports Android version 4.1 and above.
Yes, we assist all our Paid Subscribers in publishing the app. We build and refine our knowledge by constantly monitor policy changes and also by testing the changes on our own apps before recommending implementation best practices.
These are the available permissions:
- Audio (NSAppleMusicUsageDescription)
- Calendar Event (NSCalendarsUsageDescription)
- Contact (NSContactsUsageDescription)
- Photo (NSPhotoLibraryUsageDescription)
- Calendar Reminder (NSRemindersUsageDescription)
Yes, credolab provides the modular SDK and you can customise the permission according to the existing permission inside your iOS App. However, it is not available for testing in our trial version. Please talk to our Sales Representative to learn more about it.
The minimum iOS version supported is iOS 9.0.
Yes, we assist all our Paid Subscribers in publishing the app. We build and refine our knowledge by constantly monitor policy changes and also by testing the changes on our own apps before recommending implementation best practices.
The insights can be retrieved via the single API we call "Dataset Insight API".
In order for you to test the Dataset Insight API you need to obtain the login credentials from credolab. To find out more, please refer to this link.
The Dataset Insight API v5.0 delivers the device information (e.g., device identifier, model, brand, whether it's repeated upload, etc.), the credoscore (or multiple scores), and the fragment(s). Depending on their particular use case and requirements, each Paid Subscriber has customised scorecard and fragments.
A scorecard is a statistical measurement of the relative credit risk profile of an applicant. The main purpose of credolab's scorecard is to create a ranking of applicants by estimating their probability to default. In accordance with credit bureau scorecards and scores, the higher the credolab score, the less likely the customer is to default.
The trial environment is configured with a testing scorecard. The credit score generated is used for API testing only.
Credolab use standard FICO format to return the score.
No, we don't recommend you to use the score calculated by the testing scorecard during the trial period. The credit score generated by the testing scorecard is for testing purposes only.
A Fragment is any information or insight, besides the risk score, that can be extracted from the digital footprint of a device. This information or insight can be delivered only if the relative permission is declared via the manifest of your app.
Sample fragments include:
- Number of applications in the "Gambling" app category.
- If the user has the "Facebook" app installed.
- Number of photos from camera.
We configured a sample fragments that currently are being used by some of our clients such as:
- Device
- Permission
- Velocity
- Installed Apps tracking
- Contacts information
Yes, Fragments can be customised depending on your requirements. However, customised fragments are only available to our Paid Subscribers.
Sample fragments include:
- Number of applications in the "Gambling" app category.
- If the user has the "Facebook" app installed.
- Number of photos from camera.