Skip to content

Data & Privacy

Grid Getter collects and stores the following data when you use the service:

Data typeWhy we store it
Name, email, phoneYour account identity and notifications
TimezoneScheduling automations correctly
Tesla OAuth tokenAccessing your energy system on your behalf
Energy telemetry (power readings)Historical charts, DemandGuard decisions, automation logs
Automation configurationsYour saved automation rules
Subscription statusDetermining which features you have access to
Notification preferencesSending you the right alerts
Push notification tokensDelivering push notifications to your devices
Action logsAudit trail of what your automations have done
Site location (lat/long)Fetching local weather data
Weather snapshotsDashboard conditions and forecasts (auto-expires after 3 days)

We don’t store your Tesla account password, payment card numbers (Stripe handles payments), or any data from Tesla vehicles.


Grid Getter collects two kinds of diagnostic data: reports about things that break, and records of which features people actually use. Both are on by default, and each has its own switch.

SettingWhat it collects
Crash and error reportsThe error itself, where it happened in the code, your app version and your device type. Sent only when something goes wrong.
Product analyticsWhich features get used and how people move through the app, plus a recording of your session so we can see where the interface confuses people.

Product analytics run on PostHog. Crash reporting on the iOS and Android apps runs on Firebase Crashlytics; on the web, PostHog catches errors as well.

Every event carries which platform it came from and which Grid Getter environment you were on. Once you sign in, events also carry your Grid Getter account ID. That’s the same identifier our support logs use, and it’s what lets us trace a problem you’ve reported back to what the system was doing at the time. Signed out, events are anonymous and no profile gets created for you.

What a session recording can and can’t see

Section titled “What a session recording can and can’t see”

Everything you type is masked before the recording leaves your browser. We see that you filled in a field; we don’t see what you put in it. Card numbers never enter the picture at all, because payment details are typed into a frame Stripe controls and a recording can’t reach inside it.

What a recording does show is your own account as it appeared on screen — the pages you moved through and the figures on them. It’s the view you were already looking at, minus anything you typed.

On the web:

  1. Go to Settings → Data
  2. Find the Privacy section
  3. Switch off Crash and error reports, Product analytics, or both

On iPhone, the same two switches live under Settings → Privacy. On Android, open the drawer (☰) and go to Settings → Privacy.

On the web, both switches take effect the moment you flip them — no reload. In the mobile apps, analytics stops immediately and crash reporting stops from the next launch. Either way the setting is remembered, so once it’s off it stays off until you turn it back on.

Opening the Energy Plan editor from inside the iOS or Android app loads a Grid Getter web page in a built-in browser. That page deliberately reports nothing of its own — the app around it is already doing the reporting, and counting both would turn one person into two.

If an ad blocker or privacy extension blocks PostHog, nothing breaks. Grid Getter carries on exactly as normal and the events simply never arrive.

Turning both switches off has no effect on how Grid Getter works. Your automations, DemandGuard and notifications all behave the same.


You can download a full export of your Grid Getter data at any time — automations, energy history, action logs, and billing records — in CSV or JSON format.

  1. Go to Settings → Data
  2. Click Request Data Export
  3. Wait for the export to process — you’ll receive an email and an in-app notification when it’s ready (usually within a few minutes)
  4. Click the download link in your notification or on the Settings → Data page
  5. Your download is available for 30 days

Deleting your account permanently removes your account data from Grid Getter’s systems — your profile, energy history, automations, action logs, billing records, and Tesla connection. This action cannot be undone.

  1. Go to Settings → Account
  2. Click Delete Account
  3. Read the warning about what will be deleted
  4. Type delete in the confirmation field
  5. Click Confirm Delete

After deletion:

  • Your account and all associated data are removed
  • Any active subscription is cancelled
  • Your Tesla OAuth token is revoked
  • You’ll be logged out immediately

One category of data outlives the account: product analytics events (which features were used, and any session recordings). These help us understand why people leave, and they age out on their own schedule — recordings within 30 days, events within a year. They carry an internal account ID rather than your name or email, and once your account is deleted that ID no longer maps to anything. If you’d like them gone sooner, email support@gridgetter.com with the subject line Data Request and we’ll remove them.


If you’re in the European Union, you have the right to request access to, correction of, or erasure of your personal data. Email support@gridgetter.com with the subject line Data Request and we’ll respond within 30 days.


Data typeRetention period
Energy telemetryUntil account deletion
Action logsUntil account deletion
Deleted account dataRemoved within 30 days of deletion (except analytics, below)
Weather snapshots3 days (auto-expires), or immediately on location change/removal
Backup systemsUp to 90 days after account deletion
Product analytics events1 year, including after account deletion (removed sooner on request)
Session recordings30 days, including after account deletion
Crash reports90 days

Email support@gridgetter.com for any privacy-related questions.