PolignLegal

Contents

  1. 1. Parties and term
  2. 2. What the agreement covers
  3. 3. Support
  4. 4. Supported releases and upgrades
  5. 5. Roadmap priority
  6. 6. What Customer provides
  7. 7. Fees and invoicing
  8. 8. Renewal and ending
  9. 9. Software license
  10. 10. Data and confidentiality
  11. 11. Publicity
  12. 12. Warranty and liability
  13. 13. General
  14. Schedule A

Polign Production Agreement

Version: production-agreement-2026-11-05
Published: November 5, 2026
Term: 12 months
Fee: US$24,000 per year, flat, invoiced once a year
Metering: none
How it takes effect: signed by both parties, with Schedule A completed. This page is the reference text; it is not accepted by clicking.

Customer runs Polign Recall, and polign_db if it is Customer's store, on its own infrastructure under the free licenses that ship with each release. This agreement adds Polign to Customer's team for a year: a named contact with defined response times, supported releases with upgrade help, and priority on the roadmap.

One number, invoiced once. Nothing is counted: no nodes, agents, seats, or requests. The software itself stays free and keeps running whether or not this agreement is renewed.

1. Parties and term

This Production Agreement (the “Agreement”) is between Polign, Inc., 16893 SE 47th Way, Bellevue, WA 98006 (“Polign”), and the customer named in Schedule A (“Customer”). It takes effect on the date the last party signs (the “Effective Date”) and runs for 12 months (the “Term”), subject to renewal and ending under section 8.

2. What the agreement covers

The Agreement covers Customer's use of Polign Recall (“Recall”), the agent memory and state software Polign publishes under the Apache License 2.0, on any database backend Polign supports when the Agreement is signed. At signing those backends are polign_db, PostgreSQL with pgvector, MongoDB, and Qdrant. A backend Polign adds later is covered from the day Polign documents it as supported.

When Customer uses polign_db as the store (“polign_db Store”), the Agreement also covers polign_db itself: the storage engine, its object storage layout, upgrades, and recovery, as described in sections 3 and 4.

The Agreement covers how Recall behaves on a backend. Operating a PostgreSQL, MongoDB, or Qdrant that Customer runs, including its availability, capacity, backups, and upgrades, stays Customer's responsibility. Polign helps with how Recall uses that backend, not with running the backend.

The Agreement covers Customer and its affiliates listed in Schedule A. Each production deployment, environment, and region of those entities is covered without any count or report.

3. Support

Named contact. Polign names one engineer as Customer's contact in Schedule A and names a replacement in writing if that person changes. The contact knows Customer's deployment and is the first person Customer reaches.

Channels. Customer reaches Polign by the email address and, if listed, the shared chat channel in Schedule A. Support hours are 9 a.m. to 6 p.m. Pacific time on U.S. business days.

Response times. Polign gives a first substantive response from a person, not an automated acknowledgment, within:

  • one business day for a Blocking Issue: Recall, or polign_db under a polign_db Store, is unavailable in production, is losing or corrupting records, or is returning wrong answers to a documented operation, and Customer has no workaround;
  • two business days for an issue that degrades production without stopping it; and
  • three business days for every other question, including upgrade planning, configuration, and how-to questions.

A response time is a commitment to engage, and Polign then works the issue continuously during support hours until it is resolved or a workaround is in place. It is not a guarantee of resolution time. If Polign misses a response time for a Blocking Issue twice in any calendar quarter, Customer may end the Agreement under section 8 and receive a refund of the unused part of the fee.

What support includes. Diagnosing issues in Recall and, under a polign_db Store, in polign_db; fixes in a supported release or a documented workaround; help reading the audit record (recall history, recall diff, as-of reads, and audit bundles) when Customer has to explain why an agent acted; configuration and architecture advice for Customer's deployment; and for a polign_db Store, help with the recovery runbook, including recovering a collection from its bucket.

What support does not include. Writing Customer's application code; operating Customer's infrastructure or a backend Customer runs; work on Customer's models, prompts, or embedding providers; and on-site work. Polign may offer these separately.

Polign does not operate Customer's infrastructure and never needs access to Customer's data to provide support. Customer's cloud, storage, and model costs stay on Customer's own bills.

4. Supported releases and upgrades

A “Supported Release” is the most recent minor release of Recall, and of polign_db under a polign_db Store, plus the minor release immediately before it. Polign publishes which releases are supported with each release. Polign provides fixes for Supported Releases; for an older release, Polign helps Customer upgrade to a Supported Release and then fixes the issue there.

Security fixes. Polign notifies Customer of a security fix in a Supported Release by email on the day it ships, with the affected versions and the upgrade step.

Upgrade help. Before Customer upgrades, Polign reviews the release notes against Customer's deployment and flags anything that needs a change. For a polign_db Store, Polign also confirms the on-disk and bucket format compatibility of the target release and, if a format change is involved, the order of steps and the rollback path.

Stability. Polign publishes which parts of Recall are stable, beta, and deprecated. For a surface marked stable, Polign gives at least one minor release of notice before removing it and names the replacement. The Agreement does not change those definitions, and Customer decides when to install a release.

5. Roadmap priority

Polign considers Customer's fix and feature requests before requests from users without an agreement, tells Customer within ten business days whether and roughly when Polign plans to build each one, and holds a quarterly roadmap call with Customer. Priority is a commitment to consider and to answer, not a commitment to build a specific feature by a specific date.

6. What Customer provides

