In the current implementation, a subscription from the RH customer portal attached to an org can stay in the database indefinitely past its expiration date. For operations that check the database for org bound subscriptions (e.g. private repo check) we should also check the expiration date, and if it is invalid remove it from the database.