IloClip uses only the cookies the service needs to work. We use no advertising cookies and no third-party analytics or tracking cookies, so we do not ask you to accept cookies. Our product analytics run on our own servers with pseudonymous identifiers and set no cookies.
Cookies
| Cookie | What it does | How long |
|---|---|---|
| `__Host-iloclip_session` | Keeps you signed in | Until you sign out; 30 days without use, 90 days at most |
| `__Host-iloclip_csrf` | Protects your actions from being forged by other websites | Your session |
| `__Host-iloclip_reauth` | Remembers that you just confirmed your password for a sensitive action | A few minutes |
| `__Host-iloclip_mfa_pending` | Carries a sign-in between your password and your two-factor code | A few minutes |
| `__Host-iloclip_oauth_state`, `__Host-iloclip_oauth_pending` | Protect and complete a sign-in with Google | A few minutes |
| `__Host-iloclip_staff`, `__Host-iloclip_staff_csrf` | Sign-in and protection for IloClip staff only | A staff session |
All of them are set by IloClip, are sent only to the host that set them, and cannot be read by scripts on the page where marked HttpOnly.
Storage in your browser
- Upload resume: while an upload is in progress, your browser keeps a note of which parts have been sent, so a lost connection or closed tab can continue where it stopped. It is removed when the upload finishes or after 24 hours.
- Editor drafts: unsaved caption and trim changes are kept in your browser until they are saved, so they survive a dropped connection.
Bot protection
Our sign-up and sign-in forms use Cloudflare Turnstile to tell people from bots. It may use its own storage to do this; see Cloudflare's privacy policy.
Questions
See the Privacy Notice or email privacy@iloclip.com.