PolignLegal

Contents

  1. 1. Parties and term
  2. 2. Terms used
  3. 3. Distribution license
  4. 4. Limits and End Customer terms
  5. 5. No counting and no reporting
  6. 6. Designated Releases
  7. 7. Support
  8. 8. Names and publicity
  9. 9. Fees and invoicing
  10. 10. Renewal and ending
  11. 11. Infringement claims
  12. 12. Data and confidentiality
  13. 13. Warranty and liability
  14. 14. General
  15. Schedule A

Polign OEM Agreement

Version: oem-agreement-2026-11-09
Published: November 9, 2026
Term: 12 months
Fee: one annual fee, agreed up front and written in Schedule A
Reporting: 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.

The free polign_db license lets anyone run polign_db and build services on it, but not hand the software itself to someone else. This agreement gives Customer that right: Customer ships polign_db inside the product it sells, under its own product's name, into its customers' environments.

One annual fee, agreed up front. Nothing is counted and nothing is reported: no customer list, no node count, no royalty. Copies Customer has delivered keep running whether or not this agreement is renewed.

1. Parties and term

This OEM 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 10.

2. Terms used

“polign_db” means the polign_db server, command-line tools, and documentation, in the binary form Polign releases.

“Product” means each Customer product named in Schedule A, including its later versions and renamed successors that serve the same purpose.

“End Customer” means a person or organization that receives the Product from Customer, or from a reseller or distributor of Customer, for its own use.

“Designated Release” means a release of polign_db that Customer has told Polign it ships in the Product, as section 6 describes.

“Software License” means the license file shipped with each polign_db release.

3. Distribution license

During the Term, Polign grants Customer a non-exclusive, worldwide license to:

  • copy polign_db and include it in the Product, in any packaging Customer uses for the Product, including installers, container images, machine images, and appliances;
  • distribute polign_db as part of the Product to End Customers, directly and through Customer's resellers and distributors, and sublicense to End Customers the right to run polign_db as part of the Product;
  • install, run, and maintain polign_db as part of the Product in End Customers' environments and in environments Customer operates for them; and
  • distribute polign_db releases that Polign publishes during the Term as updates to the Product.

Under Customer's name. The Product ships under Customer's own name. Customer does not need to show Polign's name or logo in the Product, its interface, or its marketing. The only notices Customer must keep are in section 4.

Affiliates. Customer's affiliates listed in Schedule A may exercise these rights for the Product. Customer is responsible for their compliance.

Customer's own use. Customer's internal use of polign_db, including to develop, test, and demonstrate the Product, is already covered by the Software License and is not limited by this Agreement.

4. Limits and End Customer terms

Part of the Product only. Customer distributes polign_db only as part of the Product. The Product must do substantially more than expose polign_db's database features, and Customer may not distribute polign_db by itself or as a general-purpose database product, unless Schedule A says otherwise.

Binary form only. Polign delivers polign_db in binary form. Customer receives no source code and may not modify, reverse engineer, decompile, or disassemble polign_db, except where the law allows it despite this term. Configuring polign_db and calling its documented interfaces is not modification.

Notices. Customer keeps the copyright and license notices inside the polign_db files as delivered, and includes the THIRD_PARTY_NOTICES file Polign ships, or its contents, wherever the Product lists its third-party notices.

End Customer terms. Customer provides the Product to End Customers under Customer's own terms. Those terms must, in Customer's own words and without naming Polign: allow polign_db to be used only as part of the Product; prohibit further distribution of it, and reverse engineering of it except where the law allows; and give no warranty and accept no liability on behalf of Customer's suppliers. Polign has no contract with End Customers and owes them nothing directly.

Resellers and distributors. Customer's resellers and distributors may pass the Product along unchanged under terms that protect polign_db at least as well as this section. Customer is responsible for their compliance.

5. No counting and no reporting

The fee does not depend on how many End Customers, copies, nodes, machines, or environments there are, on how much data they hold, or on Customer's revenue. Customer does not report End Customer names, counts, or usage to Polign, and Polign has no right to audit Customer or to contact End Customers.

polign_db has no license key and no license check. If a release can send anonymous usage telemetry, Customer may turn it off in the Product by the documented setting, and Polign does not use telemetry to count anything under this Agreement.

Not more than once in a Term, at Polign's written request, Customer confirms in writing that it distributes polign_db only as sections 3 and 4 allow. That confirmation is the only report under this Agreement.

6. Designated Releases

Customer's schedule, not Polign's. Customer decides which polign_db release each version of the Product ships and when to move to a newer one. Customer designates a release by naming it in Schedule A or later by email to its Polign contact.

Support window. Polign supports each Designated Release for 18 months from the day Customer designates it, while the Agreement is in effect, and supports up to two Designated Releases at the same time. During that window Polign provides fixes for security vulnerabilities and for Blocking Issues, as defined in section 7, as a patch to the Designated Release, so Customer is not required to take a newer minor release to receive a fix.

Security fixes. Polign tells Customer about a security vulnerability that affects a Designated Release as soon as Polign has confirmed it, and no later than Polign tells any other customer, with the affected versions and the planned fix. Customer keeps that information confidential until Polign publishes the fix.

Moving between releases. Before Customer moves the Product to a newer release, Polign reviews the release notes against how the Product uses polign_db, confirms the on-disk and bucket format compatibility of the target release, and, if a format change is involved, gives the order of steps and the rollback path for End Customer installations.

Advance notice. Polign gives Customer at least 90 days' written notice before a release removes an interface or changes a storage format in a way that a Designated Release's data cannot be read by the next release without a migration step.

7. Support

