UpgradeMajor upgrade underway: a new video studio, with more models coming soon. Stay tuned.
Inferway
All legal documents
Inferway · Legal

Data Processing Agreement

The data processing terms governing how GWMM LLC (operating as Inferway) handles Personal Data on behalf of Inferway customers.

GWMM LLC · a company registered in Wyoming, United States at 30 N Gould St, Sheridan, WY 82801

In forceLast updated November 17, 202622 min read · 12 sections

Data Processing Agreement

This Data Processing Agreement ("DPA") is entered into by and between GWMM LLC, operating as Inferway ("Inferway," "Company," "we," "us," or "our"), and the Customer entity accessing the Services ("Customer," "you," or "your"). This DPA forms part of, and is incorporated into, the Terms of Service, and governs the processing of Personal Data by the Company on behalf of the Customer in connection with the Services.


Section 1

1. Definitions

  • "Controller" means the entity that determines the purposes and means of processing Personal Data. For purposes of this DPA, the Customer is the Controller.
  • "Processor" means the entity that processes Personal Data on behalf of the Controller. For purposes of this DPA, the Company is the Processor.
  • "Personal Data" means any information relating to an identified or identifiable natural person ("Data Subject").
  • "Customer Content" means the prompts, messages, parameters, and generated completions submitted to or produced by the AI models through the Services. Customer Content is processed under the Company's Zero Data Retention commitment (Section 4) and is not retained by the Company, subject to the bounded exceptions in Section 4. Customer Content sent to a third-party model (marked third party in the model catalog) is processed by an external inference service provider and is outside that commitment (Section 4). The Company keeps an encrypted copy of a failed request to such a model only as described in Section 4 ("Failed requests to third-party models").
  • "Sub-processor" means any third-party Processor engaged by the Company to process Personal Data in connection with the Services.
  • "Processing" means any operation or set of operations performed on Personal Data, whether or not by automated means.
  • "Services" has the meaning given to it in the Terms of Service — the Inferway AI model inference endpoint, gateway, API, Sandbox, and console.

Section 2

2. Scope and Purpose

This DPA applies to Personal Data processed by the Company in connection with the Services, including account and authentication data, billing data, and non-content request metadata submitted by or on behalf of the Customer (including by the Customer's end users, API consumers, or AI Agents acting under the Customer's account). The Company processes Personal Data only on the documented instructions of the Customer, which include processing necessary to operate the Services as described in the Terms of Service and Privacy Notice. Customer Content for ordinary text inference (prompts and completions) is processed transiently to execute inference requests and is governed by the Zero Data Retention commitment in Section 4; except for the bounded exceptions in Section 4, including generated H3 result videos and text-to-image result images stored in private Cloudflare R2 storage for 7 days for customer download, the Company does not store Customer Content, and never uses Customer Content to train, fine-tune, or evaluate any model.


Section 3

3. Processor Obligations

a. The Company shall process Personal Data only on the documented instructions of the Customer. b. The Company shall ensure that personnel authorized to process Personal Data are bound by confidentiality obligations. c. The Company shall implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk, as described in Section 4. d. The Company shall not engage a new Sub-processor without giving the Customer prior notice via the Sub-processor list in Section 5, and an opportunity to object as described therein. e. The Company shall assist the Customer, to the extent reasonably necessary, in responding to Data Subject requests and in meeting the Customer's obligations relating to data breach notification and data protection impact assessments.


Section 4

4. Security Measures and Zero Data Retention

The Company implements technical and organizational measures designed to protect Personal Data against unauthorized or unlawful processing and against accidental loss, destruction, or damage, including: encryption in transit (TLS) for all API and console traffic; hashed storage of API keys (SHA-256, not reversible); access controls and role-based account membership; and per-request observability logging limited to non-content metadata for anomaly and fraud detection.

Zero Data Retention (ZDR). Subject to the exceptions in this Section, when an ordinary text inference request is served by the Company's own infrastructure, Customer Content (the prompt, parameters, generated completion, and the derived KV cache) exists solely in GPU and system memory for the duration of a single request and is released and overwritten the moment the response finishes. Prompts and text completions are never written to disk, logged in readable form, persisted to any datastore, or used to train, fine-tune, or evaluate any model. As a bounded exception for video and image generation, generated H3 result videos and text-to-image result images are stored in a private Cloudflare R2 bucket so the customer can download them via a short-lived presigned URL, and are retained for 7 days before deletion; prompts for video generation are not stored in R2; encrypted database copies follow the H3 exception below. The Company retains only non-content request metadata — timestamp, input/output token counts, model name, latency metrics, HTTP status, and an anonymous session or authenticated account identifier — for operational and billing purposes.

