LaConnet Gateway
  • Home
  • Platform
  • Solutions
  • Capabilities
  • Developers
  • Contact
Sign in Get started Sign in
Legal & Trust Centre

Cookie Policy

This policy explains cookies and similar device storage used in connection with LaConnet Gateway. A cookie is a small value stored by a browser. Local storage, embedded scripts and related technologies may also store information or access device information.

Last updated: September 25, 2026
Legal documents Privacy policy Terms & conditions Cookie policy Acceptable use Security overview

On this page

  • 1. Scope and purposes
  • 2. Gateway authentication and session storage
  • 3. Form protection and third parties
  • 4. Optional technologies and consent
  • 5. Browser controls and withdrawal
  • 6. Server records and updates

1. Scope and purposes

Storage may support sign-in, session continuity, form security and abuse prevention. A first-party cookie is set for the site you visit; a third-party cookie is set in connection with another provider. Session cookies normally last for a browser session, while persistent cookies remain until expiry or deletion, subject to browser behaviour.

Whether a technology is exempt from consent depends on its actual purpose and applicable law, not simply whether it is labelled “essential”. The Privacy Policy explains related processing of IP addresses, device information and personal data.

2. Gateway authentication and session storage

The .LaConnet.Gateway.Auth cookie supports authenticated account access. The authentication ticket is configured for a 30-day validity period that may renew during active use. A browser cookie may be session-only or persistent depending on the sign-in option; logging out ends the current application sign-in.

The .LaConnet.Sandbox.Session cookie identifies application session state, including sandbox interactions. Server-side session state is configured with a 30-day idle timeout. This timeout is different from the browser cookie’s lifetime, and browser session restoration may affect when session cookies disappear.

Security and form features may also use ASP.NET Core antiforgery cookies with generated names beginning .AspNetCore.Antiforgery. These bind form submissions to the browser and help prevent forged requests. Their exact generated names and lifetime can vary with the session and application configuration. They are not advertising identifiers.

3. Form protection and third parties

The public contact form uses Google reCAPTCHA to help distinguish legitimate submissions from automated abuse. It can process device and interaction information and set the _GRECAPTCHA cookie. Google controls its cookie lifetimes; other existing Google cookies may be involved when its components load. Google’s privacy terms apply to its own processing.

This notice does not classify every cookie a third party may set as exempt from consent. Contact info@laconnet.com directly if you prefer not to use a form requiring reCAPTCHA. Embedded payment or identity-provider components may have their own notices and storage controls.

4. Optional technologies and consent

Consent must be obtained before using non-exempt storage or access technologies where applicable law requires it. Optional analytics, advertising and unrelated personalisation must not be bundled into necessary sign-in or payment functionality, and merely browsing is not consent.

The public policy pages do not currently offer an optional analytics or advertising preference panel. This is not an invitation to accept tracking by continuing to browse. Any introduction of optional tracking requiring consent must be accompanied by appropriate information and controls before it is enabled, including a clear refusal option and a way to withdraw consent.

5. Browser controls and withdrawal

You can inspect stored cookies, expiry values and site permissions in your browser settings; delete site data; or restrict first-party or third-party storage. Settings are generally specific to a browser and device, so repeat them on other devices you use. Deleting or blocking authentication and session cookies can sign you out or prevent protected forms and account features from working.

Where a service provides an optional consent control, you can change your choice there. Browser deletion alone does not necessarily change a choice held by a provider or remove server records already collected. Contact us if you need help understanding the available controls or exercising related privacy rights.

6. Server records and updates

Cookie settings do not automatically disable server-side transaction records or security logs needed to operate and protect services. Such processing remains subject to the Privacy Policy and applicable law. We do not interpret a browser setting as permission to ignore a legally recognised opt-out signal.

Cookies and integrations can change with browser behaviour and service configuration. This notice describes the named application cookies and form provider in use at the revision date. Contact info@laconnet.com for clarification about an observed cookie or storage item, including its name, domain and the page where it appeared.

Questions about this document may be sent to info@laconnet.com .
LaConnet Gateway

Secure, connected payment infrastructure for merchant acquiring, payment orchestration, settlement, reporting and dispute operations.

Platform

  • Payments
  • Merchant operations
  • Settlement
  • Chargebacks
  • Developers

Company

  • About
  • Solutions
  • Pricing
  • Contact
  • Security

Legal

  • Privacy policy
  • Terms & conditions
  • Cookie policy
  • Acceptable use

Contact

  • Wuye District, Abuja
  • info@laconnet.com
  • +234 701 444 1843
Security-first architecture API-first integration Operational support

© 2020 – 2026 LaConnet Technologies Ltd. All rights reserved.

Privacy Terms Cookies