Cookie and Similar Technologies Policy

Version 1.1

Effective date: 15 September 2026

This Policy explains how LingoGap uses cookies, local storage, application storage and similar technologies across the LingoGap web service and native mobile application.

It should be read together with the LingoGap Privacy Policy.

LingoGap is operated and commercially provided under licence by:

Uglecare ApS

CVR: 34353255

Borups Allé 116, st. tv.

2000 Frederiksberg

Denmark

Telephone: +45 91 41 20 66

Email: support@lingogap.dk

Website: https://www.lingogap.dk

1. Cookies and similar technologies

A cookie is a small piece of information that a website may store on, or read from, a user’s browser or device.

Similar technologies can perform related functions without using a traditional browser cookie. These may include:

- browser local storage;

- authentication storage;

- application-local storage and databases;

- temporary caches;

- SDK-managed storage;

- device or application identifiers where applicable; and

- other technologies that store information on, or access information from, a user’s device.

The LingoGap native application does not rely on traditional browser cookies in the same way as the web application.

However, both the web service and the native application use limited storage and similar technologies to provide requested functionality.

The use of these technologies does not by itself mean that LingoGap tracks users for advertising or marketing purposes.

2. Technologies used across LingoGap

LingoGap uses technologies that are necessary or directly related to functions requested by the user.

Depending on the platform and feature, these technologies may support:

- signing in and maintaining authentication;

- account security;

- restoring the signed-in state;

- remembering user-selected preferences;

- saving learning progress and application state;

- flashcard and review functionality;

- providing subscription and payment functionality;

- synchronising supported account data;

- providing backup and restore functionality;

- delivering audio and speech-related features; and

- maintaining temporary technical state required for reliable operation.

Where a technology stores personal data or is used in connection with personal-data processing, that processing is also governed by the LingoGap Privacy Policy.

3. Web application

The LingoGap website and web application may use browser-based storage and provider-managed technologies.

These may include:

Authentication

Firebase Authentication may use browser storage, including technologies such as IndexedDB, local storage or temporary authentication state, to:

- sign users in;

- keep users signed in;

- restore authenticated sessions;

- complete Google Sign-In;

- manage authentication redirects or popup flows; and

- protect authenticated access.

Functional preferences

LingoGap may use browser storage to remember choices made by the user, such as:

- appearance or theme;

- audio or playback preferences;

- support-language preferences; and

- flashcard or review preferences.

Operational state

Limited browser storage may also be used to support application operation, prevent unnecessary repeated requests or writes, and maintain temporary functional state.

Payments

Website subscriptions may be purchased and managed through Stripe-hosted services.

When a user enters Stripe Checkout or the Stripe Customer Portal, Stripe may use cookies or similar technologies on Stripe-controlled pages for payment processing, fraud prevention, security, regulatory compliance and service operation.

Those technologies are controlled by Stripe and may also be subject to Stripe’s own privacy and cookie information.

Browser and network caching may also occur as part of normal web operation.

4. Native Android application

The LingoGap native Android application primarily uses application and device storage rather than traditional browser cookies.

The native application may use local application storage or databases for functions such as:

- authentication state;

- learning progress and lesson state;

- flashcards and review state;

- PD3 practice and attempt state;

- user preferences;

- temporary application state;

- local caches;

- backup and restore functionality; and

- other data required to provide requested learning features.

Some information may remain only on the device, while other supported information may be synchronised with LingoGap services.

Authentication

Firebase Authentication and supported Google Sign-In functionality may use SDK-managed or platform-managed state to authenticate the user and maintain secure account access.

Google Play

Subscriptions purchased through the Android application use Google Play Billing.

Google Play and Google services may use platform-managed information necessary to:

- process purchases;

- verify subscription status;

- prevent fraud;

- manage billing; and

- provide subscription functionality.

Google-controlled processing is also subject to the applicable Google terms and privacy information.

Microphone and speech functionality

When a user actively uses a speaking or speech-recognition feature, the application or the device may request microphone permission.

Audio or speech information may be processed by the device, operating system or relevant speech-service provider in order to provide the requested recognition or transcription functionality.

Microphone access is not used by LingoGap for advertising or unrelated tracking.

Permissions can be managed through the device’s operating-system settings.

5. Third-party technologies

Some technologies used in connection with LingoGap are provided or controlled by third parties.

Relevant providers may include:

- Google and Firebase for authentication and related platform services;

- Google Play for Android billing;

- Stripe for website payments and subscription management;

- device or operating-system providers for permissions and speech functionality; and

- infrastructure providers involved in delivering the service.

A third-party provider may process technical information independently where this is necessary for its own platform, security, fraud-prevention or legal obligations.

Further information about third-party processing and international data transfers is provided in the LingoGap Privacy Policy.

6. Analytics, advertising and optional tracking

LingoGap does not currently use its web or native application to provide behavioural advertising or cross-service advertising tracking.

LingoGap does not use application storage described in this Policy for personalised advertising.

The technologies currently described in this Policy are used for technically necessary functions, functions explicitly requested by the user, user-selected preferences, security, authentication, payment or operation of the service.

For this reason, LingoGap does not currently use a general advertising or analytics cookie-consent banner for these technologies.

If LingoGap introduces optional technologies in the future for purposes such as:

- non-essential analytics;

- advertising;

- personalised marketing;

- session replay;

- cross-site or cross-app tracking; or

- another purpose requiring consent,

those technologies will not be activated before the user has been provided with the information and consent choices required by applicable law.

Where consent is required, refusing or withdrawing consent will be made available as required by law.

7. Managing stored information

Web

Users can use their browser settings to manage or remove browser cookies, site data, local storage, permissions and cached information.

Removing browser storage may:

- sign the user out;

- reset user preferences;

- require authentication again; or

- reset temporary local application state.

Native application

Users can manage application permissions through Android settings.

Depending on the operating system, users may also be able to clear application storage or uninstall the application.

Clearing or removing local application data may remove locally stored preferences, authentication state or learning data that has not been synchronised or backed up.

Clearing browser or application storage is not the same as deleting a LingoGap account.

It also does not automatically cancel an active Stripe or Google Play subscription.

Account deletion is available through the supported LingoGap account experience and at:

https://www.lingogap.dk/account/delete

Subscription cancellation must be completed separately through the applicable billing channel.

Further information about account deletion, retention and personal-data rights is provided in the Privacy Policy.

8. Changes and contact

LingoGap may update this Policy if:

- the technologies used by the service change;

- a new platform or provider is introduced;

- the purposes for which a technology is used change;

- applicable law or regulatory guidance changes; or

- clarification is required.

The current version and effective date will be displayed at the top of this Policy.

If LingoGap introduces a technology for which consent is legally required, the required information and consent mechanism will be provided before that technology is activated.

For questions about cookies, application storage or similar technologies, contact:

LingoGap

Operated and commercially provided under licence by: