Cookie Policy

Cookie Policy: service and scope

This Cookie Policy applies to the LingoLab service at lingolab.lsa-global.com, operated by LSA.GLOBAL LANGUAGE SERVICE ACADEMY LLC. Contact contacts@lsa-global.com if you have a question about a storage item or the way a feature works. The Privacy Policy gives our postal address, the purposes of personal-data processing and the rights that may apply to you.

LingoLab runs within a WordPress website and uses supporting hosting and payment services. The list below identifies the storage used by the LingoLab software and relevant WordPress authentication features. A separate site, a payment checkout or an additional website integration can have its own storage. Their presence and settings depend on the service you actually visit; an external link is not itself a record of consent.

What cookies and browser storage do

A cookie is a small value that a website can ask your browser to retain and send with later requests. It can help a server recognise a signed-in session or apply a preference. Local storage retains values for the same website within a browser profile. Session storage supports work within a browser tab or session. IndexedDB is a browser database capable of holding larger items, including a temporary recording.

These technologies have different behaviour, but their privacy relevance depends on what they store and why they are used. This Cookie Policy therefore covers more than cookies alone. A local draft is not automatically a submitted answer, and a locally available recording does not prove that the server received it. Follow the workspace’s actual save and submission status.

Essential sign-in and account access

WordPress authentication cookies support your signed-in session and access to protected pages. Names can include wordpress_logged_in_ followed by a site-specific value and secure authentication cookies such as wordpress_sec_. A WordPress login flow may also use wordpress_test_cookie to check whether cookies work. The exact values are specific to the installation and session.

These cookies allow the server to verify the session rather than asking for your password on every page. Blocking them can prevent sign-in, access to a private record or completion of an authenticated request. A session identifier is not permission to access every account: LingoLab also checks ownership and roles. This Cookie Policy does not suggest that a candidate needs access to the WordPress administration dashboard.

Sign-in duration and shared devices

Authentication-cookie duration depends on the WordPress configuration, session state and the sign-in flow. The “keep me signed in” option can extend a login, and email-verification completion can establish a remembered session. Security settings or password changes may end it sooner. We do not promise that every account will remain signed in for one fixed number of days.

On a shared computer, use your own browser profile where possible and sign out when finished. Closing a tab is not the same as signing out. Another person using a browser that still has an active session may be able to open your private pages. Clearing site cookies generally requires a fresh sign-in, but it does not cancel your plan or remove saved assessments.

The language preference cookie

The LingoLab cookie lsa_dep_locale stores a supported interface-language code: English, French, Spanish or German. Its configured lifetime is 365 days from the time the preference is set or refreshed. The server can use it to display the selected language when a page address does not specify another choice. A signed-in user’s language may also be stored with the account.

The cookie is configured with a same-site restriction and is not readable through ordinary page JavaScript; its secure flag follows whether the site is served over HTTPS. The language in the page address and the saved account preference can also affect the displayed language. Deleting this cookie alone may therefore not change the language of a signed-in account. Use the visible language selector for an intentional change.

The lsa_dep_currency cookie remembers a currency you explicitly select for up to 365 days. It uses a same-site restriction and the secure flag on HTTPS. Without a saved selection, an available host country hint or browser time zone can suggest a currency. Change it through the visible currency selector. Removing the cookie does not remove a preference already saved with your account.

Language and theme in local storage

LingoLab uses local storage entries named lsa_dep_locale and lsa_lingolab_theme to support a consistent language and light or dark appearance while you navigate. These entries do not have an automatic expiry specified by the application. They can remain until replaced, removed by the browser or cleared with the site’s browser data. They are separate from the language cookie described above.

Choosing a dark theme does not change your examination language, payment currency or subscribed preparation scope. A browser’s system appearance can provide a starting preference when no explicit selection is present. This Cookie Policy distinguishes these convenience preferences from authentication. Removing them can reset appearance without deleting your account, while blocking all storage can affect additional functions beyond the theme.

Temporary answer and writing recovery

During an assessment, session storage can retain local recovery information using the prefix lsa_dep_runtime_recovery_v1:. It can include answers, progress position, timestamps and synchronisation state associated with an attempt and module. Writing tasks can also use entries beginning lsa_dep_draft_v2_ for a particular item. These are recovery aids for your work within the browser, not public analytics profiles.

Session storage normally follows the browser’s tab or session lifecycle, but session restoration can preserve it. Do not rely on closing a window as proof that every draft has been removed. The application clears local entries during relevant completion or cleanup actions where supported. Before clearing browser data yourself, check that required work has been saved or submitted to the server.

Temporary speaking-recording recovery

The browser database lsa-dep-runtime-recovery contains a recordings store for temporary audio recovery. A record can contain an audio blob, its type, its creation time and a key relating it to an attempt, module and item. This allows the recorder to recover eligible recent work after an interruption rather than requiring every interrupted recording to be repeated.

The recovery code does not offer a recording for restoration after its 24-hour recovery limit. That limit is not a guarantee that the browser has physically erased the stored bytes at exactly 24 hours. Data may remain until the application removes it, the browser clears it or you delete the site’s storage. The Cookie Policy makes this distinction because recovery availability and physical deletion are different operations.

Cookie Policy storage inventory

The inventory on this page groups storage by purpose and location. Items described as cookies can be sent to the website with requests within their configured scope. Local storage, session storage and IndexedDB are accessed within the browser by the relevant application code. Suffixes or prefixes identify a family of values rather than one identical item on every device.

