Cookie notice

This website sets no cookies. Not one, of any kind, first party or third party.

It stores nothing in local storage or session storage, registers no service worker, embeds no tracking pixel, runs no analytics product, carries no advertising and contains no social media widget. There is no consent banner because there is nothing to consent to, and a banner asking permission for nothing would be theatre.

Two things still reach beyond the page and both are named in full below. Your browser requests two typefaces from Google Fonts, and the provider that hosts these files logs the request in the ordinary way that a web server must. Everything else on this page is detail, controls and the reasoning behind the position.

A cookie is a small file a website asks your browser to keep and send back on later requests. It is the oldest way of recognising a returning visitor, and the reason it attracts so much law is that recognising a visitor is the first step towards building a record of one.

The word has become shorthand for a wider set of mechanisms, and a notice that only addressed literal cookies would be answering a narrower question than the one you are asking. This notice therefore covers all of the following.

• Cookies, set by the site you are visiting or by a third party whose content it embeds.
• Local storage and session storage, which hold more data than a cookie and are not sent automatically with requests.
• IndexedDB and the Cache Storage API, used by applications that work offline.
• Service workers, which are scripts a site can install to sit between your browser and the network.
• Tracking pixels and beacons, which are requests for a tiny image or an empty response whose only purpose is to tell somebody that you loaded a page.
• Browser fingerprinting, which identifies a device from the combination of its characteristics without storing anything at all.
• Server logs, which are not on your device but do record that a request happened.

Of that list, this site uses exactly one item, and it is the last one, because a web server cannot answer a request without receiving it.

The table is the complete answer for this domain. There is nothing in it that we have chosen not to list.

The one script

This site loads a single JavaScript file, served from this domain. It does two things. It opens and closes the navigation menu on a narrow screen, and it fades sections in as you scroll past them. It makes no network request, reads and writes no storage, sets no cookie, and observes nothing about you. Blocking it leaves every page fully readable and every link reachable, which is how it was written on purpose.

This is the only third party your browser contacts while loading this site, and it is worth being precise about what it means.

The pages use two typefaces, Gabarito and Commissioner, requested from fonts.googleapis.com and fonts.gstatic.com. Making that request discloses your IP address to Google, along with the ordinary request headers your browser sends. Google states that the Google Fonts API does not set cookies and that font files are served from a cookieless domain, and our own content security policy prevents anything other than a stylesheet and a font from being loaded from those hosts. We have no visibility into what Google does with the request beyond what Google publishes.

How to stop it

• Block fonts.googleapis.com and fonts.gstatic.com in a content blocker, a hosts file or your browser settings. Every page then renders in a system typeface and nothing else changes.
• Turn off web fonts entirely in your browser if it offers that setting.
• Use the site with JavaScript disabled as well if you prefer. Both work.

We would rather self host the two files and remove the third party altogether, and that is the intended direction for this site. Until it happens, the position is described here rather than left for you to find in a network inspector.

Nothing in this section is stored on your device, but it is a record that a request happened and it belongs in a document about tracking.

These files are served by a hosting and content delivery provider. Like every web server, it records the request in order to answer it and to keep the service running. The record contains your IP address, the user agent string your browser sends, the path you asked for, the response code, and the approximate time. It is retained for the short operational window the provider applies and then discarded.

We do not export those logs, aggregate them, run reports over them or feed them into anything. There is no dashboard on our side. Their purpose is keeping the site available and absorbing abusive traffic, and both purposes are exhausted within days.

The privacy policy sets out what that means under the Australian Privacy Principles, including who holds it, why it counts as collection at all, and how long it lasts.

Australian visitors are used to seeing consent banners on Australian websites, so the absence of one here deserves an explanation rather than a shrug.

The law that produces banners is not Australian law

