TeC Consentry
Centralize Subscriber Consent.
Ensure Compliance. Build Digital Trust.
The telco-grade Consent Management Platform purpose-built for PDPL, GDPR, CAMARA, and UAE data protection compliance — managing the complete consent lifecycle across every channel and subscriber touchpoint.
<200ms
Real-Time Consent Validation
100M+
Subscribers Supported
99.9%
Platform Availability Target
6+
Regulatory Frameworks Covered
The Challenge
Why Telecoms Can No Longer Ignore Consent Management
Regulatory mandates, API monetization requirements, and subscriber expectations are converging — all demanding a single, authoritative consent platform.
The Problems
Mounting Regulatory Pressure
GDPR, Saudi Arabia’s PDPL, UAE’s Federal Data Protection Law, and DIFC/ADGM regulations impose strict consent obligations with significant financial penalties for non-compliance.
CAMARA API Compliance Gap
CAMARA and GSMA Open Gateway mandate verified subscriber consent before network APIs can be exposed to developers — making consent a prerequisite for 5G monetization.
Fragmented Consent Silos
Consent records scattered across CRM, apps, retail, and USSD result in inconsistency, audit failures, and costly regulatory investigations.
No Audit Trail
When regulators ask for evidence of a consent decision made 18 months ago, legacy systems cannot provide it — exposing operators to liability.
The TeC Consentry Advantage
Single Source of Consent Truth
One centralized platform every system queries in real time — CRM, campaign management, mobile apps, and CAMARA API gateways all see the same verified consent state.
Immutable Audit-First Design
Every consent action is timestamped, hashed, and permanently recorded. Produce regulator-ready evidence in minutes, not weeks.
CAMARA & Network API Ready
Purpose-built to support CAMARA API consent flows, enabling participation in Aduna, Bridge Alliance, and GSMA Open Gateway ecosystems with confidence.
Telco-Grade Performance
Sub-200ms consent validation at the 95th percentile, designed to handle millions of subscribers without slowing down customer journeys.
Key Modules
Comprehensive Consent Management Capabilities
Every capability your compliance, operations, and digital channels teams need — in one platform.
Consent Lifecycle Management
- Centralized consent repository across all channels
- 5 consent states: Granted, Denied, Pending, Withdrawn, Expired
- Version-controlled consent templates with full history
- Configurable retention & disposal policies (PDPL-aligned)
- Purpose-based consent — separate records per processing activity
- Service consent vs. marketing consent separation
Multi-Channel Orchestration
- Mobile apps (iOS & Android)
- Web portals & e-commerce platforms
- Retail & point-of-sale systems
- SMS, USSD, IVR, WhatsApp
- Customer service & call centre interfaces
- Multilingual support (Arabic & English, extensible)
Workflow Designer
- Visual drag-and-drop workflow builder
- Re-consent campaign workflows for existing subscribers
- Configurable reminder schedules & retry policies
- Workflow versioning, draft/publish, and rollback
- Trigger-based execution (onboarding, activation, modification)
- Dead-letter and replay controls for failed workflows
API-First Integration Framework
- Real-time consent validation API (<200ms P95)
- REST APIs for consent update, retrieval & withdrawal
- Bulk import/export for large-scale migrations
- CAMARA authorization server integration
- Kong API Gateway — out of the box
- CRM, Campaign, ITSM & messaging gateway connectors
Customer Self-Service Portal
- View all active consents & consent history
- Grant, deny, or withdraw consent at any time
- Manage channel preferences (SMS, email, push, etc.)
- Consent status: current state & full timeline
- Accessible opt-in / opt-out mechanisms
- Embedded in mobile app, web portal, or USSD
Audit, Reporting & Compliance
- Immutable, tamper-evident audit log for every consent action
- Regulator-ready evidence generation (PDPL, CST, GDPR)
- Consent statistics & channel trend dashboards
- Withdrawal tracking & denial rate analytics
- DPO (Data Protection Officer) reporting portal
- Advanced search & filter for audit investigations
TeC Consentry
See TeC Consentry in Action
A purpose-built admin portal, developer portal, and reporting hub — everything your team needs to govern consent at scale, from configuring consent categories to auditing every subscriber interaction.
Regulatory Compliance
Built for the Regulations That Matter Most
TeC Consentry is pre-aligned with major data protection and telecom regulatory frameworks across the Middle East, Europe, and global industry standards.
EU Regulation
GDPR – General Data Protection Regulation
Article 7 requires consent be freely given, specific, informed, and unambiguous — with the ability to withdraw at any time. TeC Consentry captures, validates, and withdraws consent in full GDPR alignment, including purpose-based consent and documented evidence of consent capture.
🌍 European Union & EEA
KSA Regulation
PDPL – Personal Data Protection Law (Saudi Arabia)
Saudi Arabia’s PDPL, enforced by the NDMO, NCA, and regulated by CST for telecoms, mandates explicit consent for personal data processing, marketing, and third-party sharing. Purpose-built for Zain KSA, STC, Mobily, and other CSPs to achieve full PDPL compliance.
🇸🇦 Kingdom of Saudi Arabia
UAE Regulation
UAE Federal & Free Zone Data Protection
The UAE Personal Data Protection Law (Federal Decree-Law No. 45/2021), alongside DIFC Data Protection Law 2020 and ADGM Data Protection Regulations, impose strict consent obligations. TeC Consentry supports multi-jurisdiction consent configuration for simultaneous compliance.
🇦🇪 United Arab Emirates
3GPP / GSMA
CAMARA Project – Network API Consent
The CAMARA Project (Linux Foundation, driven by GSMA and 3GPP) defines standards for exposing telecom network capabilities as APIs. CAMARA mandates operators obtain explicit subscriber consent before any network data — location, QoD, identity, device status — is shared with third-party developers.
🌐 Global Telco Standard
Telco Consortium
Aduna & Bridge Alliance
Aduna (Deutsche Telekom, Orange, Telefónica, Telecom Italia) and Bridge Alliance (Asia-Pacific operator consortium) build on CAMARA standards for cross-operator interoperability. TeC Consentry supports the consent requirements of multi-operator environments.
🌏 Multi-Operator Ecosystems
Regional
Additional Regional Frameworks
Beyond major frameworks, TeC Consentry’s configurable consent model adapts to Pakistan’s PECA regulations, Jordan’s Cybersecurity Law, African data protection acts, and any future emerging regulation — without requiring core architectural changes.
🌍 Middle East, South Asia & Africa
Regulatory Compliance
PDPL, GDPR, UAE data protection, and CAMARA — with configurable models for new regulations.
Real-Time Validation
Sub-200ms consent checks at P95 so your channels and CAMARA APIs never slow down.
Omnichannel Coverage
App, web, SMS, USSD, IVR, retail — one platform, one verified consent record.
Immutable Audit Trail
Tamper-evident logs capture every consent action — produce regulator evidence in minutes.
Subscriber Self-Service
Give subscribers full visibility and control — the trust that drives digital engagement.
API-First Architecture
Every capability via secure REST APIs — connect any downstream system in days.
No-Code Workflows
Operations teams design and publish consent journeys without writing a single line of code.
Telco-Grade Scalability
Horizontal scale-out to 10M+ subscribers with 99.9% availability and geo-redundancy.
Deployment
Flexible Deployment to Fit Your Infrastructure
TeC Consentry runs entirely within your data centre footprint — no dependency on external cloud services for core operations.
- On-premises (VM-based) with geo-redundancy across two data centres
- Private cloud on Red Hat OpenShift, any Kubernetes cluster, or VMware vSphere
- Production + Pre-Prod + SIT + Dev environments
- Sized for 100M+ subscribers at go-live with horizontal scale-out headroom
- Integrates with your PKI, IAM, and enterprise security zone architecture
Frequently Asked Questions
Get answers to the most common questions about TeC Consentry
How does TeC Consentry support CAMARA API compliance?
TeC Consentry integrates directly with your API gateway (Kong, Apigee, or others) to serve as the authorization and consent validation layer required by CAMARA APIs. When a developer calls a CAMARA network API — QoD, Device Location, or Number Verification — the gateway queries Consentry in real time to verify that the subscriber has granted consent for that specific data use. The decision is returned in under 200ms with a timestamped, auditable record, enabling your operator to safely participate in Aduna, Bridge Alliance, and the GSMA Open Gateway ecosystem.
Is TeC Consentry compliant with Saudi Arabia's PDPL and CST regulations?
Yes. TeC Consentry was purpose-designed for operators in the Kingdom of Saudi Arabia in alignment with PDPL requirements enforced by the NDMO and NCA, and telecommunications-specific requirements issued by the Communications, Space and Technology Commission (CST). The platform supports explicit and purpose-based consent collection, lifecycle management including withdrawal, customer data subject rights, consent evidence preservation, and configurable retention periods.
What is the consent validation response time?
TeC Consentry targets a P95 consent validation latency below 200ms. This is achieved through a Redis-backed hot-state cache for active consent records, combined with horizontal scale-out of the stateless Core Platform services. The platform is validated against this target at Pre-Production through load and performance testing prior to go-live.
Can the platform handle a re-consent migration for our existing subscriber base?
Yes. TeC Consentry includes dedicated Re-Consent Campaign Management capability. The platform identifies subscribers without valid consent records, segments them, and initiates configurable consent collection journeys through approved channels — SMS, push notifications, app prompts, USSD, and more. All interactions are centrally audited throughout the process.
Does withdrawal of marketing consent affect a subscriber's service access?
No. TeC Consentry enforces a clear separation between service consent and marketing consent, in alignment with PDPL and CST guidelines. Customers can activate, provision, and use their telecom services regardless of their marketing consent status. Withdrawing marketing consent suppresses marketing and promotional communications while leaving service delivery fully unaffected.
How long does implementation typically take?
A typical TeC Consentry deployment takes 2-3 months from project kick-off to production go-live, covering requirements analysis, configuration, channel integrations, UAT, and deployment. Because TeC Consentry is a pre-built platform, implementation focuses on configuration, integration, and validation — not custom software development.
Can TeC Consentry integrate with our existing CRM and campaign management systems?
Yes. The platform’s API-first architecture and adapter-based integration framework connects with leading CRM platforms (Salesforce, Oracle Siebel, SAP), campaign management tools, ITSM systems, and messaging gateways (SMSC, WhatsApp Business, email relay, USSD). Pre-built adaptors are available for major telecom BSS/IN vendors including Ericsson, Huawei, and Oracle.