Privacy

Privacy Policy

Effective October 28, 2026

Agent Doorbell is operated by NthPlus (“we”, “us”). It captures permitted data from the sources you connect, retains matching messages in named-agent inboxes, and notifies the receivers you choose. Agents can exchange messages and publish results to approved outputs. This policy explains what information we collect, how we use and share it, and the choices you have. It applies to agentdoorbell.com, the Agent Doorbell dashboard, agent connections, and its Teams and Slack integrations.

Information we collect

• Sign-in information. The email address you sign in with, your sign-in sessions, a password if you choose to set one, and, if we invited you, a record of your invitation: who invited you and when you were invited, first signed in or had your access revoked. Deleting your data does not remove this record, so your invited address can still sign in. When you sign in with Google, Google provides your Google account identifier, name, email address and profile photo URL. We store Google's sign-in tokens encrypted. Signing in with Google does not give us access to your Gmail.
• Connected Gmail accounts. When you connect a Gmail account, Google provides its email address and OAuth tokens that let us read that account's message metadata.
• Gmail message metadata. While a connected inbox is selected as an agent input, we read new message IDs, labels, received times, and From, To, Cc and Subject headers. We retain only source identity and metadata permitted by your source capture policy. We also read Gmail's mailbox history identifiers to find new messages. Pausing agent notifications does not stop this capture.
• Connected Outlook accounts. When you connect an Outlook.com or Microsoft 365 mailbox, Microsoft provides its email address and OAuth tokens that let us read that mailbox's message metadata.
• Outlook message metadata. When Microsoft notifies us of a new message in a connected inbox selected as an agent input, we read the message ID, received time, draft status, sender, To and Cc recipients and subject of each message that arrived in that inbox in the last five minutes, up to 100 messages. We retain only source identity and metadata permitted by your source capture policy. We also store the Microsoft Graph subscription identifier. Pausing agent notifications does not stop this capture.
• Microsoft Teams identities and installations. When you verify your Teams identity and connect an installation, we store your Microsoft tenant and user object identifiers, the verified time, the installation scope and identifier, and its connection state. A team installation can be shared, but only your own addressed messages enter your agent inputs.
• Addressed Teams messages. When you send a private message to the app or directly @mention it in a channel where it has been added, Teams can deliver the message text, sender and conversation identifiers, timestamp, and any attachment descriptors to the Bot. Supported routing covers personal chats and standard channels. When Teams identifies a private or shared channel, we reject its messages from routing; Teams does not always include channel type, so do not add the app to those channels. We keep a content-free receipt to prevent duplicate capture. Your source capture policy selects the text and details we retain. We do not fetch other channel messages or file contents.
• Slack connections and messages. We store your connected Slack workspace and human identity, authorization tokens, and capture preferences. Selected new direct messages and exact mentions visible to that identity can include channel, sender, and timestamp metadata, plus text if you enable it. Group direct messages require opt-in. We do not import history, download files, mirror later edits or deletions, or post replies as you.
• Webhook sources. For an endpoint you create, we store its name, authentication settings, and declared payload schema. From valid submissions we retain declared scalar fields and bounded nested JSON paths you explicitly select for capture, not the raw body or unselected properties. Browser publishing also records credential policies and submission identities used to enforce limits and deduplicate retries.
• Agent messages and results. We retain accepted MCP text, declared fields, explicitly selected bounded JSON, sender and recipient labels, and references to parent messages. These labels route messages; they do not create private access boundaries between agents authorized by the same customer.
• Configuration and retained messages. Named agents and outputs, source capture policies, matching conditions, shared fields, notification timing, receiver credentials, retained inbox memberships, independent reader positions, and message annotations.
• Delivery history. Notification, signal and event identifiers, source identities, delivery outcomes, and selected source details in frozen notification packets.
• Agent connections. Records of the assistants you authorize, their permission grants, and the tokens issued to them. Access applies across the customer's resources within those grants, not only to one named agent.

To connect Gmail, we request only Google's gmail.metadata permission. It does not allow access to message bodies or attachments, and Agent Doorbell never requests them.

To connect Outlook, we request Microsoft's Mail.ReadBasic permission, which does not allow access to message bodies, previews or attachments, together with openid, email and offline_access so we can identify the mailbox and keep watching it while you are away. If Microsoft does not grant Mail.ReadBasic for an account, we ask once for Mail.Read instead. That permission would allow reading message bodies, but Agent Doorbell still requests only the fields listed above.

How we use Google user data

We use Google user data only to provide the features you configure:

• to sign you in, when you sign in with Google;
• to identify the Gmail account you connected;
• to receive Gmail's notifications about new messages in that inbox;
• to retain permitted message metadata and evaluate your agent input conditions; and
• to notify your chosen receiver with the fields you approve when a message matches.

