Privacy Policy

ContractIQ collects four categories of information: account data, workspace content, integration data, and usage and log data.

Account data

• Identity details supplied when an account is created or invited: name, work email address, and the role assigned within the workspace.
• Authentication metadata. ContractIQ does not store passwords. Sign-in is delegated to the PraxisIQ identity provider, which issues the session tokens ContractIQ validates.
• Workspace membership and permissions, including which workspace an account belongs to and what it is entitled to do there.
• Billing and subscription details, such as plan, billing cycle, and subscription status. Card details are handled by our payment processor and are never stored by ContractIQ.

Workspace content

• Documents uploaded to or imported into a workspace: contracts, amendments, order forms, statements of work, invoices, and their attachments.
• Signature envelopes and their metadata retrieved from a connected e-signature provider, including envelope status, signer names and email addresses, and completion timestamps.
• Data extracted from those documents: parties, effective and expiry dates, renewal and notice terms, payment terms, currencies and values, clauses, obligations, and risk classifications.
• Anything users add on top of that content: notes, tags, corrections to extracted values, saved reports, and Ask IQ conversations.

Contracts routinely contain personal data about people who are not ContractIQ users, such as signatories, named contacts, and account managers. That data is processed on behalf of the workspace owner and is subject to the same isolation, retention, and deletion rules as the rest of the workspace content.

Integration data

• OAuth tokens and connection credentials for the providers a workspace chooses to connect, including DocuSign, Google Drive, HubSpot, QuickBooks, Amazon S3, Slack, and Microsoft Teams.
• The configuration of each connection: the folders, buckets, accounts, or channels selected as a source or destination.
• The records synchronized through those connections, such as files and folder metadata from a document store, deal and company records from a CRM, and envelope records from an e-signature provider.
• Synchronization history: what ran, when, what changed, and what failed.

A connection is only made when a workspace administrator authorizes it, and it reaches only the scopes and locations selected during setup. Disconnecting a provider revokes the stored credentials.

Usage and log data

• Application and audit logs recording who did what and when: sign-ins, uploads, imports, exports, permission changes, and configuration changes.
• Technical request data: IP address, browser and device type, timestamps, request paths, and error diagnostics.
• Product-usage telemetry: which features are used and how often, processing durations, and job outcomes.
• Cookies and equivalent browser storage strictly needed to keep a session signed in and to remember interface preferences.

Information is used to deliver the service that the workspace has asked for, and to keep it secure and working.

• To provide the platform: storing documents, extracting and classifying contract terms, generating reports and reconciliations, tracking renewals, and answering questions in Ask IQ.
• To operate connected integrations: importing and synchronizing documents and records, and writing back only where the workspace has explicitly enabled it.
• To authenticate users, enforce roles and permissions, and maintain the audit trail.
• To secure the service: detecting abuse, investigating incidents, preventing fraud, and enforcing rate and usage limits.
• To support customers: diagnosing reported problems and responding to requests, using the least data required.
• To administer subscriptions, billing, and plan entitlements.
• To improve reliability and performance using aggregated and de-identified operational metrics.
• To meet legal, regulatory, and contractual obligations.

PraxisIQ does not sell personal data, does not share it for cross-context behavioral advertising, and does not use workspace content to build advertising or marketing profiles.

Contract intelligence is the product, so it is worth being precise about how it works.

Documents added to a workspace are processed by large language models in order to read them, identify the document type, extract structured contract data (parties, dates, values, payment and renewal terms, clauses, and obligations), classify risk, and answer questions asked in Ask IQ. Extracted text and the relevant passages of a document are sent to the model as part of that processing.

Model inference runs on Anthropic Claude models accessed through Amazon Bedrock, inside the PraxisIQ cloud account, in the AWS region where the ContractIQ service is deployed. That region is a property of the deployment, not of an individual workspace: ContractIQ does not currently offer per-workspace data residency. Document content is sent to the model provider only as an input to answer that specific request.

Workspace content is not used to train third-party models, and it is not used to train models for the benefit of any other customer.

Model output is an assistance layer, not a determination. Extracted fields, classifications, and Ask IQ answers can be incomplete or wrong, and every value that matters should be verified against the underlying document. ContractIQ keeps the source document alongside the extracted data precisely so that verification is possible.

No decision with a legal or similarly significant effect on an individual is made by ContractIQ automatically. The platform presents information to people who decide what to do with it.

ContractIQ relies on a small set of providers to run. Each is bound by contract to process data only on documented instructions and to protect it appropriately.

• Amazon Web Services: hosting, compute, object storage, managed databases, and queues for the platform and its data.
• Amazon Bedrock, serving Anthropic Claude models: the large language model inference described above.
• The PraxisIQ identity provider: authentication, session issuance, and workspace entitlement.
• A payment processor: subscription billing and payment card handling. PraxisIQ receives subscription status, not card numbers.

Providers that a workspace connects itself (DocuSign, Google Drive, HubSpot, QuickBooks, Amazon S3, Slack, and Microsoft Teams among them) are not PraxisIQ subprocessors. They are the customer's own services, reached with credentials the customer authorizes, and the customer's agreement with that provider governs what happens to data there. Data flows to such a provider only where the workspace has enabled that flow.

Information may also be disclosed where the law requires it, to enforce our agreements, to protect the rights and safety of users or the public, or to a successor entity in a merger, acquisition, or sale of assets. Where notice of a legally compelled disclosure is permitted, the affected customer will be notified.

Every document, extraction, report, integration connection, and conversation belongs to exactly one workspace, and the platform segregates data by workspace. Application requests are scoped to the workspace of the authenticated session rather than to anything the browser supplies.

