Privacy Policy

Last updated: September 3, 2026

Deskcovered is a product of ActivePitch, Inc. Deskcovered ("Deskcovered," "we," "us," or "our" — each meaning ActivePitch, Inc.) provides an AI assistant service that answers and places phone calls, keeps a phone sheet, and manages contacts, calendar items, tasks, and — when you connect it — email (the "Service"), available at deskcovered.com. This policy explains what information we collect, how we use it, who we share it with, and the choices you have. It applies to our customers and their team members, to visitors of our website, and to people who call or are called by a customer's assistant.

Questions or requests: deskcovered@gmail.com.

The short version

We collect what you put into the Service, plus records of the calls your assistant handles.
A direct call you place yourself (“Call Direct”) is not recorded or transcribed. We keep the time, the number dialed, and the outcome. A direct call placed from the browser uses your microphone for that call only. The audio goes to the phone network and is not recorded.
We use that information to run your assistant. We do not sell personal information, and we do not use it for advertising.
Our website uses no advertising or analytics trackers — only sign-in cookies.
AI and telephony vendors process content on our behalf to provide the Service. We do not train AI models on your content.
If you connect Gmail, our use of Google data follows Google's Limited Use rules, described below.
Email us at any time to access, correct, or delete your information.

Information we collect

Information you provide

