Read this article to know what data is stored by Yet Another Mail Merge, how it is stored and used.
What data is stored?
YAMM stores user and usage data, as detailed in the table below, in Google Cloud Platform.
Type of data | check_circle We store: | cancel We don't store: |
---|---|---|
User identification |
|
|
Mailing document/Email |
|
|
Mailing lists |
|
|
Files & its contents |
|
|
Email tracking data |
|
|
Subscription data |
|
|
We store only data that is necessary for YAMM to function to its entirety. Deleting some of all of this data may interrupt YAMM’s functionality. However, if you do not want us to store your data, you can send us your request, and we will permanently delete it from our database.
What are the Google services used by YAMM?
Here is the complete list of Google Cloud Platform services used by YAMM 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 YAMM to provide its services | PII | |
Google Analytics | To track essential metrics on app usage (active users, number of emails/campaigns sent) towards improving or introducing product features. | Non-PII | |
Stackdriver Logging Log Management and Analysis |
For real-time error monitoring of the YAMM service for investigation and analyze the cause of the errors. | Non-PII | |
BigQuery 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 |