Skip to content
cccskills
FreePublished on GitHub

legal-impressum-world

International legal notice requirements. UK, Switzerland, USA, and worldwide best practices for multi-jurisdiction websites.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (2)

  • SKILL.md9.5 KB
  • source.json677 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

International Legal Notice Requirements

Jurisdiction: Worldwide (non-EU focus)

Related Skills:

This skill covers legal notice requirements for websites outside the EU, including UK (post-Brexit), Switzerland, USA, and international best practices.


1. United Kingdom (Post-Brexit)

Legal Framework

Law/RegulationScope
Companies Act 2006 (s.82, s.1139)Company websites
Business Names Act 1985Trade names
Electronic Commerce (EC Directive) Regulations 2002Still applicable
Consumer Contracts Regulations 2013B2C online sales
UK GDPR + DPA 2018Privacy requirements

Required Information

Companies (Ltd, PLC)

FieldRequired
Company name✓
Registered number✓
Place of registration (England/Wales, Scotland, NI)✓
Registered office address✓
VAT number (if applicable)✓
Directors (if stated on stationery)Optional

Sole Traders / Partnerships

FieldRequired
Owner/partner names✓
Business address✓
VAT number (if applicable)✓

UK Template

COMPANY INFORMATION

[Company Name] Limited
Registered in England and Wales
Company Number: [12345678]
Registered Office: [Full Address]

VAT Registration Number: GB [XXX XXXX XX]

Contact:
Email: [email@example.com]
Phone: [+44 XXX XXX XXXX]

2. Switzerland

Legal Framework

LawScope
Art. 961 OR (Obligationenrecht)Commercial register disclosure
Art. 954a ORBusiness correspondence requirements
DSG (Datenschutzgesetz)Privacy requirements
UWGUnfair competition

Required Information

FieldRequired
Company name (exact Firma)✓
Legal form (AG, GmbH, etc.)✓
Registered seat (Sitz)✓
Commercial register entry (CHE-Nr.)✓
MWST/TVA number (if applicable)✓
Address✓
Contact (email/phone)Recommended

Swiss Rechtsformen

FormGermanFrenchItalian
AGAktiengesellschaftSASA
GmbHGes. m.b.H.SàrlSagl
EinzelfirmaEinzelunternehmenEntreprise individuelleDitta individuale
KlGKollektivgesellschaftSNCSNC
KmGKommanditgesellschaftSCSAc
GenossenschaftGenossenschaftCoopérativeCooperativa

Swiss Template

IMPRESSUM

[Firma] AG
[Strasse Nr.]
CH-[PLZ] [Ort]
Schweiz

Handelsregister: [Kanton]
CHE-[XXX.XXX.XXX]
MWST-Nr: CHE-[XXX.XXX.XXX] MWST

Kontakt:
Tel: +41 [XX XXX XX XX]
E-Mail: [info@beispiel.ch]

3. United States

Legal Framework

The US has no federal Impressum requirement equivalent to EU/DACH regions. However:

RequirementScope
CAN-SPAM ActCommercial emails
CCPA/CPRA (California)Privacy for CA residents
State business registrationVaries by state
FTC regulationsAdvertising disclosure

Recommended Disclosures

While not legally mandated like in DACH/EU, best practices include:

FieldReason
Business nameTrust, legal clarity
Physical addressCAN-SPAM, credibility
Contact email/phoneCustomer service, trust
State of incorporationLegal clarity for LLCs/Corps
Privacy policy linkCCPA, state laws

California-Specific (CCPA/CPRA)

Required for businesses with CA customers:

  • "Do Not Sell My Personal Information" link
  • Privacy policy with specific disclosures
  • Contact method for privacy requests

US Template (LLC Example)

COMPANY INFORMATION

[Company Name], LLC
A [State] Limited Liability Company

Mailing Address:
[Street Address]
[City], [State] [ZIP]
United States

Contact:
Email: [email@example.com]
Phone: [+1 (XXX) XXX-XXXX]

Privacy: See our Privacy Policy

4. Other Countries

Canada

