Privacy policy

Signing in uses Google as the identity provider. Nectar requests only the basic sign-in scopes — openid, email and profile— which give it your email address, your name and your profile picture.

The email address is used to check you against the household’s allowlist and to identify you within the application. Your name and picture are used only to show who is signed in and to attribute changes in the activity history. Nectar requests no access to Gmail, Drive, Contacts, Calendar or any other Google service, and cannot read them.

Nectar has no connection to any bank and never asks for banking credentials. Financial data reaches it in one way only: a household member exports a statement from their own bank and uploads the file.

That data — transactions, account balances, budgets, savings goals, loans and investment holdings — is stored so the application can do its job. It is never sold, never shared with third parties, and never used for advertising or analytics.

Data is held in a PostgreSQL database hosted by Neon in Sydney, Australia, and the application runs on Vercel. Both encrypt data in transit and at rest. Nectar keeps a record of changes to financial information — who changed what and when — so that unexpected figures can be explained later.

Only the two people on the household allowlist. Any other Google account is refused at sign-in, before any account record is created for it. There are no other users, no administrators outside the household, and no third party with access to the data.

Financial history is kept for as long as the household uses the application, because the value of a budgeting record is in its history. Either household member can ask for their Google account information or the entire dataset to be deleted, and it will be removed from the database and its backups.

If how Nectar handles information changes, this page changes with it and the date above is updated. Questions about this policy can be sent to glen@formatdigital.co.nz.