Privacy in the technical preview

Last updated November 13, 2026

Pictured: TP-C011 electronics enclosure shell, a synthetic test part from the benchmark.

TruePart has not yet published its full privacy policy. Until it does, this page states what the public preview at truepart.ai does and does not do with data. We will not accept customer drawings through the public site until the full policy is published; uploads are open only to invited pilot accounts, as described below.

What this site collects

No public sign-up or uploads are offered. Invited pilot participants have accounts (see below).
TruePart’s own site code sets a few first-party cookies and keeps a few values in your browser, listed under Cookies and browser storage. Only with your consent does it record first-party usage events (described under Site usage events) or, on some public pages, load advertising and analytics tags from other companies (described under Advertising and analytics tags), with one exception: outside the EU and EEA, the United Kingdom and Switzerland, it loads a web-analytics tag on its public pages unless you opt out (see Web analytics by default). You give, refuse or change consent, and opt out, in the site’s banner and under Your Privacy Choices; without consent, and outside that exception, the site does neither. Wherever you are, it also counts how often its public pages are viewed, without cookies or identifiers and keeping only totals (see Page counts without cookies). Pages with a form also load a bot check from our content-delivery provider, described under Contact forms.
The site is delivered through our hosting and content-delivery providers. What your browser exchanges with the site’s pages and the pilot workspace passes through them, including sign-in details and, for pilot users, the project information shown in the workspace. They process standard request data (such as IP address, browser user agent, and the page requested) to deliver and protect the site. To stop attacks that use stolen passwords, the content-delivery provider checks sign-in attempts against lists of passwords known to have leaked, and can briefly block an address that keeps using them. The content-delivery provider adds its own security script to the pages to protect them from automated abuse, and can set a short-lived security cookie.
If the page breaks one of the site’s security rules (its content security policy), your browser can send TruePart an automatic report. The server logs the rule, the address it blocked, the page’s path and, when the report names them, the script that caused it and its line; nothing else from the report, for 30 days.
If you send a contact form or email us, we receive your message and address and use them to read and answer it, and to limit abuse as described under Contact forms.
If you request access to the Technical Preview, we store your request in TruePart’s own database to review it (see Requests for access).
Software agents can read TruePart’s public information through its agent interfaces, and can register for a higher rate limit (see Agent interfaces).

Cookies and browser storage

The site asks for your consent before it sets or reads anything optional. The first time you open one of its pages, a banner at the bottom of the page offers three equally prominent choices: Accept all, Essentials only (every optional category off), and Customize, which opens the site’s preference center so that you can decide each category on its own. Every optional category is off until you turn it on, and until you choose, nothing optional runs. You can change your choice at any time with Your Privacy Choices or Cookie settings, linked from every page (see Your Privacy Choices). Outside the EU and EEA, the United Kingdom and Switzerland, the banner is a notice with OK and Your Privacy Choices, and the web-analytics tag runs until you opt out (see Web analytics by default); every other optional category is off until you turn it on. Nothing optional can run without JavaScript in your browser. The page counts described under Page counts without cookies are not one of these categories: they set and read nothing in your browser, and they are never made when your browser sends Global Privacy Control or Do Not Track.

The optional categories, and what each one allows:

Analytics: TruePart’s own usage events (see Site usage events), and the tags of a web-analytics service and a session-analytics service (session recording) on the pages where tags may load. Outside the EU and EEA, the United Kingdom and Switzerland, the web-analytics tag also runs before a choice, until you opt out.
Advertising measurement: the tp_attr cookie, which keeps where your visit came from; the tags of the web-analytics company’s tag manager and advertising service, and, together with Ad personalization, of six other advertising platforms (social-network, professional-network, discussion-site, short-video and search advertising); the use of the web-analytics company’s tags for advertising (its “ad storage” and “ad user data” settings); and the reports TruePart’s servers send about a request for access (see Advertising and analytics tags).
Ad personalization: lets the advertising services use your visit to build advertising audiences and to personalize the ads you see on other sites. The site passes this choice to the web-analytics company’s tags, and TruePart’s servers pass it with their reports to that company. The six other advertising platforms cannot receive it separately, so the site’s code loads their tags, keeps their identifiers with a request for access, and lets TruePart’s servers report to them only when you allow both Advertising measurement and Ad personalization. Turning it off stops their tags from loading, removes their cookies under this site’s address, and stops further reports to them; what a platform collected while its tag was allowed is then that platform’s to handle.

The banner does not ask about what the site needs to work: the sign-in cookies, the tp_consent cookie that keeps your choice and the tp_consent_sent value that notes whether TruePart’s service has received it, the tp_notice cookie that notes you saw the web-analytics notice, the theme you pick, and our content-delivery provider’s security cookie and the forms’ bot check (see Contact forms). None of the site’s tags or cookies is in a functionality or preferences category.

The site works out your country, and in the United States and Canada your state or province, from the location our content-delivery provider reports for your connection. It uses that location to choose the banner’s wording and the set of rules (a profile) your choice is recorded under: the EU and EEA, the United Kingdom, Switzerland, California, the other U.S. states and DC, Québec, the other Canadian provinces and territories, Brazil, the rest of the world, or an unknown location. In the EU and EEA, the United Kingdom and Switzerland, nothing optional runs until you consent. In every other profile (the United States, Canada, Brazil and the rest of the world), the web-analytics tag runs on the public pages until you opt out, and everything else waits for your consent. Places with their own country code but EU-style rules (the EU’s overseas regions with their own code and the Åland Islands, Gibraltar, Jersey, Guernsey and the Isle of Man) are treated like the EU: nothing optional runs until you consent. When your location is not known (it is missing or cannot be read), the site uses the most protective profile, which also asks first. A country whose state or province matters but is not reported gets that country’s most protective profile. The page counts are made in every profile (see Page counts without cookies). Your choice is kept for 12 months. The banner asks again after that, when the version of this notice changes, or when you visit from a location with a different profile; until you choose again, nothing optional runs (where the web-analytics tag runs by default, only that tag), and an earlier opt-out still applies while your browser keeps it.

If your browser sends Global Privacy Control or Do Not Track, the site treats the signal as your refusal of every optional category, whatever you chose before: it shows no banner, runs nothing optional, makes no page count, and its preference center says the signal is honored. Where the web-analytics tag runs by default, it is your opt-out of that tag.

Every cookie and stored value, with its category and how long it is kept:

tp_consent: Strictly necessary · 12 months Your consent choice (see The record of your choice, below).
tp_notice: Strictly necessary · 12 months Notes that you saw the web-analytics notice (its version only).
tp_consent_sent (local storage): Strictly necessary · until you clear this site’s data Which of your choices TruePart’s service has confirmed receiving.
tp_id, tp_at, tp_rt, tp_staff, tp_pkce, tp_ch, tp_ended, tp_revoke: Strictly necessary · from two minutes to 30 days Sign-in and session security, set only once you start to sign in.
Security cookie: Strictly necessary · short-lived, set by our content-delivery provider Protects the site from automated abuse.
tp_theme: Your setting · one year The theme you chose with the theme button; set only when you press it.
tp_sid (session storage): Analytics · until you close the tab The random session identifier of TruePart’s usage events.
tp_ft (local storage): Analytics · until you clear this site’s data or the site removes it The campaign and referring site of your first visit that had them.
tp_attr: Advertising measurement · 90 days Where your visit came from: campaign details and click identifiers.
_ga, _ga_<id>, _gid, _gat…: Analytics; outside the EU and EEA, the UK and Switzerland also before a choice, until you opt out · set by the vendor; duration per the vendor The web-analytics service’s cookies under this site’s address.
_clck, _clsk: Analytics · set by the vendor; duration per the vendor The session-analytics service’s cookies under this site’s address.
_dc_gtm_<id>: Advertising measurement · set by the vendor; duration per the vendor The tag manager’s cookie under this site’s address.
_gcl_…, _gac_<id>: Advertising measurement · set by the vendor; duration per the vendor The web-analytics company’s advertising cookies under this site’s address.
_fbp, _fbc: Advertising measurement and Ad personalization · set by the vendor; duration per the vendor A social network’s advertising cookies under this site’s address.
li_fat_id: Advertising measurement and Ad personalization · set by the vendor; duration per the vendor A professional network’s advertising cookie under this site’s address.
_uetsid, _uetvid, _uetmsclkid: Advertising measurement and Ad personalization · set by the vendor; duration per the vendor A search engine’s advertising cookies under this site’s address, which its tag also copies into local storage (_uetsid, _uetsid_exp, _uetvid, _uetvid_exp).
_rdt_uuid: Advertising measurement and Ad personalization · set by the vendor; duration per the vendor A discussion site’s advertising cookie under this site’s address.
_ttp, _tt_enable_cookie: Advertising measurement and Ad personalization · set by the vendor; duration per the vendor A short-video service’s advertising cookies under this site’s address.
_twclid: Advertising measurement and Ad personalization · set by the vendor; duration per the vendor Another social network’s advertising cookie under this site’s address.

TruePart’s own site code sets these first-party cookies, on this site only:

tp_consent (12 months): your consent choice, as described under The record of your choice. The site’s code sets it when you choose in the banner or the preference center, and replaces it each time you change your choice. Your browser sends it with each request to this site, so that the server can tell whether to show the banner, and scripts on the page can read it. It holds the record (its random identifier, the time and your choices), never your name or email address.
tp_attr (90 days): where your visit came from: the campaign details and advertising click identifiers in the link you followed (for example utm_source or gclid), the name of the site that referred you, the page you landed on, and when. The site sets it only after you consent to advertising measurement, when you open the home page, the Request Access page, or the Privacy, Terms or Security page without being signed in, and never when your browser sends Global Privacy Control or Do Not Track or reports that it is driven by automation. If you refuse or withdraw that consent, the site’s code removes it, and a tp_attr cookie your browser has without that consent (from an earlier visit, for example) is removed the next time you open one of the site’s pages. When it is set, a later link with campaign details or a click identifier replaces what was kept; other visits leave it as it is, and each time it is written its 90 days start again. Your browser sends it with each request to this site, where the server does not read it; the site’s code adds its contents to a request for access only when advertising measurement was allowed for your visit (see Requests for access), and passes its campaign details, landing page and referring site (not the click identifiers) to the advertising and analytics tags when they load.
tp_theme (one year): if you choose a theme with the site’s theme button, your browser keeps that choice (“light” or “graphite”) so that pages open in that theme. It identifies no one, and TruePart uses it for nothing else. Like tp_attr, it can be read by scripts on the page, including the advertising and analytics tags when they load.
Sign-in cookies (invited pilot accounts and TruePart staff): when you sign in, TruePart’s server keeps your session in cookies that page scripts cannot read: tp_id and tp_at (your sign-in tokens, kept as long as the tokens last: currently one hour, never more than 24 hours) and tp_rt (the token that renews them; the cookie is kept for up to 30 days, but the token stops working 12 hours after you sign in, and the cookie is removed when you sign out or your session ends). TruePart staff who open the workspace from TruePart’s staff console get tp_staff instead (for up to an hour). If you sign in through the identity service’s own sign-in page, tp_pkce keeps a random value, the sign-in’s state and the page to return to (the site’s own sign-in form does not use it). Once your password is accepted, tp_ch keeps the next step, including the email address you are signing in with. Each lasts at most ten minutes. If your session ends without you signing out (it expires or can no longer be renewed or verified), or after your access is revoked, tp_ended records that it ended (only that, or that access was revoked, nothing about your account) for 12 hours, so the sign-in page can tell you why; signing in or signing out removes it. When you sign out, tp_revoke keeps a copy of your renewal token for at most two minutes, sent only to the site’s sign-out address, so the server can revoke it. None of these cookies is set unless you start to sign in.

The site also uses these values in your browser’s storage, not in cookies:

tp_sid (the tab’s session storage): the random session identifier of the usage events (see Site usage events), gone when you close the tab.
tp_ft (local storage, kept until you clear this site’s data or the site removes it): the campaign source, medium and name and the referring site of the first visit that had a campaign source or came from another site. It is saved the first time that visit sends a usage event, and sent with every later usage event. It is not saved when the usage events are off (see Site usage events).
tp_consent_sent (local storage, strictly necessary): the identifier and number of the latest record of your choice that TruePart’s service confirmed receiving (see The record of your choice), so that the site sends your choice again only until it is received. It holds nothing else.
tp_privacy_choice (local storage): a value that earlier versions of the site read before loading advertising and analytics tags. It never counts as a choice, nothing on the site writes it, and the site’s code removes it when it finds it.

When the advertising and analytics tags load, they set and read their own cookies and browser identifiers, some under this site’s address and some under the addresses of the companies that provide them, for as long as those companies choose (see Advertising and analytics tags). The names the site’s code knows under this site’s address are listed above, with the category of the tag that sets them. TruePart’s own site code reads the identifiers the tags set under this site’s address when you send a request for access, and stores them with it when advertising measurement was allowed for your visit (the six other advertising platforms’ identifiers only when Ad personalization was allowed too; see Requests for access). Clearing this site’s data in your browser removes the cookies and values listed above and the cookies the tags set under this site’s address. It does not remove cookies those companies keep under their own addresses. Without your consent to a category, the site’s code itself removes TruePart’s own values for it (tp_sid and tp_ft without Analytics, tp_attr without Advertising measurement) and tries to remove the cookies listed above for that category’s tags under this site’s address (the six other advertising platforms’ without either Advertising measurement or Ad personalization), each time a page of the site loads in your browser and when you withdraw that consent.

Web analytics by default

When the location our content-delivery provider reports for your connection is outside the EU and EEA, the United Kingdom and Switzerland (for example in the United States, including when it reports no state, in Canada, in Brazil, or elsewhere in the world), the site loads the tag of a web-analytics service from another company on its public pages without asking first, unless you have opted out. It does not do so in the EU and EEA, the United Kingdom or Switzerland, in the EU’s overseas regions with their own country code, the Åland Islands, Gibraltar, Jersey, Guernsey or the Isle of Man, or when your location is not known: there it asks first, as described under Cookies and browser storage. It never loads on the sign-in pages, in the pilot workspace, or for a signed-in visitor.

The service receives, with each page you view: the page’s full address (including any campaign details and click identifiers in it), its title, and the page that referred you; your IP address, from which it works out your approximate location; your browser and device details, including screen and window size, language and time zone; the site’s usage events listed under Advertising and analytics tags (how far you scroll, the buttons and links you use, and time on the page), which also show the page you leave the site from; and your country and region as our content-delivery provider works them out. It sets its own cookies (_ga, _ga_<id>) under this site’s address.

Its advertising features stay off: the site turns off its use of the data for advertising audiences and ad personalization, does not pass click identifiers on links, and tells it that ad storage, ad user data and ad personalization are not allowed, until you allow Advertising measurement or Ad personalization in Your Privacy Choices. No other optional category (TruePart’s own usage events, the session-analytics service, the tag manager and the advertising tags) runs before you turn it on.

To opt out, open Your Privacy Choices and turn Analytics off and save, or choose Essentials only; the site removes the service’s cookies under this site’s address, reloads the page, and does not load the service again while your browser keeps your choice in the tp_consent cookie. The site asks your browser to keep it for 12 months (after that, or when this notice changes, the banner shows again, and the opt-out still applies while the cookie is there), but your browser may delete it sooner: Safari and other browsers built on WebKit keep cookies the site’s script writes for at most 7 days, and clearing your site data removes it. Once it is gone, the site treats you as a new visitor and loads the service again until you opt out again. If your browser sends Global Privacy Control or Do Not Track, the site treats it as your opt-out and never loads the service; that opt-out does not depend on a cookie. Opting out does not delete what the service already received.

The banner’s OK closes the notice and sets the tp_notice cookie, which keeps no identifier and only notes the version of this notice you saw.

When you choose in the banner or the preference center, the site’s code keeps your choice in the tp_consent cookie and sends a copy to TruePart’s own service, which keeps it as the record of your consent. A record contains only: a random identifier made for your browser (it stays the same when you change your choice), a number that goes up with each change, when you chose, your choice for each category, the version of the consent text you were shown (this page and the banner; currently 2026-11-13.6 in the EU and EEA, the United Kingdom and Switzerland and for an unknown location, and 2026-11-13.4 everywhere else), the profile your location selected and its version, whether you chose in the banner or the preference center, and whether your browser sent Global Privacy Control. TruePart’s service adds the time it received the record and, when our content-delivery provider reports it with the request, your country. A record does not contain your IP address, browser user agent, name or email address.

TruePart keeps each record for 1095 days (three years) after it receives it. Its servers use the latest record for your identifier to decide whether a usage event may be kept, whether a request for access may keep where your visit came from, and whether its progress may be reported (see Advertising and analytics tags), and they act on a record only while it is still valid: made under the current version of this notice, for the profile it names, and within the last 12 months. If your choice does not reach TruePart’s service (a lost connection, for example), your browser still follows it, sends it again each time you load a page of the site until the service confirms it, and Cookie settings says that it is not confirmed yet; until it arrives, TruePart’s servers act on the last choice they received, and without one they treat your visit as having no consent.

Site usage events

To understand which parts of the site help visitors, and which campaigns and referring sites bring visitors to it, the site can send TruePart a short record when you view certain pages or use parts of them (for example, “page viewed”, “scrolled down the page”, “video played”, “button selected”, “link to another site followed”, “Request Access form started”, or “sign-in submitted”). It sends these records only after you consent to Analytics, and stops when you withdraw that consent. The records go to TruePart’s own service, which keeps one only when the latest record of your choice (see The record of your choice) allows Analytics and was made without Global Privacy Control; the site sends that record’s identifier with each one, and the service checks it but does not keep it with the event. When advertising and analytics tags have loaded for your visit, the events of the pages where they load (page views, scrolling, video, buttons and links selected, and the Request Access form) are also sent to them, as described under Advertising and analytics tags. Sign-in, demo and pricing events are not sent to them. These records are separate from the page counts described under Page counts without cookies, which keep no record of a visit.

Each record that TruePart’s service keeps contains only:

the event name, the time it happened, the time our service received it, and, for most events, a random identifier of the event;
a random session identifier made for your browser tab (tp_sid, above). It is not stored with your name, email address or account. But a request for access keeps the identifier of the event that sent it, so the records of the tab that sent the request can be connected to the request, and so to the name and email address in it and, if you are invited, to your account;
the path of the page (without anything after a “?”);
a device class (mobile, tablet, or desktop), worked out from the window width;
the campaign source, medium, and name from the link you arrived by (the “utm” parameters) and the host name of the site that referred you: those of this visit, and those of your first visit that had them (tp_ft, above);
for some events, a short label from a fixed list: the button or link you selected and where it is on the page, which legal page you viewed, which Request Access field you completed or what kind of error the form showed (the field’s name, never what you typed), or, when a sign-in fails, whether the sign-in service refused it (for example, a wrong email address or password) or a server or network error stopped it;
for signed-in users (pilot participants and TruePart staff), on the demo: short identifiers of the demo part, stage, action, or the demo requirement, question or CAD feature selected (the demo is synthetic; these are not your data); on the pricing page: the public plan, its plan group (individual or organization), and which of its buttons you select.

The records never contain drawings or text read from them, requirement values, geometry, files or filenames, pilot project data, or what you type into a form. The events service does not read or store your IP address, browser user agent, or cookies, and sets no cookies. (Our hosting and content-delivery providers still process standard request data, as described above.)

Each record expires 400 days after it is received, and the database then deletes it automatically, usually within a few days; database backups can keep it for up to 35 days longer.

The site sends no usage records, and saves neither tp_sid nor tp_ft, without your consent to Analytics, and never when your browser sends Global Privacy Control or Do Not Track or reports that it is driven by automation.

Page counts without cookies

Wherever you are, including the EU and EEA, the United Kingdom and Switzerland, the site counts how often its public pages are viewed, where the views come from and from which country. The count is not one of the optional categories you choose in the banner: it sets and reads nothing in your browser, sends nothing to another company (none of it reaches the web-analytics service), and TruePart keeps only totals, never a record of your visit. In the EU and EEA, the United Kingdom and Switzerland it is the only measurement made before you consent.

When you open one of the site’s public pages without being signed in, the site’s code sends TruePart’s own service only: the path of the page (without anything after a “?”); the day; a device class (mobile, tablet, or desktop), worked out from the window width; and where the view came from: directly, from another page of this site, from a link with campaign details (with its “utm” source, medium and name), or from a search engine, a social network, an AI assistant or another site (with that site’s host name, never the address of the page); and your country as our content-delivery provider reports it (never your region or city; nothing when it is not known). The request carries no cookie, no identifier of you, your browser, your visit or your consent choice, and no referring address. TruePart’s service adds one to the total for that combination of page, day, device class, source and country, and keeps nothing else. It does not read or store your IP address or browser user agent, and keeps no time of day.

Each total is deleted 400 days after its day, usually within a few days of that; database backups can keep it for up to 35 days longer. (Our hosting and content-delivery providers still process standard request data, as described above.)

The site does not count a view when your browser sends Global Privacy Control or Do Not Track or reports that it is driven by automation; on the sign-in pages and in the pilot workspace; or for a signed-in visitor.

Advertising and analytics tags

On the site’s public pages, for visitors who are not signed in, the site can load tags from other companies that provide web analytics, tag management, advertising measurement, and session analytics: a web-analytics service and a session-analytics service under Analytics, and the same web-analytics company’s tag manager and advertising service under Advertising measurement, and six other advertising platforms under Advertising measurement and Ad personalization together. It loads only those TruePart has switched on. No tag loads on the sign-in pages. When you are signed in, including in the pilot workspace, only the web-analytics tag can load, under the same consent rules. It receives page views only: the page’s address with every project, drawing or other identifier replaced by a placeholder and without its query, a fixed page name, and no advertising features. The tag manager, the session-analytics service and the advertising tags never load for a signed-in visitor.

A tag loads only when all of these are true:

TruePart has switched the tag on and approved its activation, and has not engaged its emergency kill switch, which stops every tag and every report for everyone;
your browser does not send Global Privacy Control or Do Not Track and does not report that it is driven by automation;
you have consented to the tag’s category, and that choice is still valid. Wherever you are, or when your location is not known, the tags load only after you give consent, and they stop when you withdraw it. The one exception is the web-analytics tag on public pages outside the EU and EEA, the United Kingdom and Switzerland, which loads until you opt out (see Web analytics by default).

The tags run in your browser, so these companies receive your IP address and browser details with each request, and collect what their own settings tell them to. In addition, the site’s code sends them:

each page you view: its full address (including campaign details and click identifiers in it), its title and the page that referred you (in the signed-in workspace: the address with identifiers replaced and without its query, and a fixed page name); your screen and window size, language, time zone, connection type, and an approximate class of your device’s memory;
the campaign details, the referring site and the page you landed on, as kept in tp_attr (not the click identifiers or the time), and your country (and, where the provider supplies it, your region) as our content-delivery provider works them out;
the site’s usage events (the tag manager also gets each one’s random event identifier, the same as TruePart’s record) and a 15- and 60-second engagement signal that TruePart itself does not record, with fixed labels such as how far you scrolled (25, 50, 75 or 90 percent), the button, link or video involved, and the names of Request Access fields completed and kinds of form errors. The site’s own code never sends the tags what you type.

The web-analytics tag runs with its advertising features on in the EU and EEA, the United Kingdom and Switzerland, and when your location is not known (there it loads only with your consent); everywhere else, its advertising features (the web-analytics company’s audience and ad-personalization signals and link marking) are on only when you allow Advertising measurement, and ad personalization only with Ad personalization (see Web analytics by default). Before that tag or the tag manager starts, the site tells that company that no use is allowed, and then allows only the purposes you consented to: analytics storage with Analytics, ad storage and ad user data with Advertising measurement, and ad personalization with Ad personalization. With Advertising measurement, the company may use the data to measure ads; with Ad personalization, also to add your browser to advertising audiences and to personalize ads you see on other sites. The tag manager can load further tags, from the same company or others, that TruePart sets up in the tag manager’s own console rather than in the site’s code; the site does not limit what those tags collect from the page. The session-analytics tag records your visit to a page (mouse movements, clicks, scrolling and what the page showed) so that it can be replayed and summarized; the site tells it your Analytics choice through its consent setting. The site marks its forms for masking by the session-recording provider to prevent typed form contents from appearing in that provider’s recordings. TruePart labels each recording with the campaign details, landing page and referring site kept in tp_attr, and your country and region where known. These companies set and read their own cookies and browser identifiers.

When advertising measurement was allowed for your visit and you request access, the request also keeps the identifiers the tags set in your browser (see Requests for access), and TruePart’s servers can report the request’s progress: sent, qualified, approved, invited, and account activated, and for a pilot account the first project created and the first CAD generated. Reports can go to the web-analytics service and to the advertising services that TruePart connects in its administration settings. Each report carries the step, an event identifier and the time; the campaign details, click identifiers and browser identifiers the request kept, and an identifier derived from the request (for the web-analytics service, only when it has no browser identifier); for some services the page you landed on; and, for the services that take them, consent settings that match your choices (ad storage and ad user data from Advertising measurement, ad personalization from Ad personalization). A report never includes your name or email address. A report to an advertising service can include a one-way hash of your email address when TruePart turns on matching for that service, which lets the service recognize an account of its own with the same address. Reports come from TruePart’s servers, without your IP address, and each step is reported only within six days of happening. TruePart’s servers send a report only for a request that carries the identifier of your consent record, and only while your latest record allows Advertising measurement (and, for every service but the web-analytics service, Ad personalization), was made without Global Privacy Control, and is still valid (see The record of your choice): they check it again before each report, so once your withdrawal of that consent reaches TruePart’s service, no further report is sent.

Your Privacy Choices

Your Privacy Choices and Cookie settings, linked from every page of the site, open the site’s own preference center, where you can give, refuse or withdraw consent for each category at any time, without an account. It shows your current choice, when you made it, and the last six characters of its identifier, which you can quote if you ask us about it. It shows Essential first, always on (it keeps the site working: sign-in, security and remembering your choices), then a switch for each category, describing the kinds of service each one allows, and Save, Accept all and Essentials only.

When you turn a category off and save, or choose Essentials only, the change applies in your browser at once: the site records your new choice (see The record of your choice), tells the web-analytics company’s tags and the session-analytics tag that the uses you withdrew are no longer allowed, removes what it can of the cookies and values of those categories, and reloads the page if a tag had already loaded, so that no tag keeps running; from then on it sends no usage events without Analytics. TruePart’s servers apply the change once your new choice reaches TruePart’s service, normally within seconds: from then on they keep no usage event without Analytics and send no further report about a request for access without Advertising measurement (or, to the six other advertising platforms, without Ad personalization). Until it arrives they act on the last choice they received; the site sends it again, and Cookie settings says so, until it is confirmed. Withdrawing does not delete what was already sent to TruePart or to those companies; to have a request for access deleted, ask us on this page. Where the web-analytics tag runs by default, turning Analytics off and saving, or Essentials only, is also your opt-out of that tag.

Turn on Global Privacy Control or Do Not Track in your browser and the site treats it as a refusal of every optional category, whatever you chose before: from the next page you open, it loads no advertising or analytics tags, sends no usage events, and sets or uses no tp_attr cookie, and the preference center says the signal is honored (where the web-analytics tag runs by default, this is also your opt-out of it). If the signal is on when you send a request for access, TruePart’s servers never report that request’s progress to another company. Turning it on later does not change a request already sent or delete what the tags already received; to stop reports about a request, ask us on this page to delete it. The bot check on pages with a form is not affected by these choices or signals (see Contact forms). Clearing this site’s data in your browser removes the cookies and stored values listed above, including tp_consent (so the banner asks again) and those the tags set under this site’s address, but not cookies those companies keep under their own addresses.

Contact forms

A form sends your name, email address, company (required on the pilot, sales, partnerships and investor forms, optional otherwise) and message to the TruePart mailbox for the form’s topic. A support form opened from a support link in the pilot workspace also adds, below your message and shown to you before you send, the page you came from, the project and job identifiers, the project’s state, and any failure code or error reference. The message is delivered by our email-delivery provider to our business mailboxes; the site itself does not keep a copy in a database. The email stays in that mailbox like other business email; the form service sets no date for deleting it. To have a message deleted, ask on this page.
To limit abuse, the form service counts messages per IP address and hour, and per email address and day. The counts are kept under a hash of the IP address or the email address, not the address itself. Someone with access to the counts could still work an IP address out by trying every possible one, or match an email address they already have, so the counts are kept only briefly: each expires 2 hours after the first message counted in its hour (IP address) or 2 days after the first counted in its day (email address), and the database then deletes it automatically, usually within a few days. To send a message only once, the service keeps a single hash of the email address and the message together until a day after the message is sent, then deletes it the same way. Its logs record the topic, whether the message was sent and the bot check’s result, not what you wrote, for 30 days.
To keep out automated spam, the forms use a bot check from our content-delivery provider. On every page with a contact or Request Access form (including the home page, the Request Access page and this page; on the sign-in page, only once you open its help form), your browser loads the provider’s check as soon as the page opens, whether or not you send anything and whether or not your browser sends Global Privacy Control or Do Not Track. TruePart’s code does not pass the check what you type, but the provider’s script runs in the page with the form, and the provider receives your IP address and information about your browser and device. It is usually invisible and asks you to do something only when it needs to. When you send a form, TruePart’s server also sends the check’s result and your IP address to the provider to confirm it.
Forms for business enquiries accept only work email addresses.
The form’s own code sends what you write only to TruePart’s email service (the advertising and analytics tags described above can also run on this page). We do not add you to a mailing list because you wrote to us.

Requests for access

TruePart is in invite-only Technical Preview. When you send the Request Access form, TruePart stores your request in its own database so that the team can review it. A request contains:

