Frequently Asked Questions
Question 1: What is Veloxity SDK and Does it impact my application’s performance?
• Veloxity Software Development Kit (SDK): This is a very light, low battery and low CPU consuming, device software that gets integrated with any existing user application(s) in Android, IOS, Unity and React Native environments and used for collecting behavioral/habitual data. The SDK enables constant communication with Veloxity Cloud where real-time information flow takes place, notifications are activated to reach out to consumers in a timely and relevant manner. Veloxity SDK is;
- Easy to integrate, takes about 1 hour,
- Consumes less than 1% battery/day,
- Lightweight, very low CPU, very low network data consumption,
- Works independent from the application,
- User Privacy conscious and respectful.
• The Veloxity SDK is an isolated background service. It is going to be actively monitoring the significant events even the app is not up and running. However it is not going to be active if there is no change in the location of the phone, or there is no
activity at the phone at all.
Question 2: How Do I Integrate The SDK? What do you require from my side?
The documentation and a video for seamless integration is available at (https://www.blinnk.com/how-to-integrate.html)
Veloxity SDK integration is extremely simple process and it can take up to an hour of the application developer’s time if the client does not require in app data services.
Question 3: What is the SDK’s impact on battery?
• Very minimal. For a full, active usage scenario SDK consumes less than 1% of the battery in a day.
Question 4: In case of downtime what is the expected behavior and its reflection on the app?
• The Veloxity SDK is an asynchronous service and works independently from the app. That is no uptime/downtime behavior will have any effect to the app. In addition, the SDK sends data in a best effort manner which means even in the rare case of a server unavailability, the unsent data does not affect neither the app nor the phone
Question 5: What kind of permissions would SDK require from the users?
• Only Location permission is required, both for IOS and Android.
Question 6: Is SDK capturing and/or storing any PII 'personal identifying information'?
• NO. Veloxity SDK creates a unique random identifier for each user device. But PII like real name, imsi, imei, phone number, email address, social media ids (sucs as FB, Instagram, Twitter, or alike), credit card number, citizenship number, home or work address, or anything similar are NOT collected nor stored. In terms of PII, it is much safer than well known Analytics SDKs or APIs.
• Looking at Veloxity data, there is no possibility to identify what the person's identity is, nor there is a reversible function to identify it.
• An important note: Veloxity offers an option in the case the Client wants to match Veloxity data with the customer identities that it stores in its CRM. Veloxity may share the device identity through its SDK with the Client’s app, which can be stored in Client’s servers. Then any data can be shared right after with the client’s servers with the device identity, which will enable The Client to identify the user. In this optional case, Veloxity servers still don’t have any PII stored, only the Client does!
Question 7: What is Blinkk?
Veloxity Platform’s User Interface (BLINNK): “Blinnk” is the client facing web portal where main reports/analysis are generated, and behavioral insights about the data collected are presented in a user-friendly GUI module. This easy-to-use interface also allows for self-configuration of marketing/sales campaign design and creation. Veloxity customers have access to the user interface through a demo account.
Question 9: Do we need to integrate a custom version of Veloxity SDK in our app?
• No but it is highly recommended. In order to fully benefit from Veloxity data enrichment capabilities you will need to integrate Veloxity’s generic SDKs in the app. There are two separate SDKs provided one for Android and one for IOS. In the case that the Client only requires Veloxity generated behavior data, it is simply adding the SDK and initiating it with a simple command.
• However, if the Client prefers to provide the in-app consumer behavior as well, then during the SDKs integration, the Client needs to use custom data class of the SDKs for any data that it sees fit to be sent to Veloxity servers.
Question 8: Who is Veloxity’s User Base?
• Veloxity Inc.’s user base consists of consumers who own smartphones including mobile apps. For a mobile user to be a part of the Veloxity network, they need to accept Veloxity’s user consent text and remain in the application minimum a week to be profiled by Veloxity big data algorithms.
• The SDK integration to Customer specific mobile app is also possible. It is an optional but commonly used feature and particularly useful if the customer desires to retarget its already engaged customers with the company’s mobile app or match their in-app behavior with Veloxity’s out-of-app behavioral segmentation.
Question 10: Where does Veloxity get its data ?
Veloxity collects three types of GDPR respectful data from the mobile phones.
Human Behavior Data (Veloxity Data): 1st Party Data from mobile devices (user behavior recorded in a device). The typical data contains user’s location, physical and online activities, user’s environmental conditions, electronic devices used, internet usage, sleeping habits, travel habits, shopping habits and more.
• Mobile App. Usage Data: 2nd Party Data (user behavior recorded in the mobile app) which includes user’s activities in the hosting app such as content consumed, products purchased, pages visited.
• Optional CRM Data: Veloxity can optionally integrate its client’s GDPR permitted CRM data into Veloxity cloud and match with 1st and 2nd party data for enrichment of consumer information.
• Human behavior data and mobile app data requires integration of the Veloxity SDK into the company’s mobile apps. However, the integration of the optional CRM data requires data transfer from Client CRM server to Veloxity cloud directly.
Question 11: Where is the data being stored, who have access to it and what is the data retention policy?
The data is stored in our Veloxity servers. Veloxity uses clouds such as Amazon and Azure. By Q2-2020, Veloxity will only be using Azure servers. By the end of Q2-2020, Customer’s will be given the option to choose the country for the servers where Azure is already available. For the time being, The cloud serves are physically located in Canada.
• The data can only be accessed by Veloxity’s own admin personnel, through a secure VPN, where the accessing IP addresses have to be predefined. All access logs are kept indefinitely. No third party company, including Veloxity partners and subcontractors, under no circumstances, can reach to data or to data servers.
• The data retention policy is in parallel with GDPR regulation accepted by the EU countries. That is in the case any device owner decides to remove the app or the device owner decides to take the data collection consent back, the device-based data is removed from the servers. Otherwise the data is collected starting by the first approval of the data collection consent with no time limit until the consent is taken back or the app is removed.