Regional legal documents and country-specific privacy policies

Regional Legal Documents and Country-Specific Privacy Policies

We implement country-specific legal document systems for websites operating in multiple jurisdictions. Our team builds jurisdiction detection, document versioning, user consent recording, and region-specific routing for privacy policies, cookie policies, and terms of service. Delivery takes four to six working days. We have implemented compliance systems for 30+ organizations operating in EU, US, and CIS markets. Our systems have passed regulatory audits and legal team reviews without requiring rework.

A website that operates in the EU, the United States, and CIS countries simultaneously must serve different legal documents to different users. GDPR in Europe, CCPA in California, Federal Law 152-FZ in Russia, and PIPEDA in Canada impose different consent requirements, document content, and retention obligations. Using a single document for all regions creates legal exposure.

What's Included in Our Regional Legal Documents Service

We deliver the complete legal document system turnkey. The scope covers:

• IP-based jurisdiction detection using MaxMind GeoIP2 or similar
• Regulation classification: GDPR, CCPA, CIS, or default for each detected country
• Document routing: serve the correct privacy policy, cookie policy, and terms for each jurisdiction
• Document versioning with effective date scheduling
• User consent recording with timestamp, IP address, user agent, and document version
• Admin interface for uploading new document versions and setting effective dates
• Automatic switchover to new versions on the effective date

How Does Jurisdiction Detection Work?

The detection layer reads the visitor's IP address, maps it to a country, and classifies the country into a regulatory group. Users can also choose their country explicitly via a preference cookie.

class UserJurisdiction
{
    public function detect(Request $request): string
    {
        if ($country = $request->cookie('user_country')) {
            return $country;
        }

        $reader  = new \GeoIp2\Database\Reader(storage_path('geoip/GeoLite2-Country.mmdb'));
        $record  = $reader->country($request->ip());
        return $record->country->isoCode ?? 'DEFAULT';
    }

    public function getRegulation(string $countryCode): string
    {
        return match(true) {
            in_array($countryCode, EU_COUNTRIES)        => 'gdpr',
            $countryCode === 'US'                       => 'ccpa',
            $countryCode === 'RU'                       => 'rfz152',
            in_array($countryCode, ['UA', 'BY', 'KZ'])  => 'cis',
            default                                     => 'default',
        };
    }
}

Document Storage and Routing

Legal documents are stored in a versioned database table. Each row contains the document type, regulation, locale, version number, effective date, and content. The routing layer looks up the correct document for the current user and falls back to the default document if a jurisdiction-specific version is not available.

CREATE TABLE legal_documents (
    id           BIGSERIAL PRIMARY KEY,
    type         TEXT,         -- privacy-policy, terms, cookie-policy
    regulation   TEXT,         -- gdpr, ccpa, rfz152, default
    locale       CHAR(2),
    version      TEXT,         -- 2.3.1
    content      TEXT,
    effective_at DATE,
    is_current   BOOLEAN DEFAULT false,
    created_at   TIMESTAMPTZ DEFAULT NOW()
);

Route::get('/legal/privacy-policy', function (Request $request) {
    $jurisdiction = app(UserJurisdiction::class)->detect($request);
    $regulation   = app(UserJurisdiction::class)->getRegulation($jurisdiction);
    $locale       = app()->getLocale();

    $document = LegalDocument::where([
        'type' => 'privacy-policy',
        'regulation' => $regulation,
        'locale' => $locale,
    ])->first()
    ?? LegalDocument::where([
        'type' => 'privacy-policy',
        'regulation' => 'default',
        'locale' => $locale,
    ])->first();

    return view('legal.document', compact('document', 'regulation'));
});

Why Is Document Versioning Critical?

Legal documents change. GDPR articles get reinterpreted, CCPA gets amended, and your legal team updates the privacy policy as your product evolves. Every time a document changes, users who previously consented need to be notified, and their new consent needs to be recorded separately.

A versioned document system handles this automatically. The new version gets an effective date in the future. On that date, the system switches to the new version. Users who visit after the effective date see the new document and are prompted to re-accept.

Consent Recording

