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.
GraspIO products provide an email functionality (through the Camera and Email blocks of the GraspIO Studio mobile app). You can thus send emails from the board (or GraspIO Cloud) to your registered email address (in the Camera block) and other other email addresses (in the Email block) selected by you while creating your projects in GraspIO Studio.
Camera block:
By using these blocks in your projects, You agree that You have understood the usage of this block and have authorised the GraspIO board and Cloud service to send you emails and media on your registered email ID.
Email block:
By using these blocks in your projects,You agree that You have understood the usage of this block and have authorised the GraspIO board and Cloud service to send emails and media on your behalf to the email addresses selected by You while using this block/application.
Additionally, you agree that you understand that the email functionality on GraspIO is designed such that there is a minimum 15-minute interval between successive emails sent by the Service.
A total of 20 email blocks (or a maximum of 40 emails, 2 emails per block) can be used in a day.
You are responsible for designing projects and IoT solutions that consider this aspect in their design and functionality. GraspIO will not be held liable for any loss (of data or otherwise) or damage caused due to a failure to consider this limitation while using the Service.
You are responsible for designing projects and IoT solutions that consider this aspect in their design and functionality. GraspIO will not be held liable for any loss (of data or otherwise) or damage caused due to a failure to consider this limitation while using the Service.
You are solely responsible for Your conduct and any data, files, information, images, photos, video clips, sounds, and/or any other content or materials that You create, transmit, or share via the usage of this functionality. GraspIO does not access, share, or publish this information that is stored on the GraspIO Cloud for a period of 7 days in compliance with standard data storage procedures.
You agree that you understand and accept the below:
GraspIO uses Secure Socket Layer (SSL) encryption for communication between any GraspIO Products/ Services. This includes any communication between the GraspIO Cloud, the GraspIO Studio app as well as GraspIO hardware products. Data collected by GraspIO via its Products, Websites and Services is stored on secure third-party servers.
Content created (or collected) by You for your projects such as image, audio, and video content along with data such as sensor values, dashboard data, etc. are saved and linked to your account.
Any media content created using the Camera and Email blocks is saved on the GraspIO Cloud as per the third-party security standards and deleted after a period of 7 days from creation.
Audio recordings created as part of the Playback block in GraspIO Studio in a project are encoded before it is saved on the GraspIO IoT Cloud. This data can be decoded only using GraspIO technology, thus ensuring data security and privacy.
Any user content created by You, such as images, audios, videos, and zip files are not password-protected at the time of transmission to other platforms such as email or notifications.
Though GraspIO complies with the above security practices and standards for transmission and storage of data, a possibility exists that an unauthorized third-party could discover user content while it is being transmitted over the internet from GraspIO to your personal accounts during the process of sharing or exporting data/user content. No method of transmission over the Internet, or method of electronic storage, is 100% secure, therefore, we cannot guarantee its absolute security.
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.
A project may be deployed to the GraspIO board over the internet using GraspIO’s Cloud service, IoT Cloud. All cloud related services are measured using Cloud Calls. A Cloud Call is a traffic based measurement. Any one-way communication between GraspIO Cloudio and GraspIO Studio App via IoT Cloud is one call.
Each board is preloaded with 50,000 free Cloud Calls. Upon completion of 50,000 calls, 100 daily non-cumulative calls are credited to your account for life. Cloud Calls plans that require usage above these limits can be purchased via the GraspIO Studio app as per the payment terms outlined therewith.
The daily calls are credited at 12:00 AM GMT.
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.
A project on GraspIO Studio is created using a combination of blocks. Each block consumes a certain number of calls that are deducted from your account. This number is deducted from the account each time (and every time) this block is executed.
Cloud calls for a project are calculated based on
o The number of times it is deployed.
(Each instance of deployment (be it on a board, or a repeated case of deployment) of the project counts as a separate call)
o The blocks included inside it
(Includes additional feature based calls for advanced blocks, and execution calls corresponding to internet calls used directly or indirectly by the block)
For a project the number of calls incurred will be sum of the three calls explained below.
o Deployment call – Call(s) made when the project is deployed. This refers to 1 call per instance of deployment.
o Execution call - Call(s) made as part of the project execution. Corresponding call rates will be levied each time the feature is executed.
o Special call - Call(s) made by a special block(s) which either uses the Internet or includes blocks with unique capabilities within the project.
Each time a project is deployed, 1 deployment call is made.
In addition, the Cloud calls corresponding to individual functions or blocks within the project are deducted from your account.
The calls corresponding to each block/function are summarized below.
Block / Function | Number of Execution Calls | Number of Special Calls |
---|---|---|
Read | 0 | 0 |
Stop | 0 | 0 |
Speak | 10 | 0 |
Notification | 10 | 0 |
20 | 0 | |
Camera | ||
Photo | 10 | 0 |
GIF | 20 | 0 |
Video | 100 | 0 |
Timelapse | 100 | 0 |
Playback | 0 | 10 |
Monitor * | 1 | 9 |
Speech | 10 | 9 |
Schedule | 10 | 9 |
IFTTT(Trigger)** | 5 (For every trigger instance) | 100 (Per sensor) |
IFTTT(Action)*** | 100 | 100 |
* 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.
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.
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:
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.
This is used to allow GraspIO to temporarily create files for the below purposes
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.