Google permission scope
When you send through Gmail, Feature Voice requests the gmail.send scope. This allows sending voting emails you create, not reading or modifying your mailbox.
Trust center
Email permissions and customer data should be easy to understand
Feature Voice is built for private customer feedback. This page explains what the app asks for, why it asks for it, and how customer voting data is handled.
Customer email handling
Recipient emails are used to deliver voting requests, track delivery state, record votes, and honor unsubscribes.
Unsubscribe support
Voting emails include unsubscribe handling so customers can opt out of future Feature Voice voting requests.
Provider flexibility
Teams can use Gmail, Feature Voice sending, Mailgun, or Resend depending on plan and sending needs.
What `gmail.send` means
Free accounts can send voting emails through Gmail. To do that, Google requires Feature Voice to request the `gmail.send` permission after you choose Gmail as the sender.
This permission is limited to sending messages. It does not grant access to read, search, delete, or modify emails in your mailbox.
If your team prefers not to use Gmail sending, you can try Feature Voice delivery with five recipient sends. Paid sending options can continue with Feature Voice, Mailgun, or Resend.
Practical privacy controls
Private invite-only voting
Votes are sent only to the customer emails you choose. A public roadmap or public voting board is not required.
Unsubscribe handling
Customers can unsubscribe from future voting requests, and unsubscribed recipients are skipped in future sends.
Result sharing controls
Teams can share voting results when needed and anonymize voter emails before sharing sensitive outcomes.
Account deletion
Account settings include an account removal flow for teams that need to delete their workspace data.