ProductOverviewHow It WorksCapabilitiesFor Your Team
TrustOverviewData Protection & GovernanceSecurity & AccessOwnership & ConfidentialityAudit & Accountability
ResourcesTechnical OverviewAPI OverviewSupport
CompanyAbout AscentMLContactRed Mountain Innovations
Talk to AscentML

Governed from upload to deletion

Data that powers a model should be handled with the same discipline as the model itself.

AscentML validates and screens every dataset before it is used, keeps an immutable version history, and only removes data permanently when you ask or when the contract requires it.

  1. 1

    Attest before upload

    AscentML is intended for non-regulated business data.

    Before a dataset is uploaded, the user attests that it does not contain:

    • Personally identifiable information (PII)
    • Protected health information (PHI)
    • Other regulated information

    That attestation is the first control. It is not the only one.

  2. 2

    Upload securely

    Files are uploaded directly to your organization’s isolated storage using short-lived, single-purpose upload links. Storage locations are assigned by the platform, never by the client.

    Before a dataset moves forward, the upload is verified server-side for existence, size, and integrity.

  3. 3

    Validate the data

    Each dataset is profiled for common quality problems before it is used for model development:

    • High rates of missing values
    • Constant or near-constant columns
    • Potential target leakage

    Users can identify the target column and any known leakage columns during upload so they are handled correctly from the start.

  4. 4

    Screen for sensitive information

    Every dataset goes through automated screening for possible sensitive or prohibited information.

    High-confidence findings

    The dataset is rejected and does not proceed.

    Ambiguous findings

    The dataset is quarantined. It is released only after both your organization and an AscentML administrator approve.

    Screening results — quarantined findings awaiting review.
  5. 5

    Version everything

    Dataset versions are immutable. Once a version is created, it does not change.

    Models record the dataset versions and feature definitions they were built from. Derived features are stored as versioned definitions, so lineage covers both the raw data and the transformations applied to it.

    When someone asks what a model was trained on, there is a precise answer.

  6. 6

    Retain and delete deliberately

    Customer data is not automatically purged during an active contract.

    Deletion in the platform is soft by default, so records can be recovered if something is removed by mistake.

    Permanent deletion happens only at verified customer request or at contract termination. Purge operations are explicitly authorized, audited, and cover related records, stored files, model artifacts, cached explanations, and batch outputs.

What we log—and what we do not

Operational logs exist to run and support the service. They are not a second copy of your data.

Prediction records include

  • Timestamp and request ID
  • User and model version
  • Prediction and confidence
  • Source and error status

Full input retention is optional and can be configured.

Application logs exclude

  • Raw dataset rows
  • Full API payloads
  • Passwords
  • API key secrets
  • Unmasked sensitive values

Current scope

AscentML is not currently positioned for workloads that require HIPAA, FedRAMP, or similar regulated-environment assurances.

If your use case sits near that boundary, we would rather discuss it directly than leave it to interpretation.

Have specific data-handling requirements?

Tell us what your organization expects from a vendor handling its data. We will walk through how AscentML meets those expectations and where the current boundaries are.