The plugin
Installing the Permitude plugin adds two hooks to Claude Code, one for each direction. The first sends us the design file itself, only when your design is checked. Checking a design means building it and running the code checks on our servers, so the design has to reach us — see The studio below. It reads the one file each check names, and nothing else. It runs only when a check runs, and sends nothing at any other time. The second saves your purchased permit packet: when you ask for it, this hook downloads the PDF from us into the folder you are working in. It sends us nothing — it only receives.
Your messages, your other files, their contents, their names, and the directory you are working in are never sent — the hooks do not read them and cannot send them.
The hooks fire only in sessions Permitude is loaded in. The install command we publish scopes Permitude to the single folder you install it in, so sessions you start anywhere else send us nothing at all — the hooks are not loaded there and do not run. You can also load Permitude for one session only, with nothing written to your configuration; the plugin’s README shows both.
The plugin sends nothing else on its own. Everything the plugin can do is a request Claude Code makes on your behalf while you are working on a design.
Signing in
You sign in through our sign-in provider (WorkOS). Signing in gives us neither your name nor your email address, and we store neither. The provider confirms who you are; on our servers your account is an opaque ID, and your projects are stored under it. The provider holds your email and sign-in history under its own privacy policy — that is how we can still connect an account to its owner when the law requires it, without holding your identity ourselves.
The studio
When you design with Permitude, the design itself is on our servers: each version that is checked, the resulting structure, and the drawings we produce from it. We use it to run your design, to check it, and to produce your drawing set, and we keep it so you can come back to it.
We use your designs, check results, and feedback to run the service and to fix and improve it. Reusing your designs beyond your own project — as examples, templates, or training material — happens only if you separately agree when we ask. One such choice exists today: the design gallery, described next. We do not sell your designs, and we do not share them with advertisers.
The design gallery
On each project, you can choose to share that project’s design with other customers in exchange for the same privilege: a project that shares may browse the design gallery — designs other customers shared the same way. The choice is offered when a project starts, it is optional, and declining changes nothing else — checking, drawings, and packets work identically either way.
Before a shared design enters the gallery, we remove the identifying details it carries: the designer’s name, the property address, the parcel number and site coordinates, and all free-form text. What remains — the geometry and structured data of the design — is the thing being shared. A gallery entry names no account and no project. We remove the fields and text that identify you, but we cannot make a design anonymous beyond that: its shape and dimensions are public.
Sharing is permanent. A shared design is public, other customers may reuse it in their own designs, and it cannot be recalled — including by deleting your account. The exact terms are presented on the page where you make the choice, and which version you accepted is recorded the way a terms acceptance is.
Your address
A permit drawing set names a property. If you give us an address, we use it to look up public records for that parcel and to place your project on it, and it appears on the drawings we produce for you — a permit set legally must name its property. Property records are public, so an address can identify a property’s owner; we treat the address on a project as identifying the customer who created it.
The designer’s name
Your design may contain the designer’s legal name. You provide it for one purpose: it prints on the drawings you adopt and sign. It lives inside your design, so it is kept and deleted with your designs, and the permanent records described below never contain it.
Paying
Payments are processed by Stripe. Your card details go to Stripe, never to us. Stripe tells us that a project’s packet was paid for, and we keep that record with the project. Stripe holds your payment details and receipt under its own privacy policy.
Records we keep even after deletion
When you accept the Terms of Service, we record which version you accepted, when, and under which account. When you buy a packet, we record the purchase. When you share a project’s design to the gallery, we record that choice. These records are permanent — they are the evidence that an agreement, a sale, or a sharing choice happened, and we keep them even if you later delete your account and designs. They contain no name or email; they name the account and, for purchases and sharing choices, the project.
Who touches the data
We run on a small set of providers: our sign-in provider (WorkOS), our payment processor (Stripe), and Cloudflare, which serves this site and our service endpoints. Each holds only what its job requires. Nobody gets your data for advertising, and we do not sell it.
Turning it off
Removing the plugin removes the hooks: /plugin uninstall permitude in
Claude Code. Nothing is sent after that. To silence it in one folder without
removing it, /plugin disable permitude.
To have your account and its designs deleted, write to support@permitude.com. Deletion removes your designs and drawings; the acceptance, purchase, and sharing records described above remain, and designs already shared to the gallery stay in the gallery — sharing cannot be undone.
Contact
Permitude LLC, a Pennsylvania limited liability company (entity number 0015814252, registered office 710 Parkview Blvd, Pittsburgh, PA 15215) — support@permitude.com. The Terms of Service are at permitude.com/terms.