Security, privacy, and operational trust

    Give security and procurement teams a clear path to evaluate Scops.

    This page publishes only what we can stand behind in writing, and names a defined process for everything else. Where information is not public, we say so instead of implying a capability.

    We publish no certification logos, audit outcomes, uptime figures or security-control claims here. Statements about our security posture are made in writing, to your team, during the review process.

    Public facts

    What we can confirm publicly.

    Each item below is published elsewhere on this site or approved in writing by the responsible owner.

    A published privacy policy

    Our privacy policy describes what personal data we collect through the website and platform, how it is used, who it may be shared with, and the rights you can exercise. It is the baseline document for any privacy review and is public, dated, and versioned on this site.

    Read the privacy policy

    We do not sell personal data

    As stated in the published privacy policy, Scops does not sell personal data. Data may be shared with service providers who help operate the platform, where required by law, or in connection with a business transfer.

    See the data sharing section

    A named contact for data requests

    Access, correction, deletion, objection, portability and consent-withdrawal requests can be sent to info@scops.io, as set out in the privacy policy. Requests from your customers can be routed through the same contact during a live engagement.

    Commercial terms are published

    Plan tiers, active-member thresholds and onboarding scope are published on the pricing page, so procurement can review the commercial model before a conversation starts.

    See pricing

    Security review process

    How a security review with Scops runs.

    A defined sequence, not a promise about controls. Each step has an owner on both sides and a written outcome.

    1. Step 01

      Initial questionnaire

      You send your standard security or vendor questionnaire, or we start from the scope of the deployment you are considering. We confirm who on our side owns the response and by when you will receive it.

    2. Step 02

      Security documentation under NDA, if applicable

      Where documentation is not public, it is shared under an NDA. We agree in advance what can be shared, in what form, and with whom on your side it may be circulated.

    3. Step 03

      Technical review

      A working session between your security or IT team and ours, covering the specific integration you plan to run: what data moves, in which direction, through which interfaces, and which of it is required for the loyalty logic you want.

    4. Step 04

      Agreed responsibilities

      The review closes with a written split of responsibilities between your organisation and Scops for the agreed scope, so nothing is left implied. This becomes part of the contracting discussion.

    Data and privacy

    Data and privacy questions.

    Answers here are limited to approved statements. Anything else is answered under the review process rather than on a public page.

    Service and support

    Service and support commitments.

    Only as published in our pricing. No uptime percentage is published on this page.

    Enterprise SLA

    The pricing page lists the SLA on the Enterprise plan as discussed in scoping. That is the only SLA position we publish: the terms are set per engagement, in writing, and we do not publish an uptime percentage on this page.

    See the plan comparison

    Support response

    Support response expectations are published per plan in the pricing comparison table. Anything beyond what is published there is agreed in scoping.

    Compare plans

    Onboarding and ownership

    Onboarding scope is published with the plans. Who owns configuration, integration work and change approvals after go-live is written down during the security review, so support expectations and responsibilities match.

    See onboarding scope

    Trust package

    Request the trust package.

    For security, IT and procurement teams. Tell us the scope you are evaluating and we route your questionnaire to the right owner.

    • We confirm who owns the response and by when.
    • Non-public documentation is shared under NDA where applicable.
    • A technical review session covers your specific integration scope.
    • The review closes with a written split of responsibilities.

    Please do not include confidential system details or personal data in this form. We use your answers only to prepare the review, as described in our privacy policy.