Skip to content
IronMemo

Legal

Cookie Policy

Last updated
October 11, 2026
Version
4.16
Product
IronMemo
Operator
OXFORD CONSTRUCTION LLC
Contact

In short. IronMemo uses Strictly Necessary technologies to operate and protect the service. The optional ones are Analytics (Google Analytics 4 and Yandex Metrica, including session replay) and Advertising (Google Ads conversion measurement). What runs before you answer the banner depends on where you are (section 5). In the EEA, the United Kingdom, Switzerland and Quebec nothing optional runs until you choose Accept All, even after an ad click. In the United States, Canada (except Quebec), Mexico and Japan the Google Analytics and Google Ads cookies are on by default. Everywhere else Google Analytics is on by default, and the Google Ads cookies are on for a visit that arrives through a Google Ads, Yandex Direct, Meta Ads or Microsoft Ads click. Outside the EEA, the United Kingdom, Switzerland and Quebec, a visit through one of these ad clicks also gets IronMemo's own attribution cookie ironmemo_attr (the click identifier and the landing time only). Yandex Metrica loads only after Accept All, in every region. Reject Non-Essential turns everything optional off and deletes the optional cookies IronMemo can reach; the Global Privacy Control signal is treated as a refusal (section 10). The Cookie settings link at the bottom of every page reopens the banner, so you can change your answer at any time. The application at app.ironmemo.com writes its separate ironmemo_attr_app cookie only after Accept All.

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 or, where the regional default in section 5 turns them on, until the visitor refuses; 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; Google Analytics is also on by default outside the EEA, the United Kingdom, Switzerland and Quebec (section 5).
  3. Advertising - helps measure advertising performance and conversions (Google Ads). Enabled by Accept All; also on by default in the United States, Canada (except Quebec), Mexico and Japan, and for paid-ad landings elsewhere outside the EEA, the United Kingdom, Switzerland and Quebec (section 5).

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; if one ships, this Policy will be updated first. The Cookie settings link at the bottom of every page reopens the banner, so the choice can be changed or withdrawn at any time (section 10). 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. What they may store before you answer the banner depends on the region Google derives from your IP address:

  • EEA, United Kingdom, Switzerland and Quebec (including the EU outermost regions that have their own country codes): all four consent signals (ad_storage, ad_user_data, ad_personalization, analytics_storage) stay denied until Accept All. The tags set no cookies, read none and send only cookieless technical pings. A visit from a paid ad is no exception, and IronMemo does not write ironmemo_attr there before Accept All (section 7).
  • United States, Canada (except Quebec), Mexico and Japan: all four signals are granted by default, so the Google Analytics and Google Ads cookies in the table are set before you answer. Reject Non-Essential, the Cookie settings link and Global Privacy Control turn them off (section 10).
  • Everywhere else: analytics_storage is granted by default, so the Google Analytics cookies are set; the three advertising signals stay denied except under the paid-landing exception below.

Paid-landing exception (outside the EEA, the United Kingdom, Switzerland and Quebec only): a visit identified by a gclid, gbraid, wbraid, yclid, fbclid or msclkid URL parameter, or by an ad-click cookie (_gcl_aw, _gcl_gb, _yclid) set earlier, gets the three advertising signals granted on landing, so _gcl_aw, _gcl_gb and _yclid can be written and the Google Ads conversion ping can attribute the click. On the same landing IronMemo writes its own first-party HttpOnly attribution cookie ironmemo_attr from the server response (section 7 describes the payload and section 8 lists the row). The exception never applies after a recorded Reject Non-Essential or with Global Privacy Control. In every region the banner is still shown: Accept All grants all four signals and Reject Non-Essential denies all four, for the rest of the visit and forward; a Reject is itself recorded through a cookieless ping. Yandex Metrica is not loaded at all until Accept All, in every region; 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

