What we set, and why
We use a small number of cookies. We don't use advertising or third-party
analytics cookies.
| Name | Purpose | Lifetime |
|---|---|---|
__amtel_session |
Customer-side session cookie. HTTP-only, SameSite=Lax. | 30 days |
__amtel_admin_session |
Admin-console session cookie. HTTP-only, SameSite=Lax. | 24 hours |
__amtel_csrf |
Double-submit token paired with the session. Read by JS to attach as a header on POST/PUT/DELETE. | Same as the session above |
Sub-processor cookies
A few sub-processors set their own cookies when you interact with their flows:
- Google reCAPTCHA runs on the public quote, contact, and developer-application
forms. Google sets cookies undergoogle.comfor fraud prevention. See Google's
policies linked from the bottom of forms that include reCAPTCHA. - Flutterwave (payment gateway) sets cookies on its own domain when you complete
a payment. We don't see these.
How to manage
Browsers let you view and delete cookies in their settings panel. Removing__amtel_session or __amtel_admin_session signs you out. Removing __amtel_csrf
will cause the next form submit to fail until you sign in again.
If you want to opt out of analytics cookies and reCAPTCHA, you can browse the public
parts of the site without signing in or submitting forms — none of the cookies above
get set until you do.
Changes
If we add or remove cookies, this page and the table above will be updated. We'll
note material changes via the email associated with your account where applicable.