Skip to content
IronMemo

Legal

Cookie Policy

Last updated
August 28, 2026
Version
4.7
Product
IronMemo
Operator
OXFORD CONSTRUCTION LLC
Contact
info@ironmemo.com

In short. IronMemo uses Strictly Necessary technologies to operate and protect the service. The consent banner offers a single choice: Accept All enables Google Analytics 4, Google Ads conversion measurement and Yandex Metrica (including session replay); Reject Non-Essential leaves them disabled. Google Tag Manager and the Google tags load before the choice in a cookieless mode (Google Consent Mode v2) and set no cookies until you accept; Yandex Metrica does not load at all until you accept.

This summary is provided for convenience and does not replace the full Policy below.

1

Scope

This Policy applies to all pages of:

  • ironmemo.com;
  • app.ironmemo.com;
  • other IronMemo subdomains that link to this Policy.

The consent architecture has no page-level exceptions. Optional cookies and storage are used only to the extent disclosed in the current table and only after the applicable consent; the cookieless pre-consent behaviour of the Google tags is described in section 5.

Similar technologies may include cookies, local storage, session storage, pixels, tags and software components that store information on, or access information from, a user’s device.

This Policy supplements the Privacy Policy, Terms of Service and Data Processing Agreement. Those documents address account data, recordings, transcripts, summaries, tasks and other service data.

2

Consent categories

IronMemo uses one category model in the banner, this Policy, the Privacy Policy and the technical registry:

  1. Strictly Necessary - required to operate, secure and remember choices for the service. These technologies do not depend on the banner answer.
  2. Analytics - helps us understand how the website is used (Google Analytics 4, Yandex Metrica). Enabled by Accept All.
  3. Advertising - helps measure advertising performance and conversions (Google Ads). Enabled by Accept All.

The banner offers a single binary choice: Accept All enables both optional categories together, Reject Non-Essential disables both. There is no per-category switch and no separate Cookie Settings panel today; if one ships, this Policy will be updated first. The model does not use separate Functional, Preference or Marketing categories: a technology that stores a requested language or interface preference is Strictly Necessary and listed in the table below.

3

Strictly Necessary technologies

Strictly Necessary technologies may be used to:

  • maintain and protect a user session;
  • provide account sign-in;
  • protect forms, authorization and the service against fraud or abuse;
  • complete a payment requested by the user;
  • remember the cookie banner choice;
  • support technically necessary authorization when connecting integrations.

They operate without optional consent only to the extent necessary for a requested function or service security.

5

Analytics

IronMemo measures website use with Google Analytics 4 (through Google Tag Manager) and Yandex Metrica.

Analytics may be used to understand:

  • which public pages are opened;
  • how visitors reach the website;
  • which devices and browsers are used;
  • how visitors interact with public pages;
  • where technical or interface difficulties occur.

The two providers activate differently. Google Tag Manager and the Google tags load on every page in Google Consent Mode v2 with all storage denied by default: before (or without) consent they set no cookies and read none, and send only cookieless technical pings; after Accept All the consent state switches to granted and the cookies in the table below appear. Choosing Reject Non-Essential is likewise recorded through a cookieless ping. Yandex Metrica is not loaded at all until Accept All; after it, the Metrica script activates with click mapping and session replay (Webvisor) enabled - it records page interactions, including text typed into forms on the public website.

IronMemo configures Google Analytics so that it does not receive:

  • meeting names or meeting identifiers;
  • participant names or email addresses;
  • recording, transcript, summary or task content;
  • user, workspace or organization identifiers;
  • search terms entered against Customer Content;
  • OAuth codes, tokens or other secrets;
  • sensitive URL paths, query strings or fragments.

One exception applies to the list above: after Accept All, Yandex Webvisor records text typed into forms on the public website (section 5) - including a name or email address a visitor chooses to type there.

6

Information that may be processed

After the applicable consent, Analytics or Advertising providers may process:

  • cookie, browser or device identifiers;
  • IP address and approximate country or region derived from it;
  • browser, device type, operating system, language and timezone;
  • sanitized page URL, page title and referrer;
  • timestamps, session information and interaction events;
  • advertising click identifiers and campaign attribution parameters;
  • whether a disclosed conversion event occurred.

IronMemo sanitizes the page information it sends to Google (URLs, titles, referrers) so that it does not reveal Customer Content or private application identifiers. That sanitization cannot apply to Yandex Webvisor, which records form input on the public website verbatim after Accept All (section 5).

After Accept All, session replay and click mapping ARE active through Yandex Metrica (see section 5). IronMemo does not use Meta, LinkedIn or TikTok advertising pixels. A new tracking technology may not be introduced without being added to the table, disclosed in this Policy and subjected to the applicable consent.

7

Advertising

Google Ads conversion measurement loads on every page in cookieless Consent Mode v2 together with the other Google tags; it stores nothing and reads nothing until Accept All, after which the conversion cookie (_gcl_au) activates.

Advertising technologies may be used to measure which advertisements lead to registrations or other conversions identified in the current registry.

IronMemo does not sell personal information or provide it to data brokers.

Retargeting or personalized advertising may be used only when it is:

  1. enabled in the production configuration;
  2. expressly disclosed in the current table; and
  3. activated only after Advertising consent.

A transmission for retargeting or cross-context behavioral advertising may qualify as a sharing of personal information in certain jurisdictions. IronMemo does not make that transmission before Advertising consent and does not receive payment for it.

9

Third-party providers

Google

Google provides Google Analytics 4, Google Ads and Google Tag Manager. The container and the Google tags load on every page in cookieless Consent Mode v2; Google-set cookies appear only after Accept All. Google may process the related information in the United States and other countries.

