Terms of Service v2.0

Effective: May 25, 2018
GraspIO reserves the right to modify this Agreement at any time and in its sole discretion. The date of the latest revision will be noted at the top of this page. Modified terms will be notified in advance either via email or a mobile app notification, and will become effective on the date of the revision . Your use of the Site, Products, or the Services after the date changes become effective constitutes your acceptance of the modified terms. You are responsible for regularly reviewing this Agreement and any additional terms or notices posted on the Site.

Section 1: Definitions

Section 2: General Terms

Section 3: Projects

Section 4: Email

Section 5: Voice Recording and Speech Recognition

Section 6: Data Transmission and Storage

You agree that you understand and accept the below:

Section 7: IoT Cloud Metering

Note: GraspIO reserves the right to modify the Cloud Call Metering charges at any stage. Modified terms will be notified to you in advance either via email or the mobile app and will become effective immediately upon posting on the Site. Your use of the app or the Services after the date changes become effective constitutes Your acceptance of the modified terms.

It is to be noted here that all call related credits (Free calls and daily calls) apply to one board and are non-transferable between boards linked to, or held under the same account.
Besides during deployment and execution of GraspIO projects, Cloud calls are made for execution, data collection and transmission, over the IoT Cloud. It is to be noted that certain advanced IoT features of the GraspIO app are designed to work only with/through the IoT Cloud.

Block / FunctionNumber of Execution CallsNumber of Special Calls
Monitor *19
IFTTT(Trigger)**5 (For every trigger instance)100 (Per sensor)

* 1 Call per value per mobile device.

Each instance of fetching a sensor data value on GraspIO Studio consumes 1 call per mobile device. For example: If John’s project fetches and displays 30 values from 1 sensor in a 30-minute monitoring duration, 30 calls are made. If John monitors 2 sensors in the project, 60 values are collected, and hence, 60 calls made. However, if John fetches the same data on GraspIO Studio running on another mobile device, the same number of calls will be consumed again by this second session.

Call deductions will begin once the project is uploaded to the board irrespective of the applet creation on IFTTT. So, if the board is configured to work as a Trigger for IFTTT, call deductions will be made when the triggers are fired on the device even if the applet is not created or enabled for the board. Every time a project is uploaded, and 1 Sensor-Trigger is set, 1 deployment call is made, in addition to 100 Special calls for the sensor. Each subsequent trigger (as and when fired during the course of the project's run-time) consumes 5 calls. Further, if 3 sensors are being used as Triggers in 1 project, 1 deployment call is made, in addition to 300 Special calls (100 for each sensor) being deducted at the time of upload. Over and above this, 5 calls are consumed each time a trigger is fired.

Section 8: Data and Permissions

While creating your account with GraspIO, we use your email ID to register, identify, and manage your account. We confirm that we do not process, share, publish, or misuse this data. You can delete your account with GraspIO using the Delete account option in the GraspIO Studio. This will permanently delete all your data with GraspIO.


Any media such as captured images, video, and audio are owned by you. We do not access this information that is linked to your account and saved in an encrypted format on the IoT Cloud. Any data created using the Email and Camera block is saved for a period of 7 days. Any voice related media is saved in your account. Deleting your project deletes this data from your account.

Modifying and deleting your account

You can delete your account with us at any time. Since the projects and media is related to your account, at this stage, you cannot modify the email ID associated with your account. You can however, delete your existing account after migrating your projects to the new account.

Deleting your account deletes all current projects and any IFTTT associations will be discarded.


The GraspIO Studio mobile app uses certain permissions in order for you to create and deploy your projects. These are explained in detail below:

Voice record, speech recognition

These permissions are required for the functioning of the Voice and Playback blocks.

The Voice block lets you record a voice prompt which is further processed using speech recognition before being used in the project deployment. The usage of these blocks in your projects therefore require Voice Record and Speech Recognition permissions. The Playback block lets you record audio that can be used in your projects. This audio is recorded using the Voice record permissions of your device.

Storage and Read/Write

This is used to allow GraspIO to temporarily create files for the below purposes

USB Twinkle

The USB Twinkle process transfer the network credentials from the mobile device to the Cloudio hardware using a USB connection between the two.The network data is temporarily written into a file that is accessed by GraspIO to retrieve the details. This file is deleted after the transfer of credentials is completed.


The voice recording created as part of the Playback functionality is temporarily saved on the mobile device before it is encoded for transmission and further usage when the project is deployed.This file is deleted immediately after the encoding is completed.

Section 9: Restrictions

Section 10: Trademarks and Attribution

Section 11: Disclaimer of Warranties

Section 12: Limitation of liability