The paths members use day to day, reading, searching, exporting, reporting, and asking questions, return only the content of the workspace they belong to. Object storage keys, background jobs, extraction runs, and audit records also carry workspace scope, so segregation is maintained outside the request path as well as inside it.

PraxisIQ does not represent that this segregation is absolute. Administrative and maintenance operations exist that are not scoped to a single workspace, and no security control is free of defects. Any gap found in workspace scoping is treated as a security issue and remediated, and reports can be sent to the contact address below.

Access within a workspace is further limited by role. Administrative actions such as connecting an integration, inviting members, or changing workspace settings are restricted to administrators.

• Data is encrypted in transit using TLS between the browser, the ContractIQ API, and every provider the platform calls.
• Documents and files are held in Amazon S3 with server-side encryption enabled on the bucket, and the application database has storage encryption enabled. Both are encrypted at rest by the cloud provider.
• Access tokens for connected providers are issued to a single workspace and are encrypted by the application before they are written to the database. They are never returned to the browser and are never exposed through the API.
• Access to a connected provider is renewed through that provider's OAuth refresh flow when a token expires. A workspace administrator can revoke a connection at any time by disconnecting the provider, which discards the stored credentials.
• Object storage blocks all public access. Documents are served through short-lived presigned links issued only to authorized members of the workspace that owns them.
• Access to production systems is limited to the personnel who need it, authenticated through the identity provider, and logged.
• Administrative and data-affecting actions are recorded in an audit trail.
• PraxisIQ holds a SOC 2 Type II attestation. The report is available on request.

No platform can promise perfect security. If a breach affecting personal data occurs, PraxisIQ will notify affected customers and any regulator entitled to notice within the timeframes the applicable law requires.

Workspace content is retained for as long as the workspace exists, because the value of a contract repository is that it remembers. Retention is otherwise governed by the following rules.

• Deleting a document removes it and its derived extractions from the workspace, so it is no longer accessible in ContractIQ: it leaves the repository, search, reports, and Ask IQ. Some underlying stored copies of the original file, in object storage and in backups, may be retained after that point. Deleting in the application is not, on its own, verified destruction of the underlying file.
• A customer who needs verified destruction of the underlying files should request it using the contact details below. That is handled as a specific request rather than by the delete action in the application.
• When a subscription ends, workspace content remains available for export during a wind-down window and is then deleted from the application within a commercially reasonable period after termination. The qualification above about underlying stored copies applies here too. A customer that needs a specific deletion deadline, or written confirmation of destruction, should agree it in writing with PraxisIQ.
• Account records are deleted when the account is removed, except where retention is required to complete a transaction, resolve a dispute, or satisfy a legal obligation.
• Audit and security logs are retained for as long as they are needed for security, accountability, and legal purposes, and are not trimmed on request. An audit trail that can be edited by the people it records is not an audit trail.
• Billing records are retained for the period required by tax and accounting law.
• Aggregated and de-identified operational metrics that cannot be linked back to an individual or a workspace may be retained indefinitely.

A workspace administrator can request deletion of specific content, or of the workspace as a whole, at any time using the contact details below.

Data is stored in the AWS region where the ContractIQ service is deployed. That region applies to the whole deployment rather than to an individual workspace, and per-workspace data residency is not currently offered. Support, engineering, and incident response may require access from other countries, and the providers listed above may process data outside the region where it is stored.

Where such a transfer involves personal data protected by the laws of the European Economic Area, the United Kingdom, or Switzerland, it is made under an approved transfer mechanism, ordinarily the European Commission Standard Contractual Clauses together with any additional safeguards the transfer requires.

Depending on where you live, you may have some or all of the following rights over personal data about you.

• Access: obtain confirmation of whether your personal data is processed, and a copy of it.
• Correction: have inaccurate or incomplete personal data corrected. Values extracted by the platform can also be corrected in the application, and the correction is what the workspace then uses.
• Deletion: request erasure of your personal data, subject to the retention obligations described above.
• Export: receive your data in a structured, commonly used, machine-readable format, or have it transmitted to another provider. Workspaces can export documents, extracted data, and reports from the application at any time.
• Restriction and objection: ask that processing be limited, or object to processing based on legitimate interests.
• Withdraw consent: where processing rests on consent, withdraw it without affecting processing already carried out.
• Complain: lodge a complaint with your local data protection authority.

If your data sits in a workspace operated by your employer or another organization, that organization controls it. Send the request to them and PraxisIQ will assist them in fulfilling it. Requests sent directly to PraxisIQ about such data will be forwarded to the workspace owner.

Requests are answered within the period the applicable law sets, and identity is verified before any data is released.

ContractIQ uses cookies and browser storage that are strictly necessary to run the application: keeping a session signed in, protecting against cross-site request forgery, and remembering interface preferences such as the selected workspace.

The application does not use advertising cookies and does not permit third-party advertising trackers. Blocking strictly necessary cookies will prevent sign-in from working.

ContractIQ is a business application, is not directed to children, and is not intended for anyone under 16. PraxisIQ does not knowingly collect personal data from children. If such data has been collected, it will be deleted on notice.

This policy may be updated as the product and the law change. The date at the top of this page always reflects the current version.

Where a change materially affects how personal data is handled, PraxisIQ will give reasonable advance notice before it takes effect, by email to workspace administrators or by a notice in the application.

Questions about this policy, or a request to exercise any of the rights above, can be sent to privacy@praxisiq.ai.

The data controller for account, billing, and usage data is PraxisIQ LLC.

General information about PraxisIQ is available at praxisiq.ai.