Cookie Policy

Last updated

This policy identifies everything Podee stores on your device, and the purpose of each item. It supplements ourPrivacy Policy.

We use strictly necessary cookies only. We employ no analytics, no advertising and no tracking pixels, and we disclose nothing to third parties for their own purposes. Under the Privacy and Electronic Communications (EC Directive) Regulations 2003, cookies that are strictly necessary for the provision of a service requested by the user do not require consent, which is why you are not asked to dismiss a consent banner. We do send error reports to a third party in order to fix faults. That reporting stores nothing on your device and is described in section 3.

1. What we store

NameTypePurposeExpires
SESSIONCookie, first partyIdentifies your session. It is set when you begin signing in, and it carries you through Tesla's sign-in screen and back: the session it points to holds the values that establish that the reply we receive from Tesla belongs to the sign-in you started, and holds your signed-in state afterwards. In its absence you could neither sign in nor stay signed in.On sign-out, or after 14 days without use
XSRF-TOKENCookie, first partyCarries a token that the app sends back with every request that changes something. It is what allows us to tell a request you made from one another site made in your name while you happened to be signed in.When you close your browser
themeLocal storage, first partyRecords whether you have selected light or dark mode, so that the site does not display the wrong theme on load.Until you clear your browser storage
Stripe's own cookiesCookie, set by Stripe on Stripe's siteWhen you add or change a payment card, we send you to Stripe's own payment page to do it. Stripe sets its cookies there, on its own site and under its own policy, in order to detect fraudulent use of cards. We embed no Stripe code in Podee, so no Stripe cookie is set on our site.Determined by Stripe

2. What we do not use

If we introduce any item that is not strictly necessary, we will obtain your consent before setting it, and will update this policy beforehand.

3. Error reporting

When the service fails in your browser, it sends a report of the fault to Sentry, our error tracking provider, so that we are able to correct it, and it tells Sentry when a page is opened so that we may measure how often a release fails in use. Neither stores anything on your device. No cookie is set and nothing is written to local storage, and for that reason no consent is sought: the Privacy and Electronic Communications (EC Directive) Regulations 2003 govern the storing of information on your device and the gaining of access to it, and error reporting does neither.

It is nonetheless data leaving your browser for a third party, so we would rather you knew of it here as well. What the reports contain, what we have configured Sentry not to collect, and how long they are kept, is set out under Error reports in our Privacy Policy.

4. Controlling cookies

You may block or delete cookies through your browser settings, and may clear local storage by the same means. You should be aware that blocking our cookies will prevent you from using Podee at all: the sign-in cannot be completed without the session cookie, and the service has no alternative means of recognising you between requests thereafter.

Guidance in respect of each major browser is available ataboutcookies.org.uk.

5. Enquiries

Please write to privacy@podee.app if anything in this policy is unclear to you, or if you believe that we are setting an item this policy does not identify.