Privacy Protocol

To maintain a synchronized operational overview, Watchtower synchronizes multiple streams of data: • Account Data: Secure encryption of identity markers, credentials, and authorization levels. • Entity Architecture: Structural data regarding organizational hierarchies, competitor profiles, and strategic goals. • Operational Data: Real-time media coverage, social signal feeds, and internal documents provided via secure upload or third-party integration. • Metadata: Technical telemetry required for system optimization, security auditing, and forensic log maintenance.

Data in Watchtower is processed to produce strategic analysis: sentiment scoring, narrative clustering, transcription of broadcast media, and alignment scoring against your stated goals. This processing uses third-party AI models, not our own. Text, documents and article content are sent to Google (Gemini) and OpenAI. Audio captured from broadcast monitoring is sent to Google, Groq or ElevenLabs to be transcribed. Text is converted to embeddings and stored with Pinecone so the assistant can recall it later. These providers process content on our instructions, under API terms that exclude it from training their models. Watchtower's assistant produces recommendations, drafts and analysis. It can be wrong. Nothing it generates is a substitute for your own editorial, legal or professional judgement. We maintain data isolation: your organisation's data is not visible to other entities on the Watchtower network, and it is not used to train any model. Permanent storage is reserved for historical analysis and trend forecasting.

Watchtower employs a high-intensity security framework to protect against unauthorized data exposure: • Encryption: All data is secured using AES-256 at rest and TLS 1.3 in transit. • Access Control: Role-based access control (RBAC) ensures that intelligence is only visible to personnel with the requisite clearance level. • Siloing: Every entity operates within a distinct, logically isolated data silo to prevent cross-contamination of sensitive information.

Our integration with Google Drive and Google Calendar follows the 'Limited Use' requirements. Data Accessed: Watchtower only accesses specific Google Drive documents (e.g., messaging guides, strategy briefs) and Google Calendar events (e.g., media appearances, internal meetings) that are explicitly authorized or uploaded by the user. Data Usage: This data is used solely for the purpose of strategic analysis, allowing our system to compare external media coverage with your internal messaging goals and to synchronize operational tasks. We do not store third-party credentials and utilize secure OAuth protocols for all external channel handshakes. Your Google data is never used for AI model training or shared with any third parties.

Watchtower is built on third-party infrastructure, and running the service means your data passes through it. The providers who may process it on our behalf fall into these categories: • Cloud hosting and storage — running the application and background workers, and holding the database, job queues and media (broadcast clips, transcripts, images). • AI model providers — analysis, drafting, speech-to-text for broadcast audio, and the memory that lets the assistant recall your earlier material. • Collection services — web search, page retrieval and collection of public posts from the platforms you ask us to monitor. • Sign-in providers — Google or Microsoft, depending on how your organisation signs in, and (only if you connect them) Google Drive and Calendar. • Email and error reporting — transactional and alert email, and error reports that may incidentally include the URL and account identifier attached to a failure. We do not sell your data and we do not share it with anyone for their own purposes. Customers can request the current list of named sub-processors at privacy@watchtwr.com.

Account and configuration data is kept for as long as your account is open. Collected coverage — articles, social posts, broadcast transcripts and the analysis derived from them — is kept for as long as your account is open, because its value is the historical trend. You can delete individual items at any time. Live broadcast recording is a rolling buffer with a fixed size cap. It is continuously overwritten within hours; only the segments you or your monitors clip are kept. Operational logs (job runs, errors, audit entries) are pruned on a rolling schedule. On request, we will delete your account and its data within 30 days, other than what we must keep for legal or accounting reasons. Closing an account triggers the same deletion. Backups age out on their own cycle, so a copy may persist in backup for a short period after deletion from the live system.

Watchtower sets only what it needs to work. There are no advertising cookies, no analytics cookies and no third-party trackers. • Session cookies keep you signed in and protect forms against cross-site request forgery. Removing them signs you out. • A language cookie (ENTITY_LOCALE) remembers the language of the entity you are working in. • Local storage in your browser holds interface preferences, such as which panels you left open. Because none of these are used for advertising or tracking, we do not show a consent banner. If you block them, sign-in will not work.

You can ask us for a copy of the personal data we hold about you, ask us to correct it, ask us to delete it, or object to how we are processing it. Where the GDPR or Israel's Privacy Protection Law applies, these are your rights under it and we will answer within the time those laws require. Where your organisation is our customer, it is the controller of the material it collects through Watchtower and we are its processor; we will pass a request on to them where that is the right route. Watchtower monitors public media. Journalists, officials and public figures who appear in that coverage can contact us about the material we hold on them at the address below. Contact: privacy@watchtwr.com