Privacy & Data Handling Policy
Partcl, Inc.
Effective Date: August 20, 2026
Previous version: August 3, 2026
1. Introduction
This policy describes what information Partcl, Inc. ("Company," "we," "us," or "our") receives, how we use it, and how long we keep it, in connection with:
- Boson, our GPU-accelerated electronic design automation toolchain (synthesis, placement, clock-tree synthesis, static timing analysis, and related commands);
- other Partcl EDA tools that use the same licensing service;
- the licensing and billing service at
api.partcl.comand the customer portal; - software downloads; and
- the websites at
partcl.com
(collectively, the "Services").
It covers both personal information and information about your use of the Software, because for our customers the second question — what does Partcl learn about our designs? — matters at least as much as the first.
The short answer: your designs stay on your infrastructure. Boson runs on hardware you control. It does not transmit your design files to us, and we have no facility to receive them. What can reach Partcl is a small, fixed set of licensing, metering, and explicitly given product-feedback values, described below.
2. Operating modes
What leaves the machine depends on how the Software is licensed. Three modes matter:
| Mode | How it is licensed | What reaches Partcl |
|---|---|---|
Evaluation image (boson-eval) | A time-limited license bundle is baked into the image. No API key. No network path to Partcl is required. | Nothing from the running tool. Usage is enforced locally against that bundle. |
| Local licensing daemon | You run a Partcl licensing daemon on your network (PARTCL_METER_URL). Grant and finalize traffic stays on that daemon. | We see consumption when a license bundle is issued, renewed, or otherwise reconciled with our licensing service — not the design. Command-miss events (see §4.2) go to the daemon; they reach us only if that deployment is configured to report them. |
Cloud-metered / enrolled (boson-release and similar) | Each session authenticates with your organization's API key and talks to https://api.partcl.com. Without a working key and outbound HTTPS, metered commands refuse to run. | The fields in §4. Unlicensed and development builds that have no metering source configured send none of this. |
If you need fully disconnected operation beyond the evaluation image, contact contact@partcl.com.
3. Information you provide
- Account and contact information: the organization's legal name; the names, email addresses, and job titles of people you designate as administrators; API key labels; and billing contact details.
- License acceptance records: when an authorized representative accepts our license agreement, we record who accepted it, their stated name and title, the organization, the version and a cryptographic hash of the exact text shown, the time, the IP address the acceptance came from, and the browser user-agent string. This is evidence of consent and is retained as such; see §8.
- Payment information: billing details and payment method, processed by a third-party payment processor. We do not store full card numbers.
- Communications: what you send us in support requests, correspondence, and deliberate in-product feedback (
report_feedback; see §4.3). - Download and delivery: the contact details we use to send you a download link and, separately, a decryption key. Using a signed download URL records that the URL was redeemed (see §5).
4. Information the Software can transmit
This section is the complete inventory of what a Boson session can send to Partcl besides files you attach to an email. Nothing else is collected from the tool.
4.1 Licensing and metering (cloud-metered sessions)
When a cloud-metered session starts, and again around each metered run (for example update_timing, compile, or other commands that require a timing permit), the Software contacts api.partcl.com. Those exchanges carry only:
- API key identity — the Bearer key authenticates the request and attributes it to your organization. We store key identifiers and labels, not a reusable copy of the secret as issued.
- Client version — the Boson version string, sent as
client_versionand as the HTTPUser-Agent(boson/<version>), so we can tell which build ran. - Session ping — an authenticated read of your organization's plan, key label, and remaining gate-run balance (
GET /v1/usage/me). This records that a session connected. It burns no credits. - Run kind — a short label for the operation (for example
sta). - Billable size — an estimated gate-run count when a grant is reserved, and the actual count at settlement. For a single timing evaluation this is the post-map standard-cell instance count. Multi-evaluation runs multiply by the number of evaluations (for example, loaded corners). This is the unit we bill. It is a size, not a design.
- Design fingerprint — a 32-byte SHA-256 digest of three integers from the loaded design: cell count, net count, and pin count. It is not a hash of your netlist, RTL, constraints, or names. Two designs with the same three counts produce the same fingerprint. We use it to bind a grant to the run it was issued for, so a reservation cannot be replayed against different work.
- Grant identifiers and settlement — the server-issued grant id, and at finalize the actual gate-run count. A local crash-recovery journal on your machine (see §6) exists only so an interrupted run can be settled later; the journal is not uploaded as a file.
- Update check — if you run
boson updatewith an API key, we receive the client version and return whether a newer release exists for your organization's channel. If one does, we return a short-lived download link, a checksum, and a decryption key for that artifact.
We retain signed grant and settlement records so consumption can be re-verified later, by us or by you.
Standard HTTPS server logs for these requests also include IP address, timestamp, path, and status code.
4.2 Command-miss and wish telemetry (licensed builds only)
If you type a command Boson does not recognize, or you run boson wish <verb> [--why "…"], licensed builds may send a best-effort event:
- the command / Tcl proc name only — never argument values;
- optional nested name segments, a closest-known-command guess, and whether the resolver matched anything;
- the Boson version;
- the optional
--whynote, only if you supplied one.
This is product telemetry, not billing. It does not reserve or spend gate-runs. Delivery failure never fails your command. Unlicensed builds write the same record only to a local file (see §6).
Cloud-metered sessions POST this to api.partcl.com. Daemon-metered sessions POST it to your local daemon.
4.3 Deliberate feedback (report_feedback)
Feedback is given, never scraped. The only thing that produces a feedback payload is the shell command report_feedback. There is no background collection, no batching of shell history, and no automatic crash reporter.
The payload contains a category (bug, missing-feature, performance, docs, or other); your message; the Boson version; whether the session was interactive; and either the name of the last command plus a sanitized last-error string, or a -context note you typed instead. Free text is redacted on the machine before it is sent: design-file names (including basenames), hierarchical instance paths, escaped Verilog identifiers, and numbers with timing or electrical units are stripped or replaced. Each field is capped at about 4 KB. The exact payload is printed in the session. Interactive sessions ask for confirmation before sending.
Feedback uses the same API key as metering (POST /v1/usage/feedback). It burns no gate-runs and carries no design fingerprint. It is sent only when a cloud API key is configured; a daemon-only session has no feedback transport.
To turn the command and its invitations off:
set_app_var feedback_enabled false
4.4 What we do not receive from the Software
To be unambiguous about the boundary:
- We do not receive your design files — no Verilog, SystemVerilog, SDC, Liberty, netlists, LEF/DEF, SPEF, UPF, or reports.
- We do not receive design content: no module, cell, net, pin, or instance names; no timing, slack, power, or area figures; no file paths (feedback redacts those if they appear in text you typed).
- We do not receive command arguments — only command names, in the two channels in §4.2 and §4.3.
- We do not use your designs to train models. This is not a policy choice we could quietly reverse — we do not possess the data.
The fingerprint and gate-run count in §4.1 deserve an honest caveat. The fingerprint is stable for a given trio of counts, so we can see that some design of that size was run more than once, and a party who already holds a candidate design could test whether the counts match. The gate-run number tells us how large the run was. Neither reveals the contents of a design to anyone who does not already have it.
5. Websites, downloads, and cookies
5.1 partcl.com (this site)
The marketing site is a static site. When you visit it we, and our processors, see ordinary web-server and analytics data: pages viewed, referrer, approximate location derived from IP, browser and device type, and timestamps.
This site uses Google Analytics. Google sets analytics cookies and receives the page-view data above, under Google's terms. We use it to understand which public pages are read, not to advertise to you across the web, and we do not sell that data. You can block analytics cookies in your browser; the site still works.
The site also loads fonts from Google Fonts. That is a request from your browser to Google.
5.2 Customer portal and api.partcl.com
The billing and download portal uses cookies and similar technologies only to keep you signed in and to operate the site. We do not place advertising or cross-site tracking cookies on the portal.
5.3 Signed software downloads
Release and evaluation images can be delivered as an encrypted artifact behind a time-limited signed URL. Redeeming that URL is a request to our cloud storage (Google Cloud). Storage access logs can include the time of the download and the network address that fetched it. The decryption key is sent on a separate channel and is not part of that URL.
6. Data that stays on your machine
Boson writes local state that is not uploaded as part of metering:
- a crash-recovery journal of in-flight license grants, under the per-user state directory (
$XDG_STATE_HOME/boson/meteringor~/.local/state/boson/metering); - desire-path / wish records (
…/boson/desire-path/); - interactive shell history (
~/.boson_history), if you use the readline REPL.
Those files never contain your design. You can delete them; doing so does not delete billing records we already settled.
7. How we use information
- Authenticate you and your users, and verify your license and entitlements.
- Meter consumption, deduct credits, apply usage limits, and invoice.
- Show you remaining balance and available updates.
- Provide support, and diagnose problems you report or send via
report_feedback. - Learn which commands people look for that Boson does not have yet (names and optional wish text in §4.2).
- Detect and prevent fraud, abuse, and security incidents.
- Send technical and account notices.
- Understand how the public website is used (page-level analytics only).
- Comply with tax, accounting, and other legal obligations.
We use aggregate metering statistics — for example, total gate-runs processed across all customers, or the distribution of run sizes — to plan capacity and improve performance. Those aggregates are derived from the values in §4.1 and contain no design content.
We do not use design files, netlists, or RTL to train models, because we do not receive them.
8. How long we keep information
| Category | Retention |
|---|---|
| Usage and billing records, including signed grant and settlement records | 7 years after the end of the billing cycle they belong to |
| License acceptance records (§3), including the IP address and user-agent captured at acceptance | While the agreement is in force, then 7 years |
| Account and contact information | While the account is active, then 7 years to the extent it forms part of a billing record |
| Portal and API server logs, sign-in records, signed-URL redemption logs | 12 months |
| Command-miss and wish events (§4.2) | While useful for product planning, then deleted or aggregated; not treated as billing records |
| Feedback submissions (§4.3) and support correspondence | 3 years after the matter is closed |
| Website analytics | As configured in Google Analytics and under Google's retention settings |
The seven-year periods track the outer edge of tax, accounting, and contract-dispute exposure. After the applicable period we delete the information or irreversibly anonymize it, except where a longer period is required by law or where information is subject to a live legal hold.
9. How we share information
We share information with third parties only as follows:
- Infrastructure — licensing, billing, and download storage run on Google Cloud Platform in the United States.
- Website analytics and fonts — Google Analytics and Google Fonts, on
partcl.comonly (see §5.1). - Payment processing — billing details are handled by our payment processor.
- Legal requirements — where we are compelled by law or valid legal process.
- Business transfers — if we are involved in a merger, acquisition, or sale of assets, information may transfer as part of that transaction, subject to this policy.
- With your instruction — where you ask us to.
We do not sell personal information, and we do not share it for advertising.
10. Security
We implement technical and organizational measures appropriate to the sensitivity of what we hold, including encryption in transit and at rest, access controls and authentication, signed billing records, and hardware-backed key management for the keys that sign license grants. Cloud-metered builds verify grants against a verification key baked into the binary at compile time. No method of transmission or storage is perfectly secure, and we do not claim otherwise.
11. Your rights and choices
You may ask us to access, correct, export, or delete personal information we hold about you by contacting contact@partcl.com. We will respond as required by applicable law.
Limits worth stating plainly:
- License acceptance records and billing records cannot be deleted on request for as long as they are needed as evidence of the agreement or to meet our legal obligations. They are retained under §8 and then deleted.
- Some records are append-only by design, because their value is that they cannot be quietly rewritten. We can delete them at the end of their retention period; we cannot alter them in place.
- You can disable in-product feedback with
set_app_var feedback_enabled false. You can decline to runwishwith a--whynote. Evaluation images and unlicensed builds do not send §4 data to us at all. - You may opt out of promotional email using the unsubscribe link in those messages. This does not affect technical or account notices.
- You may block analytics cookies on
partcl.comin your browser.
12. International data transfers
Information may be transferred to and processed in countries other than your own. Where personal data is transferred out of the European Economic Area, the United Kingdom, or Switzerland, our infrastructure sub-processors provide appropriate transfer safeguards, including the EU/UK/Swiss Standard Contractual Clauses, the EU-U.S. and Swiss-U.S. Data Privacy Frameworks, and the Swiss Federal Act on Data Protection. Our licensing service, usage and billing records, and download storage are hosted on Google Cloud Platform in the United States.
13. Children's privacy
Our Services are sold to organizations and are not directed to individuals under 13. We do not knowingly collect personal information from children under 13, and will delete any that comes to our attention.
14. California privacy rights
If you are a California resident, the California Consumer Privacy Act gives you rights to know what personal information we collect, to know whether it is sold or disclosed (we do not sell it), to access and delete it, and to equal service and price. Contact contact@partcl.com to exercise them.
We do not sell personal information and we do not share it for cross-context behavioral advertising.
15. European privacy rights
If you are in the European Economic Area, the United Kingdom, or Switzerland, you have rights under the GDPR and equivalent laws to access, rectify, erase, restrict processing of, port, and object to processing of your personal data, and to withdraw consent. Contact contact@partcl.com to exercise them.
Our lawful bases are performance of a contract (licensing, metering, billing, support, and delivering software you ordered), legitimate interests (security, fraud prevention, aggregate capacity planning, product planning from command-miss names, and operating the public website), and compliance with legal obligations. Opt-in wish text and report_feedback messages are processed because you chose to send them.
16. Changes to this policy
We may update this policy. When we do, we will post the new version at https://partcl.com/privacy and update the Effective Date above, keeping a pointer to the version it replaced. Material changes to how we handle information will be notified to account administrators. Changes take effect when posted.
This policy describes our practices; it is not a licence to your designs, and it does not grant us rights in them. Your rights in your designs are governed by your license agreement, under which your designs remain your confidential information and your property.
17. Contact us
Partcl, Inc. Email: contact@partcl.com Website: https://partcl.com This policy: https://partcl.com/privacy