데이터 보호를 위한 기술적 조치

당사의 데이터 보호 방식

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.

안전한 쿠키

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].