The below describes the flow of user data through Knarr systems. This is data that is captured specifically about users who are using the Knarr platform, not the data that those users are working with inside the platform. The latter's information is detailed HERE@$@#$@
Sign Up Data
When a user signs up for Knarr, that user's information is stored in our authentication provider, Auth0. From there, there user's information is linked into Mailchimp via an integration workflow through Zapier. Metadata about the integration is stored within the Zapier log files.
Log In Data
When a user logs into Knarr for the first time, that user is instantiated in a backend database that sits behind an Amazon VPC. Only the user's Auth0 identifier is stored there and that is what is used for permissions and access within the platform.
When a user is instantiated, that user's email address and Auth0 identification ID are stored in Stripe, Knarr's payment processing system. This data is used only to allow users to upgrade or downgrade subscriptions.
When users log in, the transaction log of the login is recorded in Auth0 for less than 14 days and sent to Loggly, where it resides for less than 14 days before being purged from the system. Additionally, there is a Zapier integration that stores this login data to a google sheet for the Knarr product team to understand user loads. This data is purged weekly and does not contain any PII.
Knarr does not capture user-specific information about logins and platform usage. Though the capability is available in Google Analytics, we do not leverage that capability because tracking peoples' every movement, even with good intentions, is anathema to our core beliefs about privacy, whether a free user or a paid user.
Instead, we ask that our users please provide feedback in our community so we can continue to improve the product via feedback that is willingly shared.
All server data is processed via Amazon CloudWatch for logging and monitoring purposes. No user-specific data is stored in CloudWatch.