Decision: Connect an inbox only if you need the assistant to work with its messages and accept the processing described in Perplexity’s privacy notice. Changing the email used to register, or using a temporary address on another website, does not protect messages in an inbox you authorize.
This guide is for people deciding whether to connect Perplexity Email Assistant to a personal or work inbox, and for anyone who wants to separate registration privacy from email-content privacy.
Last updated: October 28, 2026. The policy facts below were checked against Perplexity’s privacy notice, which shows an update date of October 23, 2026, and its product update notes. See the privacy notice and official Email Assistant update. Recheck the notice and the connection consent screen before authorizing an account; the actual permission display matters.
Perplexity email assistant privacy depends on what you connect
There are two different decisions that can look like one:
- Giving a service an email address during account registration gives it an address for account-related communication. That action alone does not establish that the service can access the messages in that inbox.
- Connecting an email provider to Email Assistant is a separate authorization. Perplexity’s privacy notice says that when a user chooses to connect an email provider, the service analyzes sent and received email content to provide reply suggestions.
That distinction is the first privacy checkpoint. A user who changes the address used to register may reduce exposure of their primary address to a sign-up form. They have not, by doing so, changed the content available through a separately connected inbox.
The notice describes a purpose for processing email content; it does not, by itself, specify the exact permissions shown for every account type or connection method. Do not assume that every user sees the same authorization scope, or that providing an address authorizes access to an entire mailbox. Read the screen shown during connection and compare it with the provider’s permission documentation. For Gmail API permissions, Google documents scopes with different access levels, so the specific scope matters—not merely the fact that an account is being connected. Google’s Gmail API scope reference explains those distinctions.
| Decision metric | What the available evidence says | What to check before proceeding |
|---|---|---|
| Email-content processing | Perplexity says connected email content may be analyzed to provide reply suggestions. | Confirm which mailbox is connected and read the consent screen’s stated access. |
| Model-training use | The privacy notice says email content in this described context is not used to create, train, improve, or fine-tune AI models. | Keep this statement limited to the email-content context described by the notice. |
| Address exposure | A registration address and an authorized inbox are different privacy layers. | Check whether a form only asks for an address or whether an account connection is also requested. |
| Ongoing access | The connection is an account authorization, not just a one-time address submission. | Review the provider’s access controls and how to remove an authorization. |
The distinction between content processing and training is especially important. Will Perplexity Email Assistant use connected messages to train AI? Its privacy notice says email content is not used to create, train, improve, or fine-tune AI models in the described Email Assistant context. That is a specific statement about model use; it does not mean the messages are never processed. The same notice describes analysis of sent and received messages to generate reply suggestions.
Compare the privacy trade-offs by metric
A primary inbox may be convenient because it already contains the conversations the assistant is meant to help with. That convenience comes with a broader potential exposure: the mailbox may hold personal, work, financial, or account-recovery messages unrelated to the replies the user wants help drafting. Assess the actual contents and the permission screen rather than treating “primary inbox” as a simple on/off risk label.
A separate inbox can narrow the set of messages available to the assistant—but only if it is a real, usable mailbox and the relevant messages are routed there. It is not enough to create a new address and then connect the primary inbox anyway. Nor is an empty separate account useful if the user expects the assistant to work on conversations that remain elsewhere.
| Inbox choice | Best fit | Main privacy cost or limitation |
|---|---|---|
| Primary inbox | The assistant needs to work with conversations already held there, and the user accepts the described content processing. | It may contain many messages beyond the specific conversations the user has in mind. |
| Separate, ongoing mailbox | The user can route only relevant correspondence into a dedicated account and can maintain access to it. | It requires deliberate separation and may not include existing conversations. |
| Temporary receiving address | A low-trust registration form only needs an address for a limited interaction. | It is not a replacement for a durable mailbox and does not shield another inbox that has been connected. |
Should the assistant connect to a primary inbox or a separate one? Choose the primary inbox only when its existing conversations are necessary and the user accepts the scope shown during authorization. Choose a separate, ongoing mailbox when the desired workflow can be contained there and the user can keep that account accessible. If neither condition is true, do not connect an inbox just to test the feature; first identify which messages the assistant needs.
The practical test is not whether a separate account sounds more private in theory. It is whether the account actually limits the messages that become available to the assistant, remains usable for the intended work, and can be recovered when needed. An account used for important correspondence should not be abandoned casually. Users who need a long-term recovery address should maintain one they control, rather than relying on an address intended only for short-lived registration.
Where a temporary address helps—and where it stops
A temporary address can help with a different privacy problem: a website’s registration form asks for an email address, and the user does not want to expose their primary address to that site. An address used for a low-trust sign-up can separate that form from the person’s everyday inbox and make it easier to avoid follow-up marketing in the primary account.
That protection ends at the boundary of the form. Can a temporary email address protect messages in an inbox already connected to the assistant? No. It can change which address is submitted to an external registration form; it cannot alter the contents or authorization of a different inbox the user has connected. If the concern is email-content processing, the relevant actions are to review the permission screen, decide whether the feature is worth that processing, and choose whether to connect any mailbox.
Use this distinction to route the privacy problem:
- Concern: a low-trust website will collect the primary address. Consider an address-isolation approach. The guide to separating email addresses can help distinguish disposable addresses, aliases, and ongoing mailboxes.
- Concern: an assistant will process inbox content. Review the authorization and the privacy notice before connecting. A temporary address entered somewhere else does not solve this.
- Concern: a service needs a durable route for replies or account recovery. Use an inbox the user can keep accessing, or an email alias that forwards to a controlled mailbox. A disposable receiving address is not automatically a suitable long-term contact.
- Concern: an address is exposed but the user still wants to receive messages. Compare an alias or forwarding arrangement with a separate mailbox. The inbox comparison guide covers how those options differ in use and continuity.
For a broader look at the limits of address separation, the email privacy guide can help frame what an address can hide—and what it cannot.
What to verify at each stage
Before registration: Identify whether the form only requests a contact address. If so, the user can decide whether to submit a primary address, an alias, or a separate address. Keep this decision distinct from any later request to connect an inbox.
Before authorization: Read the connection screen carefully. Note which email provider and account will be connected, what access the screen describes, and whether the user is comfortable with that access. The product update describes the assistant’s email-reply purpose; the privacy notice describes how connected email content is handled. Neither should be used to guess details that the authorization screen does not show.
After connection: Check the provider’s account-access controls and know how to remove access if the feature is no longer needed. Google’s guidance on reviewing and removing third-party account access explains how users can manage connected access for Google accounts. Removing an authorization is a control for future access; it should not be treated as proof that previously processed data has been erased. For deletion or retention questions, consult the service’s current privacy notice rather than assuming a result not stated there.
When the workflow changes: Reassess the choice if the user starts using the assistant for a different inbox, routes new categories of messages into a separate account, or sees a changed consent screen. A mailbox that was suitable for a narrow set of replies may no longer be suitable after it accumulates unrelated personal or work messages.
The privacy decision in one sentence
Connect an inbox only when its email content is needed for the assistant’s reply suggestions and the user accepts the processing described in the current notice. Use a separate, durable mailbox when it genuinely limits the relevant content and remains practical to maintain. Use a temporary address for low-trust registration forms—not as a shield for an inbox already authorized.
If the task is simply to keep a disposable sign-up away from the primary address, HourInbox can be considered as an address-isolation option; it does not replace a connected mailbox or protect its messages. For that narrower use, consult HourInbox’s available service information and keep the assistant’s mailbox decision separate.
Use temporary email for short-term tasks and a stable address for ongoing contact.
Use a countdown inbox for one-off tasks. If you’ll need to receive messages later, set up a long-term forwarding alias.