Cookie Policy
This page lists every cookie and piece of browser storage Automation uses, what each is for, and how to control them.
1. What these are
A cookie is a small file a website stores in your browser and reads back on your next request. Automation also uses two related browser features called local storage and session storage, which hold data in your browser but, unlike cookies, are not sent to the server with every request.
We group them by what they do. Essential ones make signing in and using the platform possible; without them it cannot work. Others are optional.
2. Essential cookies
These are set because the platform cannot function without them.
| Name | Purpose | Expires |
|---|---|---|
auth_cookie | Keeps you signed in after you authenticate. Without it every page would ask you to sign in again. | When the session ends, or as configured for your account |
| Trusted-device cookie (named after your account identifier) | Set when you tick "Trust this computer" during two-step verification, so that device is not asked for a code every time. HttpOnly and HTTPS-only. | 12 months if trusted; otherwise when you close the browser |
session_cookie | Identifies your server-side session. Used for short-lived state such as counting failed sign-in attempts. | When the session ends |
csrf_token | Anti-forgery token. Stops another site from submitting forms as you. | When the session ends |
Essential cookies do not require consent, because turning them off would mean you could not sign in at all.
3. Browser storage
These stay in your browser and are not transmitted with each request. They remember interface state so the platform behaves consistently between visits.
| Category | Purpose | Type |
|---|---|---|
| Session identifiers | Random identifiers that tie this browser to your sign-in, so the session list on your profile can recognise and end this device's session. | Local storage |
| Current workspace | Remembers which project you were working in. | Session storage |
| Approximate location | Set only if you grant the browser's location permission, for features that record where an entry was made. | Local storage |
| Interface preferences | Assorted small settings such as dismissed hints, panel states and layout widths, so the interface stays as you left it. | Local storage |
4. Analytics and security
Google Analytics
We use Google Analytics to see which parts of the platform are used and where people run into trouble. It sets cookies such as _ga and _ga_<id> to distinguish visitors and sessions, typically lasting up to two years.
This is aggregate measurement. We do not use it to profile individuals or to advertise. You can opt out with Google's browser add-on, or by blocking these cookies as described below.
Google reCAPTCHA
After several failed sign-in attempts, the login page presents a reCAPTCHA challenge to tell a person from an automated script. Google sets its own cookies and collects browser signals to make that judgement. This is a security measure and cannot be disabled while the challenge is active, though it only appears after repeated failures.
Approximate location
When you sign in, the page asks IPInfoDB for an approximate location from your IP address. This is recorded with the sign-in so you can spot an unfamiliar one in your session list. It is a network lookup rather than a cookie, and does not use your device's GPS.
5. How to control them
Every major browser lets you view, block and delete cookies and clear site storage, usually under Settings, then Privacy.
Blocking analytics
Blocking analytics or third-party cookies for this site has no effect on how the platform works. Nothing breaks.
Blocking essential cookies
Blocking the cookies in section 2, or clearing them mid-session, signs you out and prevents you from signing back in. Clearing the trusted-device cookie means the next sign-in asks for a verification code again.
Clearing local storage is safe: you will lose remembered interface preferences and the session list may stop recognising this device, nothing more.
6. Changes to this policy
We update this page when the cookies or storage we use change. The "last updated" date above always reflects the current version.
7. Contact
Questions about cookies or anything on this page:
Insource Inc Pvt. Ltd.Buddhanagar, Kathmandu
Nepal · Reg. No. 299184/079/080
Phone: +977 9802324841
Email: [email protected]
See also our Privacy Policy and Terms of Service.