Privacy-respecting analytics setup

Privacy-respecting analytics setup is a one-off project: we audit what and how is currently collected and reconfigure your analytics (GA4, Metrica, etc.) in a privacy-minded way — implement Consent Mode/a consent banner with correct logic (collection only after consent where required), anonymization, disable collection of unnecessary personal data, limit transfer to third parties, set reasonable retention periods, configure data minimization and masking of sensitive fields. Honestly about the main limitation: this is a TECHNICAL setup that reduces what is collected and privacy risks, but it is NOT a legal guarantee of GDPR/152-FZ compliance and does not replace a lawyer — whether consent and which policy texts are needed and whether processing is lawful is assessed by your lawyer; we implement their requirements technically. Honestly about the trade-off: a privacy setup may reduce data granularity (some events/fields are not collected, conversions are modeled without consent) — a conscious trade of privacy for completeness. Honestly about the essence: this is privacy-minded collection setup, NOT writing legal policies (separate/with a lawyer), not analytics itself and not metric growth. Honestly about data: correctness depends on a correct consent implementation and tagging; wrong consent logic = either over-collection or data loss. Requirements: access to analytics/tags/site and your (or your lawyer's) privacy requirements. Maintenance: when the site and rules change the setup needs upkeep. An important boundary: this is privacy-minded analytics setup, not a legal audit, not drafting policies and not real-time privacy monitoring (a separate service). If you collect no personal data and have no trackers, the setup may be minimal. Picture this: instead of 'we collect everything without consent and don't know the risks' you collect only what is needed, with consent and anonymization. The base price starts from 15,000 ₽ per project; it depends on the number of systems and consent complexity.

• Analytics collects unnecessary personal data without clear consent.
• There is no correct Consent Mode/banner and consent logic.
• Data goes to third parties and is stored indefinitely.
• You do not understand the privacy risks of the current collection.

• Audit of current collection (what and how is collected)
• Implementing Consent Mode/a banner with correct logic
• Anonymization and minimization of collected data
• Disabling unnecessary collection and limiting third-party transfer
• Reasonable retention periods, masking sensitive fields
• Flagging risk areas (legal assessment — by a lawyer)
• Settings documentation
• Handover of access and an instruction

• Only what is needed is collected, with consent and anonymization
• Fewer privacy risks (legal assessment — by a lawyer)
• Control over data storage and transfer
• Analytics configured carefully (completeness may consciously decrease)

• We clarify privacy requirements (yours/the lawyer's), systems; collect access
• We audit collection, implement consent, anonymization and minimization
• We verify the consent logic and collection, hand over documentation

• Does this make me compliant with GDPR/152-FZ?

  No. This is a technical setup that reduces the volume and risks of collection, but not a legal guarantee of compliance. Whether consent and which policy texts are needed and whether processing is lawful is assessed by your lawyer; we implement their requirements technically.

• Won't I lose data from a privacy setup?

  Some granularity may decrease: without consent some events/fields are not collected, conversions are modeled. It is a conscious trade-off of privacy and completeness; we set the logic to lose the minimum necessary.

• Will you write my privacy policy?

  No, policy texts and the legal assessment are prepared by a lawyer. We implement the privacy setup technically (consent, anonymization, minimization) per your or legal requirements and flag risk areas.