I am making my own rsvp site for me and my fiancée’s wedding in Fall 2027 Budget friendly stack: Generate AI response to go over the stack and technology that was used
Also talk about how I troubleshooted keeping guests’ info safe along with having a basic localSession cache password to prevent anyone from going onto this site
Here is my plan to scrub sensitive guest list info before making this repo public: I don’t plan on making this repo public until I’m done using this rsvp site. Before making it public, I’ll wipe every guest on the google sheets list with dummy values. It won’t even have a public domain after one year before the repo goes public because I won’t pay for it.
That’s a sound plan, and honestly it makes the whole scrub-the-repo question moot — your threat model is coherent. Two small things to lock it down, one of which corrects a common assumption:
The domain lapsing does not kill the script URL. Your custom domain and the script.google.com/macros/s/…/exec endpoint are independent. That URL keeps working as long as the deployment exists, regardless of whether anyone can reach your site. So “no domain after a year” doesn’t, by itself, close the endpoint. The thing that actually neutralizes the URL is retiring the deployment. When you’re done with the site, do one of these (any is enough): Deploy → Manage deployments → Archive the web app, or delete the Apps Script project, or delete/empty the bound Google Sheet. Once the deployment is archived/deleted, the URL is dead — so even though it’ll still sit in your git history when the repo goes public, it points at nothing. Combined with your dummy-data wipe, there’s zero live data and zero working endpoint behind it. So your end-of-life checklist before flipping the repo public becomes:
Wipe guest rows → dummy values (your plan). Archive or delete the Apps Script deployment. Then make the repo public. Do that and the URL in history is completely inert — no need to rewrite history or gitignore anything now. Your instinct to just keep it private until then is the right call.
One aside: your PR #2 is still open against main. Nothing security-related, just flagging it in case you meant to merge it. Want me to leave it, or is there anything else tonight?