Privacy

Your email is never stored

When you open a contact, messages between you and that person are fetched from Gmail, rendered, and discarded. No subject, body, or preview line is ever written to the database. The only thing saved is a single timestamp recording that the most recent message existed.

Your network is yours alone

Every table is filtered at the database by the signed-in account. Isolation is enforced by Postgres row-level security, not by application code, so a bug in the app cannot show one person another person’s contacts.

Nothing is sold, and nothing is tracked

There is no advertising, no analytics, no tracking pixels, and no third-party scripts. Your data is not sold, rented, or shared for anyone else’s purposes.

Mail and calendar are separate, later, optional decisions

Signing in asks only for your name and email address. Gmail access is requested per mailbox, only when you connect one. Calendar access is a further, separate grant on top of that.

Three sources, and no others.

From signing in

Your name, email address, and Google account identifier. Google sign-in requests only the “openid” and “email” scopes — it does not request access to your mail or calendar.

From you

Contacts you add or import (name, address, phone, title, company, school, profile URL, notes), conversations you log including any transcript you paste, job postings you save, email templates you write, and settings such as the addresses you send from.

From Google, only if you connect it

Described precisely in section 03.

If you enable notifications, the browser’s push endpoint and its encryption keys are stored, along with a short device label such as “Chrome on macOS” so you can tell your devices apart well enough to turn one off.

Access is read-only in both cases. This app cannot send mail, and cannot create, modify, or delete calendar events.

Gmail — read on demand, never retained

When you open a contact’s profile, the app searches your mailbox for messages to, from, or copying that one address, and shows sender, subject, date, and Gmail’s own preview line. That data lives in the response and in your browser tab. It is not written to the database and it is not cached on the server. Closing the page is the end of it. One field is written as a result: the date of the most recent message, used to know when you last spoke.

Calendar — three fields, and only for matched meetings

The app reads events in a fortnight either side of today that have between one and six outside attendees. Attendee addresses are compared against contacts you already have. For an event that matches somebody, three things are stored: the event’s identifier, its start and end times, and its title. Attendee lists, descriptions, locations, conferencing links, and every event that matches nobody are held in memory for the length of that check and then dropped.

Tokens

The token that lets the app refresh its access is encrypted before storage using AES-256-GCM and is never sent to your browser. Access tokens are minted on the server, used, and discarded.

Networth’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

No email bodies in the database

This is an architectural rule, not a setting, and it is not configurable.

No sending on your behalf

Email features prepare a draft and hand it to Gmail or your mail client for you to review and send yourself. The app never requests permission to send.

No automated processing by an AI model

No contact, note, transcript, message, or calendar entry is sent to any AI or large language model service. Everything the app calls “scoring”, “coverage”, or “responsiveness” is arithmetic over rows you already wrote.

No call recording

The app never records audio. Transcripts exist only if you paste one in yourself.

No bulk collection from anywhere

Contacts come from your own Google mailbox, a file you export and upload yourself, or typing. When you paste a job posting URL, the app reads that one page, at that moment, because you asked it to.

You. Each account’s data is isolated at the database by a row-level security policy that ties every row to its owner, so the separation holds even if the application misbehaves.

There is exactly one place where anything is read across accounts, and it is disclosed here because it is the only one: the daily notification job needs to know who has something waiting. It reads counts only — how many follow-ups, how many overdue. No name, address, company, or contact identifier ever leaves the database for that job. The worst it could reveal is how busy someone’s week is.

These providers process data in order to run the service:

Supabase

Database and authentication. Your contacts live here.

Vercel

Hosting. Requests pass through; nothing is stored there.

Google

Sign-in, and the Gmail or Calendar APIs you have connected.

A push service

Only if you turn on notifications — Apple, Google, or Mozilla, depending on your browser. Payloads are encrypted end to end and the relay cannot read them.

Data may also be disclosed if the law requires it. It will not be sold, and it will not be transferred as an asset without notice to you.

How long

Until you delete it. Nothing here expires on its own, because a contact you have not spoken to in two years is exactly the one the app exists to remind you about.

Deleting a contact

Removes that person and everything attached to them — logged conversations, transcripts, calendar matches — immediately and permanently.

Withdrawing Google access

Revoke it at myaccount.google.com/permissions at any time. The stored token stops working the moment you do. Because no message content was ever kept, there is no mail to delete afterwards.

Deleting everything

Write to solomonjmoon@gmail.com and your account and all of its data will be deleted within 30 days.

Traffic is encrypted in transit. Google refresh tokens are encrypted at rest and never reach the browser. Access control is enforced by the database rather than by application code, which is the strongest guarantee available here.

No system is perfectly secure, and this one is maintained by one person. Nothing on this page is a warranty that a breach cannot happen.

Data is stored and processed in the United States. If you use the service from elsewhere, you are asking for it to be handled there.

The service is not directed at children and is not intended for anyone under 16.

Depending on where you live you may have rights to access, correct, export, or erase your data. Nearly all of that is available directly in the app; for anything that is not, ask at the address below and it will be handled.

If this policy changes in substance, the effective date at the top changes with it. If the change materially affects how Google data is handled, you will be told before it takes effect.