Privacy Policy for NotGoogle!

1. Introduction

cl0q (“we,” “us,” or “our”) operates the website notgoogle.com (“Service”), an open-source search engine. Your privacy is paramount; this policy explains what information we collect, how we use it, and your rights.

2. Information We Collect

• Search Queries – We temporarily process your search terms to generate results.
• Server Logs – We record anonymous connection data: IP address, timestamp, URL requested, user agent, referrer.
• Cookies – A minimal, session-only cookie may be used to improve performance; no tracking across sites.

We do not collect or store any personally identifiable information (PII) such as names, email addresses, or precise geolocation.

3. How We Use Information

• Deliver Service – Process your queries and return results.
• Performance & Security – Analyze logs for uptime, abuse prevention, and debugging.
• No Profiling – We do not build user profiles or serve personalized ads.

4. Cookies & Local Storage

We use in-memory or session cookies only to maintain search sessions. You can disable cookies in your browser; the search engine will still function.

5. Third-Party Services

• Proxy to Go Backend – Your queries are forwarded to our Go server on the same host; no third-party analytics.

6. Data Retention

• Search Queries – Stored only transiently in memory; not written to disk.
• Server Logs – Retained for up to 30 days, then automatically rotated/purged.

7. Security

• HTTPS with HSTS enforces encrypted connections.
• We regularly apply security updates to both OS and application.
• No user-submitted data is ever stored in a database in PII form.

8. Children’s Privacy

Our Service is not directed to children under 13. We do not knowingly collect any information from children.

9. Changes to This Policy

We may update this policy from time to time. If we make material changes, we’ll post the new date above and highlight significant updates on our homepage.

10. Contact Us

For questions or requests regarding your data, please reach out to @chrisknowshtml on X

or