Аккаунт в General iT
Войдите или создайте аккаунт для управления услугами в панели.
Страны не найдены. Попробуйте другое название или код.
MODULE FOR 1C-BITRIX
Yasnokor
YasnoCore Privacy Control manages consent for data processing and cookie settings in forms on 1C-Bitrix websites. All settings and the event log are stored on your server without external cloud services. The module provides an adaptive banner with categories: Necessary, Analytics, Marketing, and Preferences. Visitors can reopen settings and change their choices.
YasnoCore Privacy Control manages consent for data processing and cookie settings in forms on 1C-Bitrix websites. All settings and the event log are stored on your server without external cloud services.
The module provides an adaptive banner with categories: Necessary, Analytics, Marketing, and Preferences. Visitors can reopen settings and change their choices. Marked analytics and marketing scripts run only after the user selects the corresponding category. Blocking known analytics systems until consent is obtained is optional.
Forms containing fields for email, phone, name, or message automatically include a mandatory consent checkbox. Specific forms can be excluded from this rule. Individual settings are available for each site in multisite installations.
The module logs actions of users logged into the Bitrix account. Records include the time, selected categories, policy version, and page address. Features include CSV export, retention period settings, automatic deletion of outdated records, and technical audit.
In version 1.0.18, the logging logic differs for guests. A guest's cookie selection is saved only in the browser, and the form submits normally after the checkbox is set. Guest actions are not recorded in the log, and logging in is not required to use forms or configure cookies.
After logging into a 1C-Bitrix account, background recording of user actions is activated. Form content is not included in the journal. Instead of direct account identifiers and technical data, protected hashes are used.
Cookie selection and form submission operate independently of the journal recording process. If recording fails due to network issues or load restrictions, the visitor will see a message on the open page. Leaving the page can also interrupt the recording process.
New client-side events are stored for up to seven days. Previously accumulated records remain subject to the original retention rules. Old anonymous events are available in a separate archive and do not become records of authorized users.
For whom
The module is intended for online stores, corporate websites, educational projects, web studios, and website support services on the 1C-Bitrix platform.
Important
The journal links an action to a 1C-Bitrix account but does not verify the identity of a specific person and does not serve as legal proof of consent. The module provides technical tools; the website operator determines the documentation, legal grounds for data processing, and organizational measures.
The YasnoCore Privacy Control module manages consents, cookies, and event logging. Proper operation of the event log requires standard user authentication and the preservation of server sessions within the Bitrix system. Pages accessible to authenticated users cannot be served from the general cache to other visitors. Detailed configuration instructions are provided in the installation documentation.
General iT can take care of implementing “YasnoCore Privacy Control — consents, cookies, and event log”, including installation, configuration and result verification.
UPDATE HISTORY
YasnoCore Privacy Control 1.0.18: the log is available only to authorized users.
- Recording requires an active Bitrix account in the handler and service; the user is taken only from the server session.
- One-time permissions are linked to the account, session, site, and action; changing the account or logging out prohibits the use of the old permission.
- Guests have access to local cookie selection and standard forms, without requests to the log.
- Account limits of 8/minute and 200/day have been added, regardless of IP or session changes.
- Refusals no longer create technical events or permanent warnings.
- New account events are separated from historical data; previous records and retention periods are preserved.
- Logging into an account does not grant the record the status of legal proof of consent.
Security check fixes for YasnoCore Privacy Control version 1.0.17.
- The share of a single subnet is limited to 15 records per minute; technical marks belong to the untrusted stream and do not affect the settings evaluation;
- server-side journal skip history has been added: no more than one technical mark per minute per site, stored for up to 7 days; marks are not counted as consents;
- anonymous telemetry has been separated into a separate view and CSV; standard export excludes it;
- mandatory aggregate limits for the anonymous stream per site have been introduced: 60 records per minute and 2000 per day UTC;
- the 200 records per day UTC limit has been supplemented with IPv4 /24 and IPv6 /64 aggregation; a refusal is provided upon reaching the storage threshold;
- deviations are explicitly shown to the visitor and operator without blocking cookie selection or standard form submission;
- server ownership of tokens, their one-time use, source separation, and the retention periods of existing records have been preserved.
Security check fixes for YasnoCore Privacy Control version 1.0.16.
- Server-side log skip history added: no more than one technical mark per minute per site, stored for up to 7 days; marks are not counted as consents;
- Anonymous telemetry separated into a separate view and CSV; standard export excludes it;
- Mandatory aggregate limits for anonymous traffic per site introduced: 60 records per minute and 2000 per day UTC;
- The 200 records per day UTC limit supplemented with IPv4 /24 and IPv6 /64 aggregation; refusal provided upon reaching the storage threshold;
- Deviations are explicitly shown to the visitor and operator without blocking cookie selection or standard form submission;
- Server ownership of tokens, one-time use, source separation, and retention periods of existing records preserved.
Security checks corrections for YasnoCore Privacy Control version 1.0.15.
- Anonymous telemetry has been separated into a distinct view and CSV format; standard exports exclude it.
- Mandatory aggregate limits for the anonymous stream to the site have been introduced: 60 records per minute and 2000 records per day UTC.
- The 200 records per day UTC limit is supplemented with aggregation of IPv4 /24 and IPv6 /64; a refusal is provided upon reaching the storage threshold.
- Deviations are explicitly shown to visitors and operators without blocking cookie selection or standard form submission.
- Server ownership of tokens, their one-time use, source separation, and retention periods for existing records have been preserved.
Security check fixes for YasnoCore Privacy Control 1.0.14.
- Anonymous event counters are separated from records of the trusted server source; they are not represented by statistics of confirmed agreements;
- A verified atomic limit of 200 records per UTC day has been added for the source;
- Exceeding the daily limit is clearly displayed and does not block local selection or form submission;
- Fixes for sessions, single-use tokens, record owner, loads, and migration 1.0.13 have been preserved.
YasnoCore Privacy Control 1.0.13 security check fixes.
- One-time tokens are bound to the server session, site, action, and page path; the API does not extend token lifetimes;
- Record identifiers are generated by the server; there is no search for external records by UUID from the request;
- Declined requests do not consume the general limit and do not split the limit table;
- Load on the journal does not block cookie selection or form submission; record errors are displayed separately;
- New anonymous records are stored for no more than 7 days; historical data is preserved;
- The migration corrects the erroneous attribution of old anonymous records without deleting them.
Security fixes for YasnoCore Privacy Control 1.0.12.
- anonymous records are clearly labeled as 'declared by the client';
- the provenance flag is passed as a separate typed argument and is not taken from JSON;
- the rate limit for anonymous records has been reduced to 10 per minute;
- the interface explicitly states that the anonymous journal does not certify identity.
Security fixes for YasnoCore Privacy Control 1.0.11.
- requests without Sec-Fetch-Site and Sec-Fetch-Mode are rejected;
- all limits and the one-time token are consumed before checking for a duplicate UUID;
- the flag for an attested browser context is stored and output in the journal and CSV;
- quota exhaustion is visible in the audit and does not block legitimate records.
Security fixes for YasnoCore Privacy Control 1.0.10.
- consent recording requires a server-signed one-time token;
- the chain of trusted proxies is parsed from right to left;
- journal quotas, cleanup by EXPIRES_AT, and visibility of losses in the audit have been added.
Security check fixes for YasnoCore Privacy Control 1.0.9.
- Added idempotent migration for tables, indexes, salts, and the cleanup agent;
- Introduced limits per site and address, trusted proxies, and UUID idempotency;
- Policy version is determined by the site setting, cleanup is performed in batches by index.
Adjustments based on moderation feedback: precise marketing name. Security check issues resolved: server-side binding to SITE_ID, atomic limits without NAT locking, and retention periods per site.
Adjustments based on moderation feedback: precise marketing name. Protection of the anonymous log against DoS: strict UUID and cookie validation, limits per visitor and IP, indexed queries.
Adjustments based on moderation feedback: precise marketing name. Portable SQL audit; full license agreement; banner configuration fix, CSV protection, and policy link protection.
Adjustments based on moderation feedback: precise marketing name. Portable SQL audit; full license agreement.
Security enhancement for YasnoCore Privacy Control 1.0.4.
- The public endpoint accepts only JSON requests with a confirmed same-origin context;
- Fetch Metadata verification has been added to block cross-site requests;
- The full pseudonymized visitor hash has been excluded from CSV exports;
- CSV files are protected against caching and MIME sniffing.
Fix for YasnoCore Privacy Control 1.0.3 based on a full scenario test.
- Fixed handling of POST requests to the consent logging endpoint;
- Added verification of the executable endpoint structure in the build.
Compatibility fix for YasnoCore Privacy Control 1.0.1 with the Marketplace protective packager.
- Resolved a syntax error during installation of the protected build;
- Functionality of version 1.0.0 remains unchanged.
USER EXPERIENCE
How does this solution work in a real project? Share your experience and help others choose.
There are no reviews of this solution on git.ru yet. Tell us what worked well and what could be improved.
Verified purchaseAdd a key if you wish. A verified review gets a badge, priority placement and more rating weight.
Open to every clientJust sign in to your account. A key is optional; all reviews are moderated.
YOUR PROJECT INFRASTRUCTURE
FROM THE SAME DEVELOPER
Yasnokor
YasnoCore Content Control is a module designed to monitor content freshness on a website. It assists editors and administrators in identifying outdated promotions, news, job vacancies, events, and documents that remain active after their validity period has expired. The functionality checks the standard InfoBlock field labeled "Activity End Date".
The YasnoCore Voice module for the on-premise version of Bitrix24 converts call audio recordings into text transcripts and structured meeting protocols. Capabilities include uploading files via the administrative interface and utilizing pre-built protocol templates for meetings, sales, marketing, production, finance, and commercial negotiations.
SitePulse is a compact technical control panel for websites on the '1C-Bitrix: Site Management' platform. The module helps administrators quickly identify issues with agent execution, mail event processing, and available server disk space. After installation, SitePulse adds a new section to the administrative panel.
MORE FOR YOUR WEBSITE
The module automates image compression on the website in accordance with Google PageSpeed Insights recommendations. It supports integration via CDN OptiPic, allowing optimization without modifying image URLs. The main advantage of CDN integration is the automatic conversion of images to the modern WebP format to minimize file size. Browsers that support WebP receive images in that format.
The module is designed for online stores running on the 1C-Bitrix platform to automate the integration of supplier product catalogs. It is also suitable for news and city portals to facilitate content population. The solution supports data import in Excel, XML, YML, CSV, and RSS formats.
The module is designed for the «1C-Bitrix: Site Management» platform and enables importing infoblock elements, including products, from Excel files. It also supports data loading into Highload blocks.
BEFORE YOU ORDER