Safety evidence. As an exception to Zero Data Retention, the content of requests that the Company's safety systems determine to involve suspected child sexual abuse material or other illegal content is encrypted and retained for up to 12 months as evidence, and may be disclosed to law enforcement or reporting organizations as required by law. Customer Content from other requests is not retained, except for the separate, limited retention exceptions described in this Section.

Uploaded input media. If the Customer uses the media upload endpoint (/v1/media/uploads), the images the Customer uploads are stored in a private Cloudflare R2 bucket for at most 48 hours, or until the Customer deletes them with DELETE /v1/media/{id}, whichever comes first, and are used only to serve the Customer's own inference requests. They are deleted when the Customer's account is deleted. This is a bounded exception to Zero Data Retention, alongside the result video and image exception above; apart from these two exceptions, the exceptions for safety evidence, failed requests to third-party models, and H3 prompts and optional processing described in this Section also apply.

Inference for self-hosted models is served by the Company's own infrastructure. Models marked third party in the model catalog are served by the external inference service providers listed by category in Section 5; Customer Content sent to them is not covered by the Zero Data Retention commitment in this Section, the provider's own retention and training terms apply, and a self-hosted model is never served by them. Customer-selected MiniMax official enhancement and future 2K upgrades are third-party processing, not a failover or fallback path. AI support conversations are not part of the inference service; they are answered by a model the Company runs on its own infrastructure, are not passed to a third-party model provider, are not Customer Content, and are not covered by the Zero Data Retention commitment in this Section.

Failed requests to third-party models. When a request to a model marked third party in the model catalog has been sent to an external inference service provider and ultimately fails for any reason — including an error response, a timeout, a connection failure or an interrupted response stream — after every retry and alternative route has also failed, the Company keeps an encrypted copy of the request payload as sent to the provider, the provider's error responses where there were any, the failure type, its timing and the provider host used, solely to determine the cause of the failure. The copy is encrypted with AES-256-GCM in PostgreSQL on AWS in the United States, is accessible only to authorized Company personnel through an internal tool that logs every access, is not used to train, fine-tune or evaluate any model, and is erased after no more than 30 days or on account deletion, subject to a lawful preservation hold. Encrypted S3 database backups rotate out within 30 days and are outside that erasure. API keys, client IP addresses, the request's user and metadata fields, and output already streamed to the Customer are never kept. Successful requests, requests to self-hosted models, and requests to third-party models marked as zero data retention by their provider are not kept.

