NOWFREELANCE TECHNOLOGY / IN DEVELOPMENT

Transform sensitive data before it travels.

A privacy-focused data transformation layer designed to help organisations reduce unnecessary exposure across AI tools, applications and automated workflows.

Designed for organisations adopting AI, automation and data-driven operations.

THE BUSINESS CHALLENGE

Adopting AI should not mean losing control of sensitive information.

Customer support, CRM platforms, analytics, external AI services and automation tools can all process information that identifies people or reveals confidential business context. The challenge is to make useful workflows possible while limiting unnecessary data exposure.

01

Personal information

Names, contact details, identifiers and customer records move between systems.

02

AI adoption

Teams want to use AI capabilities without copying unnecessary personal or confidential data into prompts.

03

Fragmented workflows

Different tools apply different controls, making consistent handling and traceability harder.

WHAT THE ENGINE IS DESIGNED TO DO

A reusable privacy layer between data and the systems that use it.

The intended engine goes beyond manual find-and-replace. It is being designed around repeatable transformation, protected mappings, configurable rules and controlled restoration.

⌕

Detection

Identify candidate sensitive information using configurable patterns and, as the product evolves, specialised detection methods.

⇄

Transformation

Replace direct identifiers with consistent tokens or pseudonyms while preserving the structure needed by a workflow.

▤

Protected mappings

Keep the relationship between original and transformed values separate, with encryption and access controls as core design requirements.

✓

Policy controls

Apply rules according to data type, purpose, workspace and authorised role.

↺

Controlled restoration

Restore original values only in approved contexts and through an explicitly authorised process.

⌁

Integration

Expose reusable capabilities through SDKs and APIs so the engine can sit inside existing business workflows.

UNDER THE HOOD

Designed as infrastructure, not as a standalone text utility.

The target architecture separates transformation logic from user interfaces and keeps identity mappings, policy decisions and integrations as distinct concerns. These are design goals, not a claim that every component is already implemented.

Core processing layer

Detection & classificationPatterns, entity types and confidence handling
Transformation coreDeterministic mappings and reversible tokenisation
Policy enginePurpose, workspace, roles and permissions

Security & integration layer

Encrypted mapping vaultKey management, separation and access control
Audit and governanceTraceable events without unnecessary sensitive payloads
SDK / API connectorsApplications, AI providers and workflow platforms

SECURITY, PRIVACY & COMPLIANCE

Built to support responsible data handling and stronger controls.

Privacy Engine is being designed to support privacy and security practices relevant to regulated organisations. Its role is to provide technical capabilities that can contribute to a wider compliance programme.

EU

GDPR / RGPD

Relevant design areas include data protection by design and by default, security of processing, data minimisation and pseudonymisation where appropriate.

27001

ISO/IEC 27001

An information security management system standard. The engine may support selected technical controls within an organisation's wider ISMS.

27701

ISO/IEC 27701

Privacy information management. Relevant to organisations establishing governance and controls for personal information.

27017

ISO/IEC 27017

Cloud security controls that may be relevant when the engine is deployed in cloud environments.

27018

ISO/IEC 27018

Protection of personally identifiable information in public cloud services, where that deployment model applies.

42001

ISO/IEC 42001

AI management systems. Relevant to governance around AI use, risk and operational accountability.

Important compliance statement: Privacy Engine is a technology in development. It is not a certification, legal opinion or guarantee of GDPR or ISO compliance. Pseudonymised data can remain personal data under GDPR if it can be attributed to an individual using additional information. Compliance depends on the organisation's context, configuration, processes, contracts and wider technical and organisational measures.

Current prototype

Try the first manual transformation workflow.

The Replacer demonstrates the basic idea: define replacements, transform text and restore mapped values. It is an early interface for exploring the concept—not the automated Privacy Engine described above.

Prototype safety notice: This browser demo stores mapping data in localStorage without encryption. Use fictional sample data only. Do not paste real personal, confidential or regulated information. This prototype must not be treated as a production security control.

Replacer / Manual prototype

Explore reversible text substitution using fictional examples.

WHO IT IS FOR

One engine. Different ways to create value.

↗

For businesses

Assess where sensitive information flows through AI, customer operations and automation. Explore how a transformation layer could reduce unnecessary exposure in a specific workflow.

{ }

For developers & technology teams

Explore a reusable core, SDK and API approach for integrating privacy-aware transformation into applications and data pipelines.

◎

For privacy & security teams

Discuss data flows, threat models, access boundaries, retention and evidence needed to assess whether the technology fits an organisation's control framework.

DEVELOPMENT ROADMAP

From manual proof of concept to reusable privacy infrastructure.

The current prototype validates a narrow interaction. The roadmap makes the distinction between what exists and what still needs engineering, security design and validation.

Prototype exists

01 · Core extraction

A standalone transformation core and manual browser interface.

Planned

02 · Secure vault & policies

Encryption, key lifecycle, tenant isolation, permissions and governed restoration.

Planned

03 · Detection & integrations

Automated detection, APIs, SDKs, audit events, testing and independent security review.

LET'S EXPLORE YOUR USE CASE

Where does sensitive data move in your organisation?

Tell us about an AI, application or automation workflow. We can map the data exposure points and explore whether Privacy Engine could become part of the solution.

Discuss your workflow →