データ保護のための技術的措置

私たちのデータ保護について

You trust us with access to your ad accounts, CRM data, and analytics. This page lists the concrete measures we apply to protect that data.

プラットフォームで実装されていること

Technical measures at the traffic, storage, authentication, and infrastructure layers

データの暗号化

TLS 1.3 for all traffic. Integration OAuth tokens are stored encrypted (AES-256). Passwords use bcrypt with cost factor 12.

安全な認証

Two-factor authentication (2FA). OAuth 2.0 for all integrations. JWT with automatic key rotation. Brute-force protection via rate limiting.

データの分離

Multi-tenant architecture: each workspace's data is isolated at the database level. Access to other tenants' data is not possible at the query layer.

操作監査

All user actions (login, password change, integration connection, data export) are recorded in an immutable log with IP and device info. Retention: 12 months.

安全なCookie

Auth cookies are marked HttpOnly, Secure, and SameSite=Strict. CSRF protection uses double-submit cookies plus X-Requested-With.

境界防御

Cloudflare WAF at the edge, DDoS protection, and automatic IP blocking when limits are exceeded. nginx with configured security headers (HSTS, CSP, X-Frame-Options).

要件への準拠

We operate in line with Russian Federal Law 152-FZ on personal data. For users in the EU and US, additional rights under GDPR and CCPA apply — see /privacy.

152-ФЗ

Documented in the Privacy Policy (/privacy). Processing is carried out in compliance with Russian Federal Law 152-FZ.

TLS 1.3 + HSTS

Enforced HTTPS on all pages with HSTS-preloaded.

OAuth 2.0

Secure authentication for 48+ ad and analytics platforms.

透明なポリシー

The full list of subprocessors, processing purposes, and retention periods is published at /privacy.

私たちのエンジニアリングの慣行

最小権限の原則

We request only the OAuth scopes the service cannot function without. Within the team, access to production data is role-based.

パラメータ化クエリと入力バリデーション

All database queries are parameterized. Server-side HTML sanitization. CSP for XSS protection.

シークレットのローテーション

JWT keys rotate every 90 days with a 7-day overlap. The OAuth token encryption key rotates every 180 days with background re-encryption.

再現可能なビルドと依存関係の監査

CI runs a dependency vulnerability scanner on every merge. Container builds are deterministic.

脆弱性を発見しましたか？

We value the contribution of security researchers. If you have discovered a vulnerability in our system, please report it to us confidentially.

If you followed this disclosure channel in good faith, we will not pursue legal action against you.

[email protected]

Юридическая информация

AdMetric — платформа маркетинговой аналитики. Услуги оказываются двумя юридическими лицами:

ООО «АДМЕТРИК» (ИНН 9726112159, ОГРН 1267700088391, Российская Федерация) — обслуживание клиентов на территории РФ, приём платежей в рублях, обработка персональных данных в соответствии с Федеральным законом № 152-ФЗ.
ИП Sobolev (Республика Казахстан) — обслуживание клиентов за пределами РФ, международные платежи, интеграции с зарубежными рекламными и аналитическими платформами.

Оператором персональных данных выступает то юридическое лицо, с которым у пользователя заключён договор; оно определяется страной регистрации пользователя и указывается в платёжных документах.

Единый адрес для запросов по персональным данным: [email protected].