Effective October 12, 2026 · Operated as IPAlive
Information we collect
- Account information: email address, account identifier, password hash, email verification status, account plan and preferences. If Google sign-in is enabled and you choose it, we also receive the verified email and Google account identifier needed to sign you in.
- Host information: selected hostname and domain, current IPv4/IPv6 addresses, check-in timestamps and IP-change records.
- Updater information: reported software version, platform, update progress and safe failure categories. Check-ins indicate updater activity; they do not measure device uptime or inspect files on your device.
- Notifications: alert preferences, webhook configuration, event payloads, delivery attempts and outcomes. Webhook endpoints and signing keys are stored encrypted. Session and hostname credentials are verified against stored hashes. Browser-approved device setup temporarily holds an encrypted hostname credential until it is claimed or expires.
- Security and support information: request/network metadata used for access controls and rate limits, administrative activity records, and messages or diagnostic details you send to support.
Why we use this information
We use it to authenticate accounts, maintain DNS records, associate hosts with their owners, deliver requested alerts and webhooks, manage updater releases, enforce account limits, investigate errors and prevent abuse. Administrators can access account and host information needed to operate and support the service.
Public DNS and your network
Your dashboard is private, but DNS is public. Anyone who knows or discovers a hostname can look up its published IP address. DNS resolvers and other third parties may cache or retain those records. Changing or removing a record does not erase third-party copies.
IPAlive receives the public address used by an updater request or an address explicitly supplied by the updater. A VPN, proxy or network gateway can change the address observed by the service. IPAlive does not provide a VPN, tunnel or firewall.
Cookies and browser storage
We use a secure session cookie for sign-in, normally lasting up to 24 hours, and temporary security cookies when applicable. The PWA caches public offline resources; its service worker does not cache API responses or authenticated account pages. The current application has no advertising or behavioral analytics integration. Cloudflare may process additional browser and network information to provide security and bot protection.
Providers and information sharing
- Cloudflare hosts the website and backend, stores service data and DNS records, provides Turnstile bot protection, and forwards support email. See Cloudflare’s privacy policy and Turnstile privacy notice.
- Resend handles outgoing account and service emails, including recipient addresses and message contents. See Resend’s privacy policy.
- Your chosen webhook endpoint receives subscribed events, which may contain hostnames, IP addresses and check-in times. Its operator controls what happens to that data after delivery.
- Google processes incoming support messages in our Gmail inbox and, if enabled and selected, provides Google sign-in. Support mail is stored outside IPAlive’s application database. See Google’s privacy policy.
We do not sell account information. We may disclose information where necessary to comply with lawful requests, investigate abuse or protect the service and its users. Providers may process information in countries other than your own.
Support replies
Authorized administrators can send support and PR replies through Resend. IPAlive keeps reply metadata (sender, recipient, subject, sending status and provider delivery events) for approximately 30 days. Reply bodies are processed to send the message and are not saved in IPAlive’s application database. Email providers may retain message contents under their own policies.
How long information remains
Account details, current host records and saved configuration remain while needed to operate your account. We do not automatically delete a host or its DNS records merely because its updater stops checking in.
- IP-change history is kept for approximately 90 days; dashboard access to this history is a Premium feature.
- Notification delivery and service activity records are generally kept for approximately 30 days.
- Verification and reset links expire; expired sessions, security counters and temporary records are cleaned up through service maintenance.
Cleanup runs periodically, so records may remain briefly beyond these periods. Provider logs, cached public DNS, support correspondence and backups can have separate retention periods. Security or legal needs may require retaining relevant records longer.
Your choices and requests
You can change notification settings, disable webhooks and rotate hostname credentials in your dashboard. Removing an updater from a device does not close the account or remove its published DNS records.
For account closure, access, correction, deletion or other privacy requests, email support@ipalive.link from your account address where possible. We may verify account ownership before acting. We handle requests according to applicable law and explain any information we must retain. You may also have the right to complain to your local privacy authority.
Policy changes and contact
We will update the effective date when this policy changes and communicate material changes through the site or account email where appropriate. Privacy questions go to support@ipalive.link.