Cookies and local storage

Cookie Policy

This policy explains the cookies and similar browser-storage technologies used on Enrike’s corporate website and authenticated application.

Last updated: 30 July 2026

1. What these technologies are

Cookies are small files stored on a device. Similar technologies include local storage, session storage, pixels, and software development kits. They can support security, sessions, preferences, analytics, or advertising.

2. Current position

Optional analytics is enabled only with your permission.

The corporate website uses Google Analytics only after you select “Accept analytics” in the cookie banner. Selecting “Reject optional” keeps analytics disabled. We do not use advertising cookies.

3. Storage used to provide the service

Technology or providerPurpose and duration

Cookie preference (local storage)Remembers your analytics choice in enrike-cookie-consent-v1 for 180 days. If storage is unavailable, the choice applies only to the current page.

Google Analytics (_ga and _ga_* cookies)Measures website usage only after consent. Cookie expiry is controlled by Google Analytics settings. Withdrawing consent stops analytics and removes accessible first-party Google Analytics cookies.

Supabase authentication storageMaintains the signed-in session, refreshes access tokens, and completes secure login or password-recovery redirects. Persists until sign-out, deletion, or token expiry.

Enrike and hosting security storageDelivers requested pages, protects restricted areas, balances traffic, and prevents abuse. Session-based or retained only as operationally necessary.

hCaptchaDetects automated signup attempts and protects accounts. Used when the signup challenge is loaded and subject to hCaptcha’s security retention.

Stripe Checkout and customer portalProcesses payment, subscription, fraud-prevention, and portal sessions on Stripe-hosted pages. Duration is controlled by Stripe.

Exact cookie names can vary when a provider changes its implementation or when session settings differ. These technologies are used only to provide a service requested by the user, maintain security, or process a requested payment.

4. Browser-local file processing

Enrike parses selected CSV and XLSX files in the browser and generates the completed download locally. This processing does not use cookies to profile the file or its contents. Email or postcode values selected for enrichment are still sent to the Enrike API as described in the Privacy Policy.

5. Third-party pages

When you open Stripe Checkout, the Stripe customer portal, hCaptcha, or another third-party site, that provider may use its own cookies under its policy. Enrike does not control storage placed directly by a third party on its own domain.

6. Your controls

Use the “Cookie settings” button on any page to review or change your analytics choice. Withdrawing consent reloads the page to stop analytics. You can also review, block, or delete cookies and site data in your browser settings. Blocking necessary authentication or security storage can prevent signup, sign-in, billing, or protected features from working. Signing out removes the active Enrike session from the application, subject to browser and provider behaviour.

7. Changes and contact

If Enrike introduces additional optional analytics, personalisation, or advertising technologies, we will update this policy and present consent controls before activation where required. Questions can be sent to enrike@higuera.ai.