Privacy controls built into the system that stores the data.
A consent banner cannot see where personal data actually goes.
The real privacy work starts after a visitor makes a choice. Requests, deletion, retention, access, and audit records need to understand the collections and workflows behind the interface.
Website
forms + accounts
Relationship Intelligence
contacts + deals
Analytics
sessions + events
Chatbot
messages + intent
Agents
actions + tool calls
Privacy workflows that understand the data model.
Tej provides reusable privacy primitives. We configure and extend them around the client's website, Relationship Intelligence, analytics, chatbot, forms, vendors, and operating process.
Consent records
Purpose, source, notice version, status, expiry, and withdrawal history.
capture + versionTracking controls
Separate aggregate measurement from behavioural tracking that requires consent.
gate + enforceData requests
Turn access, portability, correction, restriction, and deletion into assigned workflows.
verify + fulfilCollection-aware erasure
Delete, anonymize, redact, or unlink records according to the data model.
plan + executeRetention schedules
Surface records for review and run configured anonymization or purge jobs.
schedule + logOperational audit
Record consent changes, access, exports, erasure, purges, and admin actions.
observe + provePrivacy Infrastructure is a technical layer, not a legal guarantee. Legal basis, notices, regulatory interpretation, and retention policy should be reviewed with the client's privacy advisor.
Aggregate insight first. Behavioural tracking only when allowed.
The code can separate low-risk aggregate measurement from personal tracking, then apply each consent choice across analytics, Relationship Intelligence enrichment, chatbot behaviour, and personalisation.
Measure the system without building a personal history.
Connect behaviour only to the purposes the visitor accepted.
A request becomes an operational workflow, not a search across vendors.
Access and erasure requests can move through verification, data discovery, policy review, collection-level actions, fulfilment, and audit inside one controlled process.
Receive
Capture request type and subject details.
Verify
Confirm identity before exposing or changing records.
Map
Find records across configured collections and integrations.
Review
Apply deletion, anonymization, retention, and legal-hold rules.
Fulfil
Export or execute the approved collection-level plan.
Audit
Record the actions and preserve the required proof.
When agents process personal data, the system needs accountable records.
An AI agent may create a contact, book a meeting, or invoke another approved action. The privacy layer can record which agent acted, what data was used, the purpose, and the authority for that action.
One operator view for consent, requests, retention, and audit.
The team can review privacy work inside the admin system it already uses, with queues, deadlines, forecasts, purge history, and recent activity in one place.
Build privacy infrastructure into your platform. Not around it.
Bring us your data model, consent needs, vendors, retention rules, and operational workflows. We will map the technical privacy architecture and build the controls into the system.