LeaveSave

Privacy Policy

Effective date: September 24, 2026

Last updated: September 24, 2026 (Location / home pin)

Contact: [email protected]

Who we are

LeaveSave (“we”) is a consumer EV charging planner that helps you schedule charging around your calendar and, if you enable it, send charge commands to a vehicle you connect — so you can leave ready and save on rates without babysitting the charger.

Information we collect

How we use information

Sign you in; plan charging around your schedule; run charge commands you start in the app; if you enable smart charging, run automated charge commands on a schedule; provide support and security; improve the product (including via Amplitude analytics).

Automated charging

Smart charging is off by default. If you turn it on, the service may start, stop, or adjust charging without a separate tap each time. You can turn it off anytime in Settings. If automated charging was paused and then resumed, we show an in-app notice with a one-tap disable before automated commands continue.

Sharing

We use service providers that process data for us (hosting, Google, Google Gemini for optional calendar-assisted planning, your vehicle account provider, and Amplitude). We do not sell personal information and do not use personal information for cross-context behavioral advertising in this MVP.

Google Gemini (AI planning)

With your affirmative consent, we may send calendar event titles to Google Gemini by default so the service can classify events and improve charging plans. We may include event descriptions or locations only when needed for classification quality. We configure Gemini to avoid retaining prompts for model training. We use this only to provide that user-facing planning feature. We do not use Google Calendar data to train or improve generalized / non-personalized AI or machine learning models. LeaveSave operators and internal tools (Amplitude, logs, URLs, toasts, support, dashboards) cannot read Gemini prompts or responses that contain calendar event content. You can withdraw consent or disconnect Google Calendar in Settings; after that we stop sending calendar content to Gemini. We delete or scrub planning copies that included calendar event content within a reasonable period.

Google user data (Limited Use)

LeaveSave’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Sign-In and Google Calendar (read-only) data only to authenticate you and to plan charging around your schedule. We do not sell this data or use it for advertising. When you consent to Gemini-assisted planning, Calendar-derived fields sent to Gemini are used only for that user-facing feature under the Limited Use requirements.

Retention

Vehicle command logs are kept for 90 days, then deleted or anonymized. Sign-in and connection tokens are removed when you disconnect Google or your vehicle, or delete your account. Analytics identifiers are deleted or scrubbed when you delete your account, where feasible with our providers. Home map pin and ZIP are kept while your account uses those features, then removed when you clear them or delete your account. Other account data is deleted within a reasonable period after account deletion, except where we must keep something for security or legal reasons.

Your choices and California privacy rights

Children

LeaveSave is not directed to children under 13.

Security

Credentials and API tokens are stored server-side. Do not share verification codes or secrets in chat or email beyond official support channels. LeaveSave operators and internal tools (logs, analytics, support, dashboards) cannot access individual calendar event content; retained planning signals are non-human-readable. The signed-in user may see their own schedule in the app as needed. Gemini prompts/responses that include calendar event content are not available to LeaveSave operators or internal tools. Home map pins and coordinates are not available to LeaveSave operators or internal tools (logs, analytics, support, dashboards).

Changes

We will post updates to this page and revise the effective date.