It does not I believe, but if you try to upload it again, shouldn’t it produce the same error?
Now, I’m not saying your idea/product is unethical nor impractical, quite the opposite! This is a common aspect of user-driven apps. I understand your use case. My point is that if you’re dealing with contact information, it should be handled through a backend service.
I cannot help you with the ChatGPT plus problem sadly, that is a decision only you can make.
However, if you did want to use a custom GPT in a way that’s both secure enough for actual production and achieving what you want without errors, I would turn this into a cloud service, or cloud managed product, whereby you withhold this information in a managed database architecture of some form, and use the custom GPT to make API calls to your spreadsheet/database.
This allows you to leverage custom GPTs effectively, providing the accurate information in a way that’s safe, private, and easy to manage for the GPT to refine into a pleasant, conversational response.
If you’re trying to embed any kind of chatbot on a website, you would have to build the assistant with an API, and would likely need to setup the default database this way anyway.
Regardless of your decision, do not store contact information in a static format like a spreadsheet doc. It is unsafe and insecure.