peripatetical

Privacy Policy

Last updated 13 November 2026

This policy covers peripatetical.com, including the product pages, the support form, and entries from the former CloudMonitor waitlist. It is written to describe what the site actually does, rather than to reserve every right a longer document might.

CloudMonitor, Cottage Goods Hawaiʻi and Side Hustles Hawaiʻi are open, and each handles your data under its own privacy policy, presented before you sign up. CloudMonitor in particular handles materially more sensitive data — credentials for your cloud accounts. This document does not cover the apps.

If you already use a Peripatetical product, its own privacy policy is the one that applies to you, not this page. The legal index lists them.

Who is responsible

The site 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. Where this policy says “I” or “me”, it means that party, acting through the person who runs it.

Peripatetical is a two-person business. The person reading your waitlist submission or support ticket is normally the person who wrote the site; a family member can see them too when covering as a backup, and is bound by a confidentiality undertaking.

For anything in this policy, including deletion requests, use the support page, which opens a ticket. A formal written notice can go to support@peripatetical.com instead; that address is for legal notices, not a support channel.

What is collected

If you joined the waitlist

The waitlist form closed when CloudMonitor opened on 12 November 2026. Submitting it stored the following:

DataSourceWhy
Email address You type it So I can contact you about CloudMonitor. This is the only reason.
What you're running (optional) You type it Free text describing your infrastructure, if you choose to share it. It helps me decide which scanners to build first. Leave it blank and nothing is lost.
A one-way hash of your IP address Automatic Used solely to limit how many submissions can come from one address in an hour. Your IP address itself is never stored — it is put through SHA-256 with a fixed label and only the result is kept. A hash of an IP address is not anonymous: someone holding it, with enough computing time, could test addresses against it. It is therefore treated as personal data, used for nothing but the hourly count, and is currently kept with your entry until the entry is deleted.
Two-letter country code Automatic Provided by Cloudflare. Tells me roughly where interest is coming from. It is country-level only, not a location.
Browser user-agent string Automatic Retained to distinguish real submissions from automated ones.
Time of submission, and which page the form was on Automatic Ordering and abuse handling.

Submitting the same address twice updates your entry rather than creating a second one.

If you use the support form

Sending the form on the support page opens a ticket containing:

DataSourceWhy
Your name, email address, subject and message You type them So a person can read the ticket and reply to you.
Which product the message is about You choose it Routing only.
Two-letter country code, browser user-agent string, time of submission, and a ticket reference Automatic To tell real tickets from automated ones, to order them, and so you can refer to the ticket later.
A one-way hash of your IP address Automatic Used solely to limit how many tickets one address can open in an hour. It is held separately from the ticket, in the same Cloudflare database as the waitlist, and is never sent to the ticket system. The note about hashed addresses above applies to it too.

The ticket and any replies are stored in a ticket system I run myself, hosted on Microsoft Azure in the United States, with an encrypted backup copy and a standby in Google Cloud, also in the United States. Replies are written by a person and sent to the address you gave. If the form cannot reach the ticket system, nothing is stored and the page tells you so rather than pretending it succeeded.

I may use an AI assistant to help sort, summarize and prioritize tickets before I read them, which means the text of a ticket — including your name and email address — may be processed by that assistant's provider, Anthropic. A person reads every ticket and writes every reply.

Please do not put passwords, API keys or cloud credentials in a ticket. They are never needed, and the form is not the place for them.

If you only read the site

We count visits, without cookies and without knowing who you are. Each page you open sends one small record to our own Mission Control service: the page address (with any query string removed), the site that linked you here, your country, a coarse device and browser type, and how long the page took to load. Your IP address is used only to look up the country and is never stored. To count unique visitors without a cookie, we combine your IP address and browser with a random value that we delete 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. Records are deleted after 90 days. There is no advertising, no tracking pixel and no third-party analytics service.

Cloudflare, which serves the site, keeps short-lived operational logs of requests as part of delivering and protecting it. That is ordinary infrastructure logging, and we do not use it to build any profile of visitors.

