DRG 008
SHEET 01 / 08
SCALE MINIMAL
ISSUED 26.04.2026
REV A · UK GDPR ALIGNED
// SHEET 01 OF 08 DRG-008 · PRIVACY · REV A · UK GDPR ALIGNED
exhibit h privacy posture surface not a cookie banner
blackmenta.com/privacy · UK GDPR · PECR · controller: BlackMenta Ltd
H privacy datum · collect minimum · state plainly
$cat /etc/blackmenta/privacy.notice

data should be minimal not theatrical

what is collected
email · session · minimal logs
collection boundary
what is not
ad pixels · cross-site profiles · fingerprints
// privacy.v0 Strictly-necessary storage.
No banner when there is nothing to sell.
DIM: 6 categories · 4 lawful bases · 14d log floor · 0 ad cookies
controllernamed
cookiesnecessary only
ad pixelsnone
analyticsnone
logs14 days

Collect the minimum. State it plainly. Operate it accordingly.

This page is the public privacy notice for BlackMenta Ltd. It names the controller, maps the data, states the lawful basis, fixes the retention windows, names the processors and lists the rights. If a sentence here is not enforceable in the deployed stack, the sentence is wrong — not the stack.

UK GDPR aligned strictly-necessary cookies no ad pixels no behavioural profiling
no Google Analytics no fingerprinting no cross-site tracking no surprise profiling
basisconsent · contract · LI
retention14d · 30d · account-life
rightsUK GDPR Art. 15–22
contactprivacy@blackmenta.com
checksum controller · data map · lawful basis · retention · processors · rights
BM / PRIVACY SURFACE collect → minimise → retain → rotate → honour rights
01 · controller named before content 02 · purpose before collection 03 · retention before storage 04 · enforcement before promise
// EX.X · COLLECTION PERIMETER What is not collected.
no ad pixels no Meta pixel, no LinkedIn insight tag, no TikTok pixel, no programmatic retargeting beacons.
no cross-site profiles no behavioural identifier shared with third parties to follow you around the open web.
no fingerprinting no canvas, font-list, audio-context or device-fingerprint collection by design.
no marketing analytics no Google Analytics, no Mixpanel, no Segment, no Heap, no “just to see how things are going” tracker.
no surprise consent no consent banners that re-prompt until you click “accept”. nothing requiring consent ships in the first place.
no children targeting BlackMenta surfaces are not directed at children. no profiling, no marketing, no design oriented at minors.
// the controller

The accountable entity is named.

controller · company no. · office · contact · supervisor
CT.01
controller

BlackMenta Ltd

The data controller is BlackMenta Ltd, a UK-incorporated company registered in England & Wales. Public record verifiable on Companies House.

Verify record
CT.02
company no.

№ 16988667

Companies House number 16988667. Incorporated 26 January 2026. Active. Annual filings published on the public register.

See officers
CT.03
privacy contact

privacy@blackmenta.com

Privacy enquiries, rights requests, complaints and processor questions. The named route — not a generic inbox routed to the wrong queue.

Privacy request
CT.04
supervisor

UK ICO

UK Information Commissioner’s Office is the supervisory authority. Complaint rights are available through the ICO if a request is not handled appropriately.

ICO complaint route
// SHEET 02 OF 08 · DATA MAP

Collect the minimum; state it plainly.

REF 02.X · 6 CATEGORIES · PURPOSE-LIMITED

The ICO says privacy notices should explain why personal data is processed, how long it is kept and who it is shared with. This map is the public version of that explanation. If a category does not appear here, BlackMenta should not be collecting it.

ref category what / why input
02.1 email Used to respond to enquiries, route preview requests, issue magic links or handle privacy/legal/security messages. you submit
02.2 profile Name, company, country, role or intent may be used for reviewer routing and disclosure-context decisions. you submit
02.3 session Session cookie, user-agent and basic session metadata keep gated surfaces functional and detect suspicious session reuse. functional
02.4 query telemetry For Menta / AI surfaces, limited event rows may record agent, tier, blocked-or-not flag, latency and hashed query identifiers where telemetry is enabled. Plaintext questions should not be retained as product analytics. limited
02.5 access logs Server and edge logs may contain truncated or minimised network metadata for security, abuse prevention and incident response. Full IP storage should be avoided unless legally or technically necessary. security
02.6 what is not collected No ad identifiers, no cross-site behavioural profiles, no advertising pixels, no Google Analytics-style marketing analytics, no device fingerprinting by design. excluded
Reading rule: if a row above stops being accurate, this sheet must update before the deployed stack changes — not after. Drift in the data map is the most common reason a privacy notice becomes a lie.
// SHEET 03 OF 08 · LAWFUL BASIS

