Privacy policy.

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

Editors can disable or delete notification rules. They can also remove the add-on and its Google authorization from their account. For questions or privacy requests, email support@nexusworld.dev.

This website and billing preview

The website does not ask for form answers or card details. The layout preview runs in your browser. Optional account-linked sandbox checkout creates test subscription records as explained below. If you contact support by email, the information you send is used to respond. Hosting services process requests and technical connection information to deliver the site. Google Identity Services is loaded on the billing page to offer sign-in. No advertising trackers or analytics scripts are installed by this website.

Future payments

Live paid billing is not enabled. The optional test checkout is hosted by Bachs and requests an email to create sandbox checkout and subscription records. For account-linked billing tests, Google verifies your identity. We store your stable Google account identifier, email, display name, checkout references, signed billing events and subscription status in a private database on our Namecheap hosting. The billing service uses these records to activate test Pro for the correct account and prevent duplicate or fraudulent activation. We send your verified billing email and an internal account reference to Bachs; no form answers are sent to Bachs or our billing server. Browser sessions use a secure, essential session cookie that expires after four hours of sign-in. Billing records are retained while needed to provide and investigate the test service; contact support@nexusworld.dev to request deletion. Do not enter real payment details. Bachs processes checkout information under its privacy policy. This policy will be updated before live billing or paid account activation is introduced.