The interface
Buttons, defaults, wording, timers, disclosures, prompts and visual hierarchy.
DigiData deceptive-design products
Three focused products examine the parts of deceptive design that a screenshot cannot settle: the route a consumer must follow, the variant the system chooses and the moment at which adaptation becomes exploitation.
One question per product. Reasons before scores. Evidence before badges.
The problem
Conventional dark-pattern reviews tend to inspect visible interface elements. That remains useful for false urgency, preselection, disguised advertising, hidden costs and other practices that appear directly on the screen.
Deceptive design often operates across a longer chain. The consumer may face a different route when cancelling than when subscribing. A system may serve different interfaces according to profile, history or predicted value. The same design may acquire different significance when the system identifies fatigue, distress, financial pressure or developmental vulnerability and adapts the interaction around it.
The screen is evidence. It is not always the complete object of assessment.
Buttons, defaults, wording, timers, disclosures, prompts and visual hierarchy.
What appears before and after the choice, how often it appears and how much friction surrounds each route.
Profiling, optimisation, triggering conditions, experimentation, adaptation and measured outcomes.
The products
Each product answers one bounded operational question and produces a reasoned record. None claims to certify legal compliance.
Measure the distance between yes and no.
Compare the route into a commitment with the route to refuse, reverse or leave it. Identify which extra burdens protect the consumer and which merely obstruct the choice.
Explore PARITY →One service. Many users. Show who sees what.
Reconstruct how profiles, predictions and operating conditions alter the interface, sequence, price, offer, disclosure or friction delivered to different users.
Explore MIRROR →Do not label the person. Test the moment.
Assess whether a consumer's circumstances, the system's knowledge and the surrounding choice architecture combine to create an exploitable vulnerability event.
Explore MOMENT →The shared method
The suite moves beyond pattern spotting without treating every persuasive feature as unlawful. It reconstructs the mechanism and then applies the relevant legal or governance threshold.
What does the consumer encounter: a prompt, default, timer, ranking, offer, delay or disclosure?
Where does it appear, what surrounds it, how often does it recur and which alternatives remain available?
What is the system optimising: task completion, conversion, spend, retention, data disclosure or time?
Does the system change timing, content, friction or support according to profile, context or feedback?
Does the architecture materially impair choice, obstruct a right, exploit susceptibility or create a defined consumer harm?
The decision lifecycle
The deceptive-design products complement FAIRTEST and DELTA. They do not duplicate them.
Should this experiment or design variant launch?
Are the trader-preferred and consumer-protective routes meaningfully comparable?
Which users or conditions receive different routes, and what causes the difference?
Does the system use that difference to exploit a vulnerability event?
Does a later change require any earlier assessment to reopen?
FAIRTEST and DELTA appear here as adjacent DigiData products in development. The three pages in this package concern PARITY, MIRROR and MOMENT.
Shared technical architecture
The planned applications will use one schema-driven browser engine with product-specific question sets, evidence structures and deterministic outcome rules.
Assessment answers and evidence remain in the browser unless the organisation deliberately exports them.
Generative AI will not determine the outcome class. The method should remain reproducible and reviewable.
Users can save, reopen, version and transfer a structured project file and generate a print-ready reasoning record.
SVG diagrams will render matched pathways, decision surfaces and person-system-context chains.
The first release will not be a surveillance platform. It will not crawl authenticated journeys, replay identifiable users or infer hidden system logic from a screenshot. Users must supply or test the evidence on which the assessment relies.
Proposed pricing
A fictional demonstration explains the method. A single-assessment licence supports one bounded decision. An organisation licence supports repeated internal use.
| Product | Public demonstration | Single assessment | Organisation licence |
|---|---|---|---|
| PARITY | Free | £395 + VAT | £7,500 per year + VAT |
| MIRROR | Free | £695 + VAT | £12,500 per year + VAT |
| MOMENT | Free | £495 + VAT | £9,500 per year + VAT |
| Complete suite | Three fictional demonstrations | Purchased separately | £22,500 per year + VAT |
No per-seat pricing at launch. These assessments require legal, design, product, data science, operations and audit teams to work together.
Professional review remains separate. Software access does not include an independent legal opinion, audit or certification.
What the suite is not
The tools do not declare that every nudge, recommendation, personalisation or retention measure is unlawful. Nor do they convert complex legal tests into a single compliance score.
Bright-line practices remain bright-line practices. A false countdown timer or obstructive cancellation route does not become acceptable because an organisation completes a sophisticated assessment.
Regulatory direction
EU law already prohibits certain manipulative interface practices under the Digital Services Act. The forthcoming Digital Fairness Act is expected to address manipulative interfaces, addictive design, unfair personalisation and the exploitation of vulnerabilities more broadly. Enforcement in the United Kingdom and United States continues to show the operational significance of cancellation friction and obstructive journeys.
Legal and market context checked on 16 August 2026. The products remain methods in development, not statements of settled law.
Start with the right question
Choose the product that matches the operational decision. Use the suite only where the evidence chain genuinely requires all three.