Privacy policy

Effective September 29, 2026.

LevelUp CRM is the contact and relationship tool the LevelUp Economy team uses internally. LevelUp Economy runs it. This page says what it keeps, where it keeps it, who it shares it with, and how to have something removed. Questions go to lana@levelupeconomy.com.

Only people with a Google account on the levelupeconomy.com domain. Anyone else is turned away at the sign-in page.

When a teammate signs in, the CRM keeps their email address, their name and the address of their Google profile picture, so their work can be credited to them. Everyone who signs in sees the same records. There are no private records.

What the CRM keeps, and where

The CRM keeps the working record of the team's relationships:

Contacts and companies: names, job titles, email addresses, LinkedIn profile addresses, tags, owners and notes.
Deals and tasks: what is being worked on, with whom, and when it is due.
Timelines: notes, logged calls and meetings, emails, calendar meetings, website form submissions and AI research, on the record they belong to.
Imports: the rows brought in from LinkedIn files, and a history of each import.

Everything is stored in a Postgres database run by Neon. The app itself runs on Vercel. Nothing is sold, and nothing is shared with an analytics or advertising service.

Personal API tokens, which let a teammate's own AI tool talk to the CRM, are stored only as a one-way hash, so the CRM can check a token but cannot show it again.

Google data

Each teammate chooses whether to connect their own Google account. Connecting asks Google for three permissions: reading Gmail, creating Gmail drafts, and reading Google Calendar. Connecting one teammate's account does nothing to anybody else's.

Gmail, reading. The CRM looks at who each message in the last 90 days, and each new one after that, is from and to. It skips chats and anything Gmail filed under Promotions or Social. When at least one address on a message belongs to a contact already in the CRM, it keeps the subject, the sender and recipients, the date, and the text of the message as plain text with the formatting removed, trimmed if it is very long. Every other message is not fetched and not stored. The one exception is mail a teammate sent: for a person on its To line who is not in the CRM, the address and display name are kept as a suggestion, as the next section describes. Nothing is kept about people who only wrote in. The other exception is Substack's own email announcing a new subscriber to the LevelUp Economy newsletter, which the CRM reads wherever Gmail filed it. From that email it stores the subscriber's email address, the signup date, the email's subject line, Substack's label for how the person signed up (such as Direct), and the subscriber's display name when the email shows one. Nothing else in that email is stored, including the other newsletters it says the person reads.

Gmail, drafts. When a teammate presses Send to Gmail on a draft, the CRM puts that draft in their Gmail Drafts folder. The teammate sends it from Gmail. The CRM cannot send, reply to, forward or delete any email.

Google Calendar, read only. The CRM reads the teammate's main calendar from a week ago to two weeks ahead. It keeps a meeting only when someone already in the CRM is invited, and then keeps its title, times, description, video link and guest list. For a guest who is not in the CRM, it keeps only their display name and the domain of their email address, not the address itself, except as a suggestion described in the next section. It cannot create, change, accept or cancel anything in the calendar.

The permission itself. Google gives the CRM a long-lived key for the connection. The CRM stores it encrypted. When a teammate presses Disconnect, the CRM stops reading and asks Google to revoke the key, so it cannot be used again. Emails and meetings already on a timeline stay, as the team's record of the conversation.

People you wrote to or met

When a teammate emails or meets someone who is not in the CRM yet, the CRM keeps that person's email address and the display name Google shows for them, so it can suggest adding them. It keeps which teammate saw them, whether it was an email or a meeting, how many times, and when. It keeps nothing else about them: no subject, no message text, no meeting title or description, and nobody else who was on the email or the invitation.

Two things count. An email counts when the teammate sent it and the person is on its To line; copied people do not count, and neither do automatic addresses such as no-reply ones. A meeting counts when the teammate organized it or accepted it, and the person accepted it too. Mail sent to a teammate by someone not in the CRM never counts.

