Privacy & cookies
What we collect, why we need it, and how you can control it.
Updated
Download these policiesWithdraw from contract
Who handles your information
The controller is the service provider named under Provider and contact details at the end of the Service terms. Contact support@vpsmon.cloud for support, privacy requests, or security reports.
Cloud is offered for personal, non-professional monitoring. The operator acts as controller for account, billing administration, support, security and the personal monitoring service it provides. Privacy roles depend on the actual processing, not an account label: personal-use registration does not exempt Cloud from the GDPR. Processing on behalf of an employer, business, organization or client is outside this launch scope; contact us before any use that would require a controller–processor agreement. Avoid personal or sensitive information in server, process and container names and optional snapshots. We assess accidental or out-of-scope disclosures individually rather than treating your declaration as consent for other people.
Account and email information
Cloud stores your email address, password hash (not your readable password), account and workspace identifiers, verification status, and expiring security tokens. Session tokens are stored as hashes. We also keep alert settings, recipient verification, notification content and delivery status, and support correspondence you send us.
If you enable webhook alerts, Cloud stores the receiver URL, format, signing secret, incident payloads, and delivery status. Incident starts and recoveries send server identifiers, hostname, the affected resource, value, threshold, and time to the endpoint you choose. Webhooks do not send live processes or incident snapshots. You can pause webhook delivery independently of email alerts.
Your verified signup email is the default incident and recovery recipient. You can disable email alerts or verify a different destination in Alert settings. Verification, password-reset, billing and legal messages go to your account email. Reminder emails go there too: a notice before your trial ends, and one reminder about three days after signup if you have not connected a server yet. Each reminder includes an unsubscribe link, and you can turn reminders off in Account. Turning them off does not stop server alerts or account, billing and legal messages.
We record your explicit Service terms agreement, its version and document fingerprint, time, action and declared personal use. Older agreement records may contain a declared business purpose and business name; those historical records are not rewritten. Invitations store the invited email, access duration, operator note, creation/expiry times and delivery state until expiry or acceptance/revocation removes the invitation. If you submit an online withdrawal, we receive your name, contact email, contract identification, statement and submission time and record how it is handled. These records support contract administration, responding to requests and establishing or defending legal claims; they are not marketing consent.
Connected-server information
The separate vpsagent sends telemetry over outbound HTTPS only after you install and pair it. The local vpsmon dashboard does not upload to Cloud. Samples include hostname, uptime, load, CPU, memory and swap use, network counters, process count, and writable disk names, device labels, and capacity. We use these for your dashboard, history, and incident detection.
Opening server details requests the top five process names and CPU/memory percentages while you view them. Live processes stay in bounded Cloud memory only, outside the database, history, application logs, and database backups. Closing the dialog stops requests; hidden tabs stop renewing them. Requests and samples expire after 30 seconds without renewal and are cleared by the next cleanup sweep, within another 15 seconds. They do not include command arguments, environment variables, logs, or listening sockets.
Saved process and container details are a separate incident snapshot, off by default. You can turn them on with Include top processes in alerts in Alert settings, or by enabling snapshots on your agent. When a CPU, memory or disk reading first reaches your alert threshold, the agent can then send the top five process names with their CPU and memory use. Processes with the same name are combined and counted. Snapshots enabled on the agent can also send Docker container ID, name, image, state, health, uptime, restart count, port mappings, CPU, and memory. Snapshots omit process IDs, command lines, environment variables, logs, and listening sockets. These labels may reveal what you run. Turning the setting off stops new captures from agents that follow it; saved snapshots stay with their incidents until deletion.
Agent management stores installed version, operating system and architecture, remote-update availability, last contact, and update requests with the requesting account email, target version, timestamps, and progress. Updates require local opt-in and an authenticated request from your Cloud account.
Why we use this information
We use account details and the telemetry needed to provide the personal monitoring features you request to perform our agreement with you (GDPR Article 6(1)(b)). Our legitimate interests (Article 6(1)(f)) in keeping Cloud secure and reliable support abuse prevention, proportionate diagnostics and handling support requests. We send reminder emails based on our legitimate interest in helping you use the service you signed up for; you can object at any time by unsubscribing or turning reminders off. We count anonymous visits to our home, demo and sign-up pages based on our legitimate interest in understanding which pages and campaigns lead people to sign up (Article 6(1)(f)); see Cookies and browser storage. Where a legal obligation applies, Article 6(1)(c) supports the necessary processing. Historical business-contact administration is based on the legitimate interest in administering that relationship. We assess actual roles before any processing on another controller’s instructions. Optional incident snapshots are off by default; enabling them is a collection setting, not consent on behalf of other people. Stop future snapshots by disabling them on your agent or disconnecting it.
Hosting and network providers process IP addresses and technical requests to deliver and protect the site. The system journal is configured for up to 14 days, subject to its size limit; a separate syslog copy rotates weekly and retains four archives, so diagnostic records can remain for about five weeks. Logs can appear in recovery copies under the rules below. Email-abuse quotas use keyed, pseudonymous identifiers rather than readable recipient or IP values; these are not anonymous. We do not sell personal information, serve targeted advertising, or make decisions with legal or similarly significant effects solely by automated profiling.
Our legitimate interest in establishing, exercising or defending legal claims supports limited agreement-evidence retention after account deletion where the accepted policy provides for it. We keep only the identifying and agreement information described below, restrict its use to those purposes and privacy-request handling, and assess objections or requests for earlier erasure individually. Accepting service terms does not provide consent to unrelated processing.
Hosting, integrations, and international transfers
The Cloud application and its main SQLite database run on a Hostinger VPS in Vilnius, Lithuania. Hosting administration and provider services have their own processing arrangements; this does not mean every provider system is located in Lithuania.
Resend delivers account and alert emails. It receives recipients and message content, which can include server names, resource values, and incident details. When incident snapshots are on, CPU and memory alert emails can also include up to five captured process names with their CPU or memory share. Resend stores data in the United States even when an EU sending region is selected. Its data-processing agreement includes Standard Contractual Clauses for international transfers. Resend documents 30-day email/log retention on its standard plans; its own backups and account records follow its published retention terms.
The support@vpsmon.cloud inbox receives support, privacy and complaint correspondence through Hostinger mail infrastructure; its content is handled separately from the application database. Its hosting, recovery and administration are subject to the applicable mail-provider arrangements. Contact us for the applicable safeguards. We do not assume that all mail processing is in Lithuania.
Webhook receivers, including Slack when selected, process the incident information you choose to send under their own terms, privacy notices, and retention policies. Their data locations depend on the receiver and your settings. Configure only an endpoint you control or are authorized to use.
For subscription purchases through Stripe Managed Payments, Stripe/Link processes the payment and customer information needed to sell the subscription, handle receipts, taxes, and payment support. Link, as merchant of record, handles that information as a separate controller under its own privacy policy, and Link and Stripe may process it in the United States and other countries. Cloud retains customer/subscription identifiers, status, and billing-period records, not full card numbers.
Agent release checks and downloads use GitHub and signature-verification services, which receive technical network requests from Cloud or your agent. Information may also be disclosed when legally required or necessary to investigate a security incident. Contact us for information about the safeguards applicable to your data.
How long information stays
Terms agreement records and their confirmation emails remain while your account exists. When a verified account is deleted, we retain only agreement records made under the 23 October 2026 policy or a later policy that provides for this retention. The limited record contains your account email, account/workspace identifiers, policy version and fingerprint, UTC agreement time, acceptance action, declared purchase purpose/business name, and any associated checkout-session reference and link time. It records agreement and a checkout request, not proof of payment. It is kept for three calendar years after deletion, then removed by scheduled cleanup. Receipt-email bodies and delivery jobs are deleted with the account. Agreements under earlier policies without this provision are also deleted with the account, even if you later agree to a newer policy. We do not add IP addresses, device fingerprints, credentials, or telemetry to this record. A specific legal obligation or dispute may require separate, restricted preservation with a documented purpose and review date. Backup copies follow the recovery-copy rules below.
Ordinary support correspondence is reviewed for removal 12 months after the issue closes. Privacy-rights and complaint handling evidence is reviewed for removal three years after closure. Keep only information necessary for the request or a specific legal obligation or dispute; an identified need for longer restricted retention is documented and reviewed. These support records are handled separately from automatic app cleanup.
- Raw metric samples: about four hours. Five-minute history: one day. Hourly history: 30 days. Rollup boundaries and periodic cleanup can slightly extend these windows.
- Resolved incidents, their snapshots, and associated alert delivery records: normally 90 days after resolution. An anchor incident required to group an ongoing or more recently resolved activity episode remains until that episode no longer needs it and its retention period expires. Dormant episode references are removed by cleanup. Active incidents remain until resolved or the server/account is deleted.
- Account details, server registrations and last-known summary values, settings, reminder-email preference, and reminder records: until account or server deletion as applicable. Update records are limited to the latest 20 requests per server.
- Unverified abandoned accounts: 30 days. Sessions expire within seven days, or sooner for short sessions. Expired security tokens and inactive abuse-limit records are removed during scheduled cleanup.
- Scheduled encrypted database backups: one snapshot every hour. The service and its off-host collector each retain their latest successful copy; an older copy is removed after its replacement succeeds. Failed replacements preserve the last recovery copy until a new one is available. Deployment recovery keeps the latest two pre-upgrade snapshots and the binaries needed to restore them. Material from a failed upgrade is retained until recovery is resolved. Manual recovery copies and hosting-provider backups follow their own retention. A deleted account can remain in those copies until they are removed.
- Anonymous home, demo and sign-up page events: 90 days.
Deleting an account or server
You can delete your personal Cloud account in Account after confirming your password. Once deletion succeeds, this deletes its workspace, server credentials, metrics, incidents, snapshots, update records, and alert settings from the active database. Removing a server deletes its Cloud records and revokes its Cloud credential. These actions do not uninstall vpsagent from your server; its revoked credential can no longer upload to Cloud. Limited agreement evidence may remain for the period and purposes described above; it does not keep your account active or allow further monitoring or email delivery.
Self-service account deletion is blocked while a subscription is active or a pending checkout cannot be safely resolved, and for a workspace with multiple members. Scheduling cancellation for the end of a paid period does not immediately end the subscription. Contact support if you need help ending service or exercising your privacy rights; an outstanding billing issue does not remove those rights.
Database deletion does not immediately erase older backups, browser preferences, provider records, or support correspondence. Backup copies are held for recovery with restricted access. Provider records remain subject to their own retention and applicable law. You can clear browser storage yourself and contact us about other retained information.
Cookies and browser storage
The Cloud site uses the necessary first-party vpscloud_session cookie to keep you signed in and authenticate account actions. Customer sessions expire within seven days; signing out clears the cookie. Blocking it prevents signed-in features from working. We save setup checklist completion with your account so it stays completed across browsers and devices. This preference is removed when you delete your account. The public withdrawal form also uses the necessary first-party vpscloud_withdrawal cookie for up to one hour to protect form submissions against forgery. It does not sign you in or track advertising activity. The Cloud site does not use advertising or analytics cookies. To understand which pages and campaigns lead to sign-ups, the home, public demo and sign-up pages send anonymous page events to our own server: that the page was opened, campaign tags from the link (such as utm_source), the referring site's host name, a phone/tablet/desktop category derived from the browser, visible time on the page, how far it was scrolled, and which links or buttons were clicked. Nothing is stored in or read from your browser's storage for this, no visitor or session identifier is created, and IP addresses and full browser details are not recorded with these events, so individual visits cannot be linked together or to an account. Browsers that send Do Not Track or Global Privacy Control are not counted. These events are not shared with advertisers or other third parties and are deleted after 90 days. External checkout and billing pages have their own cookie and privacy notices.
Your privacy rights
Where applicable, you can request access, correction, deletion, a portable copy, or restriction of your personal information, and object to processing based on legitimate interests. Download the retained application records for your personal workspace from Account → Download account data after confirming your password. This download excludes security credentials and is not the complete response to a request concerning support correspondence, independently submitted withdrawals, provider records or information about other people. Email support@vpsmon.cloud for those records, a larger export, help when you cannot sign in, or any other rights request. We request only identity evidence reasonably necessary for the circumstances. We respond without undue delay and within one month; if a lawful extension of up to two further months is needed for complexity or the number of requests, we tell you within the first month with the reason. A refusal explains the reason and your complaint and court rights. Requests are normally free; exceptions are assessed under applicable law.
You may complain to Lithuania's State Data Protection Inspectorate or your local supervisory authority. Account information and necessary telemetry are required to provide the corresponding Cloud features; you can choose not to pair a server or end the service. Material changes to this notice will be communicated through the service or account email.
Online withdrawal submissions and acknowledgement delivery records remain while the request is unresolved. Handled requests are removed three years after submission. A specific legal obligation or dispute may require separate, restricted preservation documented by the operator. We restrict access and do not use these records for marketing.
vpsmon Cloud