squidby ivoraBack to Squid

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 to the owning host or an authorized administrator helping with setup.

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.

Feedback and support

When you send feedback, Squid stores your message, feedback category, optional experience rating, and the page you were using. Email is optional and is used if you want us to follow up. Signed-in feedback can be associated with your account and workspace. Feedback does not include sign-in tokens, URL query strings, or card information. Authorized administrators can review feedback and temporarily work in a host’s workspace to help with charger setup and support. This access and the actions they request are recorded in an activity log.

Host newsletter

The weekly host newsletter is off unless you turn it on in Settings. Squid keeps a dated record of each time you turn it on or off and the wording you agreed to. To send it, Resend receives your email address and the newsletter content. Squid records whether each newsletter was delivered, bounced, or led you to unsubscribe, and counts clicks on its links. Squid does not track whether you open it. Every newsletter has a one-click unsubscribe link; unsubscribed and bounced addresses are kept on a suppression list so they are not emailed again.

Analytics

When the operator enables them, PostHog and Google Analytics measure how the site is used: pages visited, buttons pressed, device and browser type, and approximate location. PostHog may also record sessions to help us fix problems; everything typed into forms is hidden from those recordings, and charger passwords are never recorded. Sign-in and password-reset links are not sent to either service. Card details are entered on Stripe’s own page and are never seen by analytics. PostHog and Google handle this data under their own privacy policies: PostHog and Google.

The demo

Demo chargers are saved only in your browser’s local storage. You can clear site data in your browser to reset the demo. Squid includes no advertising trackers.