Support FAQ - SMARTfit Cloud

After creating a cloud account, you can sign in and begin using your SMARTfit system as usual. If your controller has not been registered yet, you will be asked to register it.

No, by default your data will be private. By taking no action and leaving your account as private, your data will never be accessible in the public API.

Yes, later this year with the release of the public API and groups, profiles will be classified as either public or private (private is default). Data belonging to private profiles will not be able to be pulled via the API, unless it is pulled through group data retrieval calls which will be password protected by the group administrator. Data belonging to public profiles will be able to be pulled by anyone via the API.

We will also be taking a look at further developing in-app analytics that can provide an easy export of this data.

Currently, data is only accessible in the app by the owner of the data, or a managing account that has been granted permission via a management request (similar to a friend request). SMARTfit uses the very secure Azure B2C identity management service developed by Microsoft to power our Sign Up/Sign In process, with data security being one of our top priorities.

User data is associated with a user across many tables using randomly generated user ID’s, so that the owner of the data cannot be identified with simple data analysis. Information hiding is used for sensitive information such as name, DOB, gender, etc.

The storage requirement of the SMARTfit app is very small as the size of the data being collected is very small. Even if a patient should have thousands of data points, it would translate to a small number of megabytes at most. The iPad running out of storage would not be an issue, as we handle the data load efficiently by only pulling data of the logged in user, and then wiping that data upon logout or login of another user.

Absolutely. Let’s explore the example of a doctor and patients using the SMARTfit cloud. At the time of sign in, the patient’s data is pulled from the cloud SQL database onto the local SQL database of the device. Our Azure App Service (server) is configured so that our app (client) can only download user data from an authenticated account, meaning a user who has signed in via HIPPA compliant Azure AD B2C.

At the time of sign out or sign in of another user, data is wiped from the local database which provides storage and security benefits. This ensures a minimal amount of data will actually be present on the local database at one time. For a patient sign in the local database would have data for one patient and for a doctor sign in the local database would have data for themselves and their patients.

Local sign in is not the recommended sign in for the SMARTfit app. However, it is an alternative for those to use SMARTfit that do not always have internet connection. With local sign in, data accessibility is limited to the local device only. Accounts created in this mode do not have the ability to sync data to the cloud continuously.

Cloud sign in is the recommended sign in for the SMARTfit app. It allows for you to take advantage of all that the SMARTfit app has to offer, such as data accessibility from any device (inpatient, outpatient, wellness and the local gym), groups (multiple sites sharing programming), remote training, remote client program design, global statistics, development of normative data and online software updates. To use cloud sign in, internet connection is required.

Your data is still accessible via local sign in. Upon sign up of a cloud account you will be asked if you would like to copy your old data to your new cloud account. Simply enter your local sign in credentials on this device when prompted, and your data will migrate to your new cloud account.

On the home page, select the red “switch database” icon. This will allow you to toggle back and forth from local sign in and cloud sign in. Note that data is not shared across sign in modes.

You are only required to use the cloud for controller management. This means you must have a cloud account to register a controller, update software, and manage the controller password (if you choose to set a password). You are not required to use the cloud for anything else. If you would like to continue using the app via local sign in, then you may continue to do so.

SMARTfit 2.0 offers cloud sign in. Previously, SMARTfit 1.x versions only offered local sign in.

The patient’s data remains on the cloud SQL database only until they sign into the app. The Azure platform and our cloud configuration ensures encryption in transit and encryption at rest in the cloud SQL database and even uses information hiding for sensitive information such as patient name, DOB, gender, etc.

The data tab and report building features allow for queried patient data to be transferred to a laptop via Excel and PDF reports that can be generated and emailed from the mobile app. For software developers wanting access to SMARTfit’s API, please ask a support person for details.

The tablet/phone running out of storage would not be an issue, as we handle the data load efficiently.
At the time of sign in, the patient’s data is pulled from the cloud SQL database onto the local SQL database of the device. Our Azure App Service (server) is configured so that our app (client) can only download user data from an authenticated account, meaning a user who has signed in via HIPPA compliant Azure AD B2C.

At the time of sign out or sign in of another user, data is wiped from the local database which provides storage and security benefits. This ensures a minimal amount of data will actually be present on the local database at one time.

Local Sign-In
For a patient sign in the local database would have data for one patient and for a doctor sign in the local database would have data for themselves and their patients. The size of the data being collected is very small. Even if a patient should have thousands of data points, it would translate to a small number of MB at most, and not GB.