A suggestion is deleted 30 days after the person was last seen, unless a teammate adds the person as a contact or dismisses the suggestion first. A dismissed suggestion is kept, with no more than the details above, so the CRM does not suggest that person again. Nobody is added to the CRM without a teammate pressing Add.

The CRM holds only what a teammate brings in from their own LinkedIn account.

Archive and connections files. A teammate downloads their data from LinkedIn and chooses it on the Import page. The file is opened in their own browser, and only the rows the CRM keeps, such as connections and messages, are sent to it. The file itself is never uploaded or stored.
LinkedIn sync. A teammate can ask their own AI tool, on their own computer, to read their LinkedIn messages and connections in the browser they are already signed in to, and save what is new.

The CRM's server never fetches anything from LinkedIn, and never sends a message or a connection request.

Hunter

When a contact has a name and a company domain but no email address, a Find email button appears on their record. When a teammate presses it, the CRM sends Hunter, an email-finding service, three things: the first name, the last name and the company domain. Nothing else is sent, and nothing is sent unless somebody presses the button. A found address is saved marked as unverified.

Find email and Find domain share one daily allowance of 25 lookups per teammate.

AI tools

Research and outreach drafts are written by an AI model. To do that, the CRM puts together a prompt from what it holds about the record, such as the contact's details, notes and recent emails, and sends that prompt to one of two places:

A teammate's own laptop. The teammate runs a small program that picks up the job and hands the prompt to the AI tool they already use, under their own account: Claude Code (Anthropic), Codex (OpenAI) or Gemini CLI (Google). With Ollama, the model runs on the laptop itself and nothing leaves it.
Google's Gemini API, on the server. This is used only when LevelUp Economy has added a Gemini key, and the prompt goes to Google under that key.

Find domain. When a company has no domain, a teammate can press Find domain on the Data hygiene page. The CRM then sends the company's name and its location, if one is recorded, to the Gemini API on the server, which may look the company up on Google Search. Nothing else about the company or its people is sent, and nothing is sent unless somebody presses the button. A domain found this way is saved with a note naming the model and how sure it was.

Every result is labeled with the model that wrote it. Whether a provider may use a prompt to improve its models is set by that provider's terms for the account used. Google does not use prompts sent through a paid Gemini API account to improve its products, but it may use prompts sent through the free tier. For a teammate's own AI tool, the teammate's account settings with that provider decide.

Slack

The CRM posts short notices to one team Slack channel: a new website lead (name, organization, which form, and a link), a deal won or lost, a morning list of each teammate's overdue and due tasks, and a finished AI job.

Teammates can also type /crm in Slack to add a note or a task. To tell who is typing, the CRM asks Slack for that person's email address and matches it to their CRM account. Replies to /crm are shown only to the person who typed it.

Website leads

When somebody fills in a form on levelupeconomy.com, the website sends the CRM what they entered: their name, email address, organization, phone number, message, the interests or segment they picked, the role and a link to their CV for a job application, the page they were on, and which form it was. The CRM adds them as a contact, or finds the contact it already has without changing what the team entered, and puts the submission on their timeline.

Keeping and removing data

Records stay until a teammate deletes them. Nothing expires on its own, except the suggestions described under "People you wrote to or met".

Getting everything out. Any teammate can download a full backup from Settings. A backup can be restored only into an empty CRM.
Removing a person. A teammate can delete a contact from their record page. That removes the contact and their email addresses and tags, and takes them off every timeline entry. To have the emails and notes about someone removed as well, for example because they asked to be forgotten, write to lana@levelupeconomy.com.
When a teammate leaves. Their Google account is removed, which stops their sign-in and their Gmail and Calendar connection. Their API tokens are revoked. The contacts, deals and notes they added stay, because they belong to LevelUp Economy, and another teammate can take over as their owner.

Google API Services User Data Policy

LevelUp CRM'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.

Changes and contact

When this policy changes, the new version is posted on this page with a new effective date. Questions, or a request to see or remove information about you, go to lana@levelupeconomy.com.