Privacy — FormPulse

This policy explains how the FormPulse Google Forms add-on handles information when a form editor enables email notifications.

Information FormPulse accesses

FormPulse reads the current form’s title, settings, questions, and submitted answers to build notification emails. If the form collects email addresses, it can read the respondent email address for a receipt when the editor enables that option. It also uses the Google account email address of the editor who sets up the notification trigger.

How information is used

FormPulse uses the information to let editors configure notification rules, send a test email, deliver response notifications to recipients chosen by the editor, and optionally send respondents a separate receipt with their own answers. FormPulse does not use form answers for advertising.

Storage and retention

Notification rules, including recipient addresses and custom message content, are stored in the FormPulse Apps Script project’s Script Properties under the form ID. Editors can delete a rule in the add-on. FormPulse reads answers when a submission trigger runs and does not create a separate response database. Google Forms retains form responses according to the form owner’s Google account settings. Google Apps Script and Mail services may retain execution and delivery records under Google’s policies.

Sharing

FormPulse sends response details only to the email recipients selected by the form editor. An optional respondent receipt contains that respondent’s answers and excludes internal notification recipients and the form editor link. Google services process the data needed to run the add-on and deliver the emails. FormPulse does not sell Google user data.

Permissions

FormPulse requests access to the current form, permission to show its editor interface, permission to create a form submission trigger, permission to send email, and the editor’s account email address. These permissions support the functions described above.

Your choices