Cookies

This site sets no tracking or advertising cookies. There is no cookie banner because the only cookies it sets are the strictly functional preference cookies described below, which you ask for yourself. Cloudflare may set a strictly necessary security cookie to tell humans from bots; it is not used for tracking or advertising.

If you use the text size buttons (A− and A+) or the theme button in the menu bar at the top of any page, this site saves your choice in three preference cookies for all of peripatetical.com: pp_theme (light, dark or match your device), pp_font_px (the text size in pixels) and pp_prefs_at (the time of your last change). They hold that choice and nothing else, they are set only when you press one of those buttons, and they last a year. They are strictly functional: they exist only so that this site and our products open in the theme and size you picked. They are not used to track or identify you, and you can delete them in your browser at any time.

Our products can set the same cookies, and also pp_contrast and pp_motion (your contrast and reduced-motion choices), when you change those settings in CloudMonitor, Mission Control or your account settings. If you choose a theme, text size, contrast or motion setting there, this site reads the cookies, in your browser, so that it opens the same way. This site only sets the three named above.

Signing in at auth.peripatetical.com is a separate system that does set a strictly necessary session cookie, ppid_sso, for all of peripatetical.com. It lasts eight hours. This site only checks whether that cookie is present, so that it can show “Sign out” in place of “Sign in”; it does not read what is inside it. It also reads a small hint cookie, pp_mc, which auth.peripatetical.com sets at sign-in and which says only whether to show the Mission Control link in the Sites menu. You will only encounter it if you deliberately sign in, which you need to do only to use one of the apps. What the sign-in service stores is set out in its own privacy notice.

Who else touches your data

A small number of service providers, all acting on my instructions. The subprocessors page lists them across every product.

That notification, and anything you email to a peripatetical.com address, lands in my personal mailbox, which is hosted by a mainstream email provider, so it also sits there as an ordinary email.

Stripe will process payments for the products once paid plans open. This site takes no payment and sends Stripe nothing.

Your data is never sold, rented, or shared for anyone else's marketing. There are no advertisers and no data brokers involved. I would disclose data if legally compelled to, and would tell you unless prohibited from doing so.

How long it is kept

Waitlist entries are kept until you have been told CloudMonitor is open, or you ask to be removed, whichever comes first. If the product is abandoned, the list is deleted. If you have heard nothing and want to be forgotten, ask and you will be.

Support tickets and their replies are kept for up to two years after the ticket is closed, so that a returning problem has its history, and are deleted sooner if you ask. Nothing sweeps old records on a timer today: deletion happens when you ask, or when I do it by hand within those periods.

Your choices

Regardless of where you live, you may ask me to:

Ask through the support page and I will act on it, normally within a few days. There is no account to log into, and you do not need to give a reason.

If you are in the UK or the European Economic Area, the lawful basis for holding your waitlist entry is your consent, given when you submitted the form, and for a support ticket it is the legitimate interest in answering what you asked. You may withdraw consent at any time by asking, and withdrawing it does not affect anything done beforehand. You also have the right to complain to your national data protection authority.

Security, stated honestly

Submissions travel over HTTPS. Waitlist entries are stored on Cloudflare's managed infrastructure; support tickets are stored in a database that is not reachable from the public internet. Your IP address is hashed rather than stored. Access is limited to the two people who run Peripatetical.

What I will not claim is that this is a hardened enterprise environment. It is a small project run by two people. The waitlist deliberately collects as little as it can, so that if something did go wrong the worst case is an exposed email address and whatever you chose to type into the optional box. Please do not put anything sensitive in that box.

For the products themselves, which handle materially more than an email address, the security page sets out what protects your data, what is deliberately not in place yet, and how to report a vulnerability.

Children

This site is aimed at people who run cloud infrastructure professionally. It is not directed at children, and I do not knowingly collect their data. If a child's details have ended up here, tell me and I will delete them.

Changes

If this policy changes materially, the date above changes and — if the change affects data already collected — I will email the people it affects rather than quietly editing the page.