Privacy Policy

What we do with your information, in plain words.

Private Line is a private AI chief of staff you reach by text. To do its job it connects to accounts you already use, including Google Workspace. This page explains exactly what it touches, why, where that data lives, and the controls you have over it.

Effective: July 19, 2026 Last updated: July 19, 2026 Applies to: tryprivateline.com and the Private Line service
The short version

Your data stays yours. Private Line runs on a private server dedicated to you — not a shared pool. We use the accounts you connect only to run the assistant you asked for. We do not sell your data, we do not use it to serve ads, we do not use it to train AI models, and our team does not read your email in the ordinary course of running the service.

Everything below is the same commitment, spelled out.

01 Who we are

Private Line is a product of Vantum ("Private Line", "we", "us"). We provide a single-tenant AI assistant that individuals and small teams reach through a private phone number and messaging channels. When you set up Private Line, we operate a dedicated server instance for you and help you connect the accounts the assistant works across.

This policy covers our marketing site at tryprivateline.com, the Private Line dashboard, and the assistant service itself. Questions go to privacy@tryprivateline.com.

02 Google Workspace data we access

If you choose to connect a Google account, Private Line asks Google for a specific, limited set of permissions. You see and approve each one in Google's own consent screen, and you can revoke them at any time. These are the exact scopes we request and the only ones we request:

Permission
What it lets Private Line do
gmail.readonlyRestricted

Read and search the messages in your inbox so the assistant can triage what's new, summarize threads, surface what needs your attention, and understand context when you ask about something.

Read only. It cannot delete or alter your mail.
gmail.composeRestricted

Prepare email drafts on your behalf and send a draft only after you explicitly approve it. Nothing is sent silently — every outbound message waits for your yes.

We do not request the broad "send mail" scope.
calendarSensitive

Read your calendar to prepare your day and see your availability, and create, move, or cancel events when you ask it to schedule something.

Calendar changes follow the same approval behavior as email.

We do not request access to Google Drive, Contacts, Photos, or any Google product other than Gmail and Calendar. If you connect more than one Google account (for example a work and a personal inbox), each is authorized separately and shown to you by its real address in your dashboard.

03 How we use that data

We use the Google data you connect for one purpose: to power the assistant features you can see and use in Private Line. Concretely, that means:

  • Triage and summaries — reading new mail and calendar events so the assistant can tell you what happened and what needs a decision.
  • Drafting — preparing replies and messages in your voice, which you review and approve before anything sends.
  • Scheduling — checking availability and booking, moving, or cancelling events at your request.
  • Understanding your world — building a private, structured memory of the people, projects, and commitments that show up in your mail and calendar, so the assistant gives you relevant help instead of starting cold each time. This memory lives only on your own server instance.

We do not use your Google data for advertising, for building marketing profiles, for credit or lending decisions, or for any purpose unrelated to the features above.

04 Limited Use & the Google API policy

Google API Services User Data Policy — Limited Use

Private Line'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.

In practice, that commitment means all of the following:

  • We only use Google user data to provide and improve the user-facing features of Private Line described above.
  • We do not transfer or sell Google user data to third parties for advertising, market research, or any similar purpose.
  • We do not use Google user data to develop, improve, or train generalized or non-personalized AI or machine-learning models. Your data is never used to train the models behind Private Line or any other product.
  • We do not allow humans to read your Google user data, except: (a) with your explicit consent for specific messages; (b) where necessary for security purposes, such as investigating abuse or a bug; (c) to comply with applicable law; or (d) where the data has been aggregated and anonymized for internal operations. The routine work of the assistant is performed by software, not by our staff.

05 Other information we collect

Beyond the accounts you connect, we keep the minimum needed to run the service:

  • Account details — your name, the email address and phone number you use with Private Line, and your plan, so we can set up and support your instance.
  • Content you send the assistant — the messages you exchange with it, and any notes, rules, or preferences you give it, which are stored on your own instance.
  • Operational logs — basic technical records (timestamps, error traces, health checks) used to keep your instance running and secure. These are kept short-term and are not used to profile you.

The marketing site itself does not run advertising trackers. We do not sell any of this information.

06 Where your data lives

Private Line is deliberately single-tenant. Each customer gets a dedicated, isolated server instance — your data is never pooled with another customer's. Within your instance, connected-account content and the assistant's memory are stored on that server; access credentials (like the token Google issues) are held in a protected secret store, never in plain text alongside the data.

Connections are encrypted in transit (TLS). Access to your dashboard is protected by a passkey or a password plus a one-time code, and administrative access to the underlying server is restricted to our operations team for maintenance and security only.

The assistant reasons using an AI account that runs under your own subscription or key where you provide one, which keeps the processing of your content tied to your account rather than a shared one.

07 Service providers we rely on

Running the assistant requires a small number of trusted providers. They process data only to deliver their part of the service, under their own terms, and none of them are permitted to use your content to train their models under the account configurations we use:

Provider
Why we use it
Google

The source of the Gmail and Calendar data you choose to connect. Governed by Google's Privacy Policy.

Anthropic (Claude)

The AI model that reads, reasons, and drafts. Content is processed to generate the assistant's responses. Anthropic Privacy Policy.

OpenAI

Used to turn text into numerical embeddings that power the assistant's memory and search. OpenAI Privacy Policy.

Twilio & Telegramoptional

Deliver the text and chat messages between you and the assistant, only if you use those channels. Twilio · Telegram.

Hosting & infrastructure

A cloud provider hosts your dedicated server instance. Your instance is isolated at the account level.

We share your connected-account data with these providers strictly to operate the features you use, and with no one else, except where required by law or to protect the security of the service.

08 Sharing, selling & ads

We do not sell your personal information. We do not share it with advertisers or data brokers. We do not use your connected-account data to build cross-customer profiles or to serve advertising anywhere. The only parties that ever touch your content are the service providers in the previous section, acting on your behalf to run the assistant.

09 How long we keep it

Your connected-account data and the assistant's memory persist on your instance for as long as your account is active, so the assistant stays useful over time. When you disconnect an integration, we stop accessing it and the stored access token is removed. When you close your account, we delete your instance and the data on it. Short-term operational logs age out on their own.

10 Your controls

  • Disconnect anything, anytime. Every integration in your dashboard has a Disconnect control that revokes our access and clears the stored token.
  • Revoke from Google directly. You can remove Private Line's access from your Google Account at any time at myaccount.google.com/permissions.
  • Approve before anything leaves. The assistant drafts, but you approve every outbound email and calendar change.
  • Access, correct, or delete. Email privacy@tryprivateline.com to request a copy of your data, correct it, or delete your account and instance. Where the law gives you additional rights (such as under GDPR or the CCPA), we honor them.

11 Security

We protect your data with per-customer isolation, encryption in transit, secret storage kept separate from content, and access controls on both your dashboard and the underlying server. No system is perfectly secure, but the single-tenant design means a problem with one instance does not expose another. If a breach ever affects your data, we will notify you promptly and as required by law.

12 Changes & contact

If we change this policy in a way that materially affects how we handle your data, we will update the date at the top and, where appropriate, tell you directly. Continued use after a change means you accept the updated policy.

For any privacy question, request, or concern, contact us at privacy@tryprivateline.com. The data controller is Private Line, a product of Vantum.