Privacy policy

Last updated: 13 September 2026

Mario Anghel operates marioanghel.dev, its private dashboard, notification API and companion Android app. For privacy questions or requests, use the website contact form.

Information we handle

The contact form sends your name, email, company, subject and message to Mario Anghel. Hosting services may process technical request information such as IP addresses, browser details and access logs to operate and secure the website.

Google sign-in verifies your email and whether you are allowed to access the private dashboard. We store your email and session information. The application requests only identity and email access, not Gmail, Google Drive or your Google password.

The notification service stores API key names, credential hashes, expiry dates, paired-device information, push registration tokens or browser subscriptions, notification content, timestamps, delivery status and read status. Android stores its pairing credential and cached key expiry information locally. Local expiry reminders do not become entries in the API inbox.

Why we use this information

We use information to answer enquiries, authenticate approved users, deliver requested notifications, maintain notification history and protect the service. Where applicable, processing is based on steps requested before entering a contract, our legitimate interests in operating and securing the service, and consent for optional notifications. You can disable notifications in your device or browser settings.

Cookies and local storage

The dashboard uses essential cookies for sign-in security, sessions and browser registration. Browser storage remembers whether the notification prompt was shown. Signing out revokes the dashboard session and that browser registration. Browser settings let you clear cookies and site data.

Service providers

Microsoft Azure hosts the service, Turso stores application data, Brevo delivers contact-form email, Google handles sign-in and Firebase Cloud Messaging delivers Android notifications. Browser notifications use the browser vendor’s push service. These providers process the information needed for their respective functions and may process it outside your country. See Firebase privacy information and Google’s privacy policy.

Notification contents pass through our backend and relevant delivery providers. Avoid including passwords or other sensitive secrets in notification bodies; notifications may also appear on a device’s lock screen.

Retention and your choices

Dashboard sessions expire after 30 days and unused pairing codes expire after ten minutes. Expiry prevents further use; it does not necessarily erase stored records immediately. Notification history and key records currently have no automatic deletion schedule and remain until removed by the operator. Contact correspondence is kept while needed to handle the enquiry and related records. Infrastructure logs and provider records follow their respective service settings.

You can request access, correction or deletion of your personal information through the contact form. Where applicable, you may also request restriction or portability, object to processing, withdraw consent, or complain to your data protection authority. See the European Commission’s information on your rights. Requests may require identity verification.

Changes

This page will be updated when the service’s handling of information changes. The date above identifies the latest revision.