That I know.
However, there is an advanced option when you create the custom upload audience: Data Expiration (Number of days after which the audience membership will expire), where you can set a value between 1 and 180 days, therefor overwriting the 30 days default. At least this is how I understand this option.

However, once the audience was created, that info is not visible on the UI. With an API call you get a ttlInDays item in the json payload (something like "ttlInDays": 180) which seems to show the value I provide when creating the audience. So, I thought that maybe, just having that ttlInDays and the date when the audience was created, we can approximately say when the audience will expire.

However, I created a test audience from csv on Aug 20, 2025 with a Data Expiration set for 3 days. Just wanted to see what happens, without waiting too long. If I check the audience today (Sept 07, way more that 3 days after). I see "ttlInDays": 3, but the audience doesn't seem to have expired - still shows the same number of members as it did in the beginning.
So, how am I to understand the TTL in this case?