Public website terms
Explain site access, permitted use, intellectual property, acceptable use and the role of other contracts.
Current Terms of Use, effective date and authoritative publication record.
Website notices, product licences, paid subscription orders, data processing terms and negotiated enterprise agreements govern different relationships. They should be easy to find and distinguish.
Numerish publishes general public documents and manages them through a governed legal workflow. Software-specific licences and enterprise orders may impose additional rights, conditions or protections.
The descriptions below outline control expectations and evidence to evaluate. They do not claim that a specific Numerish product has completed independent certification.
Each domain brings a specific objective and a practical review item. Choose the level of assurance needed for the relevant service and regulatory context.
Explain site access, permitted use, intellectual property, acceptable use and the role of other contracts.
Current Terms of Use, effective date and authoritative publication record.
Identify the public notice alongside processing agreements and applicable country-specific requirements.
Privacy Policy, DPA where applicable and subprocessor schedule.
Distinguish desktop, cloud, seats, devices, rights to updates, permitted offline use and termination rules.
Executed licence terms, edition, entitlement certificate and accepted order.
Government, multi-country and enterprise contracts may require customised terms and regulatory approvals.
Signed order, contracting entity, jurisdiction schedule and change record.
Published changes should preserve prior approved terms, effective dates and attributable authorisation.
Legal Page Manager version history, acceptance receipts and publication audit.
Identify legal communications, commercial support channels and the jurisdiction governing each relationship.
Executed governing-law and dispute clauses and escalation contacts.
The dividing line between supplier capability and customer responsibilities should be agreed before implementation or procurement sign-off.
Draft documents are not effective agreements. A new licence or revised public policy requires the applicable approvals and publication steps before being treated as operative.
Published legal documents and the separately identified AEC360 agreement draft. A draft is not effective until authorised publication.
Request product- and version-specific artefacts; identify the relevant jurisdiction, data classes, hosting model and procurement requirements.
Controls and independently verified outcomes should not be confused.
The applicable negotiated and executed contract governs the subjects expressly covered by it, subject to mandatory law. Marketing material is not a substitute for a binding order.
A proposed licence is undergoing governed legal review. It should not be treated as effective until authorised publication and, where required, customer acceptance.