Smart home data security: why your data is safe with Cosy
Published: 19/08/16 By: April Bowles
Published: 19/08/16 By: April Bowles
Your Cosy smart thermostat has its own unique frequency – 868 MHz if you’re interested! It’s this wireless frequency that helps get your Cosy heating data from A (e.g. the controls on your Cosy Display) to B (the Cosy Switch on your wall).
Having our own special protocol that no one else can access means we’re able to guard your data securely – even more securely than Mr Tibbs, your cat, guards his comfiest blanket!
What’s more, because Cosy isn’t connected to any other devices – either via the same hub or wireless network – this means you avoid the effects of any other security breaches that may come your way through a less secure device on the same network. Phew!
Yes, it certainly is! This means that from one end of your wireless connection, right the way through to the other, your electronic data is encrypted – i.e. your data is turned into jumble of letters and numbers at one end and can only be decrypted again at the other end (by us) using a special cipher key. Clever, hey?
When it comes to data security and the storing of your details, we also have some very strict rules that we apply. These make sure that any data stored (your name, email address, password, etc.) is stored securely and that it’s not passed on to any one else – no PPI-chasers, no compensation companies, no-one without your consent!
For more info on our privacy policy and personal data practices, please take a look at the privacy policy outlined in our terms and policies section.
Like we said at the start of this post, we take data security really seriously – so if you do ever notice any out-of-the-ordinary activity on your Cosy account or receive any suspicious-looking emails, we’d really appreciate it if you could flag these up with our support team – as soon as possible – so that we can investigate further.
In the meantime, if you’d like any more information about our data encryption or privacy policy, please get in touch with our support team who’d be happy to help put your mind at rest. We look forward to hearing from you!
Cookie | Duration | Description |
---|---|---|
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__utma | 2 years | This cookie is set by Google Analytics and is used to distinguish users and sessions. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmb | 30 minutes | Google Analytics sets this cookie, to determine new sessions/visits. __utmb cookie is created when the JavaScript library executes and there are no existing __utma cookies. It is updated every time data is sent to Google Analytics. |
__utmc | session | The cookie is set by Google Analytics and is deleted when the user closes the browser. It is used to enable interoperability with urchin.js, which is an older version of Google Analytics and is used in conjunction with the __utmb cookie to determine new sessions/visits. |
__utmt | 10 minutes | Google Analytics sets this cookie to inhibit request rate. |
__utmz | 6 months | Google Analytics sets this cookie to store the traffic source or campaign by which the visitor reached the site. |
_gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |