NixBlox Privacy Policy

Last updated: September 28, 2026 (beta program) · replaces the September 8, 2026 version · what changed

This Privacy Policy describes how NixBlox LLC, a Michigan limited liability company (“NixBlox,” “we,” “us”), collects, uses, and protects information when you use our websites (nixblox.app, and the legacy redirect from getnixblox.com), the NixBlox organization portal (app.nixblox.app), the NixBlox Designer desktop application, and the optional NixBlox Capture browser extension described in Section 2 (together, the “Services”).

The short version: we collect what we need to license the software, run your organization’s account, operate the optional AI features, and support you. We do not sell your personal information, we do not share your mobile number or SMS opt-in data for anyone’s marketing, and we do not show ads. NixBlox is currently a free beta program offered only to United States users and organizations; there are no paid subscriptions and we process no payments.

Who decides how information is used. NixBlox determines how account, license, website, security, and service-usage information is processed. For personal information contained within Customer Content (for example, a client’s name on a drawing), the applicable organization generally determines why that information is stored and used, and NixBlox processes it on the organization’s behalf to provide the Services. For a Personal Organization Account, the individual account holder is the organization for this purpose; for a Business Organization Account, the organization decides through its authorized administrators.

1.Information We Collect

Beta key requests and license records. When you request a beta key we collect your name, email address, company, trade, and any message you include, together with your IP address and browser information (used to filter automated abuse). If you later give us a mobile number in a conversation, Section 4 applies. License keys are bound to the email address they are issued to, so we keep a record of each issued key: the email, the name used in the greeting, plan, serial number, issue and expiry dates, and any notes our staff add. When a key is renewed, a new serial is issued to the same email and the old record is kept.

Account and organization data. While using an active NixBlox workspace, each user is associated with an Organization Account — a workspace recorded as either Personal (one individual; not a separate legal entity; created automatically at sign-up, and again for a member left without an organization after a Business Organization Account closes) or Business (used on behalf of a legal entity). We store your account email and password credentials (held by Amazon Cognito; we never see your password), your organization’s name and settings (title-block configuration, export preferences, legal text, standard cable types, AI participation mode), uploaded images (your organization’s logo and watermark, PNG or JPEG only), member lists and roles, locations, and invitations (which include invitee email addresses and a single-use invitation token).

Project files. If your organization stores projects in NixBlox cloud services, we store those project files (drafts and published revisions), attached vault files, and related metadata (project names, who created or updated them, revision labels, edit locks, file sizes) on your organization’s behalf. Project files are your organization’s content; we access them only as described in Section 3.

Payment information. During the beta, NixBlox does not receive or store payment-card details. If paid plans are offered, payment information will be processed by the merchant of record identified at checkout under its privacy notice, and NixBlox will update this Policy before accepting payments.

Technical and usage information. The desktop application contacts our servers to confirm your license and organization sign-in, to sync organization settings and projects, and to check for software updates. When the application confirms your license and sign-in, we receive your license identifier, your account, and the time of the confirmation. These requests include standard technical data (IP address, timestamps, application version) in our server logs. The application works offline between confirmations — it requires a successful online confirmation at least every 30 days to keep operating, as described in the EULA.

Website and portal activity. When you visit our websites or the organization portal, our hosting and authentication providers may automatically receive technical information such as your IP address, browser and device type, operating system, requested pages, referring page, timestamps, and security events. We use this information to deliver, secure, and troubleshoot the Services.

Information stored on your computer. The desktop application keeps, on your own machine and not on our servers: your projects and exports (by default under Documents\NixBlox), your license key, a cached copy of your organization’s settings and catalog so the application works offline, and your preferences. The application also stores a random installation identifier used only for optional telemetry (Section 2); it is not sent with signed-in requests and is not intended to identify you by name. Uninstalling the application does not delete your projects. If you use the web viewer in the organization portal, your browser may also keep copies of the last few published drawings you opened, and any field notes you write while offline, on your device so they remain available without a connection; these copies are removed when you sign out of the viewer.

Manufacturer websites you look up. When you paste a product URL or use the AI features, the application fetches that manufacturer’s page directly from your computer, identifying itself as NixBlox. The manufacturer’s website sees your IP address as it would from a browser; NixBlox’s servers never fetch product pages on your behalf.

Agreement acceptance records. When you accept our agreements (the Beta Program Terms, the End User License Agreement, and the Terms of Service) by ticking the acceptance box after signing in to your verified account, we record which agreements and versions you accepted and cryptographic hashes of both the canonical source and the rendered static artifact for each accepted agreement; your email address and account identifier; your Organization Account and role, and whether you accepted personally or on behalf of a legal entity through a Business Organization Account; your representations about age, location, and (for a Business Organization Account) organizational establishment and authority; the date and time; your IP address and browser or device information; and where the acceptance occurred. A personal acceptance and an organizational acceptance are separate records; an individual’s acceptance never stands in for an entity’s, and a Personal Organization Account involves no organizational acceptance. After you sign in for the first time, and after any material change to the agreements, you are asked to accept the current agreements, and that acceptance is the one that governs your use. These records are immutable, are kept to document the agreement between us, and are retained as described in Section 7. You may request a copy of your acceptance record and of the terms you accepted at support@nixblox.app.

Request acknowledgment records. If the beta request form includes an acknowledgment checkbox, we keep that acknowledgment as part of the request record described above. It is not an acceptance of any agreement, does not authorize access, and is never treated as the acceptance of a later account.

Communications. If you email, text, or submit a form to NixBlox, we collect the message content and related information, such as the sender and recipient address or telephone number, timestamps, and delivery status, so we can respond and maintain appropriate business records.

We do not collect the contents of project files that are not stored in our cloud services.

2.AI Smart Import and Product Data

The desktop application includes optional AI-assisted features (“Smart Import” / “Block AI”) that help configure product blocks from a product’s own published data. These features are designed around one principle: NixBlox is designed to learn product facts, not your project designs. That is a design principle, not an absolute technical guarantee, and this Section describes exactly what is and is not sent.

What Smart Import sends. Smart Import does not automatically select or upload your project files. It sends NixBlox and its AI provider the extracted text of product pages and any spec-sheet PDF you choose. Do not select a file or URL containing project, client, personal, confidential, credential, or export-controlled information. Confirmed shared-library submissions are separately sanitized as described below. Limited operational records temporarily associate product-extraction requests with an account and organization for metering, rate limiting, moderation, and abuse prevention, as described in this Section and Section 7.

Organization participation modes. Your organization’s administrator chooses one of three participation modes: Community (the default — your organization both reads the shared product library and contributes confirmed configurations to it), Private (preserves read access to the shared library but prevents contributions), or Off (disables AI-assisted features and shared-library access for the organization). Product blocks already created remain usable in every mode. Mode changes are never retroactive.

Your consent. Before your first use of AI assist, the application asks for your consent and records your answer. Declining keeps AI assist off for you until you accept. If your organization’s participation mode changes, you are asked again before AI assist is next used.

Product addresses. Before a product page address is sent to NixBlox, written to our logs, or stored in the shared product library, the application reduces it to the public manufacturer address that identifies the product: embedded sign-in details, page fragments, and tracking or session parameters are removed, and addresses that point to private networks, local files, or non-public locations are not sent at all. The full address you pasted is used only on your own computer to fetch the page.

The free library check. When you paste a product URL or choose “Check the library,” the application checks whether the product already exists in the shared library by sending the product’s address and identifying details. This check involves no AI processing, does not consume an AI usage unit, and does not create a shared-library contribution or structured AI-metering record. Standard technical and security logs may record request metadata, such as the account, IP address, time, and outcome, as described in Sections 1 and 7. The check does not transmit or store Customer Content.

AI-assisted extraction. When you use Smart Import on a product, text from the product’s page and related vendor documents is sent to our servers and processed with an AI service provider (Section 5) to suggest product fields and port configurations. Pages that are not product pages are declined without charge. Each request is associated with your organization and your account for usage metering, rate limiting, and abuse prevention. Structured AI metering records (which product was read, when, by which account, and the units charged) are kept for 30 days and then deleted automatically. Submitted page and document text is retained for up to 30 days to deliver results, then deleted automatically. Separately, our standard server logs record each extraction and library write — including the product’s address, the requesting account and organization, and the time — for 90 days (Section 7). These logs do not contain submitted product-page or document text.

Spec-sheet upload. If you attach a spec sheet (PDF), the PDF file itself never leaves your computer. The application reads the file locally and submits only the extracted text. That extracted text is sent to NixBlox and to the AI provider in the same way as product-page text, so choose only vendor documents. For a single-product request the extracted text is not stored after the request completes; when you submit it with a batch job, the extracted text is kept with the batch-job record until the job’s records are deleted, up to 30 days (Section 7).

Product improvement telemetry. To improve extraction quality, the application can share which vendor website and which kind of data source produced a usable result. The telemetry payload omits account and organization IDs but includes the random installation identifier described in Section 1. Standard transport logs may also contain an IP address and timestamp. NixBlox treats these as technical identifiers. The payload contains no page content and nothing about your projects. Controlled by the “Help improve Smart Import” setting on each installation; organization administrators can disable it for the organization.

Product-page reachability observations. When the application reads a manufacturer’s product page and finds it gone, moved, or marked discontinued (or confirms it is still live), it may report that observation — the product’s address and the outcome — so the shared library can flag products that are no longer available. The product-level observation is not displayed with user or organization attribution. A per-account rate-limit counter is retained for 48 hours, and standard server logs may retain the request metadata for 90 days. These observations are sent only when your organization is in Community mode and you have given AI consent.

Product image links. The shared library may store a public URL pointing to a product image on the vendor’s website; NixBlox does not store a copy of that image file in the shared product library. When the application displays the image, your device requests it from the vendor’s website, which may receive ordinary request information such as your IP address, time, and device information.

Product library (confirmed product configurations). A product’s standard connector and port layout generally describes the vendor’s product rather than a customer’s system design. Shared entries are not intended to identify or describe any customer project. When you confirm a product’s port configuration and contribution is enabled, that confirmed configuration is added to a shared product library keyed to the product, so it works out of the box for other NixBlox users. Before a product configuration enters the shared library, we remove free text, network addresses, credentials, notes, and anything else that is not vendor product fact (“Public Product Data” — manufacturer, model, part number, connector types, specifications, and the product’s public address). Library entries as served to any user carry no organization or user attribution and are not presented as originating from or associated with any customer. Contributions happen only when you explicitly confirm and save a configuration — never silently — and only when your organization is in Community mode and the “Contribute confirmed product configurations” setting is on. Shared-library contributions are intended only for product facts obtained from publicly available manufacturer sources. Do not contribute information taken from customer, confidential, distributor-restricted, or other non-public materials. NixBlox may reject or remove a contribution if its source cannot be verified. Opting out of contribution does not reduce your access to the library.

Separately from the entry itself, our servers keep an internal record of which organization and account contributed or corrected each entry and when. That record exists for moderation, abuse prevention, and correcting or refunding metered usage; it is visible only to NixBlox personnel and is never served to other users or published as part of the library. We treat that record as identifiable information: each contribution or correction has its own record, retained for up to 24 months after that contribution or correction and then deleted or de-identified; a later correction by someone else does not extend the original contributor’s record. Records associated with a reported entry, an abuse investigation, or a legal dispute may be retained longer as reasonably necessary to resolve that matter. The unattributed Public Product Data may remain in the shared library.

Reporting a library entry. You can flag a shared library entry for review with a fixed reason. The library entry stores an aggregate count by fixed reason without visible user attribution. Separate server logs identify the requesting account and organization for 90 days for abuse prevention.

The NixBlox Capture browser extension. NixBlox offers an optional extension for Chrome and Edge that lets a member of an Organization Account propose a product to the organization’s catalog from the product page they are viewing. The extension acts only when you click its button, and only on the page you clicked it on. It then sends NixBlox the address and title of that page and the product details it found there — the vendor, model and part number, and links to the product’s image, datasheet and manual — so that the product can be added to, or proposed for, your organization’s catalog. It does not send pages you did not click on, your browsing history, cookies, prices, or the page’s underlying code, and it does not run in the background or watch the sites you visit. The extension communicates only with NixBlox’s own service and with our sign-in provider (Section 5).

If your organization’s participation mode allows AI-assisted features and you have given the consent described above, the extension also uses Block AI to read the page: the page’s visible text is sent to NixBlox and processed by our AI provider exactly as described in this Section, and one AI unit from your organization’s monthly allowance is used (none when NixBlox already holds a result for that product address from the last 90 days — Section 7). If you have not yet consented, the extension asks first, and you may decline; if your organization has turned AI features off, or its allowance or your own monthly limit is used up, the extension does not use Block AI and tells you so — your capture still proceeds from the page’s own details. Your organization’s administrator controls the participation mode (above).

Products you propose are stored with your organization’s catalog together with your name or email address as the proposer, the time, and the details the extension found; your organization’s administrators and the members it designates as catalog reviewers can see them, and a product that is accepted into the catalog is visible to every member of the organization. On your device the extension keeps only your sign-in, the organization you chose, and the result of your most recent capture, until you sign out or close your browser; it stores nothing else. Catalog entries and proposals are kept for as long as your organization keeps them (Section 7).

3.How We Use Information

We use the information we collect to: provide, operate, and secure the Services; issue, validate, and renew licenses; manage organization accounts, memberships, and permissions; operate the AI features and meter their use; respond to support requests; send service emails (license keys, invitations, renewal, account and security notices); improve the Services; and comply with legal obligations.

We send marketing email only if you ask for it, and every marketing email includes an unsubscribe option. Service emails are sent as needed to operate the Services.

Analytics. NixBlox owns aggregated or de-identified analytics and product insights derived from diagnostic, performance, security, and feature-usage data. NixBlox does not analyze the contents of Customer Content to create generalized product datasets or train models.

Personnel access. NixBlox personnel can view organization names, member emails and roles, license records, per-organization AI usage totals, and library reports through internal tools, in order to run the beta program, support you, and prevent abuse. NixBlox personnel do not access the contents of Customer Content except when requested by an authorized user for support, when reasonably necessary to investigate a security or abuse incident, when required by law, or when necessary to protect the Services or other users. Personnel access is limited to those with a legitimate need and is subject to confidentiality obligations.

4.SMS / Text Messaging

Providing a mobile phone number to NixBlox does not by itself enroll you in text messaging. If you separately opt in to receive text messages or initiate a text conversation with NixBlox — for example, during a support conversation — we may send one-to-one conversational text messages (SMS) related to your account, license, support requests, scheduling, and one-time verification codes you request. NixBlox does not send marketing or promotional text messages, and does not use text messaging for automated or bulk campaigns.

Message frequency varies. Message and data rates may apply. You can opt out of text messages at any time by replying STOP to any message; reply HELP for help, or email support@nixblox.app. These commitments continue to apply to any text message sent or received after your account closes, including opt-out, help, and confirmation messages.

We do not sell your mobile phone number, and we do not share your mobile number or your SMS opt-in / consent information with third parties or affiliates for their own marketing or promotional purposes. We share mobile numbers only with the service providers that help us deliver these messages (our telecommunications provider and Microsoft), and only to send the messages you have consented to receive. Providing a mobile number is optional and is not a condition of any purchase. Mobile carriers are not liable for delayed or undelivered messages.

5.How We Share Information

We share information only with:

• Service providers that host and operate our infrastructure, under terms that limit their use of the data to providing services to us: Amazon Web Services (hosting, storage, databases, sign-in, and organization email such as invitations), Resend (delivery of license-key emails), Vercel (hosting of our websites), Microsoft 365 (business email), and, for text messages you have opted into, our telecommunications provider and Microsoft (Teams Phone);
• AI service providers — currently Anthropic — to process Smart Import extraction requests (Section 2). Anthropic states that ordinary commercial API inputs and outputs are generally deleted within 30 days; that content flagged for a usage-policy violation may be retained for up to two years and associated trust-and-safety classification scores for up to seven years; that information associated with feedback submitted to Anthropic may be retained for up to five years and used for model training; and that longer retention may occur when required by law or permitted for enforcement or anonymized analysis. Under the commercial settings used by NixBlox, Anthropic does not use API inputs or outputs for model training unless NixBlox expressly opts in or provides them as feedback. Under NixBlox’s verified Anthropic API configuration and operating procedure, NixBlox does not opt Smart Import inputs or outputs into model training and does not submit them to Anthropic as feedback; NixBlox uses only Anthropic’s Messages API (no file storage with Anthropic), and NixBlox’s server logs record neither the text sent to Anthropic nor the text returned;
• Your Organization Account. If you belong to a Business Organization Account on NixBlox, its administrators can see your membership details, including your email address, role, and assigned locations, and content stored in the account’s cloud workspace;
• Share links your organization creates. An administrator of your Organization Account can create a share link that lets anyone who holds the link (and its passcode, if the administrator set one) view one published revision of a project in a web browser, read-only, without a NixBlox account, until the link expires (at most one year after it was created) or the administrator revokes it. A share link shows that revision’s drawings, material list and cable list, and your organization’s name and logo. It does not show field notes, unpublished drafts, other projects, or the name or email address of any member. NixBlox does not ask a person opening a share link who they are; we keep a count of opens and the time of the most recent open on the link record itself, and our standard access and security logs record the request as described in Section 7. Administrators decide whom to give a link to and can revoke it at any time;
• Legal and safety recipients, if required by law or to protect rights, safety, or the integrity of the Services; and
• A successor entity, in connection with a merger, acquisition, or sale of assets, subject to this Policy.

We do not sell or rent personal information, and we do not share it with third parties for their own advertising.

6.Cookies and Similar Technologies

Our websites are static pages and use no advertising or analytics cookies. The organization portal and our internal tools use strictly necessary cookies and browser storage to keep you signed in (via Amazon Cognito) and to operate the application. We do not respond to browser “Do Not Track” signals because we do not track you across sites.

7.Data Retention

• Standard access and security logs are retained for 90 days. They may contain account and request identifiers, timestamps, IP addresses, request outcomes, and — for AI extractions and library writes — the product’s public address with the requesting account and organization. They do not contain submitted product-page or document text.
• AI metering records. The per-request spend ledger and batch-job records (including any product text and extracted spec-sheet text submitted with a batch) are deleted automatically after 30 days; the monthly usage counters kept for each account and organization (units used per month, no product data) are deleted automatically after 13 months.
• Product-reachability rate-limit counters expire within 48 hours; the extracted product record cached for a product address (product data, not personal information) expires after 90 days; aggregate extraction statistics (per website, no account) expire after 13 months.
• Internal product-library contributor attribution is retained for up to 24 months after the contribution or correction it records, then deleted or de-identified (longer only for a reported entry, an abuse investigation, or a legal dispute, as reasonably necessary).
• Agreement acceptance records are retained while the applicable account or organization is active and for six (6) years after the later of the most recent acceptance or termination. A record may be retained longer while reasonably necessary for a pending dispute, legal hold, or legal obligation.
• Account, license, and organization records — beta requests, issued license keys, membership records, and the record of a closed organization (its name, account type, and closure dates) — are retained while your account or organization is active and for six (6) years after the later of the key’s expiry, the account’s closure, or the organization’s termination, for license validation, fraud prevention, tax, accounting, and legal compliance, after which they are deleted or de-identified. A beta request that does not result in an issued key or account is retained for six (6) years after the request is decided, withdrawn, or otherwise closed; if it results in a key or account, the later applicable period above applies.
• Email, support, and text-message correspondence with NixBlox is retained for six (6) years and then deleted. Website request logs are held by our hosting provider for one day; transactional email delivery logs are held by the email provider named in Section 5 under its own retention schedule. Records subject to a legal hold, security investigation, or legal obligation may be retained longer as reasonably necessary.
• Cloud project drafts and published revisions are retained until your Organization Account deletes them or the organization-closure lifecycle below begins, except that NixBlox keeps only the ten most recent cloud drafts of each project: when a newer draft is saved, older drafts beyond ten are deleted automatically. Deleted files, noncurrent versions, and backups remain subject to the deletion periods stated in this Section.
• Share links. A share-link record holds a one-way fingerprint of the link (never the link itself), a salted fingerprint of its passcode if one was set, the project and published revision it names, which administrator created it and when, its expiry, its revocation date if revoked, and open counts. It holds no information about the people who opened it. The record is deleted automatically when the link expires (the expiry the administrator chose, at most one year), and earlier if the project is deleted or the Organization Account is terminated and its content deleted under the closure lifecycle below. A revoked link is kept until its expiry so that it keeps refusing, then deleted.
• Organization catalog entries and proposals, including products proposed through the NixBlox Capture extension, are retained for as long as your Organization Account keeps them — the organization’s administrators and catalog curators may edit or delete them at any time — and are deleted with the organization’s other cloud-stored Customer Content under the organization-closure lifecycle below. A proposal record names the member who proposed it and, once reviewed, the member who reviewed it, for as long as the entry itself is kept.
• Cloud-stored Customer Content when an Organization Account closes or is terminated. A user-only closure or removal within a Business Organization Account does not trigger this rule and does not close that account. Closing a Business Organization Account does not close its members’ individual user accounts (Terms of Service Section 8). This rule applies when an Organization Account itself — Personal (on the account holder’s explicit confirmation) or Business (on a verified administrator’s request) — or NixBlox’s provision of Services to it is terminated: NixBlox records the termination date and preserves the account’s cloud-stored Customer Content for 30 days (unless retention is prohibited by law, involves unlawful content, or would create a material security risk). During that period a verified administrator, or the Personal Organization Account’s holder, may ask NixBlox for a copy of that content by contacting support@nixblox.app; NixBlox may provide one at its discretion (Terms of Service Section 8). Project files you saved locally remain on your own device. After that period the active copies are deleted, and prior versions and backups expire within the periods stated above. We do not guarantee that terminated accounts or cloud data can be restored.
• Sign-in identity after a closure. When your user account is closed (alone, or with a Personal Organization Account), sign-in is disabled immediately and the sign-in identity (email, credentials, and multi-factor enrollment) is deleted 90 days after the closure — the date is stated in your closure confirmation notice. Until then NixBlox can reopen the account on your verified written request. A legal hold on an organization you belonged to may delay the deletion. The closure record, acceptance records, and other legally retained records remain under their separate periods above.
• Database backups are point-in-time recoverable for up to 35 days.

