Ameliaby Rothian

Cookie Policy

Last updated: November 4, 2026

This Cookie Policy explains how Rothian IT LLC (“Rothian”, “we”, “us” or “our”), which operates Amelia, uses cookies and similar technologies on amelia.always.expert, on the custom domains on which the Service is offered, and in the Service itself. It should be read with our Privacy Policy, which covers the rest of what we do with personal data, including your rights and how to contact us.

1. What these technologies are

Cookies are small text files that a website asks your browser to store. Local storage and session storage are similar browser features: local storage remains until it is cleared, and session storage ends when the tab closes. A “cookieless” measurement tool stores nothing on your device but still receives information your browser sends, such as the page address. Pixels and tracking links are small images or links in an email or web page that record when they are loaded or followed. In this policy, “cookies” includes all of these unless we say otherwise.

2. Summary

Our website sets no advertising cookies and no analytics cookies, so it does not show a cookie notice. The cookies we use are the ones needed to sign in and to use the product. Visits to our website are counted without cookies, as Section 5 explains, and that count runs for every visitor.

3. Cookies

  • Sign-in (next-auth session, CSRF and callback cookies) — keep you signed in and protect sign-in. Strictly necessary. Set by us. The session cookie lasts up to 30 days or until you sign out; the others last for the browser session. A device note, kept for up to 180 days and renewed each time you sign in, lets us recognise a browser you have signed in from.
  • Connecting an account (short-lived state cookies when you link LinkedIn, Google, Meta or WhatsApp) — check that the connection you finish is the one you started. Strictly necessary. Set by us, and removed when the connection completes or shortly afterwards.
  • Internal access (staff, investor and delivery-desk cookies) — used only by people given access to those pages. Strictly necessary for them. Set by us.
  • Preferences and review links — a sidebar preference lasts 7 days, and a password-protected review link sets a cookie for that link.

4. Local and session storage

Signed-in pages and chats keep small settings in your browser, such as your light or dark choice, a sidebar’s state, draft replies, and a marker that lets a website chat carry on where it left off. A feedback tool from Gridnimbus, on most of our pages, also keeps its drafts and status there. Our demo and questionnaire forms keep what you have typed, including your name and email, in your browser so that you can finish later, until you clear it. None of these is used for advertising, and they remain until they expire, the tab closes or you clear them.

5. How we count visits

Our own website counts page views and demo requests with PostHog, hosted in the EU, in its cookieless mode. It stores nothing on your device and makes no recording of your visit. With each it records an approximate location (country, region and town or city, worked out from your connection; your IP address is not stored) and your browser’s language. Within a day, visits from the same browser and connection are counted as one visitor, using a code worked out on PostHog’s servers. It cannot recognise you from one day to the next. We rely on our legitimate interest in understanding how our website is used.

6. On our customers’ websites and in their emails

Companies using Amelia can put the same measurement on their own websites, and can choose whether it stores an identifier in your browser. They can also send links that carry a private code, so that a visit is recorded against the person who received the link, and their campaign emails record opens and clicks. Those companies decide how this is used, and their own policies explain it. Unsubscribing from a company’s emails stops your visits being matched to you. A company’s website chat may also keep a marker in your browser so that your conversation can continue.

7. Other companies’ tools

If you connect a WhatsApp number, that page loads Meta’s own sign-in tool, which may set Meta’s cookies under Meta’s policies. We do not use a Meta or LinkedIn advertising pixel on our website. Some of our website’s pages load fonts from Google Fonts, so Google receives your connection details when they load, and some embed YouTube videos, which YouTube serves under its own policies. Links to booking pages, maps and other services take you to those companies’ own terms and policies.

8. Your choices

You can block or clear cookies and stored data in your browser, though signing in will not work without the necessary ones. Your browser’s help pages explain how. Because the count in Section 5 does not identify you, we cannot exclude one visitor on request. You can stop it by blocking scripts in your browser, or write to info@rothian.com and we will explain what is held. To stop a company’s emails, use the unsubscribe link. From a few minutes after you unsubscribe, opening or clicking an email you already have is no longer recorded against you in Amelia, although the email provider that carries it may keep its own logs.

9. Changes to this policy

We may update this Cookie Policy when the technologies we use change. We will revise the “Last updated” date above and, for material changes, give additional notice where appropriate.