RequirementLaw
Business registrationProvincial
CASL (anti-spam)Contact info in emails
PIPEDAPrivacy requirements

Australia

RequirementLaw
ABN (Australian Business Number)Tax/business
ACN (Australian Company Number)Companies
Privacy Act 1988Privacy requirements

Brazil

RequirementLaw
CNPJ (Tax ID)Required on website
LGPDPrivacy requirements

China

RequirementNotes
ICP License numberRequired for hosting in China
Business license infoRequired

5. Multi-Jurisdiction Strategy

Approach for International Websites

┌─────────────────────────────────────────┐
│        Website Serves Multiple          │
│              Jurisdictions              │
├─────────────────────────────────────────┤
│                                         │
│  Option 1: COMPREHENSIVE                │
│  ─────────────────────────             │
│  Include all disclosures that          │
│  would be required in strictest        │
│  jurisdictions (DE/AT)                 │
│                                         │
│  Option 2: SEGMENTED                    │
│  ─────────────────────                 │
│  Country-specific legal pages          │
│  (/legal/at, /legal/de, /legal/uk)    │
│                                         │
│  Option 3: MINIMUM + SUPPLEMENTS        │
│  ──────────────────────────────        │
│  Base page + country-specific          │
│  addendums                             │
│                                         │
└─────────────────────────────────────────┘

Recommended: Comprehensive Approach

Include all of:

  • Full company identification (name, form, registration)
  • Physical address
  • Contact (email + phone)
  • VAT/Tax ID
  • Representatives/directors
  • Privacy policy link
  • Cookie consent
  • ODR link (if EU B2C)
  • Professional body info (if regulated)

6. Language Considerations

MarketLanguage Requirement
AustriaGerman required
GermanyGerman required
FranceFrench required (Loi Toubon)
SwitzerlandLocal language + English acceptable
UKEnglish
USAEnglish (typically)
GlobalEnglish as common denominator

Multi-Language Implementation

LEGAL NOTICE

[Tab: English] [Tab: Deutsch] [Tab: Français]

Or:

IMPRESSUM / LEGAL NOTICE / MENTIONS LÉGALES

[Combined content in multiple languages]

7. Universal Template (Global Best Practice)

LEGAL NOTICE / IMPRESSUM

Company Information:
[Full Legal Name] [Legal Form]
[Street Address]
[Postal Code] [City]
[Country]

Contact:
Phone: [+XX XXX XXX XXXX]
Email: [contact@example.com]

Registration:
[Register Type]: [Registration Authority]
Registration Number: [XXXXXXX]

Tax Information:
VAT/Tax ID: [XXXXXXXXXXXX]

[For corporations:]
Directors/Representatives: [Names]
Share Capital: [Amount] [Currency]

[For regulated professions:]
Professional Body: [Name]
License/Registration: [Number]

Legal:
Privacy Policy: [Link]
Terms of Service: [Link]

[For EU B2C:]
Online Dispute Resolution:
https://ec.europa.eu/consumers/odr/

8. Common Mistakes to Avoid

MistakeWhy It's a Problem
P.O. Box onlyMost jurisdictions require physical address
Missing emailRequired in EU/DACH
Wrong legal formMust match official registration
Outdated informationMust be kept current
Hidden/hard to findMust be easily accessible
Missing privacy linkGDPR/CCPA requirements
Generic templateCountry-specific rules ignored

9. Compliance Checklist (Global)

Universal Requirements

  • Legal business name
  • Physical address
  • Email contact
  • Phone number
  • Privacy policy

If Incorporated

  • Legal form (Ltd, LLC, GmbH, etc.)
  • Registration number
  • Registration authority/location
  • Representatives/directors

If VAT/Tax Registered

  • VAT/Tax ID number

If Regulated Profession

  • Professional body
  • License/registration
  • Professional rules reference

If B2C in EU

  • ODR platform link
  • Consumer rights information

10. Resources


Credits & Attribution

This skill is part of the webconsulting.at skills collection.

Sources: National government websites, legal databases, industry best practices

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

007

Free

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store6Updated May 27, 2026

See all skills by aibot88

Report a problem with this skill