You may see fewer entries if you only browse public pages, and more after signing in or starting a relevant assessment. Administrative tools can also use settings unavailable to candidates. A support investigation should identify the actual item, its domain and the action that created it. Do not send its secret value; a cookie name and a description of the problem are usually a safer starting point.

Cookie Policy: necessary and optional functions

Storage that authenticates a requested session or supports a requested assessment has a different purpose from advertising tracking. Language and appearance entries support navigation preferences. Whether a particular use requires consent or qualifies for a legal exception depends on the purpose, the location of the user and the applicable rules. A label in a policy does not create an exemption by itself.

The core LingoLab code does not add an advertising pixel or a general visitor-marketing tracker. This is not a claim that every separately configured website plugin has been audited through this notice. If an additional service uses optional technology requiring permission, the appropriate choice must be provided before that technology is used. Acknowledging the Privacy Policy is not a blanket cookie-consent mechanism.

Payment and other third-party pages

When an enabled payment provider opens its checkout, that provider can use cookies and similar tools for payment, session security and fraud checks. Review the provider’s notice and any choices shown on that page. The available provider and payment options depend on the checkout configuration. This Cookie Policy does not declare the precise lifetime of a provider’s cookie without checking its current implementation.

Links to official examination information and LSA GLOBAL services take you to the destination named in the link. Simply reading an ordinary link on our page is different from loading an embedded third-party player or tracker. If you follow a link, the destination site can receive ordinary connection information and apply its own browser-storage practices. Return to LingoLab to manage your preparation account.

Cookie Policy: inspect, block or remove storage

Your browser’s privacy or site-settings area lets you inspect cookies and stored website data, restrict future storage and remove existing entries. Find the settings for lingolab.lsa-global.com and check related parent-domain entries where relevant. The exact labels differ between browsers and mobile operating systems. Official browser help is more reliable than instructions written for a different version.

You can change the interface language and theme through LingoLab’s visible controls. To stop a browser retaining preferences, use its storage restrictions or an appropriately configured private session. If you cannot locate a control or need to object to a particular preference use, contact us and identify the item. We can explain the relevant function and assist with the request. Removing all website data is a broader action than resetting one preference.

Check your work before clearing data

Before clearing storage, finish or safely save an active task, confirm its server status and sign out where appropriate. Removing a local draft or unsubmitted recording can make that work unavailable for recovery. Clearing browser data while an upload is incomplete does not force the upload to finish. If the workspace reports an error, seek help before deleting the only recoverable copy of your work.

After clearing data, you may need to sign in again and reselect your interface language or appearance. A saved account preference can still be applied after sign-in. This Cookie Policy does not promise that browser cleanup restores a free trial, resets a timer or changes an access deadline: those limits are maintained by the service and do not depend solely on a local cookie.

Browser cleanup and server deletion are separate

Clearing cookies, local storage or IndexedDB affects the selected browser profile. It does not by itself delete assessment records, submitted audio, an order or an account held on the server. Conversely, deleting an assessment through the records workspace should not be treated as a universal command to clear every browser or independently held copy.

Use the archive and permanent-deletion controls for eligible assessment records, and contact us for broader privacy requests. Archiving preserves the record while moving it out of the active view. Permanent deletion is the separate action intended to remove eligible records and associated private audio through the cleanup workflow. Read the Privacy Policy for retention criteria and exceptions, including records needed for unresolved payments, security matters or legal obligations.

Microphone permissions and recordings

Microphone permission is managed by your browser and operating system; it is not itself a cookie. A speaking task needs permission to capture the audio you choose to record. You can review the browser’s indicator and revoke microphone access in site settings. Revoking permission prevents later capture through that permission but does not automatically erase a recording already submitted.

This Cookie Policy covers the browser storage used for temporary recording recovery. The Privacy Policy explains server processing and any selected AI transcription or human correction. On a shared device, check both the active login and locally retained work. Do not assume that another person’s use of a different interface language creates a separate account or a separate storage area.

When browser restrictions affect a feature

A browser may block or remove storage because of private browsing, limited device space, security preferences or an extension. The effects can include losing a remembered theme, being asked to sign in again or being unable to restore an unsaved draft. The application may still allow some work when local recovery is unavailable, but you should not assume recovery is guaranteed.

If you report a problem, include the page, approximate time, browser version and what you expected to happen. Explain whether you were signed in and whether the server showed a successful save. Avoid sending a session cookie, verification link or a private recording in an ordinary screenshot. We do not need your password to explain the storage behaviour described in this Cookie Policy.

Cookie Policy questions and privacy requests

You can ask us to explain a storage purpose or raise a concern by writing to contacts@lsa-global.com. State whether the question concerns a preference, authentication, an assessment draft or a payment page. If a value contains personal information, the rights explained in the Privacy Policy may also apply, depending on the law and the processing involved.

A request about server information is handled separately from changes you make in your browser. If a provider controls a payment-page cookie, we may direct you to that provider’s current information while still helping with your LingoLab order. You may contact the relevant authority where applicable. The official guidance links below explain storage technologies and WordPress cookies; they do not certify this website or replace your own browser’s settings.

Keeping this Cookie Policy current

The revision date identifies this version of the Cookie Policy. Storage can change when a feature, hosting arrangement or connected service changes. New optional tracking must be assessed separately; this notice is not advance permission to introduce it. We will update the relevant description when the platform’s disclosed storage practices change.

You can print or save this page for reference and compare the named entries with those visible in your browser. If an unexpected item appears, contact us with its name and domain rather than its contents. Reading this Cookie Policy does not require account registration. Its purpose is to help you understand and control a real part of using LingoLab, while keeping the distinction between convenience settings, essential access and assessment recovery clear.