Where Analytics or Advertising is enabled - after Accept All, or by the regional default in section 5 - the 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 Consent Mode v2 together with the other Google tags. Its cookies (_gcl_aw, _gcl_gb, _gcl_au) activate after Accept All; before an answer they are on by default in the United States, Canada (except Quebec), Mexico and Japan, and, elsewhere outside the EEA, the United Kingdom, Switzerland and Quebec, from a landing on a Google Ads, Yandex Direct, Meta Ads or Microsoft Ads click (section 5), so the conversion can be attributed to that click. In the EEA, the United Kingdom, Switzerland and Quebec they activate only after Accept All. Reject Non-Essential turns them off in every region.

IronMemo additionally writes its own first-party HttpOnly attribution cookie ironmemo_attr from the server response on the same paid-ad landings. The cookie value is a base64url-encoded JSON payload containing only three fields: the click identifier itself, which URL parameter carried it (gclid, gbraid, wbraid, yclid, fbclid or msclkid) and the Unix timestamp of the landing. It does not contain a name, email, account identifier, workspace or meeting identifier, IP address, page URL, referrer, browsing history or Customer Content. The server decides from the visitor's country and region, which IronMemo's hosting provider (Vercel) derives from the IP address of the request: the cookie is written outside the EEA, the United Kingdom, Switzerland and Quebec, and inside them only when Accept All was recorded before the landing; when the location cannot be determined, it is not written. It is never written after a recorded Reject Non-Essential or with Global Privacy Control. Because the cookie is set by the server, HttpOnly and first-party, it is not visible to client JavaScript, is not removed by Safari's 7-day storage cap on client-set cookies, and is not affected by ad-blockers that suppress third-party analytics scripts. Its retention is 90 days, aligned with the Google Ads default lookback window. IronMemo may use it to reconstruct a paid conversion server-side (for example, when the visitor registers or subscribes after the browser has already discarded the client-side ad cookies), sending only the identifier to the applicable ad platform’s offline conversion API. IronMemo deletes an ironmemo_attr cookie already present on the next request to the website after a Reject Non-Essential, with Global Privacy Control, and for a visitor in the EEA, the United Kingdom, Switzerland and Quebec who has not chosen Accept All (such a cookie may have been written there before October 11, 2026). The cookie is listed in section 8.

The IronMemo application at app.ironmemo.com writes a separate first-party JavaScript cookie ironmemo_attr_app after the visitor chooses Accept All. Its payload is a URL-encoded JSON containing the paid-click identifier and its kind (one of gclid, gbraid, wbraid, yclid, fbclid or ttclid), UTM campaign parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) and the ISO-8601 capture timestamp. It does not contain a name, email, account or meeting identifier, IP address, page URL, referrer or Customer Content. The cookie is scoped to .ironmemo.com, has a 90-day retention aligned with the ad-platform lookback window, and is not HttpOnly (it is readable by the application’s own JavaScript to reconstruct attribution across page loads). Unlike ironmemo_attr, it is never written before Accept All — it follows the standard consent path. Choosing Reject Non-Essential on the website deletes it. The cookie is listed in section 8.

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 where Advertising is enabled: after Accept All, or by the regional default in section 5 until the visitor refuses.

A transmission for retargeting or cross-context behavioral advertising may qualify as a sharing of personal information in certain jurisdictions. In the United States, Canada (except Quebec), Mexico and Japan, and on paid-ad landings elsewhere outside the EEA, the United Kingdom, Switzerland and Quebec, such a transmission may take place before the visitor answers, under the default described in section 5, until they refuse with Reject Non-Essential, the Cookie settings link or Global Privacy Control. In the EEA, the United Kingdom, Switzerland and Quebec IronMemo does not make it before Accept All. IronMemo 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 Consent Mode v2. Which Google cookies appear before an answer depends on the region (section 5): none in the EEA, the United Kingdom, Switzerland and Quebec; the Google Analytics and Google Ads cookies in the United States, Canada (except Quebec), Mexico and Japan; elsewhere the Google Analytics cookies, plus the Google Ads cookies (_gcl_aw, _gcl_gb, _gcl_au) on landings that carry a paid-ad click identifier. After Accept All all of them may appear. 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 - disables both, including what the regional default in section 5 had turned on.

