How to Preserve Your Projects and Files on Renderforest: Understanding the 60-Day Inactivity Policy

Modified on Wed, 26 Apr 2023 at 03:26 PM

Renderforest is dedicated to providing an efficient and user-friendly platform for all its users. As part of this commitment, the company has implemented a 60-day inactivity policy to ensure optimal performance and resource management. In this article, we'll explain what this policy entails, how it affects your projects and files, and what you can do to prevent data loss.

What is the 60-day inactivity policy? 

The 60-day inactivity policy is a measure taken by Renderforest to remove files from user accounts that have been inactive for a specified period. Users who haven't logged in for 60 days will receive a newsletter notifying them of the impending removal of their files. This policy helps maintain server efficiency and free up resources for active users.

How can I prevent my files and projects from being removed? 

To avoid the removal of your files and projects, simply login to your Renderforest account once within 10 days of receiving the email notification. Logging in and out of your account is sufficient to signal the system that you are still an active user. As a result, your files and projects will be preserved, and no data will be deleted.

What happens if I don't log in within the 10-day window?

 If you fail to log in within the 10-day period after receiving the inactivity email, your files and projects will be permanently removed from your account. Unfortunately, once your data has been deleted, it cannot be recovered. Therefore, it is crucial to take action promptly to avoid losing your valuable projects and files.

Keep track of your account activity, and remember to log in periodically to maintain access to your data on the Renderforest platform.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article