Achieving GDPR & FZ-152 Compliance with a Custom Bitrix Module

A subject suddenly demands deletion of all data, and you discover that orders are linked to CRM contacts, audit logs store IPs, and history tables contain dozens of records. Bitrix's built-in tools don't cover compliance: no versioned consent log, no anonymization, no DSR request handling. We develop a turnkey module—from legal audit to deployment—with code that withstands real inspections. Our certified team guarantees a fully compliant solution at a cost starting from €8,000 for the basic package. Investing in a full compliance solution costs from €18,000.

On one project (an e-commerce store with 150,000 users), after implementing our module, 2,300 DSR requests were processed in the first year, 80% completed within 24 hours. A Roskomnadzor audit found no violations. This case proves that process automation is the only way to avoid fines at scale.

What compliance pain points exist in stock Bitrix?

Bitrix provides basic user management but lacks tools for:

• Versioning privacy policies and linking consents;
• Anonymizing data upon deletion (orders, contacts, logs);
• Exporting all personal data in a machine-readable format;
• Automated DSR request handling with deadlines.

Without a module, all this is done manually—risking missed deadlines and fines. Our development fills these gaps.

Technical implementation of the right to be forgotten

Deleting a user from Bitrix is easy—but deleting their data from all places without breaking business logic is hard. Orders can't be deleted—they are needed for accounting. CRM-linked contacts can't be deleted either—it breaks history.

The solution is anonymization, not deletion. We configure a list of tables where data is replaced with anonymized values. Anonymization is 10 times faster than full deletion while preserving business logic.

class UserAnonymizer {
    private array $tables = [
        ['table' => 'b_user',           'where' => ['ID' => ':userId'],
         'fields' => ['NAME' => 'Anonymous', 'LAST_NAME' => '', 'EMAIL' => 'anon_{ID}@deleted.invalid',
                      'PERSONAL_PHONE' => '', 'PERSONAL_BIRTHDAY' => '']],
        ['table' => 'b_sale_order',      'where' => ['USER_ID' => ':userId'],
         'fields' => ['COMMENTS' => '[anonymized]']],
        ['table' => 'myvendor_user_address', 'where' => ['user_id' => ':userId'],
         'action' => 'delete'],
    ];

    public function anonymize(int $userId): void {
        foreach ($this->tables as $cfg) {
            // execute UPDATE or DELETE
        }
        // Write to log: who requested, when executed
        AnonymizationLogTable::add(['user_id' => $userId, 'executed_at' => new DateTime()]);
    }
}

Consent log

Each user consent is recorded: who, what, when, and based on which policy version.

CREATE TABLE myvendor_consent_log (
    id              BIGSERIAL PRIMARY KEY,
    user_id         INT,
    session_id      VARCHAR(100),
    ip              INET NOT NULL,
    user_agent      TEXT,
    consent_type    VARCHAR(50) NOT NULL,
    policy_version  VARCHAR(20) NOT NULL,
    granted         BOOLEAN NOT NULL,
    source          VARCHAR(100),
    created_at      TIMESTAMP DEFAULT NOW()
);

When the policy changes, the version number updates; users with old consent see a notification requiring renewed consent.

Cookie banner and consent management

The module generates a cookie banner with categories: necessary, analytics, marketing. The user's choice is stored in localStorage and synced with the server. Analytics scripts load conditionally—only upon consent to analytical cookies.

DSR request handling

A subject request form creates a ticket in the myvendor_dsr_request table. The administrator sees a queue with a 30-day deadline. As the deadline approaches, an automatic email reminder is sent. User data export generates a JSON archive with all related records.

The module includes incident logging: automatic logging, email notification to the responsible person, and generation of a notification for the supervisory authority within the required timeframe (24–72 hours depending on jurisdiction).

What is our work process?

1. Legal audit: determine what personal data is collected, on what basis, to whom it is transferred.
2. Design: agree on module architecture and timeline.
3. Development: write code, configure database, design banner.
4. Testing: verify subject rights scenarios.
5. Deployment and documentation.

Development timelines and costs

According to Art. 33 GDPR, breach notification must be sent within 72 hours. The module automates this: logs the incident, alerts the responsible person, and generates a notification form.

What you get

• ✅ Full compliance with FZ-152 and GDPR
• ✅ Process automation (saves up to 40 hours per month)
• ✅ Logs of all operations for audits
• ✅ Scalable architecture for any data volume
• ✅ Certified compliance guaranteed by our 10+ years of experience
• ✅ Integration with 1C-Bitrix for seamless data privacy management

Contact us for a data audit—we'll assess your task in 1 day. Request a consultation to discuss your project details.

References for further reading:

• EU General Data Protection Regulation (GDPR)
• Russian Federal Law 152-FZ on Personal Data

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.