1. What this page is
This page is published by Data Nexus Technologies Services FZ-LLC, a company registered in a free zone of the United Arab Emirates. It sets out how we treat your name, your material and your data, and what we ask of you in return.
It is a statement of practice, not a contract. Where you have a signed agreement with us, that agreement governs and this page explains it. Where you do not yet have one — during a first conversation, a pitch, a discovery call — this page is what we hold ourselves to anyway.
It is dated at the top and changes are dated too. We do not apply a change retroactively to an engagement already under way; if something material changes, the clients it affects hear it from us directly rather than by re-reading the site.
2. We do not name you
No client is named in public without written consent. That covers every surface we control: case studies, this site's pages, the register of solutions, proposals shown to other prospects, conference talks, social posts, reference calls and the logo wall we do not have.
Consent is per use, not general. Agreeing to a case study is not agreeing to a reference call, and agreeing once is not agreeing forever. You can withdraw it, and we take the material down.
What we may publish without naming you is the shape of the work: an industry, a size of operation, a technical problem and how it was solved. Where a description would identify you to anyone who knows the market, we treat it as naming you and ask first.
3. What you own
What we make for you is yours, exclusively. Source code, page copy, guides and reference material, designs, brand work, data models, configuration, documentation, prompts and knowledge bases written for your agents, the research we ran on your behalf and the artefacts it produced.
Rights transfer on final payment, in full, without a licence back to us and without a field-of-use limit. Nothing we deliver depends on a subscription to us, and nothing stops working if you stop paying us. Hosting, domains and third-party accounts are registered in your name from the first day, not ours.
If the work stops early, you keep what you paid for. Rights to every part already invoiced and settled pass to you on termination, whoever ended it and for whatever reason. We hand over the material in a usable form. We do not hold a finished component hostage to a disputed invoice — an unpaid balance is a debt to be collected, not a hostage to be kept.
One boundary. What we write for you is yours; what the world already wrote is not ours to give away. Open-source libraries, fonts, icons and any paid third-party service a project needs reach you under their own licences, which bind you exactly as they bind us. The handover names them and the licence each one sits under, so nobody has to reconstruct that from the code a year later in front of a buyer's lawyer. Nothing carrying a copyleft licence — GPL, AGPL, or any other that would oblige you to publish your own source — goes into work you resell or ship to your own customers unless we have asked you and you have said yes.
Where our own tooling ships inside your delivery — a build check, a validation type, a template that lives in your repository and runs on your deploys — you get a licence to it that is perpetual, irrevocable, worldwide, paid in full, and free to transfer: you may use it, change it, maintain it, and hand it to another firm along with the rest of the system. We keep the right to go on using it elsewhere; you never need our permission to keep your own build running. Section 5 asks you not to extract those parts and hand them on as a product in their own right. It does not, and could not, stop you operating the thing you paid for.
4. What we keep
The result is yours. The machinery that produced it is ours, and it is the part of this practice that took years rather than weeks to build.
We name the categories below on purpose. A confidentiality obligation whose edges you cannot see is one nobody can keep, and a client is entitled to know exactly what is being asked of them.
- The Deep Dive Interview. How the session is designed, sequenced and run. What is asked, in what order, and which questions exist only to test the answer to an earlier one. How the recording is then read and converted into positioning, approved first-person phrasing, a list of claims that may not be made, and a set of verified facts.
- The publication gates. Programs that run before every deployment and stop it outright. One validates every structured-data node against a dated copy of the vocabulary and refuses a reference pointing at a node that does not exist. One asserts, in both directions, that every address promising a machine-readable copy actually serves one. One holds the knowledge corpus as a graph and rejects a cycle in it, a term used but never defined, or a quantity stated without the formula behind it.
- The sourcing discipline. A type that cannot hold a number unless the number arrives with the date it was read, the address where a reader can check it, and a horizon after which it must be read again or removed. It is built and enforced by the build; we are candid on our own site that we have not yet earned the right to claim it is used everywhere.
- The evidence requirement. A register in which no entry can be published without at least one item of proof and an honestly stated boundary where the technology in question stops working. The type refuses to compile an entry that has neither.
- The measurement instruments. Fixed sets of commercial prompts, the schedule on which they are run, the way a baseline is taken before any work begins and compared against the same set afterwards. The census that records automated clients by declared purpose and operator, and the classification behind it.
- The document pipeline. Proposals and reports composed as typed modules rather than written into a template, so that a broken reference fails a build instead of reaching a client's desk.
- The working apparatus around all of it. Checklists, question banks, review procedures, internal tooling and its source, the templates, and the reasoning we walk you through in workshops.
None of this is incidental to the work. It is the reason a deliverable from us cannot contain a dead reference or an unsourced figure: not because someone was careful, but because the thing refuses to publish. That property is the asset, and it is not transferred with the files.
This is a distinction between process and result, and it cuts cleanly: you own what we produced, we own how we produce it. Keeping the method places no limit whatever on your use of the result. You can extend it, resell it, hand it to another firm, or publish it in full.
Skill is not confidential. Nothing here stops us using the general knowledge, experience and judgement our people carry in their heads after working with you — that is what a practice is. The line is between what we learned how to do and what we learned about you: the second stays with you, and no engagement leaves us with a licence to reuse your strategy, your numbers or your positioning anywhere else.
5. Confidentiality runs both ways
Most agreements in this trade bind only the supplier. This one is mutual, and the obligation on the client is narrow but real.
You agree not to disclose our methods, reproduce them, or pass them to another supplier to reproduce. That covers the categories in section 4 and the artefacts through which you encounter them: our working documents, question sets and interview structure, the source of the gates and tooling, our templates, and the internal reasoning we show you while the work is under way.
It binds your staff and the suppliers you show it to, and you agree to tell them so before you do. It runs for five years from the end of our engagement, except for anything that is a trade secret in its own right, which keeps its protection for as long as it stays secret.
Five things it deliberately does not do, because an obligation without limits is neither fair nor enforceable:
- It does not touch your use of the result. Nothing in this section restricts what you do with anything we delivered, or with tooling that ships inside it under the licence in section 3.
- It does not silence you about us. You may say who we are, that you worked with us, and what you got. We would rather you did.
- It does not cover what is already public — including the substantial amount of our method we publish ourselves, deliberately and for free, on this site. If you read it here, it is yours to repeat.
- It does not cover what you already knew, what reaches you lawfully from elsewhere, or what you develop independently.
- It does not override the law. Where a regulator, court or auditor requires disclosure, make it. Tell us if you are permitted to, so we can respond alongside you rather than after the fact.
6. Interview recordings and working material
Recordings of a Deep Dive Interview, their transcripts and our working notes on them are not released as material. Not to subcontractors, not to partners, and not as a matter of course to the client whose team was recorded.
Two reasons, and either alone is sufficient. The recording holds hours of unguarded speech from people who agreed to talk in a closed room: internal figures, deals discussed frankly, judgements about people and markets. We have no right to redistribute that, and no confidentiality agreement signed by a third party creates one. Separately, the method of running and reading these sessions is our own.
What comes out of the session is delivered instead: positioning, approved phrasing, what may and may not be claimed, priorities and verified facts. That extract is the reason the session happens, and it is more complete than the recording because it carries none of the digression.
The people recorded keep their rights. Everyone is told before we start that the session is recorded, why, and how long we hold it. Anyone in the room can ask for their own contribution to be transcribed for them, corrected, or removed from the recording, and we do it. Nothing above is a refusal of a lawful request from the person whose voice it is, or from a regulator — the paragraph is about not circulating a closed-room conversation as a document, not about standing between a person and their own words.
We hold recordings for twelve months after the engagement ends, then destroy them. Transcripts and working notes follow the retention in section 9. If you would rather we destroyed a recording sooner, say so and we will, once the extract has been produced.
7. Personal data
Two different sets of personal data pass through an engagement, and they are governed differently.
Data about your people and your customers, which we touch on your behalf. You decide what it is for; we act on your instructions and nothing else. We do not use it for our own purposes, do not sell or share it, and do not use it to train anything. Where a project connects to your customers' records, we build so the data stays in systems you control, and we do not take working copies beyond what a specific task needs and its retention allows.
Data we hold as our own — your contact details, our correspondence, the commercial record of the engagement. We keep that to run the relationship and to meet the record-keeping the law puts on us.
We work to the UAE Personal Data Protection Law and, where your users or staff are in the European Union or the United Kingdom, to the GDPR. A data processing agreement on our standard terms is available on request and we will sign yours if it is compatible; it is not a negotiation we drag out. Where personal data crosses a border in the course of the work, we tell you which countries and on what legal footing before it happens, not afterwards.
Rights requests reach us at contact@datanexus.ae. If the request concerns data we hold on your behalf, we pass it to you within three working days and help you answer it rather than answering it ourselves.
8. Artificial intelligence
We build AI systems and we use AI tools in our own work. Both deserve a straight answer rather than silence, because silence here is what most suppliers offer.
Your material does not train anybody's model. We use AI services only under terms that exclude customer content from training, and we will name the services in use on request. Where a tool cannot offer that, we do not put your material into it.
Recordings and transcripts of a Deep Dive Interview are handled by people. Where a machine assists with a transcript, it runs under the same no-training terms and the file is deleted from the service afterwards.
Anything an AI system produces for you is checked by a person before it reaches you. This is not a courtesy. A model will produce a confident figure with no source behind it, and the gates in section 4 exist precisely because that failure is invisible until someone has already quoted it.
An agent we build for you is yours — its prompts, its knowledge base, its configuration and its logs, on the same terms as everything else in section 3. What we keep is the method of building and evaluating it, not the thing itself.
What we will not claim. No system, ours included, is incapable of error. Where an agent speaks to your customers we build the boundaries of what it may say, the escalation to a person, and the record of what it actually said — so that a mistake is visible and correctable rather than deniable. That record is yours.
9. Where things are kept, who else touches them, and for how long
Other companies are involved, and you are entitled to know which. Most suppliers answer this with «available on request». Here is the actual list for this site, current at the date above.
- Vercel — hosting, deployment and the page-view count.
- Supabase — the database an enquiry form writes into.
- Telegram — where a new enquiry raises a notification, so it carries what you typed into the form.
- Cloudflare — DNS for the bare domain.
- GitHub — source control for this site's code.
- Ziina — payment links and their webhooks.
- Google Workspace — our email, so anything you write to us is held there.
Typefaces and every other asset are served from this domain, not from a content network, so no third party learns who visited a page by supplying the font on it.
Your own project will have its own list, decided with you and written down at handover. We do not add a service that changes where your data lives without telling you first.
Access is held narrowly. Credentials you give us go to the people who need them for the work and nowhere else. Every account we can protect with two-factor authentication has it. When someone leaves the project, their access ends with it, and at handover we tell you exactly which credentials to rotate.
Retention. Project material — repositories, documents, research files, working notes — is kept for twenty-four months after the engagement ends, so that we can answer a question or resume work without asking you to reassemble it. After that it is deleted. Recordings go sooner, at twelve months, under section 6. Ask us to delete earlier and we will, keeping only what the law obliges us to keep and telling you what that is.
If something goes wrong, you hear it from us. If material of yours is exposed or reaches someone who should not have it, we tell you within 72 hours of finding out — what happened, what was affected, what we have done, and what we still do not know. We would rather send an incomplete notice on time than a complete one late.
10. Subcontractors
People we bring onto a project are bound by everything on this page and receive what the work requires and nothing beyond it.
A signed confidentiality agreement lets us give someone material; it does not oblige us to. It also cannot cure the problem in section 6: an agreement protects the person receiving the material, and does not grant us a right to pass on what was never ours to pass on.
Their work is assigned to us before it starts, so that what we transfer to you in section 3 is genuinely ours to transfer and no third party holds a claim over a piece of your system. We remain answerable to you for their work as if it were our own — subcontracting is a fact about how we staff a project, not a way to move responsibility somewhere you cannot reach.
You can ask who is on your project and where they are, and we will tell you. If you object to someone for a reason, say it and we will staff around it.
11. Conflicts of interest
We work across a small number of industries and will at some point be approached by a company that competes with you. Pretending otherwise would be dishonest, so here is the actual rule.
We tell you before we take on a direct competitor, and you can object. What we will not do in any case is carry your strategy across: your positioning, your numbers, your customer research and the judgement calls made in your interview stay with you and inform nobody else's work. The general skill we developed goes with us; the specific understanding of your business does not.
We do not take commissions, referral fees or revenue share from any vendor, platform or hosting provider. That is why we can tell you a tool is wrong for you: recommending it would not pay us anything.
12. What you tell us
Anything you disclose in the course of the work is confidential by default, whether or not an agreement is in place and whether or not you marked it. That includes what you tell us before there is a contract, and it survives the end of the engagement.
We are held to the same exceptions we ask of you in section 5 — what is already public, what we knew, what arrives lawfully from elsewhere, what we develop independently, and what a court or regulator requires. If we are ever compelled to disclose something of yours, we tell you first wherever the law allows it, so that you can object before disclosure rather than learn of it after.
13. Consent, questions and complaints
To give consent, change what was agreed, withdraw it, ask for the list of services and subcontractors, request a data processing agreement, or complain about any of the above, write to contact@datanexus.ae. We reply within two working days.
A withdrawal of consent to be named takes effect on the next deployment of this site, which in practice means the same day, and we confirm when it has run. Material already published elsewhere by third parties is outside our control, and we will say so plainly rather than promise a removal we cannot perform.
This page is governed by the laws of the United Arab Emirates. If something here conflicts with an agreement you have signed with us, the agreement wins.