01
Separate public pages and customer workspaces
Public marketing content can be accessed and cached normally. Customer workspaces, administration pages, and related interfaces require appropriate access and are not public search content.
Security and trust
Security starts with clear data and access boundaries
Searchore separates the public website from authenticated workspaces and treats credentials, permissions, and public-data scope as product and operational boundaries. Enterprise requirements can be reviewed before engagement.
02
Keep credentials out of content and support messages
API keys, passwords, cookies, authorization headers, and other secrets should not appear on public pages, in examples, log summaries, or ordinary support email.
- Do not email production credentials
- Rotate a secret promptly after exposure
- Give necessary access only to authorized people
03
Report a security concern
Send reproducible steps and expected impact to service@searchore.com. Do not include unrelated personal data in a security report.
Searchore
Security starts with clear data and access boundaries
Searchore separates the public website from authenticated workspaces and treats credentials, permissions, and public-data scope as product and operational boundaries. Enterprise requirements can be reviewed before engagement.