Privacy Policy
This policy explains how the Vessalion Agent Pipeline custom UI handles user, workflow, record, outreach, and operational data.
Last updated: 2026
1. Information We Collect
The platform may store user profile details, login records, source configurations, scraper run logs, staged records, review decisions, approved records, outreach contacts, campaign activity, support tickets, export history, and system audit events.
2. How Information Is Used
Information is used to operate the custom UI, manage Agent 1 ingestion workflows, support Agent 2 outreach workflows, review and approve records, track system activity, manage support requests, and provide export functionality.
3. Public-Source Records
Public-source records captured by the platform are stored in staging before qualification and review. Records may include source URLs, evidence snippets, matched keywords, country, region, company references, contact availability, and operational metadata.
4. Account and Security Data
The platform may store hashed passwords, login sessions, verification tokens, reset tokens, role information, login audit logs, IP address, browser user agent, and security-related activity events to protect access and maintain accountability.
5. Outreach and Communication Data
The platform may store outreach contacts, email templates, campaign records, sent email metadata, replies, qualification questions, answers, and qualified opportunity information for operational tracking.
6. Geospatial Data
The platform may store geospatial zones, coordinates, boundary metadata, map layer configuration, satellite observation references, anomaly scores, confidence scores, and review status. Heavy satellite imagery or raster storage is not part of the core MVP database.
7. Data Sharing
The custom UI is treated as the primary internal operating system. Data is not automatically pushed to external systems unless a future integration or export workflow is explicitly configured and approved.
8. Data Retention
Operational records, logs, support tickets, exports, and review history may be retained as needed for traceability, debugging, reporting, and system accountability. Deleted or archived records may remain in logs where required for audit purposes.
9. Support Requests
When users submit a support request, the submitted name, email, issue type, subject, message, and attachments may be stored and emailed to the configured support address for resolution.