Cookie policy

This policy explains how AMNO Group Ltd, trading as Amno Solutions (“Amno”, “we”, “us”), uses cookies and similar technologies on amnosolutions.com and the Amno Solutions platform. AMNO Group Ltd is registered in England and Wales (company number 16870880), registered office 15 The Broadway, Woodford Green, Essex, IG8 0HL, United Kingdom.

How we handle the personal data that cookies collect is explained in our privacy policy.

A cookie is a small file a website asks your browser to store and send back with later requests, so the site can tell those requests come from the same person. Similar technologies, such as local storage, tracking pixels and device fingerprinting, do comparable things. The law on cookies covers all of them, which is why section 5 of this policy describes the one thing we keep in local storage as well as the two cookies.

We use two cookies, both strictly necessary, and we set neither until you sign in. We use no analytics or advertising cookies. We do not use tracking pixels, device fingerprinting or other tracking technologies, and we load no scripts, fonts or other content from third-party servers on our pages.

The law does not require consent for cookies that are strictly necessary to provide a service you have asked for. That is why our site has no cookie banner: there is nothing to consent to. Without these two cookies you could not stay signed in or send a payment.

If we ever want to use a cookie that is not strictly necessary, we will update this policy first and give you any choice the law requires before it is set.

Both are first-party: Amno sets them, and no one else can read them.

sessionid keeps you signed in. It holds a random identifier only, with no name, company or account details. It is marked HTTP-only, so no script on any page can read it — which is what stops one being stolen and used to sign in as you. It expires after thirty minutes without activity, or when you sign out. Strictly necessary, so no consent is needed.

csrftoken protects you against cross-site request forgery. We check it on anything that changes your account, such as sending a payroll run or adding a payee, to confirm the request came from our own pages. This one is not HTTP-only: the browser has to be able to read it so our own pages can send the value back as a header, and no write in the platform would work otherwise. It is useless to anybody without your session. It lasts a year unless you clear it. Strictly necessary, so no consent is needed.

When you start an application to open an account, your browser keeps one value in local storage: the identifier of that application, under the name amno-application-id. It is what lets you close the tab part-way through and pick the application up where you left it. It holds nothing about you or your company, only the identifier, and it is cleared when you send the application in.

It is set on the application pages, before you have signed in, which is the one thing we store before sign-in. It is strictly necessary for the service you asked for, so no consent is needed for it either.

You can block or delete cookies in your browser settings, and your browser’s help pages explain how. The public pages of our site, including this policy, our terms and our privacy policy, work with cookies blocked, because we set no cookie until you sign in.

Signing in and sending payments will not work with our cookies blocked. There is no version of the platform that works without them.

Your bank account is provided by Griffin. Griffin’s own website has its own cookie policy at griffin.com/cookies.

We will update this policy before we change the cookies we use, and show the date of the latest version at the top.

Questions about cookies: write to privacy@amnosolutions.com. If you are not satisfied with our answer, you can complain to the Information Commissioner’s Office, which regulates cookies in the UK, at ico.org.uk.