Rung Privacy Policy

Effective 26 September 2026 · think3, New Zealand

Rung is software that runs on a controller box installed in a home or building - an "installation". This policy explains what Rung does with information, and in particular with a Google account a user connects to it for backups.

Where Rung runs

Each Rung controller runs on hardware at its installation, operated by that installation's owner or installer. think3 does not operate installations and does not receive their data. Device configuration, accounts, settings and logs stay on the controller.

Google Drive, for backups

An installer may connect a Google account so the controller can keep backups of itself.

• What Rung asks for. Only the drive.file permission: Rung can create files in the connected Drive, and read or delete only the files it created. It cannot see, read or change any other file in that Drive.
• What it stores there. One file per backup, in a folder named Rung Backups. Each file is encrypted on the controller before it is uploaded, with a key held by the installation. Neither Google nor think3 can read its contents.
• What it does with Google data. Nothing beyond storing, listing, and deleting its own backup files to keep the number retained within the installation's settings. Rung does not read, analyse, share, sell or transfer any Google user data, and does not use it for advertising or to train any model.
• Where the permission is held. The access Google grants is stored only on the installation's own controller. It never reaches think3.

Rung's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

This website

rung.think3.co.nz hosts this policy, a short description of Rung, and the page Google returns a sign-in to. That page sends the browser straight back to the Rung controller that started the sign-in, carrying Google's one-time code in a part of the address that is never sent to any server. It keeps no logs of those requests, stores nothing, and cannot use the code: only the controller that started the sign-in holds what is needed to complete it. The site sets no cookies and uses no analytics.

Removing access

Access can be withdrawn at any time, either with Disconnect in the Rung controller or from the Google account's third-party access page. Backups already in Drive remain there, in the account owner's control, until they delete them.

Changes and contact

If this policy changes, the new version will be published here with a new effective date. Questions: support@think3.co.nz.