Capture and notification disclosure are separate choices. Source-wide capture determines which metadata Doorbell may retain; each agent input determines which optional fields its receiver sees. Each email notification includes its message ID and connected account identity. Grouped notifications contain at most the configured page size of 1–20 details, with a default of 5. Retained content expires seven days after acceptance; reading or delivering it does not extend that lifetime. We keep content-free email identifiers for up to 30 days to prevent duplicates. We do not fetch or send message bodies, previews, or attachments.

We do not sell Google user data, use it for advertising, use it to develop, improve or train artificial intelligence or machine learning models, or use it to determine creditworthiness. No person at NthPlus reads your Gmail data unless you give us permission for a specific support request, it is necessary for security purposes such as investigating abuse, it is required to comply with law, or it has been aggregated and anonymized for internal operations.

How we use Microsoft user data

We use Outlook data to identify the mailbox you connected, receive Microsoft Graph notifications, retain permitted metadata, evaluate agent input conditions, and send selected details to your receiver. We use Teams identity information to verify the sender and link a Bot installation to your account. Only messages addressed to the Teams app enter that capture path. A receipt sent in Teams confirms capture, not delivery or completion by the receiving agent.

We make the same commitments for Microsoft user data as for Google user data. We do not sell it, use it for advertising, use it to develop, improve or train artificial intelligence or machine learning models, or use it to determine creditworthiness, and no person at NthPlus reads it except in the circumstances listed above.

For webhook sources, capture includes declared scalar fields and explicitly selected bounded JSON paths. Notifications disclose only the fields approved for that agent input, together with source identity. The sender receives an acknowledgment after durable acceptance; notification delivery happens separately. Accepted publications can remain available even when no agent input matches.

How we share information

• Your agents and receivers. Notifications go to the webhook or MCP receiver you configure. Authorized agents can read retained data and publish messages or results within their grants. Approved outputs deliver separately published results to your selected webhooks. You control those receivers and any separate provider access you give your agents.
• Service providers. Railway hosts our application and database. Google Cloud Pub/Sub delivers Gmail change notifications, and Microsoft Graph delivers Outlook change notifications. Resend delivers sign-in codes and service alerts to your sign-in address. They process data only to provide these services to us.
• Legal requirements. We may disclose information when required by law or to protect the security of our service and its users.

We do not transfer Google user data to anyone else. If Agent Doorbell is involved in a merger, acquisition or sale of assets, we will ask for your explicit consent before transferring your Google user data.

The same applies to Microsoft user data.

Storage and security

Gmail and Outlook OAuth tokens and destination keys are encrypted with AES-256-GCM before they are stored, and sign-in codes and passwords are stored only as salted hashes, never in a form we can read. Data travels over HTTPS, and our database is reachable only from our application's private network. Access to production systems is limited to the people who operate Agent Doorbell.

Retention and deletion

• Retained content expires seven days after acceptance, including its derived delivery copies. Delivery history and source publication receipts have a seven-day retention period. Content-free email, Teams, and Slack identifiers used to prevent duplicates can remain for up to 30 days.
• Pausing an agent or output cancels unsent notifications, not capture or retained inbox membership. Removing a message from one inbox does not erase it elsewhere. Explicit erasure removes canonical content and derived copies; it cannot recall data already delivered to a receiver.
• Disconnecting a Gmail or Outlook account in the dashboard immediately deletes its stored tokens and monitoring records. Microsoft may keep sending notifications for a disconnected Outlook mailbox until its subscription lapses, within three days; we discard them.
• Source disconnection or access revocation blocks further disclosure of its retained content and cancels unsent copies. Reconnection does not restore revoked content. Slack identity ownership records can remain without credentials or access to message content.
• Deleting your data from the dashboard removes your sign-in account, sources and credentials, linked Teams identities, named agents and outputs, retained messages, receivers, and history. A shared Teams installation can remain for other linked customers; content-free duplicate receipts expire under the retention rule above.
• You can remove Agent Doorbell's access at any time from your Google Account permissions. We then stop accessing that mailbox and show it as needing reconnection.
• You can remove Agent Doorbell's access to an Outlook mailbox at any time at microsoft.com/consent for a personal Microsoft account, or from My Apps for a work or school account. We then stop accessing that mailbox and show it as needing reconnection.

Deleted data can remain in infrastructure backups until those backups expire.

Your choices

While you can sign in, you can manage sources, named agents, outputs, receivers, and retained messages in the dashboard, and delete all your data there. If your access has ended, email privacy@agentdoorbell.com and we will temporarily restore your access so you can delete your data. Contact us to ask about or correct the information we hold about you.

Google API Services User Data Policy

Children

Agent Doorbell is intended for business use and is not directed to children under 13. We do not knowingly collect their information.

Changes

We will post changes on this page and update the effective date. We will notify you by email of material changes.

Contact

Send questions or requests to privacy@agentdoorbell.com.