Privacy Policy
Last updated: November 3, 2026
1. Introduction
Welcome to IT Architecture Patterns. We are committed to protecting your personal information and your right to privacy. This Privacy Policy explains how we collect, use, and safeguard your data when you visit our website.
2. Advertising
This website does not show advertisements at present and loads no advertising code. We may add advertising in future; if we do, this page will be updated to describe it, and any cookies it uses, before any advertising starts.
If we add advertising, we plan to use Google AdSense. Google and its partners would then use cookies, including advertising cookies, to show ads based on your visits to this site and to other sites on the Internet. Where the law requires your consent, we will ask for it through a consent banner before advertising starts and before any advertising cookies are set. Before advertising starts, this page will also name the advertising vendors then used.
Controlling personalized advertising on other sites:
- You can opt out of personalized Google advertising by visiting the Google Ads Settings page.
- Alternatively, you can opt out of a third-party vendor's use of cookies for personalized advertising by visiting the Digital Advertising Alliance's YourAdChoices portal.
3. Information We Collect
We may collect certain technical information automatically when you visit our site, such as your browser type, device details, and operating system. Your IP address is also received with each request, by our hosting service and by the other services our pages load: Google (Google Analytics; Firebase, which serves some of the site's content and images; and, on some browsers, the scripts for Firebase sign-in) and, on the tool pages, cdnjs.cloudflare.com (the Reference Architecture Builder's html2canvas and jsPDF libraries) and cdn.jsdelivr.net (the Integration Contract Record (ICR) Builder's Mermaid library, if you draw a diagram). If you choose to log in using Google OAuth (sign-in is meant for the site's administrators), we authenticate your identity via Firebase Auth, which collects your email address and profile photo. Section 5 describes what Google Analytics collects. If you send a message with the contact form, section 6 describes what is kept and who receives it.
4. Cookies and Tracking
This site sets no cookies of its own. Your browser's local storage keeps your light/dark mode choice, your answers in the Integration Decision Framework, and your work in the Reference Architecture Builder and the Integration Contract Record (ICR) Builder tools; they stay in your browser and are not sent to the site. Firebase's code keeps two small IndexedDB stores in your browser: one for sign-in, which stays empty unless someone signs in (sign-in is meant for the site's administrators) and then holds the signed-in account's details and sign-in tokens until sign-out; and one that records the date and the versions of Firebase the site uses and is sent with Firebase's sign-in requests. Google Analytics sets cookies, which section 5 describes.
5. Usage Analytics and Google Analytics
We use Google Analytics 4, a web analytics service provided by Google, to count how the site is used: which pages are viewed, and whether the tools, templates and worked example are used. The Google Analytics tag loads for every visitor on the site's pages (the interactive tools opened from the Tools page do not load it). This site does not show a consent banner, so the tag runs unless you block it (see your choices below).
What Google Analytics receives for each page you view:
- The address of the page, including any query string. Google Analytics is set to remove the search words (the
qparameter that the pattern and template search puts in the address) from the address before it is sent, and from the address of the page you came from. - The title of the page, and the page you came from.
- Technical details about your visit, such as your browser and your approximate location.
- Your IP address. Google receives your IP address to provide the service and uses it to estimate your approximate location; Google states that Google Analytics 4 does not log or store IP addresses (see Google's help pages IP masking and Usage of IP address for non-EU, non-Switzerland, or non-UK users).
Events this site sends, in addition to page views:
- A tool is opened: which tool, and which page the link was on.
- A template is downloaded: which template, whether as Markdown or Word, and whether it was the blank template or the worked example.
- A template is copied: which template.
- The Appointment Booking worked example is viewed.
- A link from the worked example to one of its records is followed: which kind of record it was, such as a decision record, a requirement or the demo.
These five events carry no name, email address or free text that you typed.
Google Analytics also records some things on its own, without any code of this site: a page view each time a page loads or its address changes (including when you search or filter the patterns and templates), the start of a visit and a first visit, and how long a page is open in the foreground. It is set to record no other interactions on its own; the site owner can change that setting in the Google Analytics account.
Google Analytics uses cookies, named _ga and _ga_<id>, to tell visitors and their visits apart, and to recognise a browser that returns. The site owner's Google Analytics account sets how long detailed, event-level data is kept; summary reports built from it, such as page views by page address, are not affected by that setting. Where the law requires a legal basis for this processing, we rely on our legitimate interest in understanding and improving how the site is used. Google's use of the information is described in Google's Privacy Policy and in How Google uses information from sites or apps that use our services.
Your choices:
- Install the Google Analytics opt-out browser add-on, which stops the tag from sending data to Google Analytics.
- Use your browser's settings to block or delete cookies, or block the Google Analytics tag with the browser's tracking protection or a content blocker.
- The pages and tools of this site continue to work when Google Analytics is blocked.
6. The Contact Form
The Contact Us page has a form for questions, feedback and contributions. Nothing you type in it is sent until you submit it.
When you send a message with the form:
- What is collected: the name, email address, inquiry category and message you enter, and the time it is sent. The IP address the message was sent from is not stored. Instead, a keyed hash of the date and that address (for an IPv6 address, of its first half, the /64 network prefix) is stored with the message: it is made with a secret key, so it cannot be matched back to an address without that key, and the same address gives a different hash each day. It is used only to limit how many messages can be sent from one connection in a day.
- Where it is stored: in the site's Firebase database (Google Cloud Firestore), where it is not publicly readable. The form sends your message to a Google Cloud Function (part of Firebase), which stores it and sends the email.
- Who receives it: the site owner. A copy is sent by email through Gmail, Google's email service, to the site owner's Gmail mailbox, with your email address as the address to reply to.
- How long it is kept: the stored message is deleted automatically about 12 months after it is received. The site owner deletes the emailed copy, including the copy Gmail keeps in the Sent Mail of the account that sends it, within about 13 months of receipt.
7. Policy Updates
We may update this Privacy Policy from time to time. The updated version will be indicated by an updated "Last updated" date at the top of this page. We encourage you to review this Privacy Policy periodically to stay informed of how we are protecting your information.
8. Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us or visit our homepage at IT Architecture Patterns.