the front door is routed
BlackMenta uses named channels for named matters.
Use the route that matches the matter. Do not collapse them into one inbox.
BlackMenta uses six named channels so general enquiries, reviewer access, legal/IP, security, privacy and press do not collapse into one inbox. Do not send confidential business plans, private keys, unpublished vulnerabilities, personal data, investment proposals or legal service documents through the wrong channel. The map below identifies the registered office; it is a public company-record anchor, not a visitor office.
Four facts before any message.
BlackMenta Ltd · № 16988667
UK private limited company. Registered office shown on Sheet 02. The address is a Companies House anchor — the route is the inbox.
Verify record5 business days
Target acknowledgement window for routed messages. Security follows the /security SLA. Privacy follows UK GDPR timing.
See protocolHuman triage
No auto-responder template. No drip sequence. No marketing follow-up. Replies come from the route owner; silence means “not yet”, not refusal.
See request qualityPGP on request
Until a production PGP key is published, encrypted reporting is available on request. Do not send vulnerability detail before the channel is confirmed.
See PGP statusFour common lanes. Two more on Sheet 03.
hello@
Introductions, open conversations, basic site questions and first contact that does not require gated disclosure. The default front door.
hello@ → CR.02 previewpreview@
Whitepaper, executive summary, diligence requests, partner review and progressive disclosure routing. The reviewer-side channel.
preview@ → CR.03 legal / IPlegal@
Trademark matters, legal corrections, counsel liaison and formal IP enquiries. Formal notices also go to the registered office.
legal@ → CR.04 securitysecurity@
Vulnerability reports, responsible disclosure and urgent technical issues. Use the /security page for scope and report format.
security@ →A public record needs a place.
A static, dark, schematic location panel. It does not load a third-party map SDK, does not set map cookies and does not expose visitor data to a map provider. Use the external map link only if you want to open the address outside this site.
2nd Floor College House · Ruislip, London · HA4 7AE
17 King Edwards Road
Ruislip, London
United Kingdom, HA4 7AE
The registered office is used for formal company records and legal correspondence. It should not be treated as an operational office, event site, walk-in address or visitor location without prior written confirmation.
- Company no. 16988667 — verifiable on Companies House
- Status active · private limited company
- Jurisdiction England & Wales
- Use formal records and legal correspondence only
Choose the lane before you send.
Six routes, six recipients, six purposes. The four most common are mirrored in the route grid above this section; the two specialist channels (privacy and press) live here. Misrouted messages get rerouted, but the right route is faster.
Introductions
Open conversations, basic site questions and first contact that does not require gated disclosure. The default lane.
Reviewer access
Whitepaper, executive summary, diligence requests, partner review and progressive disclosure routing. Gated material lives behind this lane.
Counsel route
Trademark matters, legal corrections, counsel liaison and formal IP enquiries. Formal notices also go to the registered office.
Vulnerability disclosure
Security issues, vulnerability reports and responsible-disclosure routing. Use the security page for scope and report format.
Data route
Privacy questions, data handling requests and corrections related to public-site or preview-access records. UK GDPR rights run through this lane.
Media boundary
Press enquiries, quote requests and media background checks. Approved wording and asset rules live in the press kit. No launch announcement is implied by response.
A good request is easier to route.
Reviewer requests follow a four-step protocol so the route owner can match the message to the right material on the first read. Friction is on purpose; it stops good requests being treated as noise.
What not to send through the front door.
Public contact channels work best when they are not used for material that needs a different procedure. Five categories sit outside the front door — not because they are unwelcome, but because the wrong channel adds risk to both sides.
The map is public; the legal route is precise.
Routing helps; service requires more. The callout below mirrors the same rule that appears on /legal · sheet 06 — on this page so anyone using the contact form sees it before they assume email alone counts as service.
Address · copy · confirmation
The registered office shown on this page is the Companies House address for BlackMenta Ltd. Email routing supports triage and response; it does not automatically replace any method of service required by law, contract or court rule.
- Address: 2nd Floor College House, 17 King Edwards Road, Ruislip, London, HA4 7AE
- Copy: legal@blackmenta.com with a clear subject line and the matter reference
- Confirmation: email service is by agreement; ask before assuming
Four cues that make a request useful.
Not rules — cues. Four habits that turn a cold message into a routable one. Each cue costs the sender almost nothing and saves the recipient a follow-up cycle.
Lead with the matter
Subject lines that name the route and the matter beat “Hello” or “Question”. “Counsel liaison: trademark opposition” sorts itself.
One ask per message
A request bundling preview access, legal questions and a vulnerability report needs three different recipients. Split it; route each to its lane.
Context before content
Two sentences on who you are and why you are writing, before any document, link or material. Cold attachments without context get triaged last.
SLA, not instant
Target acknowledgement is five business days. Silence inside the SLA is not refusal; it is queue. Re-pinging inside the window does not move it forward.
Gated channels live behind the wall.
This page is the public routing front door. Reviewer dashboards, diligence rooms, signed-NDA channels and counsel-direct lines are released through auth.blackmenta.com — once the public route has confirmed the right context.
Other pages, in any order.
Legal · privacy · security · terms · home.
Legal identity, stated plainly
Companies House № 16988667. Registered office, jurisdiction, IP notice, formal-notice procedure. The public legal record.
Data should be minimal, not theatrical
UK GDPR-aligned privacy notice. Controller, data map, lawful basis, retention, processors, rights. Where privacy@ messages route to.
Responsible disclosure route
Scope, evidence standard, response SLA, security.txt, PGP status. Required reading before security@ messages.
Use the site. Do not rely on it
Website and preview terms. Acceptance, scope, no-offer, preview rules, acceptable use, IP and E&W law.
The holding entity, the legal wall, the public surface
BlackMenta Ltd · № 16988667 · the public cover sheet for the IP holding entity behind these channels.
Notes.
- N.01 Public, ungated. This contact page is public and ungated. It gives counterparties a verifiable address, a privacy-safe map block and the correct route for each category of message. → see Sheet 02 + Sheet 03
- N.02 Gated stays gated. Reviewer packs, private files and gated materials remain outside the public contact page. They are released through the preview channel after the right context arrives. → see preview@ · CM.02
- N.03 No launch implied. A reply from press@ is not an announcement, embargo lift or launch confirmation. Approved wording lives in the press kit; nothing more. → see press@ · CM.06
- N.04 Map privacy. The location panel on Sheet 02 is a static schematic. No third-party map SDK loads, no map cookies, no visitor data sent to a map provider. → see Sheet 02 · spec line
- N.05 Routing corrections: hello@blackmenta.com. If a route should exist that does not yet, that is a correction, not a complaint.