Account and organization details. Your name, email address, sign-in credentials (handled by our authentication provider), and organization name.
Content you add. Contacts (names, phone numbers, email addresses, companies, notes — including contacts you import from Google, Microsoft, or vCard files), calendar events, tasks, phone-sheet notes and instructions, messages you exchange with your assistant in the app, desk settings (including your assistant's name, greeting, and phone numbers), and feedback you send us.
Website inquiries. If you use the form on our landing page: your name, email, company, and message.

Information from calls

When your assistant answers or places a call, we collect the phone numbers involved, network-provided caller ID name, the audio of the conversation, transcripts, summaries, messages taken or delivered, and scheduling details discussed. This necessarily includes personal information about the people who call your line or whom your assistant calls on your behalf — their names, voices, phone numbers, and what they say.

Information from Google, with your consent

If you connect a Gmail account, we access email data as described in the "Google user data" section below. We only receive this data after you approve access through Google's consent screen. You can also connect a separate mailbox for your AI assistant; the same practices and protections apply to it. The Service reads that mailbox's incoming mail and can prepare proposed replies and new emails from it for your review — nothing is ever sent from any connected mailbox without your explicit approval.

Billing information

Payments are processed by Stripe. Your card number is entered on Stripe's hosted checkout page and never touches our servers. We store only your card's brand and last four digits (for display), Stripe's customer and payment-method identifiers, and records of your usage of the Service (such as call minutes) for billing.

Information collected automatically

Standard server logs, security and audit records (which can include the IP address of an administrative action), and the cookies described in the "Cookies" section. We do not use advertising or analytics trackers.

If you enable push notifications in our iPhone app, we store a device push token for your account (so notifications reach your phone), your notification preferences, and which notifications you've opened in the app, so the count on your phone stays right. Notification content — such as a caller's name or an email's subject line — is delivered through Apple's push notification service to reach your device. You can turn notifications off any time on the My Profile page or in your phone's settings.

How we use information

To operate the Service: answer and place calls, transcribe and summarize conversations, maintain your phone sheet, contacts, calendar, and tasks, and prepare email drafts you ask for.
To support you and improve the Service, including reviewing how the Service performed during our beta (see "Calls, recording, and transcription").
To meter usage, bill you, and maintain financial records.
To secure the Service, prevent fraud and abuse, and enforce our Terms of Service.
To comply with law.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising. We do not use your content to train generalized AI models, and our AI vendors process it only to provide their services to us.

Calls, recording, and transcription

Recording and transcription are how the Service works: your assistant listens, speaks, takes messages, and writes them down for you.

Conversations handled by your assistant are recorded and transcribed by our voice vendors as part of providing the Service. Transcripts and summaries are stored in your account; call audio is hosted by our voice vendor.
Your desk's Recording setting controls recording and transcription of bridged, person-to-person portions of calls (when your assistant connects a caller directly through to a person). When it is on, your assistant asks the caller's permission before staying on the connected call; if the caller declines or doesn't clearly agree, that portion is neither recorded nor transcribed. Callers' answers may be remembered for future calls. When the setting is off, the bridged portion is neither recorded nor transcribed and callers are not asked.
During our beta, Deskcovered staff may review call records — including recordings and transcripts — to monitor quality, investigate problems, and improve the Service.
You are responsible for using call recording lawfully in your area, as described in our Terms of Service.

Google user data (Gmail, Google Contacts, Google Calendar)

This section applies only if you choose to connect a Google account — Gmail, Google Contacts, or Google Calendar — and it governs all Google user data notwithstanding anything else in this policy.

What we access. We request the gmail.modifyscope. With it, the Service can search your mailbox, read messages you ask about, and create drafts (including replies) — this is what powers the email features shown in the app or spoken on a call you make to your assistant: finding and summarizing mail at your request and preparing drafts for your review. When you use Reply, the Service can propose a draft reply for your review, written from the thread and your own recent messages; nothing sends unless you click Send. You can also ask your assistant about your email by phone; what it reads to you on a call becomes part of that call’s transcript and recording, like anything else said on the call. Records of drafts prepared for you and messages sent at your direction appear in your account pages.

What we never do.Sending happens only when you explicitly approve a specific message. You can approve a draft by clicking Send, or — on a call with your assistant — by saying yes after it has read the draft back to you in full; a spoken approval is recorded like a click: who approved, on which call, and when. The assistant has no ability to send email on its own. By default we do not scan your mailbox in the background — we access messages only as needed to answer the requests you make. If you turn on inbox watching, the Service periodically checks for new messages and summarizes them so your assistant can flag ones that need your attention and, if you enable it, call to tell you; flagged items appear in your account pages. You can turn inbox watching off at any time, and turning it off stops the background checking immediately.

Google Contacts. If you import contacts from Google, we request the contacts.readonlyscope. We read your saved contacts once, when you click Import, and copy the names, phone numbers, email addresses, companies, notes and nicknames into your Deskcovered contacts. We never read Google's automatically saved “Other contacts”, never change or delete anything in Google Contacts, and never read your contacts in the background.

Google Calendar. If you connect Google Calendar to a desk, we request the calendar.events and calendar.calendarlist.readonly scopes (connections made before this change hold the narrower calendar.events.owned scope until you reconnect). We read the list of calendars in your Google account so you can choose which ones a desk shows. Deskcovered keeps a copy of the events on the calendars you choose (from 30 days back to a year ahead), refreshed about every 15 minutes, so your AI assistant can see and speak about your day; private events are stored only as “Busy”. Events created on the desk are written to your main Google calendar. When you change or delete an event on the desk — one the desk created or one that came from Google — that change is carried to your Google Calendar, and changes made in Google are carried to the desk. Calendars you can only view in Google are read-only here too. Deskcovered changes or deletes an event in Google only when you, or your AI assistant at your direction, change or delete it in Deskcovered. Guests on a meeting are not notified of changes made through Deskcovered.

How Google data is stored. Your Google OAuth tokens are encrypted with AES-256-GCM before they are stored, and message content is processed to fulfill your request rather than copied wholesale into our systems. Calendar events copied from Google and contacts imported from Google are stored like any other content you add to the Service, encrypted at rest by our database provider.

Deskcovered's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

We use Google user data only to provide and improve the user-facing email, contacts and calendar features described above. We do not use it for advertising of any kind, and we never sell it or transfer it to data brokers, advertising platforms, or resellers.
We transfer Google user data to others only as necessary to provide those features with your consent (for example, to the service providers listed below, who are bound to these same limits), for security purposes such as investigating abuse, to comply with applicable law, or as part of a merger or acquisition — and in that last case only with your prior explicit consent.
Humans do not read your Google user data unless you explicitly ask us to look at specific messages, it is necessary for security purposes or to comply with law, or the data has been aggregated and anonymized for internal operations.
We do not use Google user data to create, train, or improve any machine learning or artificial intelligence models — ours or anyone else's. Email content is sent to our AI vendors only transiently, per request, to produce the answer or draft you asked for, and never for model training.

Disconnecting. You can disconnect Gmail at any time from the Email page in the app — we revoke our access with Google and delete the stored tokens — or from your Google Account security settings. After disconnection we retain a record of the connection (the email address and its status) for security and compliance accounting. Disconnecting Google Contacts (from the Import screen on the Contacts page) deletes the stored tokens and keeps the contacts you already imported — you can undo an import in the app. Disconnecting Google Calendar (from Desk Settings) deletes the copied Google events from the desk; events the desk placed on your Google Calendar remain yours in Google.

We share personal information only with service providers that process it on our behalf to run the Service, each limited to its role:

Supabase — database and sign-in infrastructure.
Vercel — web application hosting.
Fly.io — hosting for our telephony bridge.
Twilio — the phone network: connecting calls and phone numbers.
Retell — voice AI platform: call audio, speech-to-text, and text-to-speech for assistant conversations; hosts call recordings.
Deepgram — speech-to-text for bridged person-to-person call segments.
OpenAI — AI processing of assistant conversations; AI-generated assistant portraits.
Anthropic — AI processing for in-app chat and call summaries.
Stripe — payment processing.
Resend — sending transactional email.
Apple — delivering push notifications to the iPhone app; notification content transits Apple's push service.
Google — the Gmail features you choose to connect. Separately, our pages load fonts from Google Fonts, which means your browser contacts Google's servers when a page loads.

Beyond service providers, we disclose personal information only: to comply with law or a valid legal process; to protect the rights, safety, or property of Deskcovered, our users, or others; or in connection with a merger, acquisition, or sale of assets, in which case this policy continues to apply and Google user data is transferred only with your prior explicit consent. We do not sell personal information.

Mobile information, text-messaging opt-in status, and consent data will not be shared with or sold to third parties or affiliates for marketing or promotional purposes. Message frequency varies. Message and data rates may apply. Reply STOP to any text to opt out and HELP for help. How texting works is described at deskcovered.com/texting.

Texts you send to your desk’s number are stored in that desk’s chat thread, the same as typed chat.

Cookies and similar technologies

We use cookies only to make the Service work: keeping you signed in, remembering which organization you are viewing, and a short-lived cookie that secures the Gmail connection flow. Your browser's local storage holds screen preferences (like whether the sidebar is folded). We use no advertising cookies and no analytics trackers.

Because we do not track you across other websites, there is nothing for a "Do Not Track" browser signal to turn off, and we do not respond to one. We do not sell or share personal information; where the law treats a Global Privacy Control signal as an opt-out request, we honor it.

How long we keep information

We keep your information while your account is active, because your assistant's memory — the phone sheet, transcripts, contacts, calendar — is the product. Specifically:

Phone-sheet history, transcripts, and summaries stay until you delete them or your organization is deleted.
Call audio is hosted by our voice vendor and subject to its retention practices.
Usage and billing records are kept for accounting and tax purposes.
Security and audit logs are kept as needed to protect the Service.
After you disconnect a Google account, we keep the record of the connection (the account's email address and its status) described in the Google section.
Feedback you send us may be kept after account closure.

Deleting your organization removes its live data from the Service. To request deletion of anything else — including your account — email deskcovered@gmail.com and we will act on it.

Security

Information moves between you and the Service over encrypted connections, our database provider encrypts data at rest, Google OAuth tokens are additionally encrypted by the application itself (AES-256-GCM), and access to production systems is restricted. No method of transmission or storage is completely secure, so we cannot guarantee absolute security — if you believe your account has been compromised, contact us immediately.

Your rights and choices

You can view, edit, and delete most content directly in the app — contacts, phone-sheet rows, calendar events, tasks, and your desk settings.
You can turn bridged-call recording and transcription on or off in Desk Settings, and disconnect Gmail at any time.
You can email us to request access to, a copy of, correction of, or deletion of your personal information. We honor these requests for all users regardless of where you live, and we will verify the request came from you before acting. We will not discriminate against you for exercising them.

If you called or were called by a Deskcovered assistant: we process that call data on behalf of the customer whose assistant handled the call. Direct requests about it to that customer; if you contact us instead, we will pass your request along and help them honor it.

Children

The Service is for adults and requires users to be at least 18. It is not directed at children, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, email us and we will delete it.

Changes to this policy

When we change this policy we will post the new version here and update the date at the top. If a change meaningfully reduces your rights, we will notify account holders by email before it takes effect.

Contact us

deskcovered@gmail.com