Customer names a technical contact in Schedule A who receives security notices and coordinates support requests. Customer gives Polign the version numbers, configuration, logs, and reproduction steps reasonably needed to diagnose an issue, and does not send Polign production data, credentials, or regulated personal data unless Polign has agreed in writing to receive them. Response times pause while Polign is waiting for information only Customer can provide.

7. Fees and invoicing

Fee. The fee for the Term is US$24,000. It is flat: nothing in the Agreement is metered, and no node, agent, seat, request, or data volume changes it.

Invoice. Polign sends one invoice on the Effective Date, payable within 30 days by bank transfer (ACH or wire) or card through the payment link on the invoice. If Schedule A lists a purchase order number, the invoice carries it.

Taxes. The fee excludes sales, use, value-added, withholding, and similar taxes, which Customer pays except taxes on Polign's income. If law requires Customer to withhold, Customer pays the amount needed so Polign receives the invoiced fee, unless prohibited.

Late payment. If an invoice is more than 30 days overdue after written notice, Polign may pause the services in sections 3 to 5 until it is paid. Nothing in the software stops, slows, or changes because of a late payment; the software has no license check and Polign has no remote control over it.

8. Renewal and ending

Renewal. The Agreement renews for successive 12-month terms unless either party gives written notice of non-renewal at least 30 days before the current Term ends. Polign may change the fee for a renewal term by giving notice at least 60 days before the current Term ends; the fee in Schedule A otherwise applies. Polign invoices each renewal term on its first day.

For breach. Either party may end the Agreement if the other materially breaches it and does not cure the breach within 30 days of written notice. If Customer ends it for Polign's breach, or under the response-time remedy in section 3, Polign refunds the unused part of the fee pro rata. If Polign ends it for Customer's breach, the fee is not refunded.

For convenience. Neither party may end the Agreement for convenience during a Term. Either party ends it at the end of a Term by the non-renewal notice above.

Effect. When the Agreement ends, the services in sections 3 to 5 stop. Customer's rights under the software licenses in section 9 continue unchanged, and the software keeps running.

9. Software license

Customer runs Recall under the Apache License 2.0 and polign_db under the license file shipped with each release, which is free, has no node or usage limit, and needs no license key or activation. The Agreement does not narrow those licenses, add any limit or usage report, or grant any right to redistribute polign_db. Shipping polign_db inside a product Customer sells needs a separate OEM agreement. Components identified as open source are governed by their own licenses.

10. Data and confidentiality

Recall and polign_db run in Customer's own environment, and Customer's memory and state records never pass through Polign. Polign receives Customer data only when Customer chooses to share it for support, uses it only to provide the services, and deletes it within 30 days after Customer asks or the Agreement ends. If shared material contains personal data, Polign processes it on Customer's instructions, and a data processing addendum is available on request and becomes part of the Agreement when both parties sign it.

Each party keeps the other's non-public information confidential, uses it only for the Agreement, and shares it only with people who need it and are bound to keep it confidential. The commercial terms of the Agreement are confidential. This duty lasts for three years after the Agreement ends, and for trade secrets as long as they remain trade secrets. A legally compelled disclosure is permitted with advance notice when lawful.

11. Publicity

Polign names Customer publicly, or shows its logo, only with Customer's prior written approval, which Customer may give in Schedule A and withdraw at any time. Customer may share feedback about Polign's products, and Polign may use that feedback without restriction or attribution, but not to disclose Customer's confidential information.

12. Warranty and liability

Polign provides the services with reasonable skill and care and will not knowingly introduce malicious code into a release. Otherwise, the software and services are provided as is, and Polign disclaims all other warranties, including merchantability, fitness for a particular purpose, and non-infringement. Customer remains responsible for backups, redundancy, and testing a release before production use.

Neither party is liable for lost profits, revenue, goodwill, or data, or for indirect, special, incidental, consequential, or punitive damages. Each party's total liability under the Agreement is limited to the fees paid or payable in the 12 months before the claim. These limits do not apply to breach of confidentiality, Customer's payment obligations, a party's fraud or willful misconduct, or liability that cannot be limited by law. This version carries no intellectual-property indemnity; one may be added in Schedule A for a specific Customer.

13. General

The Agreement, including Schedule A, is the entire agreement about its subject and replaces earlier discussions and any terms on a purchase order. Changes must be in writing and signed or emailed by both parties. Washington law governs, without regard to conflict-of-law rules, and the state and federal courts in King County, Washington have exclusive jurisdiction. Neither party may assign the Agreement without consent, except to a successor in a merger or sale of substantially all of its business. Legal notices go by email to legal@polign.com, or to Customer's notice address in Schedule A, with a copy by mail to the party's address. Neither party is liable for delay caused by events beyond its reasonable control, except payment. The parties may sign electronically and in counterparts.

Schedule A: Customer, contacts, and order details

Customer legal name[ ]
Customer address and notice email[ ]
Affiliates covered[None / list]
Customer technical contact (name, role, email)[ ]
Customer billing contact and purchase order number[ ]
Polign named contact[ ]
Support channels[support@polign.com / shared chat channel]
Backend(s) in production[polign_db in Customer's bucket / PostgreSQL with pgvector / MongoDB / Qdrant]
Environment[Cloud provider, regions, object store]
Fee for the TermUS$24,000
Publicity approval (section 11)[Not granted / Granted: Polign may name Customer and show its logo]
Additional terms (if any)[None]
Polign, Inc.Customer
Signature
Name and title
Date