Joulary Privacy Notice
Joulary ("the app") automates home EV charging using your car, your electricity tariff and your calendar. This notice explains what personal data the app and its servers process, why, who else is involved, and what rights you have. The data controller is Alexey Yudichev, who runs Joulary. You can contact him at support@joulary.com.
What we collect
- Account: your email address and display name. If you set a password, Google Firebase Authentication handles it and we never store it.
- If you sign in with Google or Apple: instead of using a password, you let that provider confirm who you are. We receive your email address, your name, and an identifier the provider uses for you. We never see your Google or Apple password. Apple's "Hide My Email" is supported. If you choose it, we receive a relay address instead of your real one, and it works everywhere in the app. Signing in this way always tells Google or Apple that you use Joulary. Signing in with an email address and password instead keeps them out of it.
- Services you connect: for Tesla, your account access tokens and your car's state (location, battery level, charging activity). Tesla also processes this data about your car under its own Customer Privacy Notice. Before a Tesla connects, the app shows what Joulary does with your car and asks you to agree to it and to Tesla's processing, and separately to the use of your car's precise location. You can read that agreement again on your car's card in Settings, and you withdraw it by removing the car. For Octopus Energy, your API key, your account number, and your tariff and consumption data. For an iCloud calendar, your iCloud app-specific password; for a Google calendar, an access token that lets the app read it (see "Google Calendar" below). For either, your calendar entries (titles, times, locations and notes). Passwords, keys and tokens for these services are stored encrypted.
- Home location: the location you set so the app knows when your car is at home. The app also uses it, rounded to about 1 km, to get the weather forecast for your area. The outdoor temperature in that forecast helps decide whether to warm or cool the car before a trip, and how long the battery can be left at a high charge.
- Notifications: a push token and a device identifier, so the app can send you notifications (for example, to plug the car in).
- History the app works out: your charging, energy and trip history, and the savings reports calculated from it.
- Technical logs: IP addresses and other details about requests to our servers, kept for security and to fix problems.
- Support messages: if you contact us, what you write, and the diagnostics described under "Contacting us" below.
The app has no advertising, no marketing, and no third-party analytics or tracking software, and your data is never sold.
Why we process it
- To provide the service you sign up for (contract, UK/EU GDPR Art. 6(1)(b)). This covers planning and controlling charging, showing history and savings, and sending the notifications that are part of the service. You only get notifications if you allow them in your phone's settings.
- To keep the service secure and working (legitimate interests, Art. 6(1)(f)). This covers preventing abuse, limiting how often requests can be made, and keeping operational logs.
- To answer you when you get in touch. Handling a support request about the service you have with us is part of providing it (Art. 6(1)(b)). If you write to us without an account, or cannot sign in to one, we rely instead on our legitimate interest in replying to an enquiry you chose to send (Art. 6(1)(f)).
Google Calendar
If you connect a Google calendar, Joulary asks Google for read-only access to your calendars. The app can see your calendars and their entries. It cannot add, change or delete anything in them.
The app reads your upcoming entries and picks out the ones that have a location and that you have marked as a car trip with one of Joulary's tags, such as "/car", in the title or notes. For those, it plans charging so the car has enough battery in time. The trips the plan is charging for, and any notification about one of them, can show the entry's title.
The location of each entry a trip is planned for goes to Google Maps Platform, which finds the place and plans the drive from your home location. A notification about a trip can name the entry, and it is delivered through Expo and through Apple or Google. The help assistant gets a trip's times, but never an entry's title, location or other contents.
We do not keep a copy of your calendar. The app reads it again each time it plans. On our servers we keep your access token, encrypted, and which of your calendars you chose to use. For entries we have already notified you about, we keep the entry's identifier and its start and end times, so we do not notify you twice, and nothing else from the entry.
To stop access, remove the Google calendar in the app, and we ask Google to withdraw it. Joulary's Google sign-in and its calendar access belong to the same Google project, so this may also withdraw your consent to "Sign in with Google", and Google would then ask you to agree again the next time you sign in that way. Deleting your Joulary account withdraws calendar access too. You can also remove Joulary's access yourself at any time in your Google Account, under Third-party connections.
Joulary's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use your calendar only to plan charging and show you your trips. It is not used for advertising or to train AI models, it is not sold, and we pass it on only as described above. Nobody at Joulary reads it unless you ask us to while we help you, it is needed for security or to investigate abuse, or the law requires it.
Emails we send you
We email you when something changes about your account itself: when the account is created, when a deletion is scheduled, if that deletion is cancelled, and once your data has actually been erased. We do this to deliver the service (Art. 6(1)(b)) and so that you can notice a change you did not make (Art. 6(1)(f)). When a deletion is scheduled, the same warning is also sent as a notification to any phone where you are signed in to Joulary and have allowed its notifications. That way it does not depend on an email reaching you.
These are service messages. They are not marketing, and we put no unsubscribe link in them. We leave the link out on purpose. If somebody else got into your account and asked us to delete it, the warning email is the only thing that would tell you before your data was gone, so we do not want you to be able to switch it off by accident. In return, we keep these emails few and strictly about your account: we will never send you marketing, newsletters, offers or product announcements, and nothing of that kind will be added to these emails.
Your email app may still show you an "Unsubscribe" button on these messages, and it works. Please read this before you use it. Our email provider adds a standard unsubscribe header to everything it sends, including messages like ours, and it gives us no way to remove it. If you use that button, all four of these emails stop, including the emailed deletion warning. Nothing else about your account changes, and you can still sign in. The warning would still reach a phone where you are signed in to Joulary with its notifications allowed. But you would lose the emailed copy, which is the one that reaches you if the app is no longer on your phone. We think you should have both, so we would rather you did not turn it off. If you already have and you want it back, email support@joulary.com and we will ask the provider to lift the block.
Our email provider is Brevo (Sendinblue SAS, France), listed below. They receive your email address, your name if you have given us one, and the message itself. They keep a delivery record for a limited period, which is why the final "your account has been deleted" email explains that a record of it outlives the deletion. Brevo stores the messages themselves in the EU. It also uses a few providers of its own outside the EU: to serve its network, for its support desk, for its internal dashboards, and for parts of its own support and maintenance team based in India and the United States. Because of this, some of the information around a message can be handled outside the EU, under the standard safeguards for such transfers. Brevo also lists several AI providers among the companies it may use, but only for optional features we do not use. We send our emails through its plain sending interface, so nothing we send you is put through any of them.
Brevo adds delivery tracking to these emails, and we cannot switch it off. Every message carries an invisible image that is fetched from Brevo when the message is displayed, and every link in it points at Brevo first and then forwards you on. This means Brevo can record that a message was opened, roughly when, the network address it was opened from, and which links were followed. We have turned on Brevo's anonymisation setting, which strips the identity from those records, and Brevo offers no way to turn the tracking off altogether for messages of this kind.
We do not use any of it. We do not read these records, build a profile of you, or change what we send based on whether you opened anything. As said above, we send you no marketing, so there is nothing to target. Our basis for the tracking is our legitimate interest in the messages actually arriving (Art. 6(1)(f)), which is the same reason the delivery record exists at all. If you would rather not be counted, leave remote images blocked. Most email apps block them until you ask for them, which stops the invisible image being fetched. You can also copy a link's address instead of clicking it.
Contacting us
There are two ways to reach a person, and they are handled differently.
From inside the app, while signed in. Your message is stored on our servers as a support ticket, with a reference we show you. We take your email address and name from your account, so you do not type them into the form. Two things may be sent with your message:
- Diagnostics. These are attached unless you turn them off before sending. They are what the app itself could see at that moment: which screen you were on, when it last heard from our server, and your platform, operating-system version, device model, app version, locale and time zone. They deliberately leave out your location, your home address, your calendar entries, your trip history and your sign-in details.
- The recent messages of your conversation with the in-app assistant. These are attached only if you switch this on, and it is off by default. The app shows you these messages before you send, so you can see exactly what would go. This is the only time we keep a copy of a conversation with the assistant.
We keep your message so we can answer it. The diagnostics and any attached conversation are encrypted on our servers and opened only while someone is working on your ticket, and we record who opened them and when. Once a ticket is closed, it and everything attached to it are deleted 30 days later. If you used one of your rights below in a ticket, we keep that ticket for as long as we need to show we dealt with it. If you delete your account, we erase all your tickets straight away, open or closed, without waiting for those 30 days. Your own tickets also appear in the copy of your data you can download at any time (Profile → Export my data): the reference, the dates, what you wrote, and whether diagnostics went with it.
By email. Writing to support@joulary.com sends an ordinary email from your own mail app to our support mailbox. This is the route the signed-out screens and this website offer, because without an account there is nothing to attach a ticket to. If you use the link in the app, it fills in the same technical details listed above and nothing else. You can read all of it, and delete any of it, before you send. The emails in that mailbox, yours and our replies, are deleted automatically 120 days after the last one in the conversation. If you wrote to use one of your rights below, we keep that conversation for as long as we need to show we dealt with it.
Either way, please send only what we need to help. If that means mentioning someone else, such as another person who drives the car, what you write about them stays part of your message and goes no further. We do not start a record about them, and it is deleted along with your message.
Who processes it for us
| Provider | Purpose | Location |
|---|---|---|
| Google (Firebase) | Sign-in, identity, push message delivery; "Sign in with Google" if you choose it | US / EU |
| Google (Calendar) | Reading the Google calendars you connect, at your direction | US / EU |
| Brevo (Sendinblue SAS) | Sending the account emails described above, and the delivery tracking that comes with them | EU (France); some of their own providers in the US |
| Tesla, Inc. | Vehicle data and commands, at your direction | US |
| Octopus Energy | Electricity tariff and consumption data, at your direction | UK |
| Apple | "Sign in with Apple" and iCloud calendar access, both at your direction; push delivery on iOS | US / EU |
| Expo | Relays push notifications. Expo also uses device information from delivery (such as IP addresses and crash traces), in aggregate, for analytics about its own service. For that use it is an independent controller under its data processing addendum | US |
| Anthropic | Runs the language model behind the in-app help assistant, only while you have turned the assistant on. It receives your question and, when the question is about your own car, what your own screens in the app are showing: your settings, which kinds of account you have connected, the charging and climate information on your home screen, your upcoming charge targets and how sure you said you are of each, the trips the plan is charging for with the battery level it expects before and after each, and the electricity prices on the Timeline. It never receives your home or car location, the titles or contents of your calendar entries, the names of your charge targets, your email address, or any password or access token. Under Anthropic's terms, your questions are not used to train models, and are deleted within 30 days | US |
| WeatherAPI.com | Gets the weather forecast for your area, which the app uses when it plans charging and warming or cooling the car. It receives your home location rounded to about 1 km, with no name, email address or account identifier | UK company; server location not stated |
| Google Workspace | Runs the mailbox behind our support address, so it holds the messages you send us and the replies we send back | US / EU |
| Our hosting provider | Runs the Joulary servers | EU or UK |
Where a provider is outside the UK and the EU, transfers rely on that provider's standard data-protection terms (Standard Contractual Clauses / UK Addendum) or on an adequacy decision. WeatherAPI.com is the exception: its own policy lets it move the rounded home location it receives to countries outside the UK and the EU without these safeguards.
Google Maps
Google Maps is not one of our processors. Google decides how it uses what it receives, as an independent controller under its own privacy policy. Google is in the US, and its terms cover the transfer with Standard Contractual Clauses and the Data Privacy Framework.
When the app plans a trip from your calendar, it sends Google Maps Platform the location written in that entry, so Google can find the place. It then sends your home location and that place, in full, with the time you need to arrive, so Google can plan the drive.
On Android, the map you use to set your home location is Google's. Google receives the area the map shows and the address you type. The Maps software in the app also sends Google information about your device and the app, crash reports, your IP address, an identifier for the Maps software and how you move and zoom the map, which Google uses to run and improve its services. On an iPhone the map is Apple's.
How long we keep it
- Your account, and the data from the services you connect: until you delete your account, or until it has gone unused for about two years. You can delete your account in the app (Profile → Delete account). After a short grace period, during which you can cancel, everything is permanently erased, including the sign-in details for those services and your history.
- Accounts nobody uses are deleted. An account counts as in use while you open the app, and also while Joulary is acting on your car for you: starting a charge it planned, or running preconditioning (warming or cooling the car before a trip) that it committed to. When neither has happened for about 22 months, we email you and notify any phone you are signed in on. The message says the account will be erased on a date about two months later, roughly two years after it was last used. Signing in before then keeps the account, and nothing is erased.
- Trip history: 12 months. These records include where each drive started and ended, so we keep them for the shortest period the app can work with. They are deleted automatically after that, whether or not you delete your account.
- Charging, climate and energy history, and the savings reports calculated from it: 5 years, so that you can still compare one year with the year before. It is deleted automatically after that.
- Support tickets raised in the app: 30 days after the ticket is closed, including the diagnostics and any conversation attached to it. A ticket in which you used one of your rights is kept for as long as we need to show we dealt with it. A ticket that is still open is not deleted on a timer. We close it. Deleting your account erases all your tickets straight away, whether open or closed.
- Email you send to the support address, and our replies: 120 days after the last message in the conversation, deleted automatically. A conversation in which you used one of your rights is kept for as long as we need to show we dealt with it.
- Application logs: up to 60 days. Access logs at the network edge (the servers that first receive your connection): up to 60 days.
- On your device, the history the app has stored is erased when you sign out or delete the account.
Your rights
You can export a copy of your data (Profile → Export my data) and delete your account (Profile → Delete account) directly in the app. These let you use your rights of access, portability and erasure yourself. You also have the rights to rectification (having your data corrected or completed), restriction of processing and objection to processing, and the right to complain to your supervisory authority (in the UK, the Information Commissioner's Office). For anything you cannot do in the app, email support@joulary.com.
Deleting your Joulary account
You can delete your account in the app: open Profile (the person icon at the top of the screen) and tap Delete account.
If you no longer have the app, email support@joulary.com from the address you use to sign in to Joulary, and say that you want your account deleted. We will confirm by email, and you do not need to install the app again.
Either way, deletion is scheduled for a 7-day grace period, during which you can cancel it, and we email you when it is scheduled. After that we permanently erase your account and everything the app holds about you: your car, energy and calendar connections and their keys, your charging, energy and trip history, your savings reports, your settings and your support tickets.
A few records last longer. Our server logs are deleted within 60 days. Our email provider keeps a record that the deletion emails were delivered for a limited period. If you used one of your data protection rights in a support ticket or email, we keep that conversation for as long as we need to show we dealt with it. Backups are replaced on a rolling schedule, and erased data goes when the backup holding it is replaced.
Children
Joulary is not directed at children and is not intended for use by anyone under 18.
Changes
Changes to this notice are published on this page with an updated effective date.