Time Champ Retention Policy FAQ

Created by Lakshmi Bhavani, Modified on Mon, 4 Nov at 6:29 PM by Lakshmi Bhavani

1. What will be the expected bandwidth usage of this tool?

The expected bandwidth usage for Time Champ is approximately 80-100 MB per user per hour.

2. How much storage is required to capture screenshots?

Each screenshot typically ranges from 150 KB to 200 KB.

Example Calculation:

The number of screenshots depends on the configured settings.
If configured to capture 1 screenshot every 10 minutes, it will capture 6 screenshots per hour.
For an 8-hour workday, that results in approximately 48 screenshots.
Each screenshot averages around 200 KB.
Thus, 48 screenshots x 200 KB = 9,600 KB (about 10 MB) of storage per user per day.

3. How much storage is required for screen recordings?

On average, each 2-minute screen recording consumes about 4 MB of storage. For an 8-hour workday, the storage requirement is approximately 1 GB per user.

Screen Recording Calculation:

If screen recording is enabled for 8 hours, there will be approximately 30 recordings per hour, totaling 240 recordings for 8 hours.
Assuming each recording is around 4 MB, the calculation would be 240 recordings x 4 MB = 960 MB (nearly 1 GB) per user for 8 hours.

4. Where is your data center located?

Time Champ's data centers are located in:
- Vijayawada, Andhra Pradesh
- Hyderabad, Telangana

5. How long will our data be stored on your server?
https://timechamp.freshdesk.com/a/solutions/articles/101000451754

6) Where is all the data stored?

Data Storage: All data is stored on AWS.
Screenshots Storage: Screenshots are stored on Azure.

7) What are the minimum system requirements to install this application?

RAM: 4 GB (if the system is up-to-date), 8 GB is recommended.
Operating System:
- Windows: Above Windows 7
- Linux: Versions 18 to 22 (For version 22, Wayland must be disabled)
- MacOS

8) How much CPU and memory does the application consume?

CPU Usage: 1 to 2%
Memory Usage: 50-60 MB

9) What URLs need to be excluded from the proxy or firewall?

*.timechamp.io
*.v3.timechamp.io (replace with sites, sites2, sites3, or v3)
https://test.v3.timechamp.io/ (site address)
https://timechampv2storage.blob.core.windows.net/
https://socketweb14.timechamp.io/
customers.v3.timechamp.io

10) What ports and IP addresses or websites need to be added to the firewall?

Ports: 443, 80, 444, and 81
URLs/IPs:
- *.timechamp.io
- *.v3.timechamp.io (replace with sites, sites2, sites3, or v3)
- https://test.v3.timechamp.io/ (site address)
- https://timechampv2storage.blob.core.windows.net/
- https://socketweb14.timechamp.io/
- customers.v3.timechamp.io

11) Is it possible for clients to store data on their side?

Yes, clients can store data on their own infrastructure. They need to provide Azure Blob Storage to store screenshots and recordings. Once configured, all screenshots and recordings will be stored on the client's side and can be accessed anytime from the dashboard. There is no retention policy for screenshots stored on the client's end.

12) If a client initially stores screenshots on their end but later wants to move to TimeChamp storage, is it possible?

Yes, clients can change the storage settings at any time. After switching to TimeChamp storage, new screenshots will be stored according to our retention policy, while previous screenshots will no longer be retained on TimeChamp storage. Only newly generated screenshots will be stored following the change.

Note: After changing the settings, previous screenshots will no longer be stored in TimeChamp storage. Only new screenshots will be stored on our end following the change.