Data governance for operators and ISPs
DPI data residency: keeping subscriber data in Saudi Arabia
DPI data residency means that the subscriber traffic a deep packet inspection platform processes, and the records it produces, stay in the Kingdom and under the operator's control. Interkey Intelligent DPI runs on the operator's own infrastructure and can operate entirely in the Kingdom, so subscriber traffic does not have to leave Saudi Arabia. Its output is metadata about applications, traffic volumes and triggered policies, and retention and access are set by the operator's data-governance rules and the contract, not by a vendor default.
A Saudi product, built by Interkey
For compliance, privacy, security and network architecture teams at telecom operators and ISPs. Reviewed November 2026.
- Where it runs:on your own infrastructure, and it can operate entirely in the Kingdom.
- What it produces:metadata about applications, traffic volumes and triggered policies.
- Who decides retention and access:you, through your data-governance rules and the contract.
- How it classifies:from flow behaviour, including encrypted traffic, without decrypting it.
Why data residency is a DPI question
A DPI platform sits where subscriber traffic passes, so it touches subscriber data by its nature. That makes residency part of the design decision, not a detail for the contract annex. An operator's compliance, privacy and legal teams need clear answers to three questions before a platform is chosen: where the traffic is processed, what is kept afterwards, and who can see it. Which laws, licence conditions and regulator requirements apply to your organisation is for those teams to determine. This page sets out the questions to put to a DPI supplier, and how Interkey Intelligent DPI answers the ones its documentation covers.
What a DPI platform handles, and what it keeps
| Data | What it is | In Interkey Intelligent DPI |
|---|---|---|
| Subscriber traffic | The packets the platform classifies, inline or out-of-band | Processed on your own infrastructure; the platform can operate entirely in the Kingdom |
| Encrypted payload | The content of encrypted flows | Not decrypted: classification uses handshake structure, packet sizing and timing, and endpoint behaviour |
| Classification output | Which application each flow belongs to, traffic volumes, and which policies were triggered | Metadata; retention and access follow your data-governance rules and the contract |
| Reports and views | Live View and the reporting layer for capacity and regulatory teams | Built from the metadata; who can query them is set in the deployment design and the contract |
Policies act per application, subscriber group or cell. Writing rules at that level keeps a deployment focused on network governance and regulatory requirements.
Residency questions to ask any DPI supplier
Put the same questions to every supplier, in the same form, and ask for the answers in writing:
1. Processing location.Where does the platform run, and can it run entirely in the Kingdom on our infrastructure?
2. Traffic leaving the Kingdom.Does any subscriber traffic, or any sample of it, leave Saudi Arabia in normal operation?
3. What is stored.Does the platform keep payload, or only metadata? Which fields exactly?
4. Retention.Who sets how long each type of record is kept, and can we change it?
5. Access.Who can query records and reports, and how is that access granted, logged and reviewed?
6. Remote support.From where do support engineers work, and what can they access during a support case?
7. Model updates.Where are classification models trained and updated, and what data does that use?
8. End of contract.How are records returned or deleted when the contract ends?
How Interkey Intelligent DPI answers
| Question | Answer |
|---|---|
| Processing location | Runs on your own infrastructure and can operate entirely in the Kingdom |
| Traffic leaving the Kingdom | Subscriber traffic does not have to leave Saudi Arabia |
| What is stored | Classification produces metadata about applications, traffic volumes and triggered policies |
| Retention and access | Set in the deployment design and the contract, following your data-governance rules, not by a vendor default |
| Encrypted traffic | Classified without decryption |
| Support | Interkey's engineering team in Riyadh, in Arabic and English |
Questions 6 to 8 depend on how your deployment is designed and contracted. Raise them at scoping, so the answers are written into the deployment design and the contract.
Writing residency into the RFP and the contract
Residency is easiest to hold a supplier to when it is written down before award. Include:
- A data inventory:each type of record the platform produces, where it is stored and its retention period.
- Access roles:which teams can query which records, with access reviewed on a fixed schedule.
- Change control:model, policy and list updates enter the live network through your change-control process.
- Support boundaries:what support engineers may access, from where, and how each session is recorded.
- Exit terms:how records are returned or deleted at the end of the contract.
For the full tender structure, see the DPI RFP requirements checklist.
Residency from the first day of a proof of concept
Residency applies to the test as much as to production. Interkey recommends a proof of concept in 3 stages, with the platform running on your own infrastructure throughout:
1. Written acceptance criteria.Include the data rules for the test: what is recorded, where, for how long and who can see it.
2. Out-of-band classification against verified traffic.The platform classifies without sitting in the forwarding path. A verified sample generated on devices and subscriptions you control contains no subscriber data, and the live traffic the platform classifies is processed on your own infrastructure. Method: Measuring DPI classification accuracy.
3. Report-only policy, then the inline decision.Rules show what they would have done before any of them acts on traffic.
See also: How Interkey runs a DPI proof of concept
Questions about DPI data residency
Does subscriber traffic leave Saudi Arabia?
What data does the platform keep?
Does it read the content of encrypted traffic?
Who decides how long records are kept?
Does data residency affect the price?
Proof of concept in three phases
Written acceptance criteria.Agree which rules are tested, on which traffic and subscriber groups, how results are measured and what counts as a pass.
Out-of-band classification against verified traffic.Measure false positives as carefully as detection for every class the rules depend on.
Report-only policy, then the inline decision.Each rule shows what it would have done; enforcement follows only after classification has proven itself.
Discuss data governance for your deployment
Tell us which data-governance requirements your compliance and legal teams apply, where you expect the platform to run, and your timeline. Our team in Riyadh replies in Arabic or English.
- Our engineers read your request
- We agree the scope of a technical session
- You see the product on a use case you choose