Security Posture

Adsideo is built for sensitive desktop work. Our goal is to minimize data movement, keep user context local-first, and make each suggestion traceable to evidence.

Current Controls

• Local-first handling for sensitive Mac context where product architecture allows.
• Password-protected pre-launch site access.
• Subscription and account access designed to be tied to user IDs.
• Limited vendor access for hosting, analytics, email, payment, and support operations.
• Product copy and policies that avoid promising invisible or unlimited data use.

AI Transparency

Adsideo should show why a suggestion appeared whenever possible, including the source context or signal behind it. Users should be able to ignore, dismiss, or turn off sensitive capture features.

Compliance Roadmap

• Finalize legal entity, governing law, and subprocessors before paid launch.
• Create a complete data retention and deletion process.
• Document model, telemetry, and cloud-processing boundaries.
• Review California, US, and international privacy obligations before broad launch.
• Add a formal security contact and vulnerability disclosure process.

Report A Security Issue

Email founders@adsideo.ai with the subject "Security report". Please avoid sharing sensitive customer data in the initial report.