YOUR DATA, WITH CARE

A little data.
A clear purpose.

This notice describes the data handled by the Squid reference application. Operators must add their contact details, retention periods, and applicable privacy terms before launching their own instance.

For hosts

Supabase stores your sign-in email, property details, charger ownership, and session references. Stripe handles connected-account onboarding and payment details. Squid stores your connected account’s identifier, not bank account or identity-verification documents. Supabase manages password authentication. When you choose Google sign-in, Google shares your account identity, email, and basic profile with Supabase. When enabled, Resend delivers confirmation, recovery, and sign-in emails. Squid stores keyed digests of email and source addresses to limit repeated requests.

Property address and charger setup

When you search for a property address, Google Maps receives the address text you enter and returns suggestions and location details. Squid saves your selected property address and location for charger setup. Google handles these requests under its Privacy Policy. Charger connection passwords are stored encrypted and shown only to the owning host.

For guests

You do not need a Squid account. An HTTP-only cookie gives your browser private access to your charging session. Squid stores energy use, charging times, payment references, and the final amount. Card details are collected by Stripe and do not pass through Squid’s servers.

Service providers

A typical deployment uses Vercel to host the application, Supabase for authentication and data, Google for address lookup and optional sign-in, Resend for account emails, Stripe for payments, and Ivora for charger control and metering. Ivora receives non-secret payment references, not your card details or Stripe credentials.

The demo