The banner most people recognise comes from Article 5(3) of the European ePrivacy Directive, which requires consent before storing information on, or gaining access to information stored in, a user's device, with a narrow exemption for what is strictly necessary. Australia has no equivalent provision. There is no Australian statute that requires consent merely because something is written to your browser.

What Australian law does require

The Privacy Act 1988 (Cth) applies to personal information, which is information about an identified individual or an individual who is reasonably identifiable. A cookie identifier or an IP address can be personal information depending on what else the holder can combine it with. Where it is, Australian Privacy Principle 3 governs whether it may be collected and Australian Privacy Principle 5 requires that you be told about the collection. Consent becomes necessary for sensitive information under APP 3.3, and it is good practice well before that point.

So the Australian question is not "did you get consent for the cookie", it is "did you collect personal information you did not need, and did you tell people". Our answer to the first is that we collect none, and this document plus the privacy policy is our answer to the second.

Why a banner would be worse than nothing

• It would ask for permission we do not need for a thing we do not do.
• Consent management platforms are themselves a third party that reads and writes to your device and often profiles the consent event.
• Training people to click through a permission box on a site that tracks nothing makes them faster at clicking through one on a site that tracks everything.

If this site ever sets a cookie that is not strictly necessary, or loads anything that profiles you, we will ask first, in plain words, with refusing as easy as accepting and with the site working either way.

None of this depends on our good behaviour. Your browser is the enforcement point and it outranks us.

• Block or delete cookies in your browser's privacy settings. There is nothing of ours to delete, and blocking everything breaks nothing on this site.
• Clear site data for amaraai.cc, which will empty the cache of the pages and images your browser has kept.
• Use a content blocker. Blocking the Google Fonts hosts is the only change it will make here, and the site is designed to survive it.
• Disable JavaScript. Every page remains fully readable, the navigation stays expanded rather than collapsing behind a button, and every section is visible without the scroll animation.
• Use private browsing, a VPN or Tor. We have no objection, nothing here is degraded by any of them, and we do not attempt to detect them.

Instructions for the settings above are maintained by each browser vendor and change more often than this page does, so we point at the vendor's own help rather than reproducing steps that will be wrong within a year.

Do Not Track is a header a browser can send to ask sites not to track the user across services. Most sites ignore it and it is now largely deprecated. We honour it in the only sense available to us, which is that we do not track anybody whether or not it is sent.

Global Privacy Control is a newer signal that expresses an opt out of the sale or sharing of personal information, and it has legal effect under some laws including the California Consumer Privacy Act. We honour it. Since we neither sell nor share personal information for cross context behavioural advertising, honouring it changes nothing about how this site behaves, which is the outcome you want.

Cross site tracking prevention built into your browser is welcome here and we do nothing to work around it. We do not use bounce tracking, link decoration, CNAME cloaking, first party proxying of a third party tracker, or any other technique for evading those protections.

This notice describes a static website. If this company releases a product, the picture changes and this page will change with it before the product is available rather than afterwards.

Two commitments constrain what that change could look like.

• Strictly necessary only, by default. Anything a released product stores on your device would exist to make the product work. Anything beyond that would be optional, off by default, and described here before it was switched on.
• No analytics without asking. If we ever want to know how a product is used, we will ask, we will say precisely what would be collected, and declining will not degrade the product.

What will not change is the content of your meetings. Audio, transcripts and notes are covered by the privacy policy rather than by this document, and the commitments there are stronger than anything in this one. No storage mechanism described on this page will ever be used to retain, index or transmit what was said in a meeting.

We may change this notice. The effective date and version at the top of this page change when we do.

If we ever begin setting a cookie, loading a third party that sets one, or installing anything on your device beyond the ordinary browser cache, this page will say so before it starts rather than after, and where consent is the right answer we will ask for it rather than assume it.

Questions about anything on this page go to hello@amaraai.cc. If you inspected the network traffic of this site and found something that contradicts this document, we would genuinely like to know, and we will treat that as a defect rather than an accusation.