Data Processing Addendum

Data Processing Addendum

This Data Processing Addendum (this "Addendum") is part of the Terms and Conditions of Nventr AI, LLC (the "Terms") and applies to every Account on nventr.io. Capitalized terms have the meanings given in the Terms. Customer is the controller (or business) of the Customer Data it brings to the Products; Nventr AI, LLC ("Nventr") is the processor (or service provider) and acts only on Customer's documented instructions, as given through the Products. If this Addendum conflicts with the Terms, this Addendum controls for the handling of Customer Data.

1. What Nventr processes, and why

Customer Data means the documents, files, prompts, outputs, database contents, and configuration Customer or its users submit to or store in a Product, and the Customer-Built Assets (apps, workflows, agents, knowledge, prompts, policies, and configuration) they create in it, together with the names and email addresses of Customer's users. Nventr processes Customer Data only to provide, secure, and support the Products as Customer directs through the Products, to generate Usage Meters (counts, never contents), and to comply with law — and for no other purpose. Nventr does not sell Customer Data, does not use it to train, fine-tune, or improve machine-learning models (its own or a third party's), does not permit its model providers to do so, and does not use it to build profiles of anyone.

2. Who can see it

• Isolation. Customer Data is stored under Customer's organization and is reachable only by the members Customer has added, within the workspace and project roles Customer assigned. These boundaries are enforced by database security rules and by server-side checks on every request; they are not a matter of staff discretion.
• No standing staff access. Nventr personnel have no path inside the Products to Customer Data without a grant from Customer. Operator accounts see platform-level metadata — organization names, member counts, job status, usage counters, health — but cannot open Customer's workspaces, knowledge, workflows, or conversations on their own.
• Customer-authorized support access. When Customer wants Nventr to look at something, an Account admin creates a support access grant in the console (Administration → Support access). The grant states its scope — one NoVA conversation, one project, one workspace, or the whole organization — and a reason, and expires after 48 hours unless the admin selects a longer period; a grant with no expiry can be created only by an Account owner. Any admin can revoke a grant at any time. Nventr's access under a grant is read-only and limited to the grant's scope, and each read is recorded in Customer's organization (who, when, what was opened, under which grant) before the content is returned.
• Engagement seats. When Customer engages Nventr to build inside its organization under a written statement of work, an Account admin seats the named Nventr personnel in the workspaces the admin names, at the role the admin chooses, for the term the admin sets (an end date is required). Those seats are ordinary workspace seats enforced by the same rules as Customer's own members; every change the seated person makes is recorded in Customer's audit trail under that person's own identity, marked as Nventr personnel. The seats are removed automatically at the end date, or at once when Customer ends the engagement.
• Per-organization encryption of stored content. Files Customer uploads and files the Products generate for Customer are encrypted at rest under a key held in Nventr's cloud key-management service. On the Business plan, the App Kit Business plan, and enterprise orders the key is dedicated to Customer's organization; on other plans content is encrypted under a platform content key with the same policy. The key's policy allows the running service to decrypt; human infrastructure identities in Nventr's cloud account may not. Any change to that key policy, and any attempt by a human identity to decrypt with the key, is recorded in Nventr's cloud audit trail and raises an alert. Hosted App Kit instances encrypt object storage with a per-instance key held on that instance.
• Privileged infrastructure access. A small number of named Nventr operators hold infrastructure credentials that could technically read structured records in the control-plane database. Those credentials are issued to named individuals, are kept out of source code and personal devices, and their use is recorded in cloud audit logs retained for at least ninety days.
• Break-glass access, logged for Customer. Outside a grant or an engagement seat, Nventr accesses Customer Data only (a) to investigate a security incident that affects Customer, or (b) when legally compelled. Each such access is recorded in Customer's organization *before* it happens — who, why, what will be looked at — and closed with notes afterwards. Customer's admins see every record under Administration → Support access → Operator access log. An empty log means no one at Nventr has looked at Customer's content.

3. Security measures

Encryption in transit (TLS 1.2+) and at rest (AES-256; stored content under the keys described in Section 2, database records under provider-managed keys); per-organization authorization enforced in database rules and server guards; uploads and downloads through short-lived signed URLs; secrets held in managed secret stores, never in code or the browser; least-privilege service roles dedicated to the Products; application logs that record identifiers, sizes, and durations rather than content; a cloud audit trail of administrative, key, and storage access with automated alerts on human access to content or keys; every server-side change to an organization recorded in that organization's audit trail; version-controlled deployment pipelines; log retention of ninety days; backups managed by the cloud providers. Nventr will not materially reduce these measures during the term.

4. Sub-processors

Nventr uses the following sub-processors for Customer Data, each bound by written terms at least as protective as this Addendum:

Model providers receive only the text needed for the action a user requested, under API terms that prohibit training on that data; they may retain API inputs for up to thirty days for abuse monitoring and then delete them. Customer may bring its own model keys, in which case Nventr's providers receive nothing. Providers Customer connects itself through an Add-On (social and media platforms, image and video model providers named in Customer's console) act on Customer's own authorization and are described in the Privacy Policy. Nventr will give at least fifteen days' notice before adding a sub-processor that will handle Customer Data, by updating this Addendum and notifying Account owners by email; a Customer that objects may terminate and receive a pro-rated refund of prepaid Fees.

5. Customer's rights and requests

Customer's owners and admins can export, correct, and delete Customer Data and remove members at any time through the console. If an individual asks Nventr directly to exercise a data-protection right over Customer Data, Nventr will refer the individual to Customer and assist Customer in responding. Nventr will provide reasonable information about its processing to support Customer's own compliance obligations, including completing security questionnaires, no more than once a year unless a security incident requires more.

6. Security incidents

If Nventr becomes aware of unauthorized access to, or loss of, Customer Data, Nventr will notify the affected Account's owners by email without undue delay and in any case within seventy-two hours of confirming it, describe what it knows, what it is doing about it, and what Customer may need to do, and keep Customer informed as the investigation progresses.

7. Retention, return, and deletion

Customer Data is retained while the Account exists. Deleted Customer Data is removed from production systems within seven (7) days and from backups within thirty (30) days, as the Terms provide. On termination of the Account, or on written request from an owner, Nventr deletes all Customer Data within thirty (30) days and confirms the deletion in writing, except where law requires retention, in which case Nventr keeps only what the law requires and continues to protect it under this Addendum. Acceptance records for these agreements (who accepted which version, when, from where) are retained as evidence of the contract.

8. Term and changes

This Addendum applies for as long as Nventr holds Customer Data for the Account. Nventr may update it to reflect changes in the Products or in law; material changes are presented to Account owners for acceptance, and the version accepted for an Account, with its content hash, is recorded on the Account and available to its admins. Where Customer requires a countersigned copy of this Addendum, one is available for enterprise orders.

Contact

Privacy and security requests: the contact form at https://nventr.io/contact, or written notice to Nventr AI, LLC, 8550 West Desert Inn Road #102-452, Las Vegas, NV 89117. Please mention "Data processing" so the request is routed and tracked correctly.

Terms · Privacy · End user agreement · Data processing addendum