Hello there, I wanted to respond to a few of the concerns brought up in this thread, as well as answer any questions that may come up!
Security and Safety
As mentioned by
@DOCAL , services that use the Tesla APIs (including Teslascope, and others like TeslaFi), have access to a vehicle's GPS coordinates and use it for calculating / logging specific metrics such as tracking drives and charging sessions.
Security is
incredibly important to me personally and many checks have been implemented across the platform to ensure we can provide a safe and secure experience for everyone who uses it. With that in mind, absolutely no location information is ever accessible publicly by anyone besides the vehicle owner, and any pages that contain sensitive data (including the requests for such) go through about six different checks to ensure of this.
Credentials and Tokens
As shared in this
comment on the Reddit announcement, the platform is built on Laravel, which uses a couple different methods for ensuring sensitive data is kept safe, which of course extends to tokens. We use AES-256 for encrypting all tokens, and then decrypt it on the fly when requesting for data from Tesla's APIs. The keys are additionally stored in an AWS Aurora database with substantial security put in place to prevent access including but not limited to only allowing the production server (also on AWS) to access it, 2FA enabled on all administrative accounts, and all other best practices followed.
To also keep our members safe, we don't disclose or even allow accessing the tokens associated to an account via any page nor request-able via data exporting. This ensures that in the case an account is compromised, a hacker can't use these tokens for malicious intent. In the near future, we'll also be implementing 2FA (OTP), which is something that TeslaFi and many other competitors don't offer. This is all in my goal of providing the safest, easiest to use (and understand) platform for Tesla vehicle owners!
Phantom Drain
There's many reasons why I began Teslascope, but at its root it began as a passion project. I wasn't happy with the experience I had navigating around TeslaFi and the various Sleep Modes and other aspects of preventing phantom drain confused me. I had seen the same experiences shared by other vehicle owners (both local, and on online communities) and wanted to make sure that the platform I worked on would solve this. I appreciate concerns like this brought up by
@tfraley .
Teslascope, through my own experience and from what was shared by a majority of the alpha testers (20+), has a slightly better time with phantom drain than TeslaFi and some other competitors and a lot of this is due to the simple Sleep Modes; of which there are only two.
You can set your vehicle to sleep between specific hours according to your timezone. In the case you're expecting to not use your vehicle for awhile (vacation, own multiple vehicles), or otherwise if you only want to use Teslascope for simply providing statistics to the fleet (vehicle firmware updates), there is also a "Quiet Mode" which fully disables all polling and essentially eliminates all phantom drain all at a single toggle.