Who supports whom. Customer supports its End Customers. Polign supports Customer's engineers. Polign does not contact End Customers and does not need access to their environments or data.

Named contact. Polign names one engineer as Customer's contact in Schedule A and names a replacement in writing if that person changes.

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: polign_db in a Designated Release is unavailable in an End Customer's production use of the Product, is losing or corrupting records, or is returning wrong answers to a documented operation, and there is no workaround;
  • two business days for an issue that degrades production use without stopping it, or that blocks a Product release; and
  • three business days for every other question, including integration, packaging, configuration, and upgrade planning.

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 10 and receive a refund of the unused part of the fee.

What Customer provides. Customer names a technical contact in Schedule A who receives security notices. Customer gives Polign the version numbers, configuration, logs, and reproduction steps reasonably needed to diagnose an issue, and does not send Polign End Customer 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.

What support does not include. Writing the Product's code; supporting End Customers directly; operating Customer's or End Customers' infrastructure; and on-site work. Polign may offer these separately.

8. Names and publicity

This Agreement gives neither party a right to use the other's trademarks. Customer may state the fact that the Product includes polign_db where it lists its components, and is not required to. 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. Polign never names an End Customer.

Customer may share feedback about polign_db, and Polign may use that feedback without restriction or attribution, but not to disclose Customer's confidential information.

9. Fees and invoicing

Fee. The fee for the Term is the annual fee in Schedule A. It is flat and agreed before signing. Nothing in the Agreement is metered and there is no royalty.

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 6 and 7 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.

10. Renewal and ending

Renewal. The Agreement renews for successive 12-month terms unless either party gives written notice of non-renewal at least 90 days before the current Term ends. Polign may change the fee for a renewal term by giving notice at least 120 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 7, 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.

Copies already delivered. When the Agreement ends for any reason, every copy of the Product that an End Customer received before the end stays licensed. Those End Customers may keep running polign_db as part of the Product for as long as they like, and nothing in the software stops.

Wind-down. Unless Polign ended the Agreement for Customer's uncured breach, for 12 months after the end Customer may keep delivering the Product, including patches of the Designated Releases it already has, to End Customers who had the Product before the end, and for 90 days after the end may fulfil orders an End Customer signed before the end. Customer may not add other End Customers after the end.

Services. When the Agreement ends, the services in sections 6 and 7 stop. Customer's own rights under the Software License continue unchanged.

11. Infringement claims

Polign's defense. Polign defends Customer against a third party's claim that polign_db, as Polign delivered it, infringes that party's copyright, patent, or trademark or misappropriates its trade secret, and pays the damages and costs finally awarded or agreed in a settlement Polign approves.

Exceptions. Polign has no obligation for a claim to the extent it arises from the rest of the Product, from a combination with something Polign did not supply where polign_db alone would not infringe, from use outside this Agreement, or from continued distribution of a release after Polign provided a non-infringing replacement and reasonable time to adopt it.

Remedies. If polign_db is, or Polign believes it may become, the subject of such a claim, Polign may obtain the right for Customer to continue, modify or replace polign_db so it no longer infringes without materially reducing its function, or, if neither is commercially reasonable, end the Agreement and refund the unused part of the fee. Copies End Customers already have are handled as section 10 describes.

Customer's defense. Customer defends Polign against a third party's claim that arises from the Product apart from polign_db, from Customer's terms with or statements to End Customers, resellers, or distributors, or from distribution outside sections 3 and 4, and pays the damages and costs finally awarded or agreed in a settlement Customer approves.

Procedure and limit. The party seeking defense gives prompt written notice, lets the other control the defense and settlement, and cooperates reasonably. A settlement that admits fault or imposes an obligation on the defended party needs its consent. Each party's total obligation under this section is limited to two times the annual fee in Schedule A. This section states each party's entire obligation for the claims it covers.

12. Data and confidentiality

polign_db runs in Customer's and End Customers' own environments, and their 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, the Product's unreleased plans, and unpublished security information 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.

13. Warranty and liability

Polign warrants that it has the right to grant the licenses in this Agreement, that it provides the services with reasonable skill and care, and that it 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 is responsible for testing each release in the Product before shipping it and for the Product as a whole.

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, Customer's distribution of polign_db outside sections 3 and 4, a party's fraud or willful misconduct, or liability that cannot be limited by law. Section 11 has its own limit.

Source code escrow is not part of this version; it may be added in Schedule A for a specific Customer.

14. General

The Agreement, including Schedule A, is the entire agreement about its subject and replaces earlier discussions and any terms on a purchase order. It adds to the Software License and does not narrow it. 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. Either party may assign the Agreement to a successor in a merger or sale of substantially all of its business or of the Product line, with notice to the other; any other assignment needs consent. Each party complies with the export control and sanctions laws that apply to it, and Customer is the exporter of the Product. polign_db is commercial computer software under FAR 12.212 and DFARS 227.7202, and Customer passes it to government End Customers with no greater rights than this Agreement allows. 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, Product, and order details

Customer legal name[ ]
Customer address and notice email[ ]
Affiliates covered[None / list]
Product(s)[Name and one-line description of each]
How the Product reaches End Customers[Installed in End Customer environments / operated by Customer for End Customers / through resellers]
Designated Release(s) at signing[polign_db version]
Customer technical contact (name, role, email)[ ]
Customer billing contact and purchase order number[ ]
Polign named contact[ ]
Support channels[support@polign.com / shared chat channel]
Annual feeUS$[ ]
Publicity approval (section 8)[Not granted / Granted: Polign may name Customer and show its logo]
Additional terms (if any)[None]
Polign, Inc.Customer
Signature
Name and title
Date