Cookie Policy

Avernic uses strictly necessary first-party cookies or similar browser technologies for functions such as:

• security and submission integrity;
• private report or plan access;
• recovery and delivery access;
• intake, session, and purchase continuity;
• requested browser-local progress; and
• remembering your privacy choice.

These technologies are separate from optional Analytics. Blocking essential technologies may interrupt a requested journey, erase local progress, or make private access unavailable.

Avernic stores one strictly necessary, first-party privacy-preference cookie for up to 180 days.

The preference contains:

• a format version;
• the explicit Analytics choice; and
• for an affirmative choice, the applicable legal-bundle version.

It contains no customer, device, journey, session, or event identifier. Rejecting Analytics does not disable essential product functionality. Saving a later choice replaces the earlier preference.

Optional Analytics measures a small, closed set of public acquisition and funnel steps. Avernic sends approved events through its server to HeyCatch, Inc. HeyCatch identifies PostHog US Cloud as a subprocessor for SDK analytics processing.

The approved event data may contain:

• a closed public-funnel event name;
• a purpose-separated HMAC-derived pseudonymous journey identifier;
• a stable public page or stage identifier;
• coarse device, browser, operating-system, viewport, acquisition, elapsed-time, and validation-reason buckets; and
• normalized, length-limited UTM source, medium, and campaign values when present.

It excludes questionnaire answers and labels, form values, free text, DOM and click text, email, name, address, raw URLs and referrers, exact IP address as an event property, full user-agent string as an event property, database IDs, Stripe objects, order or payment IDs, report or plan references, access tokens, private-link fragments, support content, and operator content.

Ordinary network transport may expose routine request metadata, such as an IP address and server transport user-agent information, to receiving infrastructure. HeyCatch code does not run in the browser. This integration creates no HeyCatch browser cookie, local-storage identity, autocapture, or session replay.

Private intake, result, report, access, recovery, delivery, support, API, Ops, QA, email-management, and any other non-allowlisted route is excluded. Payment confirmation, report generation, delivery, private-plan access, and refund events are not currently sent.

Analytics is off by default.

Use Privacy choices to:

• Accept All;
• Reject Optional;
• turn the Analytics category on or off;
• save the choice; and
• reopen the same control later to withdraw.

Withdrawal immediately blocks future Analytics events and does not degrade the product. It does not by itself delete earlier provider data.

Avernic honors Global Privacy Control at the browser and server boundaries. When GPC is active, optional Analytics remains off and Accept All cannot override the signal. Avernic does not fingerprint a browser or substitute another identifier when Analytics is blocked.

The first-party preference cookie expires no later than 180 days after it is set.

HeyCatch's reviewed materials describe SDK analytics data retention for the active subscription plus two months after subscription end, followed by deletion or irreversible anonymization unless the subscription is reactivated or deletion occurs earlier.

To request access to or deletion of eligible analytics data already collected, email hello@avernicprivacy.com and state that the request concerns optional Analytics. When possible, submit the request from the same browser used for the public journey. Avernic may request proportionate verification and may be unable to link pseudonymous provider data to a person when no verified linkage exists.

Additional request rights, exceptions, and verification details are in the Privacy Policy.