Each purpose needs a basis.

REF 03.X · UK GDPR ART. 6 · 4 BASES

UK GDPR Article 6 lists six bases for lawful processing. BlackMenta uses three. The fourth row below names a basis that is deliberately not used — legitimate interest as cover for behavioural advertising.

LB.01
// consent

Submitted requests

Where a person submits a form or request after seeing a notice, BlackMenta may process that submission for the requested purpose. Consent is specific, informed and withdrawable.

SCOPE: form submissions · voluntary contact
LB.02
// contract

Preview access

Session, login and profile data may be necessary to provide gated reviewer access or to take steps requested before access is granted.

SCOPE: reviewer accounts · magic links
LB.03
// legitimate interest

Security controls

Minimal logs, rate limits, abuse prevention and vulnerability triage may be processed for security and integrity. Strictly bounded; not a catch-all.

SCOPE: security · integrity · abuse
LB.04
// not used

Marketing profiling

Legitimate interest is not used as cover for behavioural advertising, cross-site tracking or surprise profiling. The basis exists in UK GDPR; BlackMenta does not stretch it here.

STATUS: deliberately excluded
// SHEET 04 OF 08 · RETENTION / COOKIES

No banner when there is nothing to sell.

REF 04.X · PECR · STRICTLY-NECESSARY ONLY

Under UK cookie rules, organisations must explain cookies and obtain consent for cookies that are not strictly necessary. BlackMenta’s public design target is strictly-necessary storage only — which is why this site does not nag you with a banner.

ref item retention / rule status
04.1 session cookie bm_session or equivalent session token. HttpOnly, Secure, SameSite=Lax where technically supported. Used for login/session management only. necessary
04.2 magic links Single-use login tokens should expire quickly and be purged after use or expiry. short
04.3 email / profile Kept while the profile or relationship exists, unless deletion is requested or longer retention is required for legal/security reasons. account
04.4 query rows Telemetry rows should be short-lived and purpose-limited. Default public target: 30-day rolling retention unless reviewer or legal record-keeping requires otherwise. 30 days
04.5 access logs Security logs should be minimised, truncated where possible, compressed/secured and deleted on a defined schedule. Default public target: 14 days. 14 days
04.6 analytics cookies Not used. No ad pixels. No third-party behavioural analytics. No cross-site tracking cookies. excluded
// SHEET 05 OF 08 · AI / PREVIEW BOUNDARY

Do not paste secrets into public surfaces.

REF 05.X · MENTA · REVIEWER ROUTES

Where AI surfaces are exposed publicly, the privacy posture must reflect what they actually do. The three statements below mark the line between public chat input, gated reviewer disclosure, and the limit of what BlackMenta can promise about third-party AI providers.

05.1
// public assistant

Menta / AI

AI surfaces may process the text typed by the user to generate a response. Users should not submit secrets, legal notices, security exploits, personal data about others or investment-sensitive material into public assistant boxes.

user-input warning · persistent
05.2
// reviewer gate

Preview material

Reviewer-pack documents, diligence notes and private disclosures belong in gated channels, not public chat or generic inboxes. The privacy floor is set by the channel, not by the content.

authenticated only
05.3
// no training claim

Model handling

Where third-party AI providers are used, provider-specific retention and training settings must be checked before live release. This page should not promise more than the deployed configuration enforces.

enforcement > promise
// SHEET 06 OF 08 · PROCESSORS / TRANSFERS

Processors should be named by role.

REF 06.X · DPA · SCC / IDTA WHERE NEEDED

Specific vendor names are gated to verified reviewers; the roles they play are public. The matrix below names the role, the public position, and the contractual posture (Data Processing Agreement, plus international-transfer safeguards where required).

ref role public position control
06.1 hosting Application, database or static hosting providers may process stored website and reviewer data under contractual processor terms. DPA
06.2 email Transactional email providers may process recipient address, message metadata and delivery logs for routing and security. DPA
06.3 edge / DNS DNS, TLS, security and edge providers may process request metadata necessary to deliver and protect the website. security
06.4 AI provider If an AI provider processes queries, only data necessary for the assistant response should be sent. Email/profile data should not be sent unless necessary and disclosed. limited
06.5 international transfers Where data is transferred outside the UK/EEA, appropriate safeguards such as UK IDTA, EU SCCs or equivalent contractual and technical measures should be used where required. safeguards
Disclosure rule: specific processor names are released to verified reviewers under NDA. The roles above stay public so the privacy posture is auditable without exposing the vendor list.
// SHEET 07 OF 08 · RIGHTS / REQUEST PROTOCOL

Rights requests need a route.

REF 07.X · UK GDPR ART. 15–22 · 6 RIGHTS

Under UK GDPR, six rights apply to your personal data. Each is exercisable through the named privacy contact. No friction added on purpose. Identity verification is the only legitimate gate.

RT.01
// access

What do you hold?

Request a copy of personal data associated with your email, profile or reviewer account. The response should be machine-readable where reasonable.

BASIS: UK GDPR Art. 15
RT.02
// rectification

Correct a record

Ask BlackMenta to correct inaccurate profile, contact or routing data. Drift in stored data is a legitimate request, not a courtesy.

BASIS: UK GDPR Art. 16
RT.03
// erasure

Delete my data

Request account/profile deletion, subject to legal, security or record-keeping limits. Where erasure is limited, the limit is explained, not implied.

BASIS: UK GDPR Art. 17
RT.04
// restriction

Pause processing

Request restriction while a record is checked or a dispute is resolved. Processing pauses; storage continues; the dispute gets a clock.

BASIS: UK GDPR Art. 18
RT.05
// portability

Export data

Where applicable, request a structured export of data you provided. Format: JSON or comparable machine-readable.

BASIS: UK GDPR Art. 20
RT.06
// objection

Object / opt out

Object to legitimate-interest processing or opt out of optional telemetry where available. Objection is a stop signal, not a negotiation.

BASIS: UK GDPR Art. 21
Route: all rights requests go to privacy@blackmenta.com. ICO complaint route is on the controller card above. Refusal to honour a valid right is a complaint, not a customer-service issue.

Reviewer-side privacy details are gated.

This page is the public privacy posture. Specific processor list, DPA terms, transfer mechanisms, audit logs and reviewer-side data handling are released through auth.blackmenta.com — to verified counsel, security researchers and capital under NDA.

▶ Request privacy pack
01IdentifyCounsel, reviewer, regulator.
02RoutePosture, processors, transfers or audit lane.
03DiscloseNotice → processor list → DPA terms.
no lane fits? → privacy@blackmenta.com
// NOTES · DRG-008 · GENERAL

Notes.

  1. N.01 Security controls. TLS, least-privilege access, session protection, short-lived tokens, database access controls and documented security reporting support the privacy promises on this page. → see /security
  2. N.02 Not for children. BlackMenta surfaces are not directed at children. If a parent or guardian believes a child submitted data, contact privacy@blackmenta.com. → erasure route applies
  3. N.03 Versioned updates. Material changes are dated and, where they affect active reviewer accounts or privacy choices, notified before taking effect where practical. → current rev: A
  4. N.04 Draft status. This is a public privacy-notice draft for BlackMenta Ltd. It is reviewed against the actual deployed stack, processor list and UK/EU data-transfer setup before publication as final legal text. → see signature block
  5. N.05 Privacy questions: privacy@blackmenta.com. ICO complaint route is on the controller card above.
// END OF NOTES · NTS · UNLESS OTHERWISE SPECIFIED DRG-008 · REV A
// SIG.01 · DRAWN BY Privacy Architect UK GDPR · PECR · Data minimisation
2026-Q1 · internal
// SIG.02 · CHECKED Counsel of Record UK GDPR · IDTA / SCC · ICO posture
2026-Q2 · engaged
// SIG.03 · CONTROLLER BlackMenta Ltd № 16988667 · Data Controller
2026 · privacy surface
// SIG.04 · STATUS UK GDPR aligned · Rev A Strictly-necessary · No tracking
last updated 2026-04
// DRAFTING STANDARD · BS 8888 SPIRIT · NTS MINIMAL DATA · NO TRACKING · RIGHTS HONOURED
// end of drawing 008 · 8 sheets
/privacy · the privacy notice · 2026
DRG-008 REV A · 8 SHEETS · MINIMAL · UK GDPR ALIGNED · NO TRACKING