PRIVACY NOTICE

Keep the inquiry simple.
Keep the evidence private.

Notice version: October 10, 2026. This notice explains how IP DEFENSE at IPDefense.law handles website visits and business inquiries.

Information submitted

The form collects business email, company, job title, general qualification answers, contact permission, optional educational-email consent, and a submission identifier. It does not accept files, source code, binaries, or detailed incident narratives. Do not provide privileged or confidential evidence.

Purpose and access

Submitted information is used to assess service fit and handle your review request. It is stored in an access-controlled operator database with the contact and questionnaire payload encrypted. Authorized operators can read records through the protected administration interface. Submitting a form does not create an attorney-client relationship or schedule a consultation.

Optional analytics

Analytics are off until you opt in. They record allowlisted events, public page paths without query strings, approved campaign tags, anonymous session identifiers, experiment variants, and page performance. A consented first-party measurement session uses a 30-minute HTTP-only cookie. Linked qualification, consultation, proposal, payment, and revenue milestones support acquisition reporting. Google Tag Manager and GA4 remain disabled until configured; when enabled they receive these limited measurements, never contact details, company names, or questionnaire answers. With analytics consent, limited campaign attribution may be attached to the request for acquisition reporting. Do not place personal information in campaign URLs. No inquiry answers or contact details are sent to advertising pixels. Global Privacy Control and Do Not Track override an analytics opt-in.

Your privacy preference is stored locally in the browser. Hero and offer assignments use first-party HTTP-only cookies for up to 90 days to keep the same treatment on repeat visits. Use “Privacy choices” in the footer to change your analytics preference at any time. Declining stops future analytics; withdrawal also cancels pending Google outcome delivery for the current session; already recorded events expire under the retention policy.

Paid-ad questionnaire

The dedicated questionnaire collects first and last name, work email, company, job title, an optional phone number, and four broad business-fit answers. A necessary first-party session cookie lasts up to 24 hours; a confirmation cookie lasts 30 minutes and prevents direct thank-you visits from being treated as submissions. A 30-day first-party cookie keeps the headline assignment consistent.

Questionnaire analytics and advertising have separate, optional choices. With permission, approved campaign tags and advertising click identifiers (fbclid or gclid) are stored separately from your contact fields and linked to your inquiry for CRM attribution. When configured and approved, Meta and Google receive limited view, progress and confirmed-conversion events, an opaque event identifier, and permitted browser/click identifiers. They do not receive your contact fields, questionnaire answers, or legal details. Automatic advanced matching and personalized-ad signals are not enabled by this implementation. Advertising is currently disabled pending account connection and approval. Use Privacy choices on the questionnaire to withdraw; this stops subsequent collection and cancels its pending provider deliveries. Previously received provider events are subject to that provider’s controls and retention.

Offer experiment assignments

The engagement-model comparison uses a first-party assignment cookie for up to 90 days. With analytics permission, offer impressions, selected offers, qualified consultations, and recorded revenue are attributed to the displayed section version. An offer selection also accompanies your request so the team can review the scope you chose, even when optional analytics are declined.

Experimental offer routes use a first-party, HTTP-only assignment cookie for up to 90 days to keep the same offer on repeat visits. The server stores a keyed browser identifier and a frozen offer snapshot. Optional analytics attach allowlisted campaign/source tags and a mobile/desktop category only with your permission. They record completion and business-fit status, not questionnaire answers. Approved bookings, payments, and costs may be joined to consented offer cohorts for profit reporting. Preview traffic is reported separately. Changing your privacy choice stops new measurement; existing consented records expire under retention or can be handled through a privacy request.

Team video and hero experiment

The main page compares a technical visualization, a team film, and a team portrait. The server stores an anonymous keyed assignment and the exact media revision. With analytics permission, it records video starts, unique watched milestones, video consultation clicks, and source/device categories. Qualified consultation requests and recorded paid assessments may be joined to the assigned hero. Preview visits remain separate from live test results. The static poster does not report video playback.

Video is click-to-play. YouTube or Vimeo loads only when you press play; doing so shares connection data with that provider, even if site analytics are declined. Internally hosted video does not load a third-party player. Captions and a full transcript accompany approved films. No third-party video is currently configured.

Service providers and follow-ups

CRM and educational email adapters are disabled until the operator configures approved providers. When enabled, the CRM receives business contact details, qualification answers, consent, and permitted attribution. The email provider receives an email address and an educational template only if you separately opt in. The website is hosted on Amazon Web Services. No CRM or educational-email provider is currently connected. Production providers, transfer arrangements, and unsubscribe mechanisms require disclosure and review before activation.

Retention and your choices

The configured retention job removes leads after 90 days and analytics main-site events after 30 days. Acquisition sessions, linked outcome measurements, experiment assignments, and cohort events are retained for up to 90 days, subject to the same scheduled retention job. On the AWS deployment, retention runs daily. Daily database backups are retained for seven days, so deleted records may remain in a restricted backup during that period. For access, correction, deletion, or withdrawal requests, use the business contact channel provided to you by the site operator. Include your request reference where available; do not include confidential evidence. Authorized operators can delete a record or revoke educational-email consent in the administration interface.

Technical safeguards and limits

The application uses validation, request-size limits, submission throttling, encryption, and restricted administrative access. These controls are not a security certification or an assurance of prospective-client confidentiality. Substantive evidence handling must use a separately approved workflow after conflict screening.