User & Account Management

Envestnet | Yodlee performs periodic refreshes following an adaptive refresh schedule for user data depending on user activity. If a user reduces their data access frequency or stops using the application (i.e., your application stops making data requests for that user), Envestnet | Yodlee reduces the frequency of data collection and stops the automatic data refresh if the data is not accessed for 90 days. Refreshes resume when you query data on behalf of the user again. (Note, refreshes cannot proceed if the platform cannot resolve a multi-factor authentication challenge or if user credentials are no longer valid. In this case, the user must resolve the problem before the data refresh can proceed.) Please check the refresh policy page for a detailed explanation of our data refresh policy.

If the user unsubscribes from your application, you should unregister the user from the Envestnet | Yodlee platform using the API requests. Once your request has been received, the user is unregistered, and account credentials are securely and permanently deleted from the database.

When you delete an account, the platform will stop collecting financial information from the corresponding financial institution on behalf of that user for that account. If it is the only account accessible at the institution with the bank credentials, the platform will also delete the associated bank credentials. If other accounts are associated with the same credentials, the credentials will be retained to enable account aggregation of those other accounts.

When an account is set as inactive, the platform stops updating the data for the respective account. The inactive account can later be set as active to re-enable account aggregation for that account. Yodlee does not return account details and transactions for deleted or marked inactive accounts.

To ensure account access credentials are permanently deleted, you should delete them on the corresponding /ProviderAccount.

There are no explicit means of marking a user inactive. To stop aggregating data for a particular user, you must mark all accounts of that user as inactive and then not log in with the user’s credentials.

When an account is set as inactive, the platform stops updating data for the respective account. However, the status of an inactive account can later be updated to be active.