Privacy
You work on and save your drawings on your computer
Wiring data belongs to you, your company and your customers. Pinvane does not automatically send usage statistics or error reports, and it has no built-in cloud saving. Ordinary drawing, editing and exporting happen on your computer, and the drawing data of that work is not sent to Pinvane's servers.
When you use the AI features, your request and design information go to the AI provider you chose. When you turn on the phone view, a drawing goes to a device on your local network. External AI apps and the sync folders you choose follow their own settings.
What can leave your computer
The list
| What | When | What is sent | To |
|---|---|---|---|
| Ordinary drawing, editing, exporting, the part library | — | No drawing data is sent | — |
| Usage statistics, automatic error reports, cloud saving | Never — Pinvane has no such feature | — | — |
| License check paid version | When you activate, check in or release a device, and an automatic check at most once a day | Request body: your license key and a one-way device hash (the computer's ID itself is not sent). “Release all devices” sends only the key. | Only our configured license server — no proxy from environment variables, redirects refused. Its host also sees connection data such as your IP address and the time |
| Update check release preparation | Only when you ask (Help → Check for updates, or the command line) — never at start-up or on a schedule. The update public key of the release and the published file are checked in the release procedure; until then every check says it could not check. | A request for public update information. The request carries no app version, license, device ID or project. Pinvane only checks update information — it never downloads or installs an installer by itself. | This website — the server that handles the connection processes your IP address, the time and the requested path |
| AI window off by default | Only after you turn it on, store your own API key and confirm the request card | Before anything is sent, the request card shows the company, the request and initial design facts that go and their size, what is never sent, the tools the AI may use with their argument names, and the top-level field names tool results may carry. Your request goes as you typed it, unfiltered. The initial design facts are prepared from your selected scope (the drawing you asked about, or only your selection). Later tool results are assembled from per-tool allowed fields. Pinvane checks the tools and top-level argument names offered for this request, and compares the part IDs in connection ends (from, to) against the approved scope. Nested structures are checked to a depth of 8; deeper structures are refused. Parts and wires added by the AI in this request join the scope for later calls. Other nested values are not checked against the scope. The allowed fields are, for example, ids, names, part numbers, makers, terminal names and voltages, wire labels, colours, gauges, functions, evidence grades, the two connected ends and positions; tool results may also include check summaries and proposal information. Pictures, documents, title-block names, license data, drawing-text, note, author and evidence-wording fields and file-path fields are not among them. Text you wrote into a field that is sent, such as a name or a label, can also go; path-like text in it is masked, but this does not promise to remove every path or personal detail. A tool error goes as a fixed code and sentence instead of its own text. Shared part-library search results can also go to the AI company. Each shared-library part row is rebuilt from a definition on Pinvane's shipped list whose content fingerprint matches. A row may contain the library ID, name, category, prefix, terminals, pins and size. | The AI provider you chose (Anthropic, OpenAI or Google), directly from your computer — not through us. A redirect to another address is refused. |
| Problem report | Only when you ask — Help → Report a problem…, the command line or MCP | Pinvane sends nothing to a support server. The automatic part is made from the app version, data format, build, operating system, window browser, screen language, plan, and fixed error codes with module, line and count; what you write is attached separately. You read it and send it yourself. When an AI app makes the report through MCP, the report text also goes to that AI app. | Wherever you send it (copy, your own mail app or a saved file) |
| AI app connection (MCP) | While your AI app uses Pinvane | MCP's default connection is standard input and output on this computer; the optional HTTP mode listens on this computer only, with a token. The person sets the boundary for project data: it starts with the default Pinvane folder and folders added through pinvane mcp-allow or an environment variable (a path an AI passes as a tool argument is not added), and a connection started without --project narrows to the real path of the first project it opens or creates. The shared library is separately readable; writing to it needs separate permission. This boundary does not apply to the screen, the ordinary command line or the in-app AI window, and an AI program with shell access can run mcp-allow with the person's own rights. For an AI to accept a proposal by command, a separate setting (off by default) must be on; Pinvane then checks the server-made connection identity, the session that made the proposal, the real project path, the proposal ID and the revision (acceptance by a person on screen is separate). | Your AI app — it may send what it receives to its own service, under that app's settings |
| Phone view off by default | Only while you have it on — up to 30 minutes, and it ends when the editor closes | One drawing, read-only | Devices on your local network that have the address and the token |
How it is built
- The editor and the viewer are served on this computer (127.0.0.1) and load their page resources locally; a content-security policy limits the page's requests to other sites, and requests that come from other sites are refused.
- API keys and the license key are stored in Windows Credential Manager, and used to sign in to the AI provider and to our license server.
- Projects you receive: a project bundle is unpacked in stages into a temporary folder beside the destination, checking file names and sizes. Names that point outside the project folder, to a drive, to a network share or to a Windows device are refused; more than 20,000 files, 64 MiB for one file or 512 MiB of unpacked content in total stops it; and files are moved to the final destination only after all members have passed the checks.
How we test it — and what the test does not cover
In the 2026-10-20 run, our network-audit tests passed: a scripted local workflow (new project, editing, exports, the viewer) recorded no connection beyond this computer; the license request body carried only the key and the device hash (only the key when releasing all devices); with the AI window off nothing was sent, and with it on only the chosen provider's address was tried. The update check made exactly one request, without an app version, and the problem report made no connection. Security tests in the same run confirmed, for the cases tested: requests from other sites are refused once and go no further; the allowed-field assembly of the AI window's facts and tool results, fixed error codes instead of tool error text, and the request card's lists made from the code; out-of-scope or hidden tool arguments are refused; part IDs in connection ends (from, to) are compared against the scope; shared-library rows are rebuilt from a definition with a matching fingerprint; an MCP connection refuses reading, writing and opening other projects outside the allowed folders; the path, note, author and evidence data put into the test were left out; provider and license redirects are refused; bad file names and over-limit sizes in a project bundle are refused before anything is moved to the final destination. We run them again before each release.
How it observes: audit hooks inside the Pinvane (Python) process plus that process's socket table; in the network-audit part the app's browser window was not started, and the AI test stops each connection before it reaches the real AI company (no TLS or HTTP is completed). Not covered: the browser program itself, other programs on your computer, opening exported files in other apps, a real phone or network setup, the real pinvane.com and license server in operation, and your clipboard and mail app after you copy or send a report.
This website
The site's code has no cookies, analytics, trackers or resources from other sites. The only setting it stores is light or dark, in your own browser. The web host processes connection data such as your IP address to deliver pages. Sales are being prepared, and this site does not load Paddle's checkout script yet. When sales open, the Pricing page will load Paddle.js from Paddle to open Paddle's checkout window; approval to use it for this product and the connection are not yet confirmed. Paddle's own cookie and privacy policies apply to that script and window.
Terms, refunds, third-party notices
Terms · Refund policy · Third-party notices. The full privacy policy is below. Questions: contact.
Privacy policy
Privacy policy (full text)
Version 1.0 · effective 2026-11-22
In one line — we do not receive your drawings. Pinvane does not send your drawings, design data or part libraries
to our servers. It has no automatic usage analytics, no automatic crash reporting and no cloud saving of ours. App license-check request bodies contain the license key and device hash; releasing all devices sends only the key. Purchase, claim and support processing are described below. Drawing data leaves
your computer only through features you switch on (section 3 — AI window, phone view) and AI programs you connect. A
network-audit test of the stated work flow checks this on every release (what it does not cover:
tools/wiring/pinvane/PRIVACY.md section 4).
1. What we process and why
| when | what | who receives it | why | kept |
|---|---|---|---|---|
| activating, releasing, and at most one check-in a day | license key; device hash (a one-way value made from this computer's id and the key — the id itself is never sent, and the hash differs per license so licenses cannot be linked) | our license server | pass status, the 3-device limit | what the license server keeps: a hash of the key, the device hash, first / last check-in date, pass status and period, and the Paddle order (transaction) id (a newly issued key before it is claimed: next row). A device record is deleted when you release the device; a license record 1 year after the license ends |
| payment | name, e-mail, billing address, payment method, etc. | Paddle.com (our reseller and Merchant of Record) | payment, tax, receipts, refunds | under Paddle's privacy policy. In our Paddle seller account we can see what support and legal duties need (e.g. e-mail, country, order number); we do not copy it into the license server |
| right after purchase | the Paddle transaction id and a one-time claim token made by the purchase page (kept only in the browser tab you buy in, and removed once the key is shown) — the payment notice supplies a hash of the claim token; a claim request supplies the transaction ID and the token itself, which the server checks against the stored hash | our license server | to show your license key once on the purchase-complete page (only to the page holding the token) | the license server checks the claim token linked to the purchase. The plaintext key is deleted once the purchase-complete page has fetched it, after 5 wrong tokens, or after 60 minutes (the deleted space is overwritten), and it is never put in a backup. If the payment notice carries no claim token, no plaintext key is kept at all (support issues the key again against your Paddle receipt) |
| when you e-mail support | what you write (sender address, name, subject, body, attachments) | us — mail to support@pinvane.com is passed by Cloudflare Email Routing to our company mailbox (Google Workspace) and kept in that inbox (section 4) | to answer | 3 years after the answer (the period the Korean E-Commerce Act Enforcement Decree Art. 6 sets for complaint and dispute records) |
| when you apply for the free student / teacher plan | what your application says and your school e-mail address, or the photo of your student or teacher ID you send | us (the mail takes the same route as a support mail — section 4) | to check eligibility for the free plan (a person checks it) | an ID photo is not kept after the check and is deleted within 7 days, from the company mailbox too; the rest of the application is kept like a support mail |
| when you open this website | IP address, time, requested path | the website hosting company (Cloudflare, Inc. — Cloudflare Workers static assets) | to serve the page and keep it secure | under the host's policy. The site's own code sets no cookies and uses no trackers. While sales are open, the Pricing page loads Paddle's checkout script (Paddle.js) from Paddle and the Buy buttons open Paddle's checkout window — Paddle receives connection data such as your IP address when the script loads, and the script and the window follow Paddle's cookies and policy. The step right after purchase is the "right after purchase" row above |
The current license-server code's records and database do not store IP addresses, names, e-mail addresses, program versions or file names (its request log is kept in memory only, the last 1000 requests — a fixed route name and the result code, no address, content or query string). Request limits count hashes of the key or transaction id in memory only, per minute, and never write them to disk (they are gone when the server restarts). The license server runs on our own computer in the Republic of Korea; outside requests reach it only over HTTPS through Cloudflare Tunnel, run by Cloudflare, Inc. (United States). Cloudflare processes the IP address and the request content while it delivers the request (section 4).
1-1. Retention and deletion: retention is as in the table. If you use the Free plan or the trial without a stored license key, the Software sends no automatic license check. Running an activate or release-device command yourself is separate. Records that the law says must be kept (Korean E-Commerce Act Enforcement Decree Art. 6: contract and withdrawal records, and payment and supply records, 5 years; complaint and dispute records 3 years) are mainly held by Paddle as seller of record; on our side there are only support mails and license records. When retention ends we delete the license-server record and delete the support mail.
2. What is never sent
To us: drawings, design data, part definitions, pictures, exports, project names, folder paths, computer name, user name, usage statistics, crash reports (automatic). The app's screen runs on this computer (127.0.0.1) and its content-security policy stops the page from loading outside resources (it limits the page only — the browser itself and outside AI programs are their own). The features of section 3 send what that section says when you switch them on.
3. Features you switch on
- AI window (off by default): only when you turn it on, store your own API key and send from the request card. The card shows the company, the request and initial design facts that go and their size, what is never sent, the tools the AI may use with their argument names, and the top-level field names tool results may carry. Your request goes as typed (unfiltered). The initial design facts are prepared from your selected scope (that drawing, or the parts and wires you selected); later tool results are assembled from per-tool allowed fields, and both go from your computer straight to the one AI company you chose (Anthropic, OpenAI or Google). The allowed fields are, for example, ids, names, part numbers, makers, terminal names and voltages, wire labels, colours, gauges, functions, evidence grades, the two connected ends and positions; tool results may also include check summaries and proposal information. Pictures, documents, title-block names, license data, drawing-text, note, author and evidence-wording fields and file-path fields are not among them. Text you write into a sent field (a name, a label) can also go; path-like text in it is masked, which does not promise to remove every path or personal detail. A tool error goes as a fixed code and sentence instead of its own text. Shared-library search results can also go — each shared-library part row is rebuilt from a definition on Pinvane's shipped list whose content fingerprint matches, and may contain the library ID, name, category, prefix, terminals, pins and size. Pinvane checks the tools and top-level argument names offered for this request and compares the part IDs in connection ends (from, to) against the approved scope; nested structures are checked to a depth of 8 and deeper ones are refused; parts and wires the AI adds in this request join the scope for later calls; other nested values are not checked against the scope. Never through our servers (a redirect to another address is refused); that company's policy applies. API keys are stored in Windows Credential Manager and used to authenticate with your chosen AI provider. The consent record keeps metadata such as provider, model, scope, size, fingerprint and tool count, rather than the request or design content.
- AI window — generative-AI notice (written to follow Korea's PIPC privacy-policy guideline, 2026.4 generative-AI appendix — the guideline text has not yet been checked directly; AI Basic Act Art. 31; EU AI Act Art. 50): (1) The AI window and the tools it uses are answered by the generative AI model of the company you chose. (2) What you type, the design facts sent and the AI's answers do not reach our servers, so we do not receive, collect or use them to train AI. (3) Whether that AI company uses your input to improve its models depends on its terms and settings (some free tiers may use it or let people review it); you can decline by choosing that company's no-training setting or a paid tier, or by not switching the AI window on. (4) It is better not to type personal data such as names and contact details, or secrets. (5) Tell us about inappropriate or suspicious answers by support e-mail or Help → Report a problem, and you can also report to that AI company. (6) The AI-related records that stay on this computer are described in section 6.
- AI-app connection (MCP): Pinvane talks to AI programs such as Claude, Codex or Gemini over standard input/output
on your computer (no network on Pinvane's side; the optional
--httplistens on 127.0.0.1 with a token). You set the boundary for project data: with--projectit uses that folder plus the folders you added; without it, it starts with your Pinvane folder and the folders you add withpinvane mcp-alloworPINVANE_MCP_ALLOW(a path an AI passes as a tool argument is never added), and narrows its default boundary to the real path of the first project it opens or makes, while the folders you added remain. The shared library is separately readable and writing to it needs separate permission; Pinvane-made temporary copies for previews and comparisons are also used during those operations. Common file-access points and the final export folder are checked by real path. This boundary does not apply to the screen, the ordinary command line or the in-app AI window, and an AI program with shell access can runmcp-allowwith your own rights. That AI program can send what it reads to its company — that is between you and that company. - Phone view (off by default): while on (30 minutes by default) it shows one drawing read-only to devices on your local network that have the QR's address and token. It listens on a private address of this computer and opens no router port; whether that address can be reached from elsewhere depends on your network.
- Update check (built —
pinvane update --check· Help → Check for updates): only when you ask, one signed public update file is fetched from pinvane.com and compared on your computer. The request carries no app version, license, device identifier or project; the server handling the connection processes the IP address, time and request path. No installer is downloaded or installed. Only the last accepted file's serial and issue time and the check time stay on your computer (update.json). - Problem report (built —
pinvane report-bug· MCP · Help → Report a problem): Pinvane only builds a report from a fixed list (version · build · Windows version · screen language · plan · fixed error codes with module and line) and shows it; it never sends it. You read and edit it and send it yourself (copy · your own mail app · a file). Made through MCP, the report also reaches the AI app you connected. The error log on your computer (errors.jsonl) keeps only time · code · module · line · version, for 7 days and at most 200 lines.
4. Sharing, processors, transfers abroad
- We do not sell personal data or use it for advertising. We do not provide personal data to third parties (except where the law requires it).
- Paddle (our reseller and Merchant of Record — the Paddle entity that handles your order can differ by region and is named on your receipt and checkout, e.g. Paddle.com Market Ltd, UK) receives payment data directly; transfers follow Paddle's policy. Card numbers and other payment-method data are handled by Paddle directly; we process the purchase and pass information needed to provide the license and support, and what the Paddle seller screen shows (e-mail, country, order number, etc.). The Paddle entity's country of incorporation (e.g. Paddle.com Market Ltd: United Kingdom), and the countries where and the way in which Paddle directly collects and processes Korean users' data, follow Paddle's privacy policy (linked from the checkout).
- License-server hosting: the license server and its database are on our own computer in the Republic of Korea. Outside requests are received over HTTPS by Cloudflare Tunnel, run by Cloudflare, Inc. (United States), and passed on to our server — at each activation, release, check-in, key claim right after purchase and Paddle payment notice. While passing them on, Cloudflare processes the request content and the IP address (table below).
- Notice of transfer abroad (Korean PIPA Art. 28-8(2) — Cloudflare's handling of the requests it passes to the license server, processing entrusted to perform the contract):
| item | content |
|---|---|
| recipient (name, contact) | Cloudflare, Inc. · privacy contact privacyquestions@cloudflare.com |
| country, time, method | the United States (Cloudflare, Inc.) and the countries of the Cloudflare data centers a request passes (near you and near our server) · at each activation, release, check-in, key claim and payment notice · over HTTPS |
| items | in requests, the license key (the plain key is sent only with the request; the license table stores a key hash) and the device hash; in responses, the signed license file (pass status, period, check-in dates); for the purchase step, the transaction id, the claim token and the key delivered once; Paddle payment notices (transaction data, the claim-token hash); and the IP address. On our side data is stored only on the license server in Korea (table in section 1) |
| purpose, retention | to deliver requests safely to our license server (pass status, the 3-device limit, issuing keys) / under Cloudflare's privacy policy (our server's retention: table in section 1) |
| how to refuse, effect | if you store no license key the Software sends no automatic license check (running an activate or release-device command yourself is separate); the paid license cannot be verified and you use the Software within the Free plan limits |
- Support mail route: mail to support@pinvane.com is received by Cloudflare Email Routing, run by Cloudflare, Inc. (United States), and passed on to our company mailbox, which Google keeps in Google Workspace (mail forwarding and storage entrusted to them). Cloudflare states that Email Routing does not store or access the mail it routes (Cloudflare developer documentation); a routing activity log (the action taken and the SPF / DKIM / DMARC results, among others) stays in our Cloudflare account. Student / teacher applications by mail take the same route.
- Notice of transfer abroad — support mail (Korean PIPA Art. 28-8(2) — mail forwarding and storage, processing entrusted to answer you and perform the contract):
| item | mail forwarding — Cloudflare Email Routing | company mailbox — Google Workspace |
|---|---|---|
| recipient (name, contact) | Cloudflare, Inc. · privacy contact privacyquestions@cloudflare.com | Google (the Google Workspace contracting entity for customers with a Korean billing address: Google Asia Pacific Pte. Ltd., Singapore) · Google privacy team googlekrsupport@google.com |
| country, time, method | the United States (Cloudflare, Inc.) and the countries of the Cloudflare data centers the mail passes · each time you e-mail support · e-mail transfer (SMTP) | the countries of Google's data centers (the United States and others — Google's data-center locations page) · when the mail arrives and when we reply · e-mail transfer (SMTP) and storage on Google's servers |
| items | the whole mail (sender address, name, subject, body, attachments), only while passing it on — Cloudflare states it does not store it; the routing activity log | the whole mail (sender address, name, subject, body, attachments) and our reply |
| purpose, retention | to pass the mail to our company mailbox / the activity log under Cloudflare's policy | to answer you and check student / teacher applications / deleted from the inbox when the period in the table in section 1 ends (3 years after the answer; ID photos within 7 days) |
| how to refuse, effect | if you do not e-mail support nothing is transferred; you then cannot get an answer by e-mail | as on the left |
- Requests to the AI company you chose go straight from your computer to that company (never through our servers). We do not receive or keep their content. Where that company is located and how it handles the data follow its policy.
5. Your rights
You may ask to see, correct, delete or stop processing your data. As the license server holds no names or e-mail addresses, we find your records by your license key (or the order number on your Paddle receipt). You can delete a device record yourself at any time with "release this device" in the Software. How: ask by support e-mail and we act and tell you the result within the legal period for the kind of request. EU requests: in principle within 1 month of receipt, and if the law-permitted extension is needed we tell you the reason within that period. You may also act through a representative. If you think your rights were infringed you can ask these bodies for help: the Personal Information Dispute Mediation Committee (1833-6972 in Korea, www.kopico.go.kr), the KISA Privacy Infringement Report Center (118 in Korea, privacy.kisa.or.kr), the Supreme Prosecutors' Office (1301 in Korea, www.spo.go.kr) and the Korean National Police Agency (182 in Korea, ecrm.police.go.kr).
6. What stays on your computer
%APPDATA%\Pinvane (preferences, license file, trial start date), Windows Credential Manager (license key, AI keys),
and the project folders you choose. Uninstalling keeps them; you can delete them yourself.
AI-related records: while the AI window handles a request the conversation is kept in memory and on screen, and the current
implementation does not save a full transcript to a file. However, history/ops.json in the project folder keeps consent information and
an action log, and history/changesets/*.json keeps the AI's change proposals and explanations. When a proposal is finalised, the first part
of your request (up to 120 characters) can go into the explanation, and a proposal contains the design change itself. These records are not
deleted automatically after any period and may remain in the project and its backups even after uninstalling. You manage keeping and deleting
projects and backups. This describes records the Software saves deliberately; it does not mean there are no traces in your browser profile or OS temporary storage.
7. Privacy contact
Seo Sang Weon (representative) · support@pinvane.com · GAONJH, Republic of Korea. The representative also handles privacy matters in person.
8. Changes
Announced 7 days before they take effect (30 days if unfavourable to you) on the website and in the Software. Effective date: 2026-11-22 (version 1.0).
9. Children
The Software is a professional tool for people aged 18 or over. We do not knowingly collect personal data of children under 14 and delete it as soon as we learn of it. If child data was entered, ask for deletion by support e-mail.
10. Security measures (PIPA Decree Art. 31)
- The license table stores a key hash. The claim-waiting table, which lets the key be handed over once right after purchase, holds the plain key for at most 60 minutes and then deletes it (the deleted space is overwritten); this table is never put in a backup (table in section 1). This server code's request log keeps no address, content or query string (hosting and proxy logs are separate — section 1).
- Paddle payment notices are processed only after their signature is verified, and the license file is checked for tampering by signature. The license key and AI keys on your computer are kept in Windows Credential Manager (section 6).
- The Software is built to accept only HTTPS addresses for external license requests. The license server takes requests only inside our computer
(127.0.0.1); from outside, only HTTPS requests on the fixed path (
/v1/) reach it through Cloudflare Tunnel — no inbound port is opened. The license database is backed up every day, encrypted (AES-256-GCM).
11. For users in the EU and UK (summary of GDPR Art. 13)
- Controller: for license-server data (key hash, device hash, check-in dates, pass status) GAONJH (Republic of Korea) is the controller. Paddle processes payment data independently. We have not appointed an EU representative under GDPR Art. 27; users in the EU and UK can send questions and requests to support@pinvane.com.
- Basis: license checks and pass status, support requests about a pass or purchase, and the student / teacher check you ask for — performance of the contract or steps you ask for before it (Art. 6(1)(b)). Other support answers, website access data, security and keeping records under Korean law — legitimate interests (Art. 6(1)(f): answering you, running the site and server safely, and meeting our legal duties). Hashes are treated as personal data because combined with other data they can identify a person. We have not confirmed a separate basis for UK users.
- Retention, recipients, transfers to third countries: as in the tables in sections 1 and 4. The EU has found Korea adequate (decision of 2021-12-17, maintained at the first periodic review on 2026-07-23 — Commission notice). The license server is in Korea; requests reach it through Cloudflare's network. Support mail passes through Cloudflare Email Routing and is kept in Google Workspace (section 4).
- Rights: access, rectification, erasure, restriction, objection, portability, and the right to complain to your supervisory authority. Whether giving the data is required: the key and device hash are needed to verify a paid license. The license status is decided automatically — whether this is a decision within GDPR Art. 22 is under review.