Hacker News new | ask | show | jobs
by axotopia 86 days ago
Checking right now. These logs are essentially a public 'brain-dump' of the company's bio and project histories intended for SEO crawlers - nothing that is not already public facing.

that said, I hear the concern. I am going to review and tighten access just to be safe. Appreciate the heads-upp on how it looks from the outside.
1 comments
unsnap_biceps 86 days ago
at the bottom of your list, you have a number of bio links that I presume are you and your employees, but it's not clear that they are intended to be public from first glance.
link
axotopia 86 days ago
Good catch. Those bios and lists are essentially grounding truth for the training data for the RAG. Intent is twofold: Give bot truth anchors to stay focused and manage hallucination. Brain-dump for SEO crawlers to index our expertise. Removing the fluff from our site didn't agree with the 1999 SEO tech. I'm going to tighten the access and formatting so it doesn't look like an accidental exposure to a casual observer. Appreciate the sharp eye!
link
pavel_lishin 85 days ago
I have no idea what any of that means. How does exposing what looks like PII help you with SEO?
link
axotopia 85 days ago
Good point. To clarify, it wasn't sensitive PII (no private contacts, addresses, etc.). It was just our public team bios and professional resumes.

Because we deleted our traditional 'About Us' page, Google's webcrawler are unable to interact with our AI bot. It's a problem of visibility on Google Search, the logs are our workaround if that makes sense. I left that text exposed in the backend so standard search engines (like Google) could still index who we are and what our qualifications are.

But you are 100% right that seeing it raw in the logs looks sketchy to a user. Thanks for keeping me honest here.

link
pavel_lishin 85 days ago
I guess if Tina is fine having her email address & phone number publicly available, that's her business. :shrug:.
link
axotopia 85 days ago
You caught me. Tina is my co-founder, so those are her business contacts, but you're absolutely right, still a dumb move to leave them exposed instead of routing everything through single secure point of contact. I completely missed them when I dumped our raw resumes into the RAG context.

My oversight for blindly claiming the logs were totally clean. I just updated the backend and permanently scrubbed the contacts.

Genuinely appreciate you pushing back and catching my blind spot!

link