Product Terms Framework

1. What this framework is, and what it is not

This framework is a statement of how the corporate layer and the product layer relate. It is part of the Terms of Service for this website and is published in the same legal register.

It is not a product's terms of service, and it does not create a contract about any product. It cannot: a contract about a product is formed inside that product, on terms presented there, by a person who has read them. What this framework does is tell you, before you get that far, which rules will apply and which ones will not — so that the structure of the company is something you can verify rather than something you have to reconstruct.

It was published in advance rather than after the fact: the framework first appeared on 20 July 2026, before Primanza published any product to the public. Writing the rules while there was nothing at stake in them was the point — a framework drafted around a live product tends to describe what was convenient for that product — and the first product was published under these rules rather than the rules under it.

2. Who you contract with

Unless a product states otherwise in its own terms, the counterparty for a Primanza product is Primanza LLC — the company identified in full in the Legal Notice, with the filing number and registered agent stated there. One entity, named, filed and reachable.

If a product is ever operated by a different entity — a subsidiary, an affiliate, a joint venture, or a licensee — that product's terms will name that entity, with its own legal form, jurisdiction and registration, and will say so plainly on the page where you agree to them. A product will not be presented as a Primanza product while quietly contracting you with an entity you cannot identify.

The corporate site never becomes a party to a product agreement, and using this site creates no relationship with a product's operator. Reading about a product here is reading; agreeing to a product's terms is agreeing.

3. Where a product's own rules live

Each product publishes, inside the product itself, the documents that actually govern it. At minimum:

Its own terms of service, stating the entity, the subscription or licence terms, the payment terms, the service commitments and the governing law that apply to it.
Its own privacy policy, describing what that product's application collects, on what basis, from whom and for how long — none of which is described by this corporate site's privacy policy.
Its own cookie disclosure, because a product with accounts sets at least a session cookie and this site sets none.
Its own acceptable use terms, sized to what that product actually does.
Its own support channel and its own security contact, where those differ from the company's published addresses — which is also where an accessibility barrier in the product is reported.
Where it processes personal data on its customers' behalf, its own data processing addendum and its own list of sub-processors.

A product does not inherit these from this site and is not covered by them. A corporate document that purported to answer, from here, what a product's application does with a customer's data would be answering a question it has no way to know the answer to.

4. What a statement on this site does and does not do

This corporate site describes the company and, when a product exists, presents it: what it is for, who it is for, and where to find it. Those descriptions are prepared carefully and are meant to be accurate. They are still marketing surface, and they carry no contractual weight.

Specifically, and to the fullest extent permitted by applicable law:

No description of a product on this site is a representation, warranty, condition or guarantee about that product, and none forms part of any product's contract with you.
No statement here creates a service level, an availability commitment, a support commitment, a security commitment or a data-handling commitment for any product. Those exist only where a product's own terms create them.
No statement about what a product will do, when it will do it, or what it will cost is a commitment. Plans are present intentions, not promises, and the company is under no obligation to update one it has stated.
Where a description on this site and a product's own terms differ as to that product, the product's terms govern, and the difference on this site is an error to be corrected rather than a term to be enforced.

Nothing in this section excludes liability for a statement made fraudulently, or any liability that applicable law does not permit us to exclude. It allocates weight between two documents; it does not license us to publish something untrue. If something on this site is wrong, we want to correct it — write to hello@primanza.com.

5. The registry, and what a status means

Every product Primanza publishes carries a permanent designation in the company's product registry, and the registry entry is what this site renders. Each product has a registry identifier that is never reused, and a lifecycle status. The status is a factual statement about publication, not a marketing label, and it means exactly this:

Coming soon — the product has been announced publicly. It is not presented as generally available, it may not be purchasable, and nothing about it should be treated as a commitment that it will ship.
Live — the product is generally available and this site routes you to the real application. A product is not marked live until the application is running in production at its own address.
Retired — the product has been removed from the active portfolio. It is not publicly listed, and section 9 governs what that meant for the people who were using it.
Draft — the product is being prepared or reviewed. A draft entry is never publicly visible, so if you can read about a product here, it is not a draft.

A product appears on this site only after the application behind it has been completed, brought under Primanza governance, deployed to its own address and verified in production. The registry does not carry placeholders, and the site does not publish a product page for something that does not yet exist. Where the portfolio is empty, this site says nothing about products at all rather than showing an empty shelf.

6. Product addresses: how a product is tied to the company

A Primanza product runs at an address of its own: either a domain of its own, as ReplyTune runs at replytune.com, or a subdomain of primanza.com. Either way, a product you are being asked to trust can be tied back to the company you can verify on this site, in both directions — the product identifies Primanza LLC as its operator, and this site's product index names the product and links to its address. A common failure mode of umbrella companies is that the products cannot be tied back to the parent at all.

Neither arrangement may be allowed to imply more than it is. Sharing an owner, or a parent domain, is not sharing a system:

Each product is a separate application, separately deployed, with its own database, its own credentials and its own authentication. An account with one product is an account with that product.
Signing in to one product does not sign you in to another, and does not sign you in to anything on this corporate site — which has nothing to sign in to.
Cookies are scoped to each product's own host and never to primanza.com as a parent domain, so a session is not readable across products. The Cookie Policy states this precisely for both arrangements, including what a parent-scoped cookie would have meant and why none is used.
This corporate site holds no product data and is not connected to any product's systems. It could not surface a customer's data if it were asked to.
Each product's own terms, privacy policy and support channel govern it, as set out in section 3. Neither a shared owner nor a shared parent domain makes this site's documents apply to a product.