Both buttons appear in the banner itself, in the same bar, with the same height and font size: Reject Non-Essential at its left edge, Accept All on the right, so refusing takes one click, just like accepting. There is no per-category switch; if one ships, this Policy will be updated first.

Cookie settings. A Cookie settings link at the bottom of every page of the website reopens the banner at any time, whatever was answered before, so a choice can be changed or withdrawn in two clicks. Withdrawal applies going forward and does not affect processing performed before it. Clearing this site's cookies and site data in the browser (section 11) also resets the choice; for a choice saved before 2026-08-28, clear the site data and not only the cookie, otherwise the legacy localStorage answer restores it.

Choosing Reject Non-Essential - on the first visit or later through Cookie settings - sets all four Consent Mode signals to denied and deletes the Google and Yandex cookies on .ironmemo.com that the page can reach (_ga, _ga_L3Z599N22R, _gcl_au, _gcl_aw, _gcl_gb, _yclid, _ym_uid, _ym_d, _ym_isad, _ym_visorc), together with the application's ironmemo_attr_app; IronMemo's server deletes ironmemo_attr on the next request. If Yandex Metrica was running because Accept All had been chosen, the page reloads so that the recording stops at once. Cookies controlled by another domain, such as Yandex's receive-cookie-deprecation on .yandex.com, cannot be removed by IronMemo.

Browser privacy signals

IronMemo honours Global Privacy Control. When a browser or an extension sends the GPC signal (the Sec-GPC: 1 request header, or navigator.globalPrivacyControl set to true), IronMemo treats it exactly as Reject Non-Essential: all four Consent Mode signals stay denied, the paid-ad landing exception in sections 5 and 7 does not apply and no ironmemo_attr cookie is written (one already present is deleted), Yandex Metrica is not loaded, and the banner does not ask again. The choice is recorded as a rejection, and separately marked as having come from the signal rather than from a click, so that the two are never confused. A visitor who later opens the banner through Cookie settings and chooses Accept All overrides the signal for this site: an explicit, informed choice made afterwards is the one we follow. Do Not Track is still not interpreted, because it carries no agreed legal meaning.

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.

