Peripatetical Account privacy notice
Effective 2026-10-26. This notice covers the sign-in service at auth.peripatetical.com — the one account that signs you in to every Peripatetical product. Each product has its own privacy policy for what happens after you are signed in.
Who is responsible
The Peripatetical sign-in service and the other Peripatetical services are 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. You can reach us through the contact route below.
Peripatetical is a two-person business: the owner, who built the software, and a family member who acts as a backup administrator. Both can access the data described here, only to run the service. The person who normally answers a support ticket is the owner.
What this service stores
- Your email address, the time you last proved you control it, and a display name if one has been supplied. We do not ask for or store a password. If you sign in through your organization’s single sign-on, we also keep a link between your account and your organization’s sign-in (see below).
- A one-time sign-in token each time you ask for a sign-in link. It is stored in hashed form next to your email address, works once, stops working after 15 minutes, and is deleted when you use it. A link nobody uses is cleared out the next time anyone asks for a sign-in link after it has expired.
- Technical logs kept by our hosting platform: IP address, time, the page requested and whether it succeeded. If too many requests arrive from one address we log that address when we refuse the request.
- A record of rejected sign-in links. When a sign-in link is rejected — it has expired, was already used, or is not recognized — we record when that happened, which of those it was, and two one-way codes: one derived from the email address in the link and one from the network address of the request. We cannot turn a code back into the address it came from, though we can check whether a given address produces the same code. The record is written to the technical logs above and to our internal security log in Mission Control, which is run by the same business.
- If you turn on two-step sign-in: for an authenticator app, its secret key, encrypted; for a passkey, its public key and identifier (the private key stays on your device); the name you give each method, and when it was added and last used; your recovery codes, in hashed form, and which have been used; a record that a browser’s sign-in passed the second step, which lasts up to 8 hours; and a count of recent failed tries. If our support team resets it for you, we keep a record of the reset with the reason and one-way codes instead of email addresses.
- If your organization uses single sign-on: the organization’s name, its email domains, the settings of its own identity provider, a link between your account and that provider, and a short-lived record that stops one sign-in from being replayed. Your organization, not us, controls its identity provider, and it receives and returns your sign-in when you use it.
- A security record of two-step and single sign-on events. When you add, rename or remove a two-step method, pass or fail the second step, are locked out after too many tries, replace your recovery codes, or sign in through your organization’s single sign-on (or that sign-in is refused), we record what kind of event it was, when, whether it succeeded, the kind of method, your organization if any, and one-way codes for your email and network address. The record goes to our internal security log in Mission Control, run by the same business.
Your signed-in session is not stored on our servers. It lives in a signed cookie in your browser (see Cookies) and ends when that cookie expires or you sign out.
Your Account page also shows your subscriptions and default site. Those are read, at the moment you open the page, from Mission Control — our internal admin system, run by the same business — and are not stored by the sign-in service.
Why we use it
To sign you in, to keep you signed in across our products, to sign you out of all of them at once, and to protect the service from abuse. Where UK or EU data-protection law applies, we rely on performing our contract with you (running the account you asked for) and on our legitimate interest in keeping the service secure. We do not use this data for advertising, we do not sell or share it, and we make no automated decisions about you with it.
When you sign in to a Peripatetical product, this service tells that product your email address, your role, which products you subscribe to, your default site and a sign-in session identifier, so the product can open the right account and sign-out works. If the product asks for it, we also tell it your display name, when you have set one on your Account page, so it can show your name instead of your email address. If you used two-step sign-in, we also tell it that you did, and which kind of method you used.
Who else processes this data
This is the complete list for the sign-in service, apart from your own organization’s identity provider if it set up single sign-on.
- Microsoft Azure — hosting, database and platform logs, in the United States. All data described in this notice.
- Google Cloud — disaster recovery, in the United States: an encrypted hourly copy of the database, a daily check that it restores, and a standby that runs this service only if Azure fails. All data described in this notice, decrypted only inside our own Google Cloud project.
- Cloudflare — DNS for our domain. Requests to this sign-in service go straight to our hosting provider and do not pass through Cloudflare’s network, so Cloudflare does not see your sign-in traffic.
- Resend — delivers the sign-in email, a notice to you when your two-step sign-in changes or a recovery code is used, and a notice to the operator when a new account is created. Your email address and the message containing your sign-in link or the notice; for a new account, your email address, display name if any, and how you signed in. The new-account notice lands in the operator’s mailbox, which a mainstream email provider hosts.
- Stripe — payments. The sign-in service sends nothing to Stripe. If you choose “Manage billing” on your Account page you are taken to Stripe’s own billing portal, where Stripe collects and holds your payment details directly; we never receive or store them.
Peripatetical staff sign in with a Microsoft work account (Microsoft Entra ID). Customers sign in through Microsoft only if their own organization set that up as its single sign-on.
Where it is stored
On Microsoft Azure in the United States. The database has no public network access; it is reachable only from our applications over a private network. An encrypted copy is kept in Google Cloud, also in the United States, with a standby that takes over only if Azure fails. If that ever happens, you may be asked to sign in again, and changes made in roughly the hour before the failure may be missing. If you use the service from outside the United States, your data is transferred there. Where UK or EU GDPR applies, transfers rely on the safeguards each provider offers, such as Standard Contractual Clauses.
How long we keep it
- Account record — until you delete it on the Your data page or ask us to. A record that a deletion happened, holding a one-way code instead of your address, is kept as proof that it was done.
- Sign-in tokens — deleted when used. Unused tokens stop working after 15 minutes and are deleted the next time anyone requests a sign-in link after that, so on a quiet day an expired token can sit longer than 15 minutes.
- Signed-in session — expires automatically after 8 hours.
- Two-step sign-in — each method until you remove it; recovery codes until you replace them or remove your last method; all of it until you delete your account, when it is deleted with the account. A record of a reset by our support team stays after that, holding one-way codes instead of your address.
- Technical logs — 30 days.
- Rejected-link records — 30 days in the technical logs. In the internal security log there is no automatic deletion schedule yet; those records hold only the reason and the one-way codes described above, not your email address or IP address.
- Two-step and single sign-on security records — no automatic deletion schedule yet; they hold one-way codes, not your email or IP address.
Apart from session expiry, the token clean-up above and the platform’s 30-day log retention, there is no automated deletion schedule today, including for the rejected-link records and the two-step and single sign-on records in the internal security log. Otherwise, deletion happens when you delete your account yourself, or when you ask and we do it by hand.
Cookies
Every cookie this service sets is strictly necessary for signing in, or holds an appearance choice you made. None carries an advertising or tracking identifier.
We count page visits without cookies, through our own Mission Control service. Nothing is sent when your browser asks not to be tracked (Global Privacy Control or Do Not Track), your IP address is never stored, and there are no third-party trackers. That is why there is no consent banner.
- Session cookie (
authjs.session-token, named__Secure-authjs.session-tokenon the live site) — keeps you signed in to this service. Up to 8 hours. ppid_sso— set on.peripatetical.comso your sign-in is recognized across our products. Up to 8 hours.pp_mc— set on.peripatetical.comso the Sites menu on every one of our sites can show the Mission Control link to the people who can use it. It holds only the word staff or workspace, grants no access by itself, and is deleted when you sign out. Up to 8 hours.ppid_sid— a random identifier for your browser’s sign-in session, so that one sign-out can end your session on every product. It grants no access by itself. Deleted when you sign out; otherwise lasts up to 400 days.- Short-lived sign-in cookies (
ppid_auth_req,ppid_gate_req,ppid_org_sso,ppid_link_reqandauthjs.csrf-token(both with a__Host-prefix on the live site),authjs.callback-url) — remember which product you were signing in to, tie a sign-in link to the browser that asked for it, and protect the sign-in form from forgery. Between 10 and 30 minutes, or until you close the browser. - Appearance cookies (
pp_theme,pp_font_px,pp_contrast,pp_motion,pp_prefs_at) — set on.peripatetical.comwhen you choose a theme, text size, contrast or motion setting here or in one of our products, or when you sign in and your account has a saved choice. They hold that choice and the time you made it, and nothing else. Up to a year.
Your rights
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. Wherever you live, you may ask us for any of these and we will act on the request unless the law prevents it.
How to ask. Open a support ticket at peripatetical.com/support. You can also do two of these yourself: signed in, open Your data to download everything this service holds about you as a JSON file, or to delete the account. A deletion happens straight away, signs you out of every product and cannot be undone; it needs a sign-in within the last 15 minutes and is not available while a subscription is still active. We keep only a record that it happened, holding a one-way code instead of your address. Because one account signs you in to every product, each product’s own data is deleted separately — in that product, or by asking us. There is no form to fill in, no fee, and you do not need to give a reason. We respond within 30 days and do not discriminate against you for exercising a right.
If you are a California resident, you have the rights to know, delete and correct, and to opt out of sale or sharing. 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 route serves them. If you are in the UK or EU and are unhappy with our response, you can complain to your local supervisory authority.
Children
The sign-in service is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe we have, tell us and we will delete it.
If something goes wrong
If your personal data is exposed 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. We will notify the relevant regulator where the law requires it.
Changes and contact
If this notice changes materially — a new provider in the list above, a new use of your data — we will give account holders reasonable advance notice by email or in-product notice before it takes effect, rather than quietly editing the page. The date at the top always shows the current version. Questions, requests or complaints about privacy: open a support ticket at peripatetical.com/support. It works whether or not you still have an account. The Peripatetical website privacy notice and each product’s own policy cover everything outside this sign-in service.