Please note that MAZ does not trade/sell/exchange any of our customers' users' data for any marketing purposes.
We store the following user-related data in our Database.

User related information:

When a user creates an account in your MAZ app or logs in MAZ app, the following record is stored in our database:

  • Email (stored in encrypted form)
  • Display name (in case of Facebook login)
  • The platform the user last signed in from
  • Last logged in date

Purchase related information:

When a user purchases subscription or subscription is renewed, the following record is stored in our database:

  • Product id purchased
  • Transaction id
  • End date(in case of subscription purchase)
  • Original purchase date

Print subscription(database integration) related information:

When an existing subscriber logs in the app, the following record is stored in our database:

  • Login credentials (in plain text, not encrypted)
  • Status of the user (active/inactive)
  • Response received from the database integration API

Push notification related information:

When a push notification is sent, the following record is stored in our database:

  • Device token (of the user's device) received from the app
  • User’s country

Item related (articles/videos/audio) information:

This information is related to items been viewed or saved by the end-user. It includes:

  • Article URL
  • Author
  • Publication date

Item views related information:

This information is related to how much of an article/video/audio has been consumed by the end-user. The app uses this data to open the content from the point where the user had last left off.

Receipt related information:

This information is related to receipts the app gets from the respective app store whenever the user makes a digital purchase be it an individual IAP (feed) or a subscription. Subscription renewals are also purchases. The receipt data is needed to validate purchases with the respective app store.

Metering related information:

This data is about when did the end user start consuming the meter (eg: free timed access) for a particular locked feed.

Did this answer your question?