your first and last name, work email address, company, role or job title, and the country where your business is located (the Technical Preview is available in the United States; eligibility is decided from what you state, never from your network address);
what best describes you, what you would like to use TruePart for, and your approximate number of engineering drawings per month;
anything else you chose to tell us;
when you sent it, how many times and when you last sent it again for the same email address, a hash of the email address (to recognize a repeated request), and its review: its status (new, reviewing, approved, invited, activated or declined) with the time of each change and the staff member who made it, whether the business location you stated is eligible, the reason for a decline, and, if you are invited, the identifier of your account and when you first signed in;
when advertising measurement was allowed for your visit, where your visit came from, as kept in the tp_attr cookie: campaign details, advertising click identifiers, the referring site, the page you landed on, and when;
when advertising measurement was allowed for your visit, the identifiers the advertising and analytics tags set in your browser (such as the web-analytics client identifier; the six other advertising platforms’ identifiers only when Ad personalization was allowed too);
if you made a choice in the consent banner or the preference center, the identifier of the record of your choice (see The record of your choice), which TruePart’s servers use to check your latest choice before they report the request’s progress;
the identifier of the event that sent it (see Site usage events), and whether advertising measurement was allowed for your visit, with the country (and, where the provider supplies it, the region) our content-delivery provider worked out from your IP address.

We use a request to review access to TruePart (including checking it against other requests with the same email address or company name, and against an existing account with the same email address) and, if it is approved, to invite you and to record whether the invitation was accepted. We also use where your visit came from to learn which campaigns and sites bring requests, and, as described under Advertising and analytics tags, TruePart can report the request’s progress to the web-analytics service and to advertising services. We do not add you to a mailing list because you asked. Sending a request does not create an account; an invitation does. The form accepts no files; please do not include drawing contents or other confidential information.

When a request arrives, a notification email with the details you entered (name, email address, company, business location, role, your answers and message) and the request’s identifier is sent to a TruePart business mailbox by our email-delivery provider. That email is kept in the mailbox separately from the stored request and is not deleted automatically when the request is.

To limit abuse, the request service counts requests per IP address and per email address, under hashes, in the same way and for the same short time as the contact forms. The request does not include your IP address or browser user agent, and the service logs record only the outcome of each request, for 30 days. The bot check described under Contact forms also runs on the Request Access form, including on the home page; when you send a request, TruePart’s server sends your IP address to that provider to confirm the check.

A request that is not invited expires 12 months after you send it, and the database then deletes it automatically, usually within a few days. If we invite you, the invitation itself creates your account with the email address in your request (or links an existing account that has verified the same address). From then on the request is kept with your account records, with no automatic deletion date, whether or not you accept the invitation, until you or we ask for it to be deleted. Database backups can keep a deleted request for up to 35 days longer. To have your request deleted sooner, ask on this page.

Each staff action on a request (review, approval, decline, invitation) is also written to TruePart’s administrative audit trail, with the request’s identifier, its status before and after, whether the stated business location is eligible, and the reason staff gave. These audit records are kept for at least 7 years (see Account security and administrative records) and are not deleted with the request. Once progress reporting is set up, TruePart keeps, for every request whether or not it is reported, a record of each progress step (the request’s identifier, the step’s event identifier, its time, and whether and where it was reported), without your name or email address. These records have no automatic deletion date and are not deleted with the request.

Agent interfaces

TruePart offers software agents a few ways to read its public information: an MCP server, an A2A agent, a public read-only API, and tools on the public pages. They answer from the same public information the site shows, never from an account, a request for access, or engineering data.

An agent can also register with TruePart, without an account, to get a higher rate limit on the MCP server and the A2A agent, and a person with a TruePart account can link a registered agent to that account. Neither gives the agent access to an account or its data.

What an agent sends (for example, a question to the A2A agent) is used only to answer it. TruePart does not store it, apart from the registration and link records described below.
To enforce the rate limits, TruePart counts requests per address: requests to the MCP server and the A2A agent, and an agent’s requests to register, to get or revoke tokens, or to ask for a link to an account. A count is kept under a hash of the IP address a request comes from and the minute, not under the address itself; registrations are also counted per address and hour, in the same way. Someone with access to the counts could still work an address out by trying every possible one, so they are kept only briefly: each count expires two minutes after it starts (an hourly count, two hours after its hour starts), and the database then deletes it automatically, usually within a few days; database backups can keep it for up to 35 days longer.
When an agent registers, TruePart keeps a registration record: a random registration identifier, when the registration was made and when it expires, its status (not linked, linked, or revoked) and when that changed, a one-way hash of the secret the agent needs to start a link to an account, and the identifier of its latest link request. The record contains no IP address, name, or email address. Requests made with the registration’s tokens are counted per registration and minute, and also per address and minute in the same hashed way as above (so that many registrations do not multiply one address’s limit); those counts expire like the ones above.
The access tokens and identity assertions TruePart gives an agent are signed, so TruePart can check them without keeping a copy: they are not stored. The claim token, the secret the agent needs to start a link to an account, is kept only as the one-way hash described above.
To link an agent to an account, the agent gives TruePart the email address of the person’s TruePart account and shows the person a code. TruePart keeps a record of the link request with a one-way hash of that email address and a one-way hash of the code, never the address or the code themselves, along with the registration it belongs to, its status, how many times a code was tried, and when it was made. A hash of an email address can still be matched by someone who already has the address, so the record is kept only briefly: it expires 10 minutes after it is made, and the database then deletes it automatically, usually within a few days; database backups can keep it for up to 35 days longer.
TruePart sends no email to link an agent. Only a person who signs in to the account with that email address can confirm or refuse the link. When they confirm, the registration record keeps the identifier of the account it is linked to and when it was linked.
A registration record, including any link to an account, expires 30 days after the agent registered, whether or not it was revoked. The database then deletes it automatically, usually within a few days; database backups can keep it for up to 35 days longer.
The MCP server, the A2A agent, and the public API answer with data, not a page, so they send no site usage events and load no advertising or measurement tags. A browser that reports it is driven by automation sends no usage events and loads no such tags on the pages either, and gets no tp_attr cookie. It still loads the bot check on pages with a form (see Contact forms).
As for any visit, our hosting and content-delivery providers process standard request data, as described above.

The demo project

The demo uses a synthetic drawing that TruePart generated. It contains no customer data and does not send anything to an AI provider.

Pilot participants

Pilot access is invite-only and starts with a request for access. For invited accounts, this is what happens today:

Sign-in uses a managed identity service, which holds your email address, account status, password and authenticator-app enrolment. You type your password on this site. It passes through our content-delivery provider, which checks it against lists of known leaked passwords, and TruePart’s server passes it to the identity service to sign you in. We also keep the account security records described under Account security and administrative records, and TruePart’s server keeps your session in the sign-in cookies listed under Cookies and browser storage.
Uploaded PDFs, what is read from them, your answers and approvals, and the generated CAD are stored in TruePart’s private cloud storage in the United States, encrypted at rest. Your browser reaches the files only through short-lived links issued to your signed-in account (anyone holding such a link can use it until it expires), and TruePart’s pipeline reads them to process your drawing. Authorized staff can see your projects’ records, such as the project name (taken from the uploaded file’s name) and status, in TruePart’s administrative console.
Drawings are processed by TruePart’s deterministic pipeline. The pilot does not send uploads to any AI provider.
Each upload records whether you allowed TruePart to use it to evaluate the pilot pipeline (off unless you tick the box). The upload form does not ask for permission to use your drawings for training; see Your engineering data and model training.
You can delete a project: its files are deleted, and its record is deleted from the database (point-in-time database backups keep it for up to 35 days). Our service logs keep request metadata, not drawing content, for 30 days. Administrative audit records related to the project are kept separately for at least 7 years. See Account security and administrative records.

Please do not send drawings by email unprompted.

Your engineering data and model training

Customer engineering data is not used to train shared models unless the customer explicitly chooses otherwise.

Customer engineering data means what you give TruePart and what TruePart produces from it for you: your drawings, CAD models, STEP and STL files, the requirements extracted from your drawings, your answers to clarification questions, and the other engineering files TruePart generates for you.

This is the default on every plan, including free use and the pilot. No plan changes it.
Allowing training is a separate, voluntary choice that you make explicitly. It is never a condition of a price, access, a discount, or any feature. The pilot does not ask for it.
If you allow training and later withdraw, the withdrawal applies from then on: your data is not used in training that starts after you withdraw.
Allowing an upload to be used to evaluate the pilot pipeline (described above) is a different permission, and it does not allow training.
Operational and product records that contain no engineering content, such as the site usage events, are covered by the rest of this page, not by this section.

Account security and administrative records

We maintain limited records needed to operate and secure TruePart accounts. These records may include the date and time of a successful sign-in, a count of successful sign-ins, and the time when access or active sessions were revoked.

These records help us operate account access controls, investigate account issues, and confirm that security actions have taken effect.

TruePart also maintains an internal administrative audit trail for privileged actions performed by authorized staff. Audit records may include the staff member who performed an action, the affected account or project identifier, the action requested, the date and time, the stated administrative reason, and the resulting status or outcome.

Administrative audit records are retained for 7 years to support security, accountability, operational review, and dispute investigation. They are not yet deleted automatically when that period ends.

Staff are instructed not to place customer drawing contents, CAD geometry, passwords, authentication tokens, or unnecessary personal information into administrative audit reasons.

Customer engineering files are not included in the administrative audit trail itself, and TruePart’s administrative console cannot open them. Staff views of project records in the console (such as a project’s name and status) are not written to the audit trail; staff actions that change a project are.

We limit access to these records to authorized personnel according to their job responsibilities.

Retention

Administrative audit records — 7 years (not yet deleted automatically).
Account security metadata, such as last successful sign-in and access-revocation time, is kept with no automatic deletion date.

These records are used to operate and secure accounts, and are separate from the site usage events above. One exception: the time of your first sign-in after an invitation is copied to your request for access as its activation. TruePart counts activations by campaign and, as described under Advertising and analytics tags, can report “account activated” to other companies.