leminkozey

Themistic / Concept · No app yet

veil

Before the cloud, personal data stays here.

My idea for a local layer between your app and a language model: replace sensitive information with placeholders, then restore it in the response.

Explore the flow ↓

  1. Before the request

    Detect sensitive information and replace it with unique placeholders.

  2. On your device

    Keep the mapping between each original value and its placeholder local.

  3. On the way back

    Replace the placeholders in the response with the original values.

Placeholders out. Context back.

This diagram shows the planned journey of an email address. Original values and placeholders take different paths.

veil

Concept

Your app passes the request to veil. The model would only receive the placeholder.

Request

  1. Your app

    Write to
    [email protected].

  2. veil

    Detect and
    mask locally

  3. Language model

    Write to
    [EMAIL_1].

Response

  1. Language model

    Recipient:
    [EMAIL_1]

  2. veil

    Restore the
    original value

  3. Your app

    Recipient:
    [email protected]

The mapping stays on your device.

[email protected] ↔ [EMAIL_1]
  • Concept, no app yet
  • Original values stay local
  • Resolve placeholders on the way back
Where veil stands

veil is a concept. There is no official app yet. This flow explains how the parts would work together. It does not mask any data or send requests to a language model.

The detection model: Skira 6 ↗