Who operates Vigie Watch
Vigie Watch is an individually operated notification service based in Brazil. Privacy questions and data-subject requests may be sent to support@vigiewatch.com.
Data we process
- Account email, optional profile name and image, verification status, preferences, and Terms acceptance.
- Password hashes for email/password accounts. Vigie Watch does not store readable passwords.
- OAuth provider identifiers, verified email, profile data, and encrypted provider tokens when OAuth is used.
- Seven-day browser sessions, including timestamps, IP address, and user-agent information.
- Paired-device, integration, notification, delivery, security, rate-limit, and operational records.
Why we use it
We process this data to create and secure accounts, link identities with the same verified email, deliver and synchronize notifications, manage integrations and devices, prevent abuse, diagnose failures, communicate verification or recovery actions, and comply with applicable law.
Optional product analytics
If you allow analytics, the web and iOS apps collect information about page and screen visits, feature and control interactions, onboarding steps, notification actions, permission choices, network request outcomes and timing, and diagnostic categories. The web also measures form interaction without field values, scroll depth, repeated clicks, and page performance. This helps us understand journeys, find confusing or unreliable features, and improve the user experience.
Events use a random browser or installation analytics identifier and session identifiers. These can connect activity over time on that browser or installation, so we describe the data as pseudonymous rather than fully anonymous. We do not link analytics identifiers to account names, emails, account IDs, or analytics identifiers on your other devices. Technical context may include browser or operating system version, app version, device model or category, and screen dimensions.
We exclude notification titles, bodies, images, sender and device names, notification and account IDs, search text, input values, clipboard contents, passwords, API keys, pairing codes, authentication and push tokens, full URLs, URL query strings, and raw error messages. Session replay, screenshots, keystroke recording, and advertising identifiers are disabled. We disable IP-based geolocation and remove IP event properties; analytics and infrastructure providers may receive a network IP address when accepting a connection and may process it for security and delivery.
Your analytics choice
Analytics is off until you allow it. You can decline without losing features and withdraw at any time through Privacy choices on the web or Share usage analytics in iOS Settings. The web also respects Global Privacy Control and Do Not Track. Each browser and installation has its own choice. Consent preferences and, after permission, random analytics identifiers are stored locally. Withdrawal stops future collection and clears the local analytics identity; a request already in transit may finish. It does not automatically erase events already received.
We do not sell analytics data, use it for advertising, track you across other companies’ apps or websites, or attempt to identify you from it. To request deletion of analytics already received, contact the privacy address above with the relevant browser or installation details. Because we keep analytics separate from account identity, deleting your account does not automatically identify historical analytics records.
Service providers
Infrastructure providers support hosting, databases, queues, network security, abuse protection, email delivery, and optional product analytics. OAuth providers process sign-in requests you initiate. Mobile platform services deliver notifications to paired devices. We require providers processing data on our behalf to protect it under applicable data-processing agreements and privacy requirements.
Retention and deletion
Notification retention follows your account setting. Analytics is retained only as reasonably needed to evaluate product use and reliability under our configured retention controls, or until a valid deletion request is completed. The local analytics identifier lasts until you withdraw permission, reset local storage, or an identity reset occurs. Security and operational records are kept only as reasonably needed to operate and protect the service or meet legal obligations. Browser sessions expire after seven days and may refresh after activity. Password-recovery and verification records expire. Confirmed account deletion removes account-owned data from active systems, subject to limited legal or security retention.
Security and international processing
Vigie Watch uses password hashing, encrypted OAuth tokens and device tokens, revocable credentials, restricted secrets, rate limits, and managed human-verification checks. Providers may process data outside Brazil using legally available safeguards. No system can guarantee absolute security.
Your rights
Subject to Brazil’s Lei Geral de Proteção de Dados (LGPD), you may request confirmation of processing, access, correction, portability where applicable, information about sharing, review of consent choices, or deletion and anonymization where legally available. You may also complain to Brazil’s data-protection authority.