Draft — not yet approved

Cookie policy

Engrane sets two cookies in normal use, and a third only while you are signing in with Google. This page names them and says what each is for; the rest of it is being written.

What a cookie is

A small file a site asks your browser to store, so that the next request can be recognised as yours. It is not a program and it cannot read other files.

What Engrane sets today

• access_token — keeps you signed in. Without it, every page behind the login would ask again.
• mnm_csrf — stops a form on another site from submitting a request as you. It is refreshed as you use the site.
• mnm_oauth_state — exists only while you are signing in with Google, and is deleted as soon as you come back. It ties the sign-in you started to the one that finishes, so a sign-in begun elsewhere cannot be completed here.

All three are marked HttpOnly, which means page scripts cannot read them, and all three are scoped to this site only.

What is not on this page yet

How long each cookie lives, and which consent choice covers it. Neither is stated here, because the policy is not approved and a half-filled list reads as a complete one.

Turning them off

Every browser can clear cookies and can refuse them. Refusing these will sign you out and stop forms from submitting — that is the trade, stated plainly rather than discovered later.