Version 1.2 · In force since September 11, 2026.
Most privacy policies are an inventory of taking: pages of what a company collects, keeps, matches, and sells, written to be skimmed and clicked past. This one is short because the site was built the other way around: what you do here stays on your device, and the one door where you can hand us anything is listed below, item by item.
Version 1.2 · in force September 11, 2026 · changelog: v1.0 (July 13, 2026) — first draft, fulfilling the Terms' §6 promise of a full Privacy Policy · v1.1 (September 9, 2026) — section 7 added: what the contact form collects, where it goes, and how long it stays; section 6 updated: the door is open at apply.kisop.com; the policy takes effect as a version · v1.2 (September 11, 2026) — section 3 corrected: this site runs on a machine the project operates and reaches you through Cloudflare, not from claude.ai; section 1 updated now that the intake service is running; the doors are named the way the site names them. Nothing about what is collected, kept, or shared changed.
This site is operated by Care Delivery Inc, a Delaware corporation. KISOP is our project; the vision is written at carmenw.com. This policy covers the KISOP website — the main site and standalone pages — and our own intake service behind the door described in section 6, which has been running since September 9, 2026. It does not cover your personal archive, which stays on devices you control. Keeping that archive outside company custody is a core project requirement.
This site is a reading room, not a system of record. It has no accounts, profiles, or visitor database. The absence of those systems limits what could be breached, sold, subpoenaed, or lost. Rely on that technical limit rather than a promise about future conduct.
The site sets no cookies, runs no analytics, embeds no tracking pixels, loads no third-party fonts or scripts, and fingerprints nothing. It makes no requests to anyone's servers at all once the page reaches you — self-containment is checked by machine before every release, and you can verify it yourself: open the page source, watch the network tab.
Any web server delivering a page necessarily receives connection details such as your IP address, browser type, and request time. This site runs on a machine the project operates, on its own domain. Requests reach it through Cloudflare, which provides the domain's DNS and passes traffic through its network, so Cloudflare receives those same connection details under its own terms, which we do not control. Version 1.1 and earlier said the site was served from claude.ai; that was true when they were written and is not true now, which is why this sentence is corrected in a dated version rather than quietly. The server-log policy is still owed — what our own logs keep, for how long, and what Cloudflare is set to keep. The current proposal is minimal logs, short retention, and no analytics disguised as operational logging. 📋
If you type your name so the site can greet you, save pages to your shelf, or choose a language, those live in your browser's own local storage — on your device, never transmitted to us or anyone. Clear your browser's site data and they vanish. We can't see them, back them up, or restore them, which is exactly the deal.
The plans, letters, kits, briefs, and sheets you make here are generated entirely in your browser. What you type into them never reaches us — there is no code on these pages that could send it. Printing and saving happen on your machine. Your documents are yours, from the first keystroke.
This door is one of the two places you can hand us information; the other is the contact form in section 7. It opens at apply.kisop.com, on our own intake service. The site calls it Write to us, and Apply where you are applying for a job from the jobs board: one door, one set of limits, whichever word you came through. Here is the whole exchange:
What travels: what you came to do (a message, a correction, a security report, a job application), the page or region you came from, the versions of the Guidelines and Terms you saw, whatever you type into the form, and an email address if you give one so we can verify and reply.
Where it lives: on our own intake service, on infrastructure we control — not on a marketing platform, not in anyone's ad ecosystem.
Who reads it: the founder, and the few people she names to help review — bound by the same rules on this page.
What it's for: reading what you sent, reviewing it if it is an application, replying to you, organizing regions, and keeping the member ledger. Nothing else.
What it's never for: selling, renting, trading, advertising, or profiling. We do not sell personal information, and we never will — that is a charter matter for us, not a preference.
How long we keep it: as long as it's relevant to the relationship you asked for. Write in and ask what we hold about you, and we'll show you, correct it, or delete it. The formal rights language — the statutory kind, with citations — is what counsel is reviewing now. 📋
The About Us page has a Contact us button. It is the second door, and it goes to the same intake service as the door in section 6. Use it to ask a question, suggest something for the site, report a problem, or say how you would like to help. Here is what a message carries and what happens to it.
What you type: the form asks for a name, a way to reply (an email address, or a phone number), a topic, and your message. It asks for nothing else. If you leave out a way to reply, we read the message and cannot answer it.
What travels with it: the page you sent it from, and the versions of the Guidelines and Terms in force when you sent it. The form has a checkbox saying you did not include sensitive information; the time you checked it is stored with the message as your acknowledgement.
What the server sees: anything sent over the web shows our server your IP address, your browser type, and the time. We use the IP address for one thing: a limit of five messages per address per hour. That counter lives in short-lived memory and is not stored with your message. The form also carries a hidden field that only automated senders fill in. A message with that field filled is dropped and nothing is stored.
Where it lives: on our own intake service, on infrastructure we control, in a database and in plain files we keep so the database can be rebuilt. Every change to a message's status is added to a dated log that is only ever appended to, never edited.
Who reads it: the founder, and the few people she names to help review, bound by the same rules on this page. A reviewer can add a dated note to your message; notes cannot be edited or removed afterward.
What leaves our systems: when we reply by email, or send you a link to confirm your address, that one email goes out from hello@kisop.com through Brevo, an email delivery service, which handles your address and the text of that email under its own privacy policy. That address sends; it does not receive. Mail sent to it reaches no one; to reach us, use the contact form. Once a day the service sends the founder one line with the count of new messages. That line carries no names, addresses, or message text. Nothing else about your message leaves our systems.
What it's for: answering you and following up on what you asked. Nothing else. A contact message does not put you on any list.
What it's never for: selling, renting, trading, advertising, or profiling. The same charter rule as section 6.
How long we keep it: as long as what you asked about is still open, and after that as a record of what was asked and answered. There is no fixed deletion schedule yet; counsel is setting one. 📋 Write in and ask what we hold about you, and we will show you, correct it, or delete it.
Health details: please keep them out of the form; the form says so, and section 8 says why. If you send them anyway, we treat them as confidential and delete them where we can.
Please don't put medical details into an application form; we don't want them there, and we'll say so on the form itself. We are not your health-care provider, we are not a HIPAA covered entity, and this website is not the place for your records. The entire project exists so that your health information lives with you — in your archive, in your house — and never needs to sit on a company's servers, including ours. If you send us health details anyway, we will treat them as confidential and delete them where we can; but the real protection is the design, and the design says: your records belong in your archive, not in our inbox.
This site is not directed to children under 13, and we do not knowingly collect information from them — noting that we collect almost nothing from anyone. A family's archive that includes children's information is the family's own, in the family's keeping; it is never ours.
If legally compelled to disclose information we hold, we will disclose only what the order requires and notify the affected person unless prohibited. More important, we cannot hand over information we never receive; the data-minimization rules above provide the strongest protection in this policy.
This policy is versioned and dated, and it will never change quietly. Material changes are announced in "New in this place" on the main site before they take effect, and — like the Guidelines and Terms — the version you saw travels with anything you send us, so there is a record of what you actually agreed to.
Use the contact form on the About Us page, described in section 7. We do not publish an email address because public inboxes attract impersonation and fraud; the contact form reaches the same people. A formal notice address (registered agent) will be listed here on counsel's advice. 📋
Version 1.2, in force since September 11, 2026 — section 3 corrected: the site runs on a machine the project operates, on its own domain, and requests reach it through Cloudflare, which therefore sees the same connection details; version 1.1 said claude.ai, which stopped being true when the site moved, and a policy in force is corrected by a dated version, not quietly. Section 1 updated now that the intake service is running rather than planned. The doors are named the way the site names them since September 11: Write to us everywhere, Apply where you are applying for a job from the board. Nothing about what is collected, kept, shared, or sold changed in this version — the practices in sections 6 and 7 are the same ones, and what counsel is still reviewing (the statutory rights language, a deletion schedule, the notice address) is still marked 📋 and still open.
Version 1.1, in force since September 9, 2026 — section 7 added for the contact form on the About Us page, and section 6 updated now that the Apply door is open. Version 1.0 was the first full draft, written July 13, 2026 from the project's own working notes; it was never in force. Counsel review is pending; anything counsel changes arrives as a new dated version, announced before it takes effect, and the version you saw stays on record.
What is already true regardless: the site behaviors this policy describes — no accounts, no cookies, no analytics, no external requests, tools that never transmit — are running today and are machine-checked before every release. The intake service behind both doors runs on our own infrastructure, with the limits described in sections 6 and 7 in its code.
This page will say so, dated, when any of this changes. Same as every page here.