Abuse-prevention signals. To prevent one person from opening multiple accounts to obtain free usage, the Company keeps a keyed one-way digest (HMAC) of the IP address from which an account signed up, first claimed a free video, or attempted to sign up, and of the browser user agent with which the account signed up. When you sign up, our website also stores a randomly generated identifier in your browser (in this site's local storage and a first-party cookie) and computes a digest from some browser and device characteristics (such as screen size, time zone, language and graphics rendering). Both are sent with your sign-up request; we keep only their keyed one-way digests, used only to tell whether several accounts come from the same browser, never for advertising or cross-site tracking. The address and the user agent themselves are never stored, the digests cannot be turned back into them, and they are used only to determine whether accounts or sign-up attempts are related. Digests tied to an account are kept while the account exists and erased on account deletion; digests of sign-up attempts not tied to an account are kept for no more than 12 months and then erased.

H3 prompts and optional processing. H3 prompts, rewritten prompts and MiMo drafts are encrypted in PostgreSQL on AWS in the United States and erased from the database after no more than 7 days, or on account deletion, subject to a lawful preservation hold. Encrypted S3 database backups are outside that erasure operation and rotate out within 30 days. The IR Lambda processes prompts in memory without writing them to disk. This is a further exception to ZDR. MiMo's primary inference processor is a third-party inference provider based in the United States, which retains inputs and outputs for as long as needed to provide its services and does not promise zero data retention; it may pass them to its own upstream providers, and processing locations are unspecified. Requests to MiMo, including requests that name no model, free H3 prompt enhancement and suggestions, and prompt safety screening are third-party processing outside Inferway's zero data retention commitment. MiMo enhancement remains free. For customers billed in CNY or USD, if the Customer separately chooses MiniMax official enhancement, prompts are sent from Inferway's US AWS service to Nanonoble Pte. Ltd. in Singapore and billed per token; reference images are sent only when image-assisted rewriting is offered. Future optional 2K upgrades will send a short-lived Cloudflare R2 source-video link to Nanonoble, with Lambda relaying result bytes. Nanonoble's Privacy Policy, Section 9 states personal data is stored in US data centers; this does not establish that processing or storage occurs only in Singapore. MiniMax retention and training terms remain unverified; Inferway's ZDR commitment does not cover its processing.

Specific security documentation is available upon request to hello@inferway.ai.


Section 5

5. Sub-processing

The Customer authorizes the Company to engage the Sub-processors listed below to deliver the Services. A new or replacement Sub-processor is published on this list for at least 7 days before the relevant processing may begin. This period starts when the revised legal text is actually published, not at its draft or commit date; no separate notification is sent. During that period, Customers may object: third-party models are selected per request, so Customers may decline them by not selecting them; MiniMax official enhancement and future 2K upgrades are selected per order, so Customers may decline them or contact hello@inferway.ai to disable them for their account. Continuing to use other Services does not constitute consent to optional third-party processing.

Sub-processors (Phase 1, optional third-party processing)

Self-hosted models run on Inferway infrastructure; third-party models and optional MiniMax processing are separate. Requests to models marked third party in the model catalog are served by external inference service providers and are not covered by Inferway's zero data retention commitment. Third-party models marked zero data retention in the model catalog are sent only to provider endpoints that state they do not retain prompts or responses. That statement is the provider's own and has not been independently verified by Inferway; these models remain outside Inferway's zero data retention commitment. MiMo's primary inference processor is a third-party inference provider based in the United States, which retains inputs and outputs for as long as needed to provide its services and does not promise zero data retention; it may pass them to its own upstream providers, and processing locations are unspecified. Requests to MiMo, including requests that name no model, free H3 prompt enhancement and suggestions, and prompt safety screening are third-party processing outside Inferway's zero data retention commitment. MiMo enhancement remains free. MiniMax official prompt enhancement is customer-selected, separately consented and billed per token; 2K upgrades are future optional processing. The MiniMax entries below provide advance notice, not activation. DeepInfra and Together AI are not engaged. A self-hosted model is never served by a third party. A request to a model marked third party may be served by any one of several external inference service providers in that category.

The table distinguishes self-hosted inference from customer-selected third-party processing. The Sub-processor table is regenerated from the structured data-flow contract; self-hosted inference never falls back to a third party.

NameClassificationPurposeData categoriesDirectionRetention authorityPublic label
Cloudflare R2 (H3 result storage)content storage processorStores the generated H3 768p result video and the generated text-to-image result images in a private Cloudflare R2 bucket so the customer can download them, and serves them through a short-lived presigned URL. This entry receives Customer Content and holds it at rest. A future customer-selected 2K upgrade will let MiniMax read the source video through a short-lived URL.Customer Content at rest (generated H3 result video and text-to-image result images, retained 7 days), Object key and content digest (no prompt or completion text)egressh3-retention-7dCloudflare R2 · video and image result storage (7-day retention)
Cloudflare R2 (input media storage)content storage processorStores media a customer uploads for up to 48 hours so their own later inference requests can reference it without the bytes entering the request envelope. Deleted on DELETE /v1/media/{id}, on account deletion, and by the reaper at the 48-hour retention boundary; the bucket lifecycle rule applies only as a backstop.Customer Content at rest (customer-uploaded input media, retained 48 hours), Object key and content digest (no prompt or completion text)egressmedia-input-retention-48hCloudflare R2 · input media storage (48-hour retention)
Inferway self-hosted inferenceinference processorExecutes model inference (prompt → completion) for the active Catalog models on GPU hosts that Inferway operates.Customer Content (prompt and completion, in-memory only), Model identifier, Token counts (input and output), Request timestamp and latency, Authenticated account or anonymous session identifieringressinferway-self-hosted-zero-data-retentionInferway self-hosted inference (Canada and US)
Cloudflare, Inc.metadata processorEdge TLS termination/proxy and tunnel transport. The public edge may process plaintext request bytes depending on the active zone and tunnel configuration; the tunnel forwards traffic to the Inferway Gateway. Deployed logging, caching, WAF and retention settings require separate operator evidence.Customer Content in transit (edge processing may be plaintext), Connection metadata (source IP at edge, TLS handshake)transitcloudflare-zone-policyCloudflare · edge/TLS and tunnel transport (configuration-dependent)
Functional Software, Inc. (Sentry)metadata processorReceives application error and performance diagnostics from the Inferway gateway and from inferway.ai. Does not receive Customer Content. Gateway events are rebuilt from a field allowlist before they leave the process (app/telemetry_privacy.py): prompts, completions, request bodies, headers, cookies and query strings are never copied, and an event that fails that rebuild is dropped rather than sent. Browser reporting is gated on analytics consent and applies the same allowlist rebuild.Exception type and normalized error category (no Customer Content), Approved route template (no path parameter values), Release identifier and deployment environment, Browser error stack, user agent and client IP (website only)egresssentry-error-diagnosticsSentry · error diagnostics
PostHog, Inc.metadata processorProduct analytics for inferway.ai. Captures anonymized usage events; does not receive Customer Content. Funnel milestones (signup, API key created, first request, first top-up) are additionally synced server-side from operational records, keyed by a one-way hash of the account identifier — never the raw account id.Product usage events (route, feature, no Customer Content), Pseudonymous session and account identifier, Server-synced funnel milestone events keyed by one-way-hashed account identifier, Anonymized visitor IPtransitposthog-product-analyticsPostHog · product analytics
Resend, Inc.metadata processorDelivers transactional and consented marketing emails to customers. Resend receives the recipient address, subject, and rendered message body for transmission. Prompt and completion data never enter emails. Open and click tracking are disabled.Recipient email address, Rendered email subject and content, Feedback message and optional reply email, Delivery event timestamps and statusegressresend-email-deliveryResend · customer email delivery
Vercel Inc.metadata processorWebsite hosting, performance telemetry, and edge rendering for inferway.ai. Does not receive Customer Content.Page view and route metrics (no Customer Content), Core Web Vitals (aggregate), Anonymized visitor IP for rate limitingtransitvercel-platform-aggregateVercel · website hosting
Amazon Web Services, Inc.operator infrastructureHosts the Inferway control plane: the EC2 virtual machine that runs the gateway and workers, RDS PostgreSQL for accounts and billing records, S3 for encrypted database backups, and Systems Manager for configuration and operator access. Encrypted H3 prompts, rewrites and MiMo drafts are stored in PostgreSQL and erased after no more than 7 days. Encrypted copies of third-party model requests that ultimately failed (request payload, provider error responses where any, failure type, timing and provider host) are stored in PostgreSQL and erased after no more than 30 days. Encrypted S3 backups rotate out within 30 days; database erasure does not erase backups. The IR Lambda processes prompts in memory without writing them to disk, and sends them from the United States to the selected MiniMax service. Future 2K processing will relay result bytes and source-video links through Lambda; this is not an activation notice.Account and billing records (email, wallet balance, transaction ledger), Non-content request metadata (timestamp, model, token counts, latency, status), Customer Content at rest (encrypted H3 prompts, rewrites and MiMo drafts in PostgreSQL, erased within 7 days), Customer Content at rest (encrypted copies of failed third-party model requests in PostgreSQL, erased within 30 days), Encrypted database backups in S3 (including encrypted H3 content, rotated out within 30 days), Customer Content in IR Lambda memory (no disk writes; future 2K result bytes and source-video links), Operational logs (no prompt or completion content)internalh3-content-erasure-7d-failed-request-30d-backup-rotation-30dAmazon Web Services · control-plane hosting and encrypted backups (US · us-west-2)
Inferway operator infrastructureoperator infrastructureProvides request routing, storage, caching and observability on AWS infrastructure operated by Inferway in the United States (control plane), and inference on Inferway-operated GPU hosts. Ordinary text inference is in-memory. H3 prompts, rewrites and MiMo drafts are encrypted in PostgreSQL and erased after no more than 7 days; encrypted S3 backups rotate out within 30 days and are outside database erasure.Customer Content (ordinary text inference in memory), Customer Content at rest (encrypted H3 prompts, rewrites and MiMo drafts stored in PostgreSQL, erased within 7 days), Non-content request metadata (timestamp, model, token counts, latency, status), Operational logs (no prompt or completion content), Audit and abuse-control signals (no prompt or completion content)internalh3-content-erasure-7d-backup-rotation-30dInferway operator infrastructure (US · control plane on AWS us-west-2)
Vast.ai Inc.operator infrastructureProvides the rented GPU hosts on which Inferway runs model inference. Customer Content is processed on these hosts during inference.Customer Content (processed on the rented host during inference)internalinferway-self-hosted-zero-data-retentionVast.ai · rented GPU hosts for inference (Canada and US)
Clerk, Inc.payment identity providerUser authentication and account management for the Inferway console and API key lifecycle. Does not receive Customer Content.Email address, Display name, Authentication credentials (hashed), Account identifieringressclerk-account-lifecycleClerk · user authentication
Stripe, Inc.payment identity providerPayment processing, wallet top-ups, and billing records for Inferway direct customers. Does not receive Customer Content.Payment instrument data (handled and stored by Stripe), Billing email and invoice metadata, Transaction records (amounts, timestamps, status)ingressstripe-billing-ledgerStripe · payment processing
External inference service providersthird party inference processorServes requests for the third-party models a customer selects (marked third party in the model catalog) outside Inferway's self-hosted infrastructure. Prompts, model parameters and generated responses pass to or from the external inference service provider to serve the request. Inferway does not forward account identifiers, API key identifiers, client IP addresses or the request's user and metadata fields. This processing is not covered by Inferway's zero data retention commitment; the provider's own retention and training terms apply and have not been independently verified by Inferway. Inferway keeps an encrypted copy of a request that ultimately failed for up to 30 days to diagnose the failure, except for models marked as zero data retention by their provider; successful requests are not kept. Self-hosted models are unaffected. MiMo's primary inference processor is a third-party inference provider based in the United States, which retains inputs and outputs for as long as needed to provide its services, with no zero-retention commitment. It may pass them to its own upstream providers; processing locations are unspecified. Requests that name no model, free H3 prompt enhancement and suggestions, and prompt safety screening are also served by MiMo. Another third-party inference provider remains a backup under its own configured provider policy.Customer Content (prompts, model parameters and generated responses), Model identifier and non-content request metadata needed to serve the requestegressexternal-inference-provider-policyExternal inference service providers · third-party models (no Inferway ZDR)
MiniMax International (Nanonoble Pte. Ltd.)third party inference processorOptional, separately consented Context-IR for customers billed in CNY or USD, billed per token. For the customer's separately selected feature, prompts are sent from Inferway's AWS service in the United States to Nanonoble Pte. Ltd., whose registered location is Singapore; optional reference images follow the same route if image-assisted rewriting is offered. A future optional 2K upgrade sends a short-lived Cloudflare R2 source-video link to the same recipient. Its privacy policy says personal data is stored in data centers in the United States; this does not establish that processing or storage occurs only in Singapore. MiniMax retention and training terms remain unverified.Customer prompts and reference images (only for the selected feature), Rewritten prompts; future 2K source video links, video bytes and resultsegress保留条款待核实MiniMax International · optional processing (advance notice; not activation)

Classification summary

  • Inference Processor (1): Inferway self-hosted inference
  • Third Party Inference Processor (2): External inference service providers, MiniMax International (Nanonoble Pte. Ltd.)
  • Metadata Processor (5): Cloudflare, Inc., Functional Software, Inc. (Sentry), PostHog, Inc., Resend, Inc., Vercel Inc.
  • Payment Identity Provider (2): Clerk, Inc., Stripe, Inc.
  • Operator Infrastructure (3): Amazon Web Services, Inc., Inferway operator infrastructure, Vast.ai Inc.
  • Content Storage Processor (2): Cloudflare R2 (H3 result storage), Cloudflare R2 (input media storage)

The Company selects Sub-processors that publish retention commitments appropriate to the data they receive. The active backend at any time is reflected on the System Status page (https://inferway.ai/status).


Section 6

6. Data Subject Rights

The Company will assist the Customer, taking into account the nature of the processing, in responding to Data Subject requests to exercise their rights (including access, rectification, erasure, restriction, and portability). End users may also submit such requests directly to the Company at https://inferway.ai/console#settings or https://inferway.ai/contact; the Company will notify the Customer without undue delay if it receives a request directly from a Data Subject that relates to the Customer's account.


Section 7

7. Data Breach Notification

In the event of a confirmed Personal Data breach affecting the Customer's data, the Company will notify the Customer without undue delay, and in any event within 72 hours of becoming aware of the breach, providing (to the extent known): a description of the nature of the breach, the categories and approximate number of Data Subjects and records concerned, the likely consequences, and the measures taken or proposed to address it.


Section 8

8. Audit Rights

The Customer may request evidence of the Company's compliance with this DPA (such as Sub-processor agreements or security documentation) no more than once per year, upon reasonable prior written notice, by contacting hello@inferway.ai. On-site audits are not offered; the Company will cooperate in good faith to provide reasonably requested documentation instead.


Section 9

9. Data Retention and Deletion

Except for the result-file, input-media, H3 prompt and optional-processing, and failed third-party request exceptions in Section 4, ordinary text inference content is not kept beyond a single request. Encrypted H3 prompts, rewrites and MiMo drafts are erased from the database after no more than 7 days, and encrypted copies of failed third-party requests after no more than 30 days, subject to lawful preservation holds. Encrypted S3 backups rotate out within 30 days and are outside database erasure. MiniMax retention and training terms remain unverified. Consent versions and timestamps in order records are not Customer Content and survive content erasure. The Company retains account and billing records for as long as the Customer maintains an account with the Services, and thereafter as required by applicable tax, accounting, or legal obligations. Upon account deletion — whether initiated by the Customer or in response to a verified deletion request — the Company anonymizes the associated user record (email and name are removed or replaced, and the Clerk authentication link is severed) within its systems. Billing and transaction records and per-request non-content usage records tied to the account are retained in de-identified form after anonymization for accounting, fraud-prevention, and legal-compliance purposes, consistent with the Prepaid Wallet & Credit Balance terms of the Terms of Service, under which prepaid credit balances are forfeited (not refunded) on deletion. Non-content request and usage metadata is retained for up to 90 days. The Customer or an end user may request deletion at any time via https://inferway.ai/console#settings or by contacting hello@inferway.ai.


Section 10

10. International Transfers

The Company's control-plane servers are located in the United States, and, as described in Section 5, the Sub-processors currently engaged to deliver the Services, including the hosts on which inference runs, may operate in other countries, as stated for each in that list (with certain providers maintaining global edge networks). If the Customer is located in, or processes Personal Data of Data Subjects located in, the European Economic Area, United Kingdom, or Switzerland, and requires a specific transfer mechanism, the Company relies on the European Commission's Standard Contractual Clauses (SCCs), together with the UK International Data Transfer Addendum where applicable, as the transfer mechanism for such Personal Data. Customers requiring a countersigned SCC package should contact the Company at hello@inferway.ai before transferring such data through the Services.

For customers billed in CNY or USD, separately selected and consented MiniMax Context-IR sends the selected H3 prompt from Inferway's AWS service in the United States to Nanonoble Pte. Ltd., whose registered location is Singapore. Reference images are sent only when image-assisted rewriting is offered. A future optional 2K upgrade will send a short-lived Cloudflare R2 source-video link to the same recipient. Nanonoble's Privacy Policy, Section 9 states that personal data is stored in US data centers; this does not establish that all processing or storage occurs only in Singapore. Before processing subject to China's PIPL, including processing for customers billed in CNY, the customer must receive the notice and give separate consent as described in the Privacy Notice's third-party processing section; that section also links to the recipient's contact and rights-request procedure. MiniMax retention and training terms remain unverified.


Section 11

11. Term and Termination

This DPA remains in effect for as long as the Company processes Personal Data on the Customer's behalf under the Terms of Service. Upon termination, the Company will proceed as described in Section 9 (Data Retention and Deletion). This DPA is incorporated into and forms part of the Terms of Service (https://inferway.ai/terms).


Section 12

12. Miscellaneous

a. This DPA is governed by the laws of the State of Wyoming, United States, consistent with the Governing Law section of the Terms of Service. b. Any disputes arising under this DPA are subject to the dispute resolution terms of the Terms of Service. c. In the event of any conflict between this DPA and the Terms of Service on data processing matters, this DPA prevails. d. The Company may update this DPA from time to time; material changes will be reflected by an updated "Last updated" date above.

Contact for DPA Requests

To execute a signed, counterparty-specific version of this DPA or to discuss data processing terms, contact GWMM LLC (operating as Inferway) at hello@inferway.ai, 30 N Gould St, Sheridan, WY 82801, United States.