A procurement conversation should make capability, ownership and unknowns visible.
This page is a procurement checklist, not a certification claim. Xcited Cura recommends confirming data handling, privacy, approvals, reporting, catalogue scope and market requirements for each enterprise pilot.
The review should identify the minimum participant data, the purpose for each field, who can access it, how long it is retained and which market-specific requirements apply.
A reward programme should document audience, eligibility, budget ownership, catalogue scope, approval thresholds, exceptions and the reporting audience.
The public site currently confirms a reward catalogue and analytics/reporting. Security certifications, data residency, SSO, integrations, service levels and legal treatment should be confirmed directly before procurement approval.
No. This page deliberately does not claim a certification, audit report, data residency option or legal treatment. Those details must be verified for the specific procurement process.
Start with data fields, access, retention, catalogue and fulfilment scope, approvals, reporting, support ownership and the exact market in which the pilot will operate.
Bring one audience, one moment and one reporting question. We can shape the conversation around what the organisation needs to learn.