So what you’re basically saying is to add a secret key to the shared link itself, so the user doesn’t have to do anything extra, but their privacy is protected behind the scenes. I looked into it and just added a 6-character access key for every Zync(shared link), plus basic rate limiting to stop mass scraping. It’s invisible to users but blocks most common abuse. Will keep improving it based on all your feedback appreciate it a lot!

Thanks for your detailed feedback! the current logic (auto-expiry after first view or a max of 2 days) is meant for simplicity and privacy. I posted an MVP to understand if this is worth it to continue building but seeing all the comments here it seems the major issue next is security. As the others mentioned I was planning to do either a simple CAPTCHA or optional PIN protection — whichever feels smoother for users. Appreciate you taking the time to explain the risk — that really helps me plan the next steps better!

Thanks for the insight! This is just a MVP that I buit and posted online for reviews to know if this is worth expanding more. As the other commenters have said I was planning to do either a simple CAPTCHA or optional PIN protection — whichever feels smoother for users. Zync was meant to be a frictionless sharing tool, but I definitely want to strike the right balance between ease of use and basic protection.