Security & Privacy
SiteSpry is designed as a public-facing knowledge sharing platform. Understanding how content is published and accessed is essential for protecting sensitive information.
Public Content Warning
When you upload a file to SiteSpry, you are publishing it to the internet. Every uploaded file gets a unique shareable URL, becomes publicly accessible to anyone with the link, may be indexed by search engines, and cannot be guaranteed to remain private even after deletion.
What NOT to upload
Never upload files containing:
❌ Credentials and secrets
Passwords, API keys, tokens, database connections, SSH keys, OAuth secrets
❌ Personal Identifiable Information (PII)
Social security numbers, passport numbers, medical records, financial accounts, credit cards
❌ Confidential business data
Customer exports, HR files, private contracts, NDAs, proprietary code, unpublished financials
❌ Legally restricted content
GDPR/HIPAA protected data, copyrighted material, confidentiality agreements
Safe content guidelines
Before uploading, ask yourself:
If you answered "no" or "unsure": Redact sensitive sections, remove metadata, or use a different platform for sensitive information.
File metadata and hidden content
Documents often contain hidden information:
- •Word/Excel/PowerPoint: Author names, revision history, comments, tracked changes
- •PDFs: Author metadata, creation software, edit history
- •Images: GPS coordinates, camera info, timestamps
How to clean files before upload:
- •Use "Remove personal information" features in document software
- •Export to clean PDF without metadata
- •Review "Properties" or "Document Info" before uploading
Best practices summary
1. Treat SiteSpry as a public website
Assume anything uploaded can be seen by anyone
2. Never upload confidential information
Use appropriate secure platforms instead
3. Review all content before publishing
Including AI-generated FAQs and articles
4. Clean file metadata
Remove author info, comments, and tracked changes
5. Monitor chatbot conversations
Check chat history regularly for sensitive data exposure
6. Educate your team
Ensure everyone understands these guidelines