Users in GDPR-regulated countries must explicitly accept documents. Consent records must be retained and auditable.

UserConsent::create([
    'user_id'      => auth()->id(),
    'document_id'  => $document->id,
    'ip_address'   => request()->ip(),
    'user_agent'   => request()->userAgent(),
    'accepted_at'  => now(),
]);

Consent records are stored with full audit fields. Each record links to the specific document version accepted, the user's IP address, and the timestamp. This data can be exported for regulatory audit requests.

How Long Does Implementation Take?

The implementation timeline depends on the number of jurisdictions, document types, and languages you need to support.

1. Review your target markets and identify applicable regulations
2. Design the document database schema and routing logic
3. Build the jurisdiction detection and document routing system
4. Implement the consent recording layer
5. Set up the admin interface for document management

Contact us to discuss your compliance requirements. We will review your target markets, identify the applicable regulations, and propose an implementation plan.

Web Application Security: HTTPS, CSP, XSS, CSRF, WAF, DDoS Protection

A website breach rarely looks like in movies. More often it's: a bot finds an unprotected /admin/export endpoint, downloads the customer database, and closes the connection. Or: through an outdated WordPress plugin, a web shell is uploaded, and the server starts sending spam. Or quieter: an XSS in a comment field allows stealing admin session cookies, unnoticed for months. We have analyzed dozens of such cases — each vulnerability could have been fixed at the development or audit stage.

Web application security is not a single setting. It's layers of protection, each closing a separate class of attacks. Order an audit — we'll assess the project and deliver a turnkey plan within 2–4 weeks.

How do we ensure comprehensive web application security?

HTTPS and Proper TLS Configuration

HTTPS is the minimum mandatory level. But having an SSL certificate and having a properly configured TLS are different things.

In Nginx/Apache configuration we check:

• Protocols: only TLS 1.2 and TLS 1.3, SSLv3 and TLS 1.0/1.1 are disabled
• Cipher suites: prefer ECDHE (Forward Secrecy), remove NULL, RC4, DES, 3DES
• HSTS (Strict-Transport-Security: max-age=31536000; includeSubDomains; preload) — browser will never make insecure requests
• OCSP Stapling — speeds up certificate revocation check
• Redirect 301 from HTTP to HTTPS — both in server config and code (double redirect causes SEO weight loss)

Check: SSL Labs (ssllabs.com/ssltest) should show A or A+. If B, the configuration is weak.

Let's Encrypt + Certbot for production is standard. Automatic renewal via certbot renew in cron. Wildcard certificates for subdomains via DNS-01 challenge.

Content Security Policy: The Most Powerful and Complex Protection

CSP is an HTTP header that tells the browser which sources are allowed to load resources. A properly configured CSP completely blocks most XSS attacks, even if the vulnerability exists in the code.

The problem: breaking the site with an incorrect CSP is easy. default-src 'none' — and fonts, images, JS stop working. So we start with Content-Security-Policy-Report-Only — CSP logs violations but does not block anything. We monitor reports for 2–4 weeks, refine the policy, then switch to enforcement mode.

Example of a real policy for a site with Google Analytics, Google Fonts, and Stripe:

Content-Security-Policy:
  default-src 'self';
  script-src 'self' https://www.googletagmanager.com https://js.stripe.com 'nonce-{random}';
  style-src 'self' https://fonts.googleapis.com 'unsafe-inline';
  font-src 'self' https://fonts.gstatic.com;
  frame-src https://js.stripe.com;
  img-src 'self' data: https://www.google-analytics.com;
  connect-src 'self' https://api.stripe.com https://www.google-analytics.com;
  report-uri /csp-report;

nonce — a random string generated server-side per request. Inline scripts with the correct nonce are allowed; without nonce, they are blocked. This completely breaks XSS via <script>alert(1)</script>.

'unsafe-inline' in style-src is a compromise for inline styles. It's better to remove it by moving all styles to CSS files, but that requires refactoring.

Why XSS Remains the Most Common Vulnerability?

XSS (Cross-Site Scripting) — injection of JS code through user input. According to OWASP, XSS is in the top 3 web application vulnerabilities. Three types:

Protection: never insert user input into HTML without escaping. In PHP — htmlspecialchars() with ENT_QUOTES. In Laravel Blade templates — {{ $var }} is safe, {!! $var !!} is dangerous. In React — {variable} is safe, dangerouslySetInnerHTML is dangerous. For Rich Text — use htmlpurifier on PHP or DOMPurify in the browser.

CSRF: Protecting Forms and APIs

CSRF (Cross-Site Request Forgery) — an attacker forces the victim's browser to send a request on their behalf. Example: a user is logged into a bank, opens a malicious page, which makes fetch('https://bank.ru/transfer?to=evil&amount=50000') — if the bank is unprotected, money is transferred.

CSRF tokens — standard protection for forms: the server generates a random token, stores it in the session, and inserts it as a hidden field in the form. On POST request, the token is verified. The attacker does not know the token. Laravel does this automatically with @csrf.

SameSite cookies — modern protection: SameSite=Strict or SameSite=Lax prevents the browser from sending cookies in cross-site requests. Works in all modern browsers.

API without sessions (JWT, Bearer tokens) — CSRF is irrelevant if the token is not stored in a cookie (but in the Authorization header or localStorage). However, localStorage is vulnerable to XSS — so for sensitive data, HttpOnly cookies with SameSite are preferable.

WAF and DDoS Protection

WAF (Web Application Firewall) filters HTTP traffic for attacks: SQL injection, XSS, path traversal, known exploit patterns. Options:

• Cloudflare WAF — cloud-based, OWASP Top 10 rules out of the box, custom rules via expressions. Managed Rules automatically block new threats.
• ModSecurity (Nginx/Apache) — self-hosted, OWASP Core Rule Set (CRS). Flexible but requires tuning and monitoring of false positives.
• AWS WAF — for infrastructure on AWS, integrates with CloudFront and ALB.

DDoS protection. Cloudflare at L3/L4/L7 is the de facto standard for most sites. Automatic mitigation of volumetric attacks, Under Attack Mode during active attacks. For critical infrastructure — Cloudflare Magic Transit or specialized solutions (Qrator, StormWall for the Russian market).

Rate Limiting at the application level — an additional layer. Laravel ThrottleRequests middleware: 60 requests per minute per IP for general endpoints, 5 for /login and /password/reset. Redis as a counter store — mandatory for horizontally scalable systems (otherwise limits are not synchronized between servers).

Other Mandatory Measures

Security headers. Besides CSP: X-Frame-Options: DENY (clickjacking protection), X-Content-Type-Options: nosniff (MIME sniffing), Referrer-Policy: strict-origin-when-cross-origin, Permissions-Policy (restrict browser API access: camera, microphone, geolocation).

SQL injection. Prepared statements everywhere. No concatenation of user input into SQL strings. ORM (Eloquent, Doctrine) protects by default. $wpdb->prepare() in WordPress is mandatory.

Dependency updates. composer audit and npm audit in CI/CD pipeline. Dependabot or Renovate for automatic PRs with updates. Critical CVEs — patch within 24 hours.

Secrets and configuration. .env — never in Git. Secrets in production — via CI/CD environment variables (GitHub Secrets, GitLab CI Variables) or HashiCorp Vault. Leak detection: git-secrets, truffleHog in pre-commit hooks.

How We Work

1. Audit — code scanning, configuration review, dependency analysis, manual business logic verification.
2. Planning — vulnerability remediation plan, stack selection (CSP, WAF, rate limiting).
3. Implementation — TLS setup, CSP configuration, headers, Rate Limiting, WAF.
4. Testing — re-penetration test, load testing, false positive check.
5. Deployment and Monitoring — enable production CSP, set up alerts, train the team.

What's Included

• Report with found vulnerabilities and recommendations (PDF + code snippets)
• Ready TLS configuration (Nginx/Apache)
• CSP policy with Report-Only and production versions
• WAF and Rate Limiting setup
• Dependency update plan
• Access to monitoring tools (Sentry, Datadog)
• 30 days of post-audit support (consultations, fixes)

Timeline and Cost

The budget is calculated individually — contact us for a project evaluation.