Merchant of record, seller of record: who is actually selling you the software
The operator runs the catalogue; Lemon Squeezy, LLC is the merchant and seller of record for the payment. What that arrangement changes for a buyer, what it changes for a vendor selling downloads, and the clause that answers what happens if a vendor stops publishing.
A checkout page for self-hosted software usually names two parties, and they are rarely the company whose product you searched for. On ownware.io the second name is Lemon Squeezy, LLC, and it is worth thirty seconds to know why it is there before a card number goes in.
The store's legal page answers it directly. The operator is NaTutti s. r. o., a company registered in Slovakia (EU), and "The catalog, product pages and the buyer portal on this site are run by the operator." The payment is a separate matter: "Purchases are processed by Lemon Squeezy, LLC as Merchant of Record -- Lemon Squeezy is the seller of record for the transaction and handles payment processing, tax/VAT calculation and remittance, receipts, and refunds under its own terms of sale." Two jobs, two companies. The operator runs the shop. Lemon Squeezy runs the till.
What that changes for a buyer
Merchant of record and seller of record are not decorative titles. They say who stands in the transaction, and the store's own terms spell out what follows from that, plainly enough to quote row by row.
| What a buyer wants to know | What the store's terms say |
|---|---|
| Whose name is on the receipt | Lemon Squeezy is "the seller of record for the transaction" and "handles ... receipts" |
| Who a refund request goes through | Lemon Squeezy "handles ... refunds under its own terms of sale" |
| Whose terms of sale cover the payment itself | Lemon Squeezy's, not the operator's -- "under its own terms of sale" |
| Whose law covers the purchase transaction | "the purchase transaction itself is between you and Lemon Squeezy as Merchant of Record and runs under Lemon Squeezy's own terms -- this clause covers the licence and this store, not the payment" |
| Whose law covers the licence and the store | "the law of the Slovak Republic, with its courts having jurisdiction" |
| What if the purchase was made as a consumer | "this does not take away the mandatory protections of the law of the country you live in" |
Put plainly: the name on the bank statement and the receipt is Lemon Squeezy, not the operator. A dispute over a charge or a refund runs through Lemon Squeezy's own process, because Lemon Squeezy is the party that took the payment. The licence terms and the operator's own terms cover the software and the store; they say so about themselves, twice, in the two rows above -- once for the payment, once to preserve whatever protections a buyer already has under the law of their own country. That second qualification is the page being honest about the limit of its own reach rather than claiming more than it can.
Delivery is a separate step from the payment, and the store, not Lemon Squeezy, runs it: once a purchase clears, the download link and the licence key appear on the confirmation page and arrive by email, and the purchase stays visible afterwards in the buyer portal. The payment is Lemon Squeezy's job. Handing over the product is the operator's.
What it means if you are the one selling
The same arrangement looks different from the other side of the counter. For a small vendor selling digital downloads, a merchant-of-record setup means a separate company stands in the transaction in the vendor's place: it is the one whose name is on the receipt, the one a buyer's bank asks a question of, the one that takes on the payment processing and the refund handling, under its own terms. The vendor is not the seller of record for the sale; the merchant of record is.
That covers getting paid. It does not cover getting the product to the buyer, and those are two different jobs even when one company happens to do both. A merchant of record settles the transaction; something else has to hand over the file, the licence key, and the activation limits that go with it. Deliora is built for exactly that second job: self-hosted licence-key delivery for people selling digital downloads, with keys carrying per-domain activation limits, run on the vendor's own server rather than a third party's.
A vendor selling ongoing access to hosted software, rather than a download with a key, is solving a different problem again -- that is a multi-tenant question, not a delivery one, and SaaS Kit is the product for turning a single-tenant PHP application into that shape, with its own database per tenant.
What this page does not cover
The operator's licence and the operator's terms are printed on the legal page, and they say what they cover and what they do not, in their own words:
- The licence and the store's terms are one thing; the payment is another. The page says so itself: the governing-law clause "covers the licence and this store, not the payment." The payment runs under Lemon Squeezy's own terms of sale, not the operator's.
- The software itself carries no warranty: "The software is provided as-is, without warranty -- normal for source-code products, and the reason every product has a free live demo you can try before buying."
- Support is bounded and named as such: "documentation (README and quickstart)... Support is best-effort by email for installation and defects in the delivered code -- it does not include custom development, server administration, or modifications you make to the source."
None of the above is legal or tax advice. It is a plain description of a commercial arrangement, stated in the store's own words, and nothing here should be read as more than that.
The clause that answers what if the vendor disappears
Every self-hosted purchase carries the same quiet worry: what happens to the licence if the company behind it stops publishing. This store's legal page answers that question directly, in a continuity clause adopted 23 August 2026 and written into every product's LICENSE.txt so that it binds the operator and any legal successor, not just a promise on a web page:
"If we do not publish a stable release of a product for 365 consecutive days, that product is considered no longer actively maintained, and for everyone already holding a licence the single-domain limit is lifted: run your copy on as many servers as you own or operate, and commission any developer you choose to maintain it. If no stable release is published for three consecutive years, the software in its last published form becomes available to existing licence holders under the MIT licence, automatically."
That clause sits inside the licence and the store's own terms -- the half of this arrangement the operator can actually promise. It says nothing about the payment, because the payment was never the operator's to promise on; that half belongs to Lemon Squeezy, under its own terms, for as long as the transaction exists.
The decision
Every product in this catalogue is a one-time purchase: "you download a zip and run it on your own server... no subscription, no recurring fees, and the software does not phone home to this store." The payment that gets you there runs through Lemon Squeezy as merchant of record and seller of record; the licence, the delivery, and the continuity clause above are the operator's. Read the full text on the legal page before buying, not after -- it is short, and every sentence in it is a term someone will eventually need.