Privacy policy

Last updated: October 12, 2026

Lightweight Cloud Connector (LCC) is a free, open source desktop application that runs on your computer. This policy explains what data the application uses, where it is stored and who it is shared with, and what happens when you visit this website. In short: LCC does not send your data to its developer or to any third party. Everything the application does goes directly between your computer, Google Cloud and your virtual machines.

Who is responsible

LCC and this website are developed and maintained by Jordi Lopez Reyes, based in Chile. For any privacy question, or to exercise your rights, write to aim@jordilopezr.com.

This policy is designed to comply with Chilean personal data protection law (Law 19.628 as amended by Law 21.719), the European Union's General Data Protection Regulation (GDPR) and United States privacy laws such as the California Consumer Privacy Act (CCPA/CPRA).

Google data the application accesses

When you add an account, LCC opens your browser so you can sign in with Google (OAuth 2.0 with PKCE) and requests these permissions:

  • https://www.googleapis.com/auth/cloud-platform: to manage your Google Cloud resources on your behalf.
  • openid and email: to know which account you connected and show its email address in the application.

LCC uses that access only for the features you use in the application: listing projects, instances and snapshots; starting, stopping, resetting, suspending and resuming machines; creating and deleting snapshots; opening Identity-Aware Proxy (IAP) tunnels for SSH, SFTP, RDP, VNC and other ports; publishing SSH keys through OS Login or instance metadata; reading the serial console and audit logs; and checking API and firewall status from the diagnostics tool (Doctor). Actions that change resources run when you ask for them, and Doctor's automatic fixes ask for confirmation first.

LCC'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. LCC does not use Google data for advertising, does not sell it, and does not use it to train artificial intelligence models.

Where data is stored

Everything is stored on your own computer:

  • Google credentials. Each account's refresh token is stored encrypted in the system keyring (Secret Service: GNOME Keyring, KWallet or equivalent). Short-lived access tokens are kept only in memory.
  • Windows VM credentials. If you use Windows auto-credentials, they are also stored in the system keyring.
  • Settings and account list. Your preferences and the email addresses of connected accounts are stored in ~/.local/share/lightweight_cloud_connector.
  • Logs. The application writes operational logs to that same folder, with automatic rotation (at most five 10 MB files).
  • SSH key. The first time it needs SSH access to a machine, LCC asks for permission, generates its own key in that folder and publishes the public part to OS Login or to the instance metadata, without overwriting other keys.
  • Temporary files. When an RDP or VNC client needs the password in a file, LCC creates it with restricted permissions (0600) and deletes it as soon as the client launches.

Because this data never leaves your machine for the developer, the developer has no access to it and does not process it: you control it.

Who data is shared with

The application only connects to Google services (Google sign-in, the googleapis.com APIs and the IAP tunnel relay) and to your own virtual machines through those tunnels. It includes no telemetry, analytics or automatic crash reporting, and sends nothing to the developer's servers.

Doctor's diagnostic report and the log export are only generated when you ask for them, are saved on your computer, and automatically strip tokens, passwords and API keys. You decide whether to share them with anyone.

If you choose the gcloud sign-in engine in Settings, LCC stores no credentials of its own: it reads the session the Google Cloud CLI already has on your machine.

How to delete your data and revoke access

When you remove an account in LCC, the application revokes its token with Google and deletes it from your computer. You can also remove access at any time from your Google Account permissions page. To delete everything else, uninstall the application and delete the ~/.local/share/lightweight_cloud_connector folder.

With the gcloud engine, LCC does not revoke the CLI's credentials; to do that, run gcloud auth revoke in a terminal.

This website

This website uses no cookies or analytics tools, has no user accounts and loads no third-party resources: the typeface is served from the site itself.

  • Cloudflare hosts the site and, like any web server, processes technical data from each visit (IP address, browser, requested page) to serve and protect it. The site keeps technical request logs at Cloudflare for a limited time to detect errors.
  • Your browser language is used only to choose between Spanish and English; it is not stored. The macOS notice is decided inside your browser and is not sent anywhere.
  • Downloads redirect you to GitHub Releases, and the donation link goes to Buy Me a Coffee. Those services apply their own privacy policies.
  • If you write to aim@jordilopezr.com, we will use your email only to reply to you.

Legal bases and retention

The developer only processes personal data on this website and when you write to us:

  • Technical website logs (IP address, browser, requested page): processed on the basis of our legitimate interest in serving the site, keeping it secure and fixing errors, and kept only as long as Cloudflare retains them for that purpose.
  • Emails you send us: processed to reply to you, on the basis of our legitimate interest or your request, and kept for the duration of the conversation and as long as needed afterwards to handle your query.

We make no automated decisions about you and do no profiling. We do not sell or share personal data for advertising purposes, as defined by the CCPA/CPRA or any other law.

International transfers

Cloudflare and GitHub are United States-based providers that operate servers in several countries, so technical data from your visit, and from your downloads, may be processed outside your country. Those transfers rely on the mechanisms those providers offer, such as the European Commission's standard contractual clauses or the EU-U.S. Data Privacy Framework.

Your rights

Depending on where you live, the law gives you these rights over your personal data:

  • European Union, European Economic Area and United Kingdom (GDPR): access, rectification, erasure, restriction of processing, objection and portability, and the right to lodge a complaint with your country's data protection authority.
  • Chile: access, rectification, erasure, objection, portability and blocking, and the right to go to the Personal Data Protection Agency (Agencia de Protección de Datos Personales).
  • United States (California and other states with privacy laws): to know what data we hold, to ask for it to be corrected or deleted, and not to be treated differently for exercising these rights. Because we do not sell or share personal data, there is nothing you need to opt out of.

To exercise any of them, write to aim@jordilopezr.com. We will reply within 30 days at most. Keep in mind that the data the application stores lives only on your computer: you can view and delete it yourself as explained above.

Children

LCC is a professional tool for managing cloud infrastructure and is not directed at children under 16. We do not knowingly collect data from children; if you believe a child has sent us personal data, write to us and we will delete it.

Changes to this policy

If the application changes what it collects or where it connects, we will update this page and the date above. LCC's source code is public at github.com/jordilopezr/LCC, so anyone can check what it does.