If you close your account, or your organization is deleted, we delete or de-identify associated personal information within a commercially reasonable period, except where retention is required by law or described above. Public Product Data contributed to the shared library may remain after an account or organization closes. Shared entries are not presented with user or organization attribution; however, while NixBlox retains an internal record linking a contribution to an account or organization, we treat that record as identifiable information and retain or de-identify it as described above.

8.Security

We use commercially reasonable technical and organizational safeguards: encryption in transit and at rest, access controls designed to segregate organization data and enforce authorization on service requests, rate limiting, and multi-factor authentication on administrative access. No system is perfectly secure. If we learn of a breach affecting your personal information, we will notify you as required by applicable law. Please use a strong, unique password for your account, and report security concerns to support@nixblox.app.

9.Your Rights and Choices

Depending on where you live, you may have rights to access, correct, delete, or receive a copy of your personal information, or to object to or restrict certain processing. You may request closure of your user account at any time by contacting support@nixblox.app; we verify that the request comes from the account holder before acting on it. A user-only closure within a Business Organization Account does not close that account; closing a Personal Organization Account, or a Business Organization Account on an administrator’s verified request, starts the content lifecycle in Section 7 (Terms of Service Section 8). Organization members should direct requests about organization-held content to their organization’s administrator, who controls that workspace; we support administrators in fulfilling such requests. For requests about information NixBlox controls, contact support@nixblox.app. We will respond within the timeframe required by applicable law and will not discriminate against you for exercising your rights.

AI feature choices. You can decline AI consent (AI assist stays off for you) and turn off “Help improve Smart Import” and “Contribute confirmed product configurations” on your installation; neither of those choices reduces your access to the shared library. Your organization’s administrator can set the organization’s participation mode: Private mode preserves read access to the shared library but prevents contributions; Off mode disables AI-assisted features and shared-library access for the organization. Product blocks already created remain usable in every mode.

10.Where Information Is Processed

NixBlox is based in the United States, and the Beta Services and their infrastructure are operated in the United States. Beta accounts are currently offered only to United States users and organizations. If you access our public websites from outside the U.S., the technical information described in Section 1 is processed in the U.S.

11.Children

The Services are business tools for adults; you must be at least 18 to use them, and they are not directed to children. We do not knowingly collect personal information from anyone under 18; if you believe we have, contact support@nixblox.app and we will delete it.

12.Changes to This Policy

We may update this Policy from time to time. We will post the updated version with a new “Last updated” date and, for material changes, provide notice through the Services or by email. Because NixBlox is in beta, we expect to update this Policy when paid plans launch and when features change.

Contact

NixBlox LLC — Taylor, Michigan, USA
Email: support@nixblox.app
Web: https://nixblox.app

Version history

• September 28, 2026. Added the NixBlox Capture browser extension (Section 2), share links (Sections 5 and 7), the retention of organization catalog entries and proposals (Section 7), and the web viewer’s on-device copies (Section 1).
• September 8, 2026. Updated for the current beta: agreement acceptance records, Personal and Business Organization Accounts, AI Smart Import and product-library processing, the installation identifier, retention periods, account closure, text messaging, and where information is processed.
• September 3, 2026. Interim beta publication, measured claim-by-claim against the software as built.
• July 14, 2026. First draft.