Besides the Cookie settings link (section 10), browser-level cookie and site-data management can 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.16 - October 11, 2026: the summary now says that IronMemo's attribution cookie ironmemo_attr is also written in the United States, Canada (except Quebec), Mexico and Japan, as section 7 already said; it had named the cookie only for the other regions outside the EEA, the United Kingdom, Switzerland and Quebec. Nothing changes in what runs, so no new consent event is triggered.
  • 4.15 - October 11, 2026: the summary and sections 1, 2, 4-11 now describe the regional defaults in force since September 28, 2026 (ADR 0026), which the Policy still described as denied everywhere: nothing optional before Accept All in the EEA, the United Kingdom, Switzerland and Quebec; Google Analytics and Google Ads cookies by default in the United States, Canada (except Quebec), Mexico and Japan; Google Analytics by default elsewhere. The paid-landing exception and the ironmemo_attr cookie no longer apply in the EEA, the United Kingdom, Switzerland and Quebec, where they now need Accept All, and IronMemo deletes an ironmemo_attr written there earlier. A Cookie settings link at the bottom of every page reopens the banner; Reject Non-Essential now deletes the Google and Yandex cookies the page can reach and, after an earlier Accept All, reloads the page. The ironmemo-consent-source storage key is added to the table. No new provider, purpose or category, and nothing widens what Accept All covers, so no new consent event is triggered. Rationale in ADR 0031.
  • 4.14 - October 5, 2026: section 10 now describes the banner layout: Reject Non-Essential at the left edge of the bar, Accept All on the right, both in the banner itself, with the same height and font size. No new cookie, provider, category, purpose or consent mechanism is introduced. No new consent event is triggered.
  • 4.13 - September 28, 2026: a new first-party JavaScript cookie ironmemo_attr_app is disclosed in section 7 and added to the table in section 8. It is written by app.ironmemo.com only after Accept All and carries the paid-click identifier, its kind, UTM campaign parameters and the capture timestamp; no personal data, IP address, page URL, referrer or Customer Content. Retention 90 days. No new provider, category, purpose or consent mechanism is introduced; the cookie is activated only when the visitor has already accepted. Section 4 (Summary) updated. No new consent event is triggered.
  • 4.12 - September 23, 2026: the paid-landing exception and the first-party ironmemo_attr attribution cookie now recognize Meta Ads (fbclid) and Microsoft Ads (msclkid) click identifiers alongside the existing Google Ads and Yandex Direct parameters. No new advertising pixel, script, provider or cookie category is introduced: IronMemo does not load Meta or Microsoft tracking scripts. The change extends only the list of URL parameters that trigger the existing consent exception and the existing ironmemo_attr server-side cookie. The _gcl_au cookie activation description in section 8 is corrected to reflect that it is also set when the paid-landing exception grants ad storage, matching the disclosure already present for _gcl_aw and _gcl_gb. No new consent event is triggered. Rationale in ADR 0025.
  • 4.11 - September 19, 2026: Global Privacy Control is now honoured as Reject Non-Essential, replacing the section 10 paragraph that said the signal was not interpreted. The signal suppresses the paid-ad landing exception and the ironmemo_attr cookie, keeps Yandex Metrica unloaded and stops the banner from asking; an explicit Accept All afterwards still overrides it. No new provider, cookie, category or purpose. Rationale in ADR 0023.
  • 4.10 - September 12, 2026: the cookie registry in section 8 is corrected to list the three third-party click-identifier cookies (_gcl_aw, _gcl_gb and _yclid) as individual rows. Sections 7 and 9 already named these cookies verbatim and disclosed their purpose, retention and activation rules; the v4.8 changelog also stated they appeared in the table, but they did not - only the Google Analytics conversion linker _gcl_au was listed. This release closes that disclosure gap without adding a new provider, category, purpose or technology; the cookies were already covered by section 7's Google/Yandex disclosure and by the v4.8 activation logic. No new consent event is triggered. Rationale in ADR 0019.
  • 4.9 - September 12, 2026: the paid-landing exception is extended with a new first-party HttpOnly attribution cookie ironmemo_attr, written by IronMemo from the server response on the same paid-ad landings covered by v4.8. Its value is a base64url-encoded JSON with only three fields (click identifier, source parameter name and landing timestamp) - no personal data, page URL, referrer or Customer Content. It is set only when a gclid, gbraid, wbraid, yclid, fbclid or msclkid URL parameter is present and the visitor has not chosen Reject Non-Essential. Retention 90 days, aligned with the Google Ads default lookback window. Rationale in ADR 0018. Sections 4 (Summary), 5 (Activation), 7 (Advertising) and 8 (Table) updated; the cookie is added as a new row in the table. Reject Non-Essential does not delete cookies already written but stops new ironmemo_attr cookies going forward, mirroring how the v4.8 exception handles _gcl_aw.
  • 4.8 - September 11, 2026: paid-landing exception disclosed. A visitor arriving through a Google Ads or Yandex Direct click identifier (gclid, gbraid, wbraid or yclid URL parameter) is served a three-signal ad-measurement grant on landing so the conversion can be attributed to the paid click; analytics_storage and Yandex Metrica are not covered by the exception, the banner is still shown, and Reject downgrades the state to fully denied. Rationale in ADR 0017. Sections 4 (Summary), 5 (Activation), 7 (Advertising) and 9 (Google) updated to describe the exception. The row-by-row cookie registry in section 8 was intended to be unchanged, but the entry stated _gcl_aw, _gcl_gb and _yclid already appeared as individual rows when in fact only _gcl_au was listed; that disclosure gap is closed in v4.10.
  • 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

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