Select Page

SXC Data Minimisation & Privacy Policy

(Plain-English Version)

Effective date:1st January 2026

1. Our Approach to Privacy

SXC is built on a simple principle:

We collect as little personal data as possible, and only what we actually need.

This policy explains — in clear language — how SXC handles data, what we do not collect, and how users remain in control.

Privacy on SXC is a design decision, not an afterthought.

2. What We Do Not Store

To reduce risk and protect users, SXC intentionally does not store:

  • Copies of identity documents

  • Government ID numbers

  • Biometric data

  • Payment card details

  • Real names where not required

  • Personal addresses for public display

  • Sensitive personal history unrelated to platform use

If we don’t need it to operate the platform safely, we don’t keep it.

3. Separation of Verification Data

Where identity or age verification is required:

  • Verification is handled using separate, restricted systems

  • Verification data is not publicly visible

  • Verification data is not mixed with profile, messaging, or review data

  • Verification outcomes are stored as status signals, not raw documents

This separation protects providers if:

  • A system is compromised

  • Access is misused

  • Regulations change

4. No Sale or Exploitation of Personal Data

SXC does not:

  • Sell personal data

  • Trade user information

  • Share provider or customer data with advertisers

  • Build shadow profiles

  • Monetise data behind the scenes

SXC’s business model is not data extraction.

5. Provider Control Over Visibility

Providers control:

  • What information appears on their profile

  • What is public vs private

  • When their profile is visible or paused

  • Which contact methods are enabled

  • Whether they appear in search or discovery

Visibility settings are respected across:

  • Search

  • Messaging

  • Listings

  • Public pages

Providers are never required to expose personal details to use the platform.

6. Walled Garden by Design

SXC is intentionally designed as a walled garden:

  • Access is restricted

  • Profiles are contextual, not scraped

  • Messaging is internal

  • Discovery is controlled

  • Data is not openly indexed by default

This reduces:

  • Scraping

  • Harassment

  • Doxxing

  • Unwanted exposure

Privacy is part of platform safety.

7. Limited Internal Access

Access to personal or sensitive data is:

  • Restricted to authorised staff

  • Logged and auditable

  • Used only for safety, support, or compliance

  • Never for curiosity or convenience

We design systems assuming trust must be earned internally as well.

8. Transparency & Change

If our data practices change:

  • We will explain what changed

  • We will explain why

  • We will explain what it means for users

Privacy should never be a surprise.

9. Platform Commitment

SXC is committed to:

  • Collecting less, not more

  • Designing for privacy by default

  • Protecting provider autonomy

  • Resisting surveillance-based business models

  • Treating personal data as a liability, not an asset

Your data exists to serve you, not the other way around.

10. Acknowledgement

By using SXC, users acknowledge:

  • SXC’s privacy-first design

  • Their control over visibility

  • The separation of verification and profile data

  • The limits of what SXC stores and retains