The terms under which we provide Pvalue Analytics QYNA

What acceptance means here

You do not need a dramatic click-through moment for the platform relationship to matter. If you access and use QYNA, the expectation is that you accept the basic operating framework under which we provide it — including usage boundaries, product behaviour, and the limits of what the platform is intended to do.

What this framework may include

• General platform terms like these.
• Commercial or enterprise arrangements where applicable.
• Tool-specific or workflow-specific conditions when relevant.

Typical intended use cases

• Analytics and research workflows across brand, pricing, CX, VOC, and diagnostics.
• Business interpretation, structured modelling, visualisation, and insight development.
• Internal team use, client work, or enterprise workflows where access is properly authorised.

Why we define intended use clearly

A platform like QYNA can sit close to important decisions. So we want users to approach it as a professional environment — one that supports structured thinking and faster work, but one that still requires competent interpretation and responsible handling.

What is not allowed

• Using the platform for unlawful, fraudulent, abusive, infringing, or misleading purposes.
• Uploading data you do not have the right to disclose, process, analyse, or share.
• Attempting to disrupt, probe, bypass, reverse engineer, or compromise the platform or its controls.
• Presenting outputs as infallible facts when they still require review, validation, or contextual interpretation.

Why this matters

Most misuse problems are not caused by the model or the interface. They come from bad user behaviour around rights, interpretation, and intent. So the platform relationship depends as much on user conduct as it does on technical design.

Ownership logic

• Platform IP: QYNA, its interface, workflows, product methods, and assets remain with Pvalue Analytics or its licensors.
• User data: the data you submit remains with you, your company, or the relevant rights holder.
• Outputs: generated outputs are created from your use of the platform, but that does not transfer ownership of the platform itself.

Why this structure is fair

This model reflects how serious software products work. You bring your data, your questions, and your business context. We provide the tool environment, processing logic, and product infrastructure. Both sides keep ownership where it naturally belongs.

Why change is normal

Product evolution is part of responsible software delivery. We may improve tools, adjust formats, refine workflows, redesign interfaces, introduce new plans, or deprecate lower-value features when needed. That is a sign of active stewardship, not instability by itself.

What users should expect

• Product improvements and refinements over time.
• Possible changes to tool availability, UI, outputs, plans, or workflows.
• No guarantee that every feature will remain exactly as it appears today.

What stays with you

• Checking whether the input data is accurate, complete, and appropriate.
• Reviewing outputs before internal or external circulation.
• Applying business judgement instead of relying blindly on automation.
• Taking responsibility for decisions, actions, and consequences downstream.

Why we say this plainly

The biggest risk in tools like these is not that they are useless — it is that users may over-trust them. We would rather say clearly that QYNA is there to support decision-making, not absorb accountability on behalf of the user.