Limited Use Disclosure
Andsend's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.
Justification for restricted API-scopes that Gmail users can choose to grant Andsend access to, inside the Andsend App
Andsend uses the “https://www.googleapis.com/auth/gmail.send”-scope in order to send emails (including email replies).
The reason a narrower scope would not be sufficient is because: Andsend needs the ability to send emails for providing the productivity value the Andsend web app should offer. According to Google Gmail API documentation the “gmail.send”-scope is the least restricted scope that allows for sending emails.
Andsend uses the “https://www.googleapis.com/auth/gmail.metadata”-scope in order to view headers of emails (messages) on a thread that was previously created through the API via the “gmail.send”-scope. Through the headers Andsend determines sender(s), recipient(s), the Message-ID and References (see RFC 2822 standards) to be able to reply to a thread.
Andsend will not store nor log any contents of the email body. Andsend only looks if there is a result or not, for a given query (i.e. the “boolean value”).
Andsend will only read headers and metadata from emails.
The reason a narrower scope would not be sufficient is because: Andsend needs the ability to view email headers for providing the feature to determine if a reply has been received from a specific email-address. Reply-determiniation is used by Andsend to not send any emails to any recipient that has already replied to the user. According to Google Gmail API documentation the “gmail.metadata”-scope is the least restricted scope that allows for reading the header and metadata information in emails.
The user can choose to optionally opt-in to the "https://www.googleapis.com/auth/gmail.readonly"-scope, if the user wants to allow Displaying and Analyzing replies in the Andsend platform, and guide users to improve their reply-rate and copywriting.
Andsend will not store nor log any contents of the email body. The processing is short-term lived and the user may opt-in to subprocessors such as AI GPT models for analysis. Generated tags from processing may be stored long term, while any email contents will not.
The reason a narrower scope would not be sufficient is because: The “gmail.readonly”-scope is the least restricted scope that allows for accessing the body content of an email.
Further information & details
For further information or details, please contact [email protected].