Privacy Policy
How the project handles data across the public website and application features.
Privacy position
AI Phishing Detector is presented as a security-focused project. The public site exists to explain the platform, and the application features operate with privacy expectations centered around practical phishing analysis rather than advertising or profiling.
Features this policy relates to
This policy covers the public website, Scan URL, Batch Checker, Email Analyzer, Scam Detector, Risk Heatmap, Zero-Day Detection, Campaign Clustering, Visual Detect, Auto Report, Breach Check, Hook assistant workflows, Browser Extension pages (Coming Soon), Simulate Attack and Learning, dashboard pages, and supporting public documentation pages.
Data categories
- URLs and suspicious content submitted for analysis
- Account information needed for authenticated areas
- Operational scan statistics used for dashboard and activity views
- Temporary technical controls such as rate limiting and session handling
Feature-specific privacy notes
- Scan URL and Batch Checker exist to process suspicious links for analysis and investigation.
- Email Analyzer and Scam Detector exist to inspect suspicious message content and supporting metadata.
- Risk Heatmap, Zero-Day Detection, Campaign Clustering, and Visual Detect exist to explain and deepen analysis rather than collect unrelated user data.
- Auto Report exists to assist with manual reporting after human confirmation.
- Breach Check is documented as using privacy-preserving checking logic.
- Hook exists to provide guided assistance, inline checks, and proactive page-risk prompts inside the application experience.
- The public website pages themselves are informational and act as the first access point to the project.
Cookies and sessions
Functional session behavior and request protection are part of the application. The public website is designed as a project front door, not an ad-tracking surface.
Third-party services
Some features integrate with external systems where necessary for authentication or AI-assisted workflows. Those providers operate under their own policies, and their role is limited to supporting platform functionality.
User expectations
Users should avoid submitting data unrelated to phishing analysis and should use only the workflows necessary for the security task at hand.
Contact
Questions about privacy can be sent through Contact.