Read this article to know what data is stored by Form Publisher, how it is stored and used.
What data is stored?
|Type of data||check_circle We store:||cancel We don't store:|
|Google Form data||
|Google Form settings||
|Template & markers||
|Destination folder & Files|
|Sharing & notification email addresses||
|Notification email content||
We store only the data that are necessary for Form Publisher to function to its entirety. Deleting some of all of this data will interrupt Form Publisher’s functionality.
However, if you do not want us to store your data, you can submit your request and we will permanently delete it from our database:
Storing workflow data
Form Publisher approval workflow helps routing the documents for approvals after they are generated on Google Forms submission.
In real-time, the approval and e-signature of the documents are collected in Form Publisher web app, and are not originally part of the Google Form.
So when a document approval workflow is setup, Form Publisher stores specific configuration data and the generated file information (as marked with * in the above table) in Google Firebase.
This data is essential for the web app to trigger email notification and update of the approval information in the Form responses spreadsheet, whenever there is an approval action on the document flow.
What are the various services used by Form Publisher?
Here is the complete list of Google Cloud Computing services and the software used by Form Publisher for varying purposes. It also clearly describes if your data is used as Personally Identifiable Information (PII) or Non-Personally Identifiable Information (Non-PII).
|Entity name||Service||Purpose||PII or Non-PII|
Firebase Real Time Database
A real-time database
|To store user and usage data that are essential for Form Publisher to provide its services||PII|
|Google Analytics||To track important metrics on app usage (active users, number of documents generated) towards improving or introducing product features.||Non-PII|
Log Management and Analysis
|For real-time error monitoring of the Form Publisher service for investigation and analyze the cause of the errors.||Non-PII|
A data warehouse
|To export to and aggregate the error logs & exceptions to identify the most common errors, so we can proactively fix errors to reduce impact for our users.||Non-PII|