The layers that genuinely are common across the portfolio are the company that owns everything and the domain registrations and DNS configuration it maintains for its products. We name them rather than claim that nothing at all is shared. The Security page treats that naming layer as in scope for vulnerability disclosure for exactly this reason.

7. Bringing a product under Primanza governance

A Primanza product is built as its own project and is brought under Primanza governance only once it is complete: reviewed, deployed to its own address, verified in production, and given its registry entry. Until that point it does not appear on this site in any form.

Onboarding a product changes who governs it, not what the people using it agreed to. If a product with existing users is brought under Primanza governance, the terms and privacy policy those users accepted continue to apply until they are lawfully changed, and any change is made through the change process in those terms — with notice, and with the right to stop using the product rather than accept it. Governance does not reach back and rewrite an agreement already made.

8. If a product's ownership or control changes

Primanza LLC owns the products it publishes. Ownership can change: a product may be sold, assigned, reorganised into another entity, or come under different control through a corporate transaction. This is a normal event for a company built around a portfolio, and this section states now what protection you have when it happens.

Where a product with users changes hands:

You will be told, through the product, before or at the time the change takes effect, and told who the new operator is — named, with its legal form and registration, not described as 'a member of our group'.
The terms and the privacy policy you accepted continue to apply to the acquirer until they are lawfully changed, and any change follows the notice process in those terms. An acquirer does not get to treat a change of ownership as a fresh start on your data.
Your personal data moves with the product only to the extent the applicable law and that product's privacy policy allow, and for the purposes you were originally told about. A change of ownership is not a new legal basis for a new purpose.
If the change is one you do not accept, you will have a reasonable period — at least 30 days from notice — to export your data in a usable format and to close your account, and closing it for that reason will not cost you a cancellation charge.
Where the applicable law gives you more than this, the law applies. This section is a floor, not a ceiling, and a product's own terms may improve on it but may not reduce it.

The same applies in reverse to this corporate site: if the company itself is reorganised, sold or merged, the entity identified in the Legal Notice changes, and this site's legal register is updated to identify the real operator rather than left standing as a record of who it used to be.

9. If a product is withdrawn

Products end. Some do not find a market, some are superseded, and some are not worth running any more. A portfolio company that does not say this in advance is planning to say nothing at the time.

Where a product with users is discontinued, marked retired and taken offline:

You will be given notice through the product before service ends — at least 60 days, unless a shorter period is forced by law, by an authority, or by a circumstance genuinely outside the company's control, in which case you will be told which of those it was.
You will have an export window of at least 30 days from that notice, in which you can retrieve your data in a common, machine-readable format, at no charge.
Amounts you have paid for a period of service that will not now be delivered are refunded pro rata, unless the applicable law requires more.
After the export window and any retention period the law requires, the data is deleted rather than kept indefinitely against a possible future use.
A product's own terms may give you longer or better than any of this. They may not give you less.

A retired product's page is removed from the public portfolio, but its registry identifier is never reused for anything else. A reused identifier would make the company's own record of what it has published unreliable, and that record is the point of keeping one.

10. Money is handled in the product, never here

This corporate website concludes no transaction, takes no payment, holds no payment credential and operates no checkout. Any price on this site, if one is ever shown, is descriptive and is not an offer capable of acceptance.

Pricing, billing, taxes, invoicing, refunds, renewals, cancellation and any statutory right of withdrawal are matters for the product you buy, under that product's terms and with that product's payment processor. Where a product contracts with consumers, it publishes the consumer information that jurisdiction requires — including its own dispute-resolution information — inside the product, alongside its own terms. The Legal Notice states the corresponding position for this site.

11. Complaints, and how to reach a person

A complaint about a product belongs first with that product, through its own support channel, where the people who can actually resolve it are. Routing a product complaint through the corporate site would add a step and remove the context.

Two things are properly corporate, and they come here. First, if a product's own channel has failed you — no reply, or a reply that does not address the matter — write to hello@primanza.com and it will be escalated within the company rather than returned to the channel that already failed. Second, anything about the company itself, its identity, its ownership or this framework goes to legal@primanza.com.

Data protection requests about a product are handled by that product under its own privacy policy; if you cannot find where to send one, privacy@primanza.com will route it rather than refuse it. Vulnerability reports go to security@primanza.com under the Security page, whichever layer they concern.

None of this asks you to exhaust an internal process before exercising a right. Where the law gives you a right to complain to a supervisory authority, an ombudsman or a court, you may use it whenever you wish, and nothing here is a condition on it.

12. Precedence

Where documents conflict, this is the order that resolves it. As to a product: that product's own terms govern, then this framework, then the Terms of Service for this website, and a description on this site never governs at all. As to this website: the Terms of Service govern, and this framework applies only to what it addresses.

This framework does not reduce a right you have under a product's terms or under mandatory law. If any part of it would do so in your jurisdiction, that part does not apply to you and the rest continues to.

This framework is drafted in English. Where it is translated, the English text is authoritative and prevails in the event of any discrepancy.

13. Changes to this framework

This framework will change as the portfolio does — a first product, a second entity, a jurisdiction that requires something specific. The current version is the one on this page, carrying its revision date, and the sitemap publishes that date so a change is visible to anyone watching for one.

The commitments in sections 8 and 9 are the ones that matter when they are least convenient to keep. A revision that weakened either of them would not apply retroactively to a product already published under this version: what was promised when a product was published is what applies to it.

Questions about this framework go to legal@primanza.com.