Privacy Policy

CoreLife HQ is a founder-led application operated by Nate Hood, pending formation of a separate business entity.

Your account details (email address and any display name) and the financial planning information you type in yourself: budget lines, amounts, dates, accounts you keep by hand, goals, notes, things you own and owe, and any help requests you send us.

If you choose to connect a financial institution, CoreLife HQ uses Plaid to obtain read-only account information and transaction activity. In this pilot that is limited to checking/everyday and savings accounts, transactions only, read-only.

CoreLife HQ never receives or stores your online banking username or password. You enter those with Plaid, not with us.

CoreLife HQ cannot move money, send payments, or initiate transfers. There is no payment capability in the application.

To provide CoreLife HQ itself: cash-flow planning, projections, comparing what you planned against what actually happened, reconciling bank activity with your plan, and the related features you use in the application.

We use Plaid for financial-account connectivity, and Supabase for authentication, database and application hosting services. These providers process data so CoreLife HQ can work. We do not use other data providers, advertising networks, or analytics brokers for your financial data.

CoreLife HQ does not sell your connected financial data.

Data is encrypted in transit and at rest by our infrastructure provider. Access to the application requires signing in, and every record is scoped to the account that owns it. Provider keys and secrets are held server-side only and are never sent to the browser or written to logs. Test and live bank credentials are kept separate and cannot substitute for each other. Multi-factor authentication is used on the critical administrative systems we rely on.

CoreLife HQ does not hold SOC 2 or any other security certification of its own, and we do not claim one.

Stopping a bank feed withdraws the connection with the provider and destroys the stored access key, so no further information is retrieved. It does not by itself erase what was already brought into CoreLife HQ — your planning history stays until you ask for it to be deleted.

In Settings you can delete the financial data CoreLife HQ imported from a bank. That withdraws any live connection, destroys the stored key, and removes the imported transactions and the calendar entries created from them out of active CoreLife HQ storage.

You can also ask us to delete your whole CoreLife HQ account from Settings, or by writing to iamnatehood@gmail.com. Our operational target is to carry out verified deletion requests within 30 days, or sooner where the law requires it. Deleting one person’s data never affects anyone else’s.

We keep your information only for as long as needed to run the application and support your active account, plus any period we genuinely need for security, fraud prevention, legal obligations or system integrity. Once deleted, data is no longer accessible in the live application. Temporary copies can remain inside our infrastructure provider’s routine backups for the limited period those backups are held, and are then overwritten.

A record that you gave consent, and that you asked for deletion, may be kept so we can show what was authorised and when.

We review this retention practice at least once a year, and whenever we materially change how we handle data or which providers we use.

To access, correct or delete your information, or to ask anything about privacy, write to iamnatehood@gmail.com. You can also use the Get help button inside the application.

Plaid is a separate company with its own privacy practices, which this policy does not cover. Read Plaid’s End User Privacy Policy.

CoreLife HQ is not intended for anyone under 18 during this pilot.

If this policy changes materially, we update the effective date above and tell you in the application or by email where that is appropriate.