Try our plataform
UUID

UUID

Description

Replaces the field with a randomly generated UUID V4.

Category

Anonymization

Supported Field Types

  • text
  • timestamp
  • date
  • float
  • int
  • boolean
  • time

Output Field Type

  • text

Arguments

None

Pseudo-code (Python)

def func(val):
    """
        val: field value
    """
    import uuid
    return str(uuid.uuid4())

Use the UUID Anonymization Function in Kondado

Apply the UUID function to replace sensitive field values with random UUID V4 identifiers during data transformation pipelines.

1
Identify fields requiring anonymization

Review your data sources and determine which fields contain sensitive information that should be replaced with unique, non-reversible identifiers before loading to destinations.

2
Apply the UUID transformation

In your pipeline configuration, select the UUID function from the Anonymization category. This works on any supported field type (text, timestamp, date, float, int, boolean, time) and always outputs a text-based UUID V4.

3
Validate anonymized output

Run a test extraction and verify that original values are fully replaced with random UUIDs, ensuring no traceable data reaches your data transformation outputs or downstream systems.

4
Deploy to production pipeline

Once validated, activate the pipeline to automatically anonymize fields on every run, maintaining data privacy compliance without manual intervention.

Frequently asked questions

What does the UUID function actually do to my data?▼
The UUID function completely replaces the original field value with a randomly generated UUID V4 (Universally Unique Identifier version 4). The original value is not stored, which makes UUID a strong choice for anonymization in your data transformation pipelines.
Which field types can I apply the UUID function to?▼
The UUID function supports text, timestamp, date, float, int, boolean and time as input. Regardless of the input type, the output is always text containing the UUID string.
Does the UUID function require any configuration arguments?▼
No. The UUID function takes no arguments. You select it from the Anonymization category and apply it to the desired field — every execution generates a new random UUID V4 via uuid.uuid4().
Can I reverse a UUID back to the original value?▼
No. The transformation is one-way: the original value is discarded and replaced with a random UUID. If you need to map back to original values, keep a separate, secured lookup table outside of your destination systems.
When should I use UUID instead of a hash function?▼
Use UUID when you want to remove all semantic meaning from the original data and don't need deterministic correlation across runs. Hashing (e.g., SHA-512 with key) is preferable when you need the same input to produce the same output across runs for joining or deduplication.
Written by·Published 2024-12-20·Updated 2026-04-26