This policy explains what CloudMonitor collects, why, who else processes it, and what you can ask us to do about it. The short version: we collect what the product needs to monitor the infrastructure you connect, we do not sell any of it, and the complete list of third parties who can see it is in section 6. Two sections are worth reading rather than skimming: section 5, on your cloud credentials, and section 8, on how long we keep things and what we have not automated yet.
CloudMonitor is run by Peripatetical, a sole proprietorship based in Hawaii, United States. Peripatetical is the data controller for your information. We have filed to form Peripatetical LLC: our articles of organization were filed with the Hawaii Department of Commerce and Consumer Affairs on October 3, 2026, and Hawaii's business registry is experiencing processing delays, so approval is still pending. When the State of Hawaii approves the filing, Peripatetical LLC takes over the business and we will update this page. It operates CloudMonitor and the other Peripatetical services, with the help of one other person (see the note below), and is the data controller for the personal data described in this policy.
We publish the company's name and a monitored contact route rather than the names of the people who run it. The company's registration details are available to any data-protection supervisory authority, and to you where you need them to exercise a legal right, on request through the contact details below.
Where you connect a cloud account belonging to your organization, we act as a processor for the configuration data we read from it, on your instructions, and your organization is the controller of that data. For your account, billing and support information we are the controller.
Who that actually is, and what state the service is in. Peripatetical is an independent two-person business: the owner-operator, and a family member who helps and acts as a backup administrator. CloudMonitor is a new service, launched in November 2026. Section 3 of the Terms covers what that means for the service; it matters here because it is the honest context for every commitment below.
We say it plainly because it is the single most useful thing a security review can know about a vendor it is about to hand cloud credentials to.
You can reach us about anything in this policy — including access and deletion requests — in writing at [email protected], or you can open a support ticket (in the product under Support, or through our support page if you are not signed in). Both work whether or not you still have an account, which matters if you are asking us to delete one.
This policy covers the CloudMonitor service. Our central sign-in service at auth.peripatetical.com and our public website are separate services; this policy describes what CloudMonitor receives from the sign-in service, not everything that service does.
Your email address, display name, and the organization (tenant) you belong to. Sign-in is not handled here: CloudMonitor is a relying party of our central identity service at auth.peripatetical.com, and there is no CloudMonitor password to store. That service holds your sign-in credentials and records which identity provider you used; we receive the identity claims it returns. What that service stores, and how to delete your sign-in account, is set out in its own privacy notice.
While you are signed in we keep a session record — a random identifier, the signed-in user and tenant, and an expiry — in our database. The cookie in your browser carries only the identifier. See section 11.
The credentials you provide so we can read your cloud accounts — service principal secrets, access keys, service-account keys, or role references. See section 5.
The output of scanning what you connect: resource names and identifiers, certificate and secret expiry dates, rotation status, configuration settings, and the findings we generate from them. This is infrastructure metadata. It is not the contents of your storage, databases, or secrets.
We do not read secret values, and that is a property of the code rather than a promise. The vault scanner lists secret, key and certificate properties — name, version, expiry — and never calls the API that returns a secret's value. The read-only roles described in section 5 are the second half of the same guarantee.
Only if you turn on directory scanning for a connected Azure directory. For each person in that directory: display name and sign-in name (usually a work email address), whether the account is a member or a guest (and a guest's invitation status), whether it is enabled, when it was created and when it last signed in, whether it has registered multi-factor authentication, its administrator role assignments, and whether its password is set never to expire; plus the names and expiry dates of application secrets and certificates. This is data about your staff and guests, so you need a lawful basis to share it with us. We do not ask for permission to read their mail or files.
When a scan reads your directory completely and no longer sees an account, role assignment or credential, we delete the finding about it. A scan that stops short (an error, or a read cut off part-way) deletes nothing, so a partial read never removes a finding that is still true.
You can record your own notes against any resource we scan, along with who owns or maintains it and how to reach them — a name, team, email address, phone number, chat channel, and a link to your runbook — and you can switch scanning off for an individual resource, with a reason. We store exactly what you type, unchanged.
This is the one place in CloudMonitor where you may enter personal data about other people: your colleagues, or whoever is on call for a system. Please enter only what your own organization is entitled to record about them, and prefer a team or rota address over an individual's personal contact details where either would do. We do not use these details to contact anyone — they are shown to people in your organization who sign in, and returned to you in an export. Alerts go to the destinations you configure below, never to an owner recorded here.
These entries are stored in plain text, like the rest of your configuration data, and are not encrypted at rest the way credentials are (section 5). They are deleted when you clear the note, and with your tenant.
If you set up alerting, we store the destination you chose and the URL needed to reach it, encrypted at rest. Section 7 describes what we send there and what that means for your data.
Counts of monitored resources (used to calculate your bill), sign-in timestamps, and which features you use.
If your organization starts a trial after following a referral link that another customer shared, we record which customer referred you, when, and whether the referral has qualified for that customer's credit. The referring customer sees only the date and the status, never your organization's name or anyone's contact details.
When you cancel a subscription, we ask why. The questions are optional. If you answer, we keep the reasons you ticked and the note you wrote, with the date, the subscription they are about and the user who sent them. We use them to understand why customers leave and to improve the service. Only CloudMonitor staff see them. When you cancel, a copy of your answers is also emailed to CloudMonitor staff. They are in the file you get from Download my data, and they are deleted with your account. See section 8 for how long we keep them.
Messages you send us through the contact form or the in-product support form, and our replies. The contact form is open to visitors without an account, so it also records the name and email address you type into it. A copy of every ticket is held in our internal support system; see section 6.
If your account uses the API: each key's name, who created or switched it off, and when; and, for each request, which key made it, when, from which IP address, the path requested and the result. The key itself is stored only as a one-way hash, so we cannot see or recover it.
Settings → Activity shows your account's admins a list of changes made in the account: a connection added, removed or given a new secret, an alert destination or API key created, changed or switched off, and the rotation policies saved. Each entry holds the name you gave the item, the email address of the user who did it (or, for an MSP technician working in your account, their address and their organization's name), and when. It holds no IP address, no secret and no URL. It also lists the team, pause, download and MSP-access records described elsewhere on this page, and each time CloudMonitor support viewed the account as one of your users (read-only), without the staff member's address. See section 8 for how long entries are kept.
If your account is managed by an MSP, or is an MSP's organization account, we record each time a client account is linked or unlinked, each grant, role change or removal of a technician's access, and each time a technician switches into or out of a client account: who did it, which accounts, when, and from which IP address. Both the MSP's admins and the client's admins can see these records. See section 8 for how long they are kept.
Each time an account admin downloads the account's data we record which user did it, when, and how large the file was — never what was in it — and that record goes when the account does. When an account admin schedules the account’s deletion, or restores it, we record which role did it and when, and how many stored credentials were removed; that record goes when the account does. When an account is deleted with the Delete my account button we keep a receipt: when it happened, the plan, when the account was created, whether it was erased at once or after the 30 days, and how many rows were deleted from each table. The receipt holds no name, no email address and no account or user identifier, so it says nothing about who you were. See section 10.
If you delete your sign-in account at auth.peripatetical.com, CloudMonitor replaces your email address and sign-in identifiers on our side with placeholders that cannot be reversed. Billing records, support tickets and your organization's account and audit records are kept, as described in this policy; they are linked to an anonymised user, although a ticket or record you wrote may still contain your address in its text.
IP address, browser user agent, request paths, timestamps and error diagnostics, kept for security and debugging. The product also keeps its own record of page views while you are signed in — the page path, your session identifier, your role and a one-way hash of your IP address — to understand which parts of the product are used. This record is first-party only and is not shared with any analytics provider.
We also keep daily sign-up totals: how many times a day our home, pricing, demo and free-tool pages are opened and a trial is started, grouped by the campaign link (utm_source, utm_medium, utm_campaign) you arrived from, if any. These are counts only — no IP address, session identifier or other identifier is stored with them, and nothing is counted when your browser sends Do Not Track or Global Privacy Control. When you start a trial, the campaign link you arrived from is saved with the new account.
Separately, we use Cloudflare Web Analytics, a privacy-focused web analytics service from Cloudflare, to measure how many people visit our pages and where they come from. It is cookieless: it sets no cookies, does not use local storage, and does not fingerprint your browser or track you across sites, and nothing Cloudflare reports to us identifies you. Cloudflare reports to us only aggregate figures — page views, the page that referred you, country, and device, browser and operating-system type. We use it only to understand traffic and performance, not for advertising or profiling. Cloudflare is already a subprocessor for the connection itself (see section 6); this adds web analytics to what it does for us.
Each page you open also sends one small visit record to Mission Control, our own operations service, which runs on the same hosting as CloudMonitor and is not a third-party analytics provider. The record holds the page path (with any query string removed), the host name of the site that linked you here, how long the page took to load, and a coarse device and browser type. Mission Control uses your IP address to look up your country and does not store the address. To count unique visitors without a cookie, it combines your IP address and browser with a random value that is deleted after a day, so a visit can't be linked to you or to your visits on other days. If your browser sends Global Privacy Control or Do Not Track, nothing is sent. Visit records are deleted after 90 days.
Results of the checks we run for you leave CloudMonitor only as hourly totals (how many checks ran, how many failed, response times and status codes), with no account, endpoint or address attached.
Separately, whenever a stored endpoint credential is revealed in clear text, we record who did it, when, from which IP address and with which browser. Today only the operator's owner account can do that (see section 9); no user in your account can. That audit trail exists to protect you and cannot be switched off. Each reveal appears in your account's Activity log, with the endpoint and the time; the IP address and browser do not, and we will give you those for your endpoints on request.
Screen sharing with support. If you start a screen share from Help & support, our support staff see that browser tab live while you are on a call with us: the pages you open, where you click, and what you type, with passwords, secrets and card numbers hidden before they leave your browser. Nothing is recorded. The session ends when you click End, after 30 minutes without activity, or after 2 hours. We keep only a record that a session took place (who, when, how it ended).
We do not sell personal data, we do not share it for advertising, and we do not use your data to train machine-learning models.
Where the UK or EU GDPR applies, we rely on:
We have not appointed an EU or UK representative under Article 27 of the GDPR, and we do not currently hold a security certification such as SOC 2. Both are things a buyer in a regulated market may require, and we would rather you learn that here than in a questionnaire after signing.
Credentials you provide are encrypted at rest with AES-256-GCM under a key derived
from a secret held in the application's environment rather than in the database. They
are never written to logs and are excluded from every data export the product offers.
We request read and metadata permissions only — for example Reader
and Monitoring Reader on Azure, read-only Microsoft Graph application
permissions for Microsoft 365 and Entra ID, SecurityAudit on AWS, a
dedicated read-only service account on Google Cloud and Kubernetes, a read-only
registry token or mutual-TLS Docker Engine API access for Docker, and a read-only
Connected App for MuleSoft Anypoint — and where a
provider supports connecting without a shared secret at all, such as Azure managed
identity, we recommend that path instead.
Deleting a connection here. An account admin can disconnect any connection from the Connections page, and disconnecting deletes the stored credential along with it. If you cannot do that yourself, revoke the credential at your provider first, then open a support ticket (in the product under Support, or through our support page if you are not signed in) and we will delete the record.
What that encryption does and does not do. It protects your credentials if our database or a backup of it is compromised. It does not make them unreadable to the running application, which must be able to decrypt them in order to scan. We will not tell you we are unable to access your credentials, because that would not be true. What we can tell you is that access is restricted, never logged, never exported, and revocable by you at any moment from your own cloud provider — without telling us and without our cooperation. That is the control that always works, and we would rather you rely on it than on us.
We use a small number of service providers. This is the complete list.
| Provider | Purpose | Data involved | Active today |
|---|---|---|---|
| Microsoft Azure | Hosting, database, backups, platform logs and secrets storage, in Central US (United States) | All service data | Yes |
| Google Cloud | Disaster recovery, in the United States (Oregon): an hourly copy of the database, a daily check that the copy restores, and a standby that runs the service only if Microsoft Azure fails (what you would see then is on our security page) | A copy of all service data, encrypted before it leaves Azure and decrypted only inside our own Google Cloud project, for the daily check or while the standby is running; a copy of the service’s configuration and secrets | Yes |
| Cloudflare | DNS, and the edge network every request passes through, which ends the encrypted connection to your browser and opens a new one to our servers; and cookieless web analytics (aggregate page views, referrers, country and device type) | Everything sent between your browser and the service while you use it, including page content and anything you type into a form, plus your IP address and request metadata, in transit | Yes |
| Resend | Sign-in emails, sent by our central identity service; alert emails sent by CloudMonitor itself when a check finds something you have asked to hear about; and the notice CloudMonitor sends our staff when a customer cancels | Email address; in an alert, the finding it is about — for example an endpoint label and URL, or a certificate name and expiry date; and, in a cancellation notice, the account’s name and plan, the dates, and any survey answers | Yes |
| Anthropic | AI features — the in-product assistant (paid plans), and Deep Analyze, the optional analysis of findings (Team plan and up, or the AI Insights add-on) | Only when you use one of them: your chat messages, together with your email address, your role and your organization’s name so the assistant can answer for your account; and, where you use Deep Analyze, the findings being analyzed (infrastructure metadata such as vault and secret names and expiry dates) | Yes — only when you open the assistant or run an analysis |
| Stripe | Payments — Stripe processes subscription payments; and usage reporting for your bill | When you subscribe: name, email, billing address and payment details — collected by Stripe directly and never received, seen or stored by us — plus the count of monitored resources we report against your subscription | Yes — once you subscribe; not during a free trial |
| Globalping (Volentio JSD Limited, United Kingdom) | When one of your endpoints looks down from our region, checking it from other parts of the world, so we can tell you whether it is down everywhere or only from one place | Only the address of the endpoint being checked: its host name and path, never the query string, headers or credentials, and never an endpoint that has stored credentials. Globalping makes every check public, so anyone holding a check’s id can see that address and the result | No — this check is off, and no endpoint has been sent to Globalping |
| Public domain lookup services (crt.sh; RDAP and WHOIS registries, including Verisign and rdap.org; the SpamCop blocklist) | Checking the domains you ask us to monitor: certificates issued for them and for lookalikes of them, when their registration expires, and whether their IP addresses are on a blocklist | Only what is being looked up: the domain name, typo variants of it, or an IP address. The request comes from our servers, and these services are not told which account it is for | Yes — only if you add a monitored domain |
| Public DNS and registry services (Google Public DNS, Cloudflare, NextDNS and Quad9; the registries named by IANA, or WHOIS where a registry has no RDAP service) | Answering a lookup you run in Network Tools | Only the domain name, IP address or AS number you entered. The request comes from our servers | Yes — only when you run a lookup |
| Your alert and ticketing destinations (Slack, Microsoft Teams, Discord, PagerDuty, your own webhook, or your ConnectWise, Autotask, HaloPSA or NinjaOne account) | Delivering alerts and opening tickets you configured | Details of the finding, such as its title or category, severity, resource name and location — see section 7 for exactly what each receives | Only if you configure one |
On the AI features. The in-product assistant is included with paid plans, and Deep Analyze is included from the Team plan up, or with the AI Insights add-on. Both are optional and user-initiated — nothing is sent to a model unless you open the assistant or ask for an analysis. When you do, the relevant content is sent to Anthropic's API to generate the response, and Anthropic processes it on our behalf under its commercial API terms. We do not train any model on your data. Your cloud credentials are never included. If you would rather no infrastructure metadata left our systems at all, do not use the analysis feature; the scanning and reporting that make up the core of the product do not use it.
Our own systems, not third parties. Two other systems are operated by the same two-person business as CloudMonitor, so passing data to them is not a disclosure to anyone new — but it does mean your data exists in more than one place, and a deletion request covers all of them:
Alert email. CloudMonitor sends alert email of its own, through Resend, when a scheduled check finds something you have asked to hear about — an endpoint it could not reach, a certificate or credential approaching expiry, a critical finding, or a recovery. Those emails go to the people on your account and contain the finding they are about, so infrastructure metadata such as an endpoint URL or a certificate expiry date leaves our systems in the body of the mail. You choose which types you receive, how far ahead expiry warnings begin and how often a repeat may be sent on your Alerts & notifications page. We send no marketing email.
We will update this list before adding a new provider that processes your data. If you need a formal subprocessor notification arrangement, ask us.
Alert email is on by default for the people on your account (section 6). Sending alerts anywhere else is opt-in and off until you set it up: CloudMonitor can deliver findings to a Slack incoming webhook, to Microsoft Teams, Discord or PagerDuty, to any webhook URL you supply, or open tickets in your own ConnectWise, Autotask, HaloPSA or NinjaOne account. When an alert fires — or when you send a test — we make an outbound request to the destination you configured:
That is infrastructure metadata about your environment, and once it arrives it is held by that provider under their terms, not ours.
A destination URL, PagerDuty routing key or ticketing-system credential is a credential, and we treat it as one: it is stored encrypted at rest and excluded from exports, the same as a cloud credential. Choosing where your findings go is your decision and your responsibility — the Terms ask you not to point an integration at a destination you do not control, and this is why.
When you use the API. With the API, included in every plan, software you run can read your findings, configuration and alerts using a key an account administrator created. What that software does with the data afterwards is up to you: once it has left through the API it is under your control, not ours. The API never returns stored cloud credentials or alert destination secrets.
CloudMonitor is hosted in Microsoft Azure in Central US (United States). The database is not reachable from the public internet — it is accessible only over a private network from the application itself. An encrypted copy of it is kept with a second provider, Google Cloud, in the United States, together with a standby that takes over only if Azure fails. Service data is stored and processed in the United States. If you use the service from outside the United States, your data is transferred there, and our service providers may process data in other countries. Where personal data covered by UK or EU GDPR is transferred outside those areas, the transfer relies on the safeguards those providers offer for such transfers, such as Standard Contractual Clauses.
| Data | Retention |
|---|---|
| Cloud credentials | Deleted when an account admin disconnects the connection, or on request. Deleted 30 days after the account is cancelled or its subscription ends, unless it is reactivated first. Removed at once when an account admin schedules the account’s deletion, and not recoverable |
| Alert destination URLs and keys | Deleted when you delete the destination. Removed at once when an account admin schedules the account’s deletion, and not recoverable |
| Findings and scan history, including directory and identity findings | For the life of the account, except the log of individual scan runs, which is kept 1 year, and the endpoint check results and status history in their own row; then permanently deleted 30 days after an account admin schedules the account’s deletion (at once, if they choose Erase now), or within 90 days of closure when we close an account by hand |
| Endpoint check results, and the day-by-day status history behind the marks on findings | 90 days, then deleted automatically; the latest result for each endpoint is kept with the endpoint, whatever its age |
| Account and tenant records | Permanently deleted 30 days after an account admin schedules the account’s deletion (at once, if they choose Erase now), or within 90 days of closure when we close an account by hand |
| Credential-reveal audit records | For the life of the account — they exist to be reviewed later, so we do not trim them |
| Session records | Expire automatically; 8 hours of inactivity at the longest |
| API keys | For the life of the account, including after a key is switched off or expires, as a record of who created it; switched off when the account’s deletion is scheduled and deleted with the account |
| API access records | 90 days, then deleted automatically |
| Account activity log (which connection, alert destination, API key or policy was changed, by which user, and when; no IP address) | 365 days, then deleted automatically; deleted sooner if the account is deleted |
| Records of data downloads (who, when, how large; never the contents) | For the life of the account, then deleted with it |
| Account-deletion receipts (counts per table, and whether the erase was at once or after the 30 days; no name, email or identifier) | Kept without a time limit; they identify no one |
| Billing records | Up to 7 years, as tax and accounting law requires |
| Notifications from our payment processor (which include your email address) | Contents emptied after 90 days; the record that one arrived is kept up to 7 years |
| Support tickets, including the copy in our internal support system | Up to 2 years after the ticket is resolved; redacted earlier on request |
| Cancellation survey answers (the reasons you ticked and your note) | 2 years after you send them, then deleted automatically; deleted sooner if the account is deleted |
| Platform logs (application and network logs held by our hosting provider) | 30 days, then deleted automatically by the platform |
| Daily usage readings (your billable unit count, one per day, behind the billing page’s usage chart) | 400 days, then deleted automatically |
| Cloud and SaaS cost figures (daily and monthly spend per service, read from your connected cloud accounts and, where the token allows it, the billing of connected services such as Cloudflare and GitHub) | 25 months, then deleted automatically; deleted sooner if the account is deleted |
| Alert history (when an alert was sent to you and when it cleared, and who acknowledged, snoozed or assigned it) | 400 days after the alert clears, then deleted automatically; deleted sooner if the account is deleted |
| Security finding history (when a directory finding appeared, changed or went away) | 400 days after the change once the finding is gone, then deleted automatically; deleted sooner if the account is deleted |
| Page-view records kept by the product | 90 days, then deleted automatically |
| Records of the operator signing in as one of your users to help (who, when, from which IP address) | 1 year, then deleted automatically |
| MSP access records (links, technician grants, and each switch into a client account, with the IP address) | 1 year, then deleted automatically; deleted sooner if the MSP’s account is deleted |
| Database backups (in Azure, and the encrypted copies in Google Cloud) | Rolling; a deleted record can persist in backups for up to 35 days after it is permanently deleted before it ages out |
What deletes itself, and what waits for you. A daily job deletes session records, page-view records, API access records, daily usage readings, finished support tickets, cancellation survey answers, alert history, security finding history, account activity log entries, records of the operator signing in as your users, MSP access records, and payment-processor notifications when each reaches the period in the table; it runs within a day or two of that period. The scheduled endpoint checks delete endpoint check results and status history past 90 days as they run. Other findings, scan history and account records are not swept on a timer. A scan that reads a connection completely deletes the findings it no longer sees; everything else is deleted when you delete it — a connection, a destination, or the whole account from Settings › Your data. Deleting the account stops scans and alerts and removes its stored credentials at once, keeps the rest for 30 days so you can change your mind, and then a daily job deletes it permanently; “Erase now” skips the 30 days. The 90 days in the table are the ceiling for closures you ask us to do by hand. Platform logs and backups age out on our hosting providers’ schedules.
All traffic is served over TLS. Stored cloud credentials, alert destinations and other
sensitive fields are encrypted at rest with AES-256-GCM. Data is isolated per tenant.
Sign-in is delegated to our central identity service, so CloudMonitor never stores a
password. Session cookies are marked HttpOnly and
SameSite=Lax, and are restricted to HTTPS when the connection is secure.
Sensitive material is excluded from every data export the product offers.
Who inside the business can see your data. Two people can administer the service: the owner, who operates it, and a family member who acts as a backup. Both have administrative access to the application, its database and its logs, and the second person is bound by a written confidentiality undertaking. That access is used to run the service, diagnose faults and answer your requests, and for nothing else. Your findings, configuration data and support messages are visible to either of them in that role. Your cloud-connection credentials are encrypted as section 5 describes and are not displayed anywhere in the administrative tooling. Within the application, a stored endpoint credential can be revealed by the operator's owner account — and by no other account — and every such reveal is rate-limited and recorded as section 2 describes.
No system is perfectly secure, and as section 1 says, this is a two-person operation with no third-party security certification and no external security audit behind it. Section 13 says what we will do if something goes wrong.
Depending on where you live, you may have the right to access a copy of your personal data; correct it; delete it; restrict or object to how we use it; receive it in a portable format; and withdraw consent. If you are a California resident, you have the rights to know, delete, correct, and opt out of sale or sharing — and, as noted above, we do not sell or share personal data as those terms are used in California law, so there is nothing to opt out of. Other US state privacy laws may give you similar rights; the same routes serve them.
Wherever you live, you may ask us for any of these and we will act on the request unless the law prevents it. To exercise a right, write to [email protected] or open a support ticket (in the product under Support, or through our support page if you are not signed in). Both work whether or not you still have an account, which matters if you are asking us to delete one. There is no form to fill in and no fee, and you do not need to give a reason; we may need to confirm that you control the email address on the account before acting. We will respond within 30 days, and we will not discriminate against you for exercising a right. Because your sign-in account at auth.peripatetical.com is shared across our products, tell us whether you want that deleted as well.
Two of these rights are buttons, for account admins. In the product, under Settings › Your data, an account admin can download everything the account holds as one ZIP file — a JSON file for each data set, and a manifest that says what is in it and what was left out, with stored credentials, keys and tokens never included — and can delete the account. Deleting the account has two steps. Straight away, scans and alerts stop, every stored credential is removed (and cannot be recovered), everyone on the account is signed out, and we email the account’s admins to confirm. Then the account’s data is kept for 30 days, during which an account admin can restore it and enter the credentials again; after 30 days it is permanently deleted — connections, findings, scan history, alert settings, API keys and users — with no undo. An account admin who wants it gone sooner can choose Erase now, which is immediate and permanent. The table in section 8 says what stays and for how long. It refuses while a subscription is still running, and for an account that includes platform staff; for those, ask us.
Two things are still a request rather than a button. Your sign-in account at auth.peripatetical.com is shared across our products and separate from this one, and there is no self-service for removing it yet, so ask us for that. And anyone who is not an account admin on the account cannot use either button; ask an admin, or ask us.
If you are in the UK or EU and are unhappy with our response, you can complain to your local supervisory authority.
Signing in through auth.peripatetical.com sets that service's own sign-in cookie on the peripatetical.com domain, so that your sign-in is recognized across our products. It is strictly necessary and carries no advertising or tracking identifier. CloudMonitor itself sets one cookie for every visitor: a session cookie holding a random identifier that links your browser to the session record described in section 2. It expires when you close your browser, and the server-side record expires after 8 hours of inactivity. The token that protects our forms against cross-site request forgery lives inside that session rather than in a cookie of its own. Both are strictly necessary and cannot be turned off while you use an account.
If you arrive by following a referral link that another CloudMonitor customer
shared, CloudMonitor also sets a referral cookie named cm_ref. It holds
that link's referral code and nothing else: not your name, not your email address, and
nothing about what you do on the site. It lasts 60 days. If you start a trial in that
time, we use the code to credit the customer who referred you, and then delete the
cookie. Only CloudMonitor reads it. You can delete it from your browser at any time;
the only effect is that the referral is not credited.
We also store interface preferences in your browser — your theme, font size and
help-panel state — mostly in local storage on your device. Some of them are also kept
as small preference cookies on the peripatetical.com domain, so that our other sites open
in the same theme, text size, contrast and motion setting: pp_theme (light, dark,
or follow your device), pp_font_px (your text size in pixels),
pp_contrast (more contrast, or follow your device), pp_motion
(reduce motion, or follow your device) and pp_prefs_at (the time you last changed
one of these, so the newest choice wins). They hold nothing else, last a year,
and are not used for anything but drawing the page. If you are signed in, the font sizes you
save under Appearance, and whether the Findings menu lists the most critical first, are
also kept with your account.
We do not use advertising cookies, analytics cookies, or cross-site trackers, which is why you are not being asked to dismiss a consent banner. The only usage measurement is the first-party page-view record, the daily sign-up totals, the cookieless visit count and Cloudflare Web Analytics, which is also cookieless, all described in section 2; none of them uses a cookie of its own.
CloudMonitor is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe we have, contact us and we will delete it.
If we become aware of a breach that exposes your personal data or your stored credentials in a way that puts you at risk, we will tell you — by email to the address on your account, without unnecessary delay and within any deadline the law sets — what happened, what was affected, and what to do about it, starting with revoking the affected credential at your own provider. We will notify the relevant regulator where the law requires it, and we will tell you what we know rather than the minimum we can defend.
We may update this policy. If a change materially affects how we handle your personal data — including adding a provider to section 6 or switching on one marked as not active — we will give account holders reasonable advance notice, by email or an in-product notice, before it takes effect. The effective date at the top of this page always reflects the current version.
Questions, requests, or complaints about privacy: write to [email protected], or open a support ticket (in the product under Support, or through our support page if you are not signed in).