Blog /PostSignup Permissions Explained: What We Ask For and Why

PostSignup Permissions Explained: What We Ask For and Why

A detailed breakdown of every permission PostSignup requests and the reason behind each one.

December 20, 2024
4 min read
PostSignup Permissions Explained: What We Ask For and Why

Permission Transparency

Here's exactly what we ask for when you connect your email.

Gmail Permissions

gmail.send

  • What it does: Allows sending emails from your account
  • Why we need it: To send your automated founder emails
  • What it can't do: Read inbox, modify settings, access contacts

Microsoft 365 Permissions

Mail.Send

  • What it does: Allows sending emails from your account
  • Why we need it: To send your automated founder emails
  • What it can't do: Read inbox, modify settings, access contacts

Permissions We Don't Request

Gmail (NOT requested):

  • gmail.readonly (read emails)
  • gmail.modify (modify emails)
  • gmail.metadata (access headers)
  • contacts.readonly (access contacts)

Microsoft (NOT requested):

  • Mail.Read
  • Mail.ReadWrite
  • Contacts.Read
  • Calendars.Read

Permission Changes

We will never:

  • Request additional permissions without clear explanation
  • Upgrade permissions silently
  • Use permissions for purposes beyond stated

If our needs ever change, you'll be notified and asked to re-authorize.

Ready to try PostSignup?

Start sending founder emails from your own inbox. Free forever for up to 100 emails/month.