Yandex

Yandex provides Yandex Metrica, the visitor analytics used on the public website. The Metrica script loads only after Accept All, with click mapping and session replay (Webvisor) enabled. The collected information (section 6) may be processed by Yandex in the Russian Federation, which does not hold an EU adequacy decision. Metrica cookies are listed in the table above. By choosing Accept All you consent to this recording and to the processing of the related information in the Russian Federation, where EU-equivalent privacy safeguards and remedies may not be available. Yandex also offers a public browser extension (the Yandex Metrica blocker) that stops Metrica collection on any website.

Stripe

IronMemo currently uses Stripe for payment processing. Stripe acts as an independent controller for payment data. Technologies placed by Stripe during checkout may be necessary to complete a requested transaction and prevent fraud. Their exact names and retention periods must be listed after the production checkout scan.

Support and feedback providers

A support or feedback provider may be loaded in the browser only if it appears in the registry and the Subprocessors page, or if the provider is accessed through IronMemo’s own backend without placing browser storage. Optional embedded widgets require the applicable consent.

The current Subprocessors information is available at /subprocessors.

10

Your choices and withdrawal

On the first visit, the consent banner offers:

  • Accept All - enables Analytics and Advertising together;
  • Reject Non-Essential - leaves both disabled.

Both controls sit side by side in the banner and are equally prominent. There is no per-category switch and no persistent Cookie Settings panel today; if one ships, this Policy will be updated first.

To change or withdraw a recorded choice, clear this site's cookies and site data in the browser (see section 11) and reload the page - the banner will ask again. Clearing site data matters for visits from before 2026-08-28: deleting only the cookie lets the legacy localStorage answer restore it silently. Withdrawal applies going forward and does not affect processing performed before it.

A visitor who clears the site data and answers Reject Non-Essential on the reloaded page gets the Google tags initialized in their default denied state. IronMemo does not currently remove first-party analytics cookies that were set while consent was granted - they expire on their own schedule (see the table) or when site data is cleared; third-party and HttpOnly cookies controlled by another domain cannot be removed by IronMemo at all.

Browser privacy signals

IronMemo does not currently interpret Global Privacy Control (Sec-GPC) or Do Not Track as a consent choice: the banner is the only consent mechanism. If GPC support ships, this Policy will be updated.

11

Browser controls

Browsers allow users to block or delete cookies and other site data. Blocking Strictly Necessary technologies may prevent sign-in, security, checkout or other requested functions from working.

Deleting the consent cookie removes the saved choice and may cause the banner to appear again.

Because IronMemo does not currently provide an on-site Cookie Settings panel, browser-level cookie and site-data management is the only way to clear a saved choice.

12

International processing

Google, Stripe and other providers listed in the current table may process related information outside the user’s country, including in the United States.

Applicable transfer mechanisms and further information are described in the Privacy Policy, Data Processing Agreement and /subprocessors. This Policy does not maintain a separate infrastructure map.

13

Changes and renewed consent

IronMemo may update this Policy when technologies, providers, purposes or legal requirements change.

If a change materially expands what a recorded Accept All covers, IronMemo will reset the stored consent cookie, and the banner will ask every returning visitor again. The cookie stores no version number, so this reset is the mechanism by which renewed consent is obtained.

A reset (and so a renewed request) is triggered by:

  • a new optional category;
  • a new Analytics or Advertising provider;
  • a new processing purpose;
  • retargeting or personalized advertising;
  • a material expansion of information collected;
  • a material change to the consent mechanism.

Editorial corrections, formatting changes and contact updates that do not change technologies, providers, categories, purposes or information collected may change the published Policy version without triggering renewed consent.

14

Version history

  • 4.7 - August 28, 2026: wording corrections after an external review of v4.6, published the same day: the Google Ads paragraph states that the tags load pre-consent in cookieless mode; the Google Analytics exclusion list names its one Webvisor exception; the change-management section drops a versioning mechanism that was never implemented and describes the consent-cookie reset instead; withdrawal instructions cover site data, not just the cookie, because a legacy localStorage answer could silently restore a deleted cookie; the Yandex section adds the consent acknowledgement, the Russian-Federation risk note and the Metrica opt-out extension notice; the browser-controls section stops referring to a Cookie Settings panel.
  • 4.6 - August 28, 2026: the Policy is corrected to describe the shipped consent implementation: a single Accept All / Reject Non-Essential choice with no per-category Cookie Settings; Google tags loading pre-consent in cookieless Consent Mode v2 (advanced implementation), with the rejection itself recorded through a cookieless ping; Yandex Metrica disclosed as an Analytics provider, activated only after Accept All, with click mapping and session replay (Webvisor) enabled; the cookie table expanded from one row to the full first-party and third-party registry, with the consent cookie named correctly (ironmemo_consent, 180 days); the Global Privacy Control support claim removed - the signal is not currently interpreted.
  • 4.5 — August 6, 2026: restored the banner disclosure, information-collection disclosure and GPC section; separated document versioning from consent-relevant versioning; removed mandatory reload on withdrawal.
  • 4.4 — August 1, 2026: internal release candidate; not published to production.
  • 4.3 — August 1, 2026: internal draft; not published to production.
  • 4.2 — August 1, 2026: internal draft; not published to production.
  • 4.1 — July 31, 2026: internal draft; not published to production.
  • 4.0 — July 25, 2026: internal draft; not published to production.
15

Contact

IronMemo

A product operated by OXFORD CONSTRUCTION LLC

info@ironmemo.com

The English version controls in the event of an inconsistency between the English version and any translation.