Privacy and browser notifications

Your account and organization

Wiunix ID signs you in. Aegis checks your current organization access before showing security records or accepting actions. Browser notifications do not grant access to another organization.

You choose whether to receive browser notifications

Notifications depend on your deployment and browser. When available, Aegis asks for browser permission only after you choose Enable in notification settings. Installing Aegis does not enable notifications or expand your access.

What is shared for delivery

Pulse handles delivery using a random installation ID, a recipient reference that contains no name or email, and the push subscription supplied by your browser. The browser's push service also participates in delivery. Provider credentials stay on the backend.

Notification previews are generic. They contain no incident title, organization name or private security details. Opening a notification takes you to Aegis, where sign-in and current access are checked again.

Turning notifications off or changing accounts

Turning notifications off removes consent in Aegis. Server routing cleanup and browser unsubscribe may finish at different times. A pending or unconfirmed result means cleanup is not yet confirmed; previously queued notifications may still appear.

After changing account or explicitly selecting another organization, enabling notifications requires a new registration. The old registration is not transferred. Check the current account and notification settings if cleanup remains unconfirmed.

Inbox, delivery and history

The inbox and its read markers belong to your account and organization. Delivery to a queue, acceptance by a provider, display on a device and marking an item as read are different states.

Disabling browser notifications does not delete security records or inbox read history. Aegis also keeps internal delivery and cleanup history for troubleshooting. Ask your organization administrator about access to security records and their retention.

Data kept in your browser

Aegis uses a sign-in cookie and a language preference. Offline storage contains only public application assets and a public offline page; authenticated pages, security records, notifications and credentials are not placed in that public cache.

You can change notification permission in your browser or operating-system settings. Browser permission, Aegis consent and confirmed routing cleanup remain separate controls.