All decks
Pharoah GDPR compliance door (Pharoah skin)ATTOH · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductPharoah GDPR compliance door (Pharoah skin)
Register keypharoah-gdpr
OwnerATTOH LTD (Companies House 14079382)
Live atgdpr.pharoahtechnology.com · HTTP 200 on 9 September 2026
Price£349 one-off
Built from1 register parts, 1 live, 1 probe-verified

What it does

The Pharoah GDPR compliance door helps UK small businesses manage data subject access requests, breach notifications, privacy notices and data processing agreements through an automated, human‑QA reviewed tool.

Runs on

Pharoah GDPR compliance door (Pharoah skin)
Source: estate register (products, product_parts, builder_blocks) · deploy probe 9 September 2026Evidence live
03The frameWhat this buyer's profession checks

We will measure it against the NCSC Cyber Assessment Framework.

Three checks a buyer in this field applies, whether or not they name the standard. We use them as the frame for everything that follows.

Check 1

Assets and access under control

Check 2

Detection with an evidence trail

Check 3

Response rehearsed, not improvised

Frame chosen by BRG as a summary of the NCSC Cyber Assessment Framework. Verify the wording with the body before external use.No accreditation is claimed
04Why it's better · 1 of 6Check 2 · fit for purpose

The job as the register describes it.

Small UK businesses find it difficult and time‑consuming to track DSARs, breach notifications, and privacy documentation without automated GDPR compliance tools.

Who carries it

Small businesses in the UK requiring GDPR compliance tools and support.

Source: register pain_point · audienceThe problem, stated plainly
05Why it's better · 2 of 6Check 2 · fit for purpose

What it does instead.

UK GDPR compliance for small businesses. DSAR 30-day clock, breach 72-hour timer, privacy notices, DPAs. £19/mo. Human-QA reviewed.

The Pharoah GDPR compliance door helps UK small businesses manage data subject access requests, breach notifications, privacy notices and data processing agreements through an automated, human‑QA reviewed tool.

The parts doing the work

Pharoah GDPR compliance door (Pharoah skin) verified

Root block for Pharoah GDPR compliance door (Pharoah skin) — created so the app cannot be invisible. Probe settles its real maturity.

Source: register purpose, public_blurb, product_parts joined to builder_blocks1 of 1 parts shown
06Why it's better · 3 of 6Check 1 · controls

Proof it exists, not a roadmap.

200

HTTP status of gdpr.pharoahtechnology.com on 9 September 2026 · real-content-verified

1/1

register parts verified by probe

1

parts wired live

HTTP 200

functional surface probe

Open gdpr.pharoahtechnology.com during the talk. Anything the deck claims should be visible there.

Source: register deploy_probe_code, deploy_probed_at, product_parts.verified_by_probeProbed, not promised
07Why it's better · 4 of 6Against the market, honestly

Where we lead, and where we don't.

Category: OneTrust class. Nearest rivals: OneTrust, Osano, TrustArc, DataGrail, Securiti.ai; strongest is OneTrust at enterprise scale. Our edge: The platforms are priced and configured for enterprises with a privacy function. We run the two clocks that actually carry a penalty — the 30-day DSAR and the 72-hour breach notification — for a business that has neither a DPO nor a budget for one. How we beat them: GBP19 a month against enterprise licensing, so the smallest business that still carries the obligation is served at all. Source: written 2026-08-30 from the product's own live page (title and meta description), probed this session.

Source: register vs_competitionNamed competitors are the register's, not the presenter's
08Why it's better · 5 of 6Check 2 · fit for purpose

Built for one kind of buyer.

Small businesses in the UK requiring GDPR compliance tools and support.

Source: register audience, serves_nichesOne buyer, not everyone
09Why it's better · 6 of 6Price is part of the scope

What it costs, in one line.

£349 one-off

Buying route

Payment link live
Delivered from the live product
Scope named on the next slides, so the price has a boundary
Source: register price_gbp, billing_interval, pricing_basis, payment_link_activeNo hidden rate card
10What's inside

The parts, with their verification state.

PartCategoryStateVerified
Pharoah GDPR compliance door (Pharoah skin)full-stackbuilt
Source: product_parts joined to builder_blocks · 1 of 1 shown probe-verified   not yet
12Why packaging matters

Five things a package does that a price cannot.

1
Scope becomes visible. The parts are named, so nothing is assumed.
2
Boundaries are explicit. What is outside is written down before the first invoice.
3
It is auditable. A package is a documented process, which is what the NCSC Cyber Assessment Framework looks for.
4
Buyers compare like for like. A referral needs a defined thing to refer.
5
Switching fear drops. The move is inside the package, not a project bolted on the front.
Source: BRG packaging doctrine; frame from slide 3Packaging = a compliance instrument
13This packageCut by what each part does

Pharoah GDPR compliance door (Pharoah skin), as a package.

full-stack

Pharoah GDPR compliance door (Pharoah skin)

Root block for Pharoah GDPR compliance door (Pharoah skin) — created so the app cannot be invisible. Probe set

verified
Source: product_parts grouped by builder_blocks.category1 groups
14Anatomy of the packageOn one page · 0 items of work left, filed

A package reads like a control document.

Inside the scope

  • Pharoah GDPR compliance door (Pharoah skin)

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 1 parts probe-verified, latest 3 September 2026
  • Functional surface: HTTP 200
  • Register row updated with every probe

Outside the scope today · work left

  • No build gap recorded in the register

Who signs, and where the work sits

  • ATTOH LTD owns the product and the data layer
  • 0 build packets proposed · 0 management items pending
  • Change log kept in the register
Source: product_parts (inside), deploy and part probes (evidenced), v_deck_work_left (work left; filed to manager_work and build_packets by deck_work_left_sync)One page
15Across the family

Where it hands over.

Pharaoh Sovereign CEOsovereign.pharoahtechnology.co.uk
Pharoah AIEmployment door (Pharoah skin)employment.pharoahtechnology.com
Pharoah AIFreight door (Pharoah skin)logistics.pharoahtechnology.com
ATTOHPharoah GDPR compliance door (Pharoah skin)gdpr.pharoahtechnology.com
Pharoah Autoauto.pharoahtechnology.co.uk
Pharoah BLACKLINE door (Pharoah skin)blackline.pharoahtechnology.com
Pharoah BOQ Pricer (Pharoah skin)boq.pharoahtechnology.com
Source: register rows sharing client_key One house, many doors
1 / 16
Arrow keys or space · N narration · P print
Slide 1Narration Words Running total

Production guide

How to turn these sixteen slides into a presentation video. Same structure as every deck in the family, so a crew that has made one can make them all.

1 · Deliverable

ItemSpec
Format16:9, 1920×1080, 25 fps, H.264 MP4 plus WebM. Burned captions and a sidecar SRT.
RuntimeNarration below plus screen captures of the live product; typically 8 to 12 minutes.
Framethe NCSC Cyber Assessment Framework. Verify the wording of the three checks with the body before external use.
BrandATTOH family palette as rendered here. Green only for verified and live states; red only for exclusions.
VoiceCalm, exact, never theatrical. Read figures and dates in full. Numbers are the register's, and the register is cited on every slide.

2 · Runtime plan

#SlideNarrationWordsStarts

3 · Screen captures

4 · Full narration

5 · What this deck must not say

  • No numbers that are not on a slide with a register source.
  • No accreditation by the NCSC Cyber Assessment Framework; the frame is a lens, not a badge.
  • No named competitor read aloud unless the audience asks; the register's names are on slide 7 for the presenter.
  • No client names, volumes or tenure unless the register carries them.

6 · Regenerate

This deck is generated from the estate register. Update the product row, re-run the deck build, redeploy. Do not hand-edit this file.