Cookie Policy
Last updated: 3 September 2026
1. Scope
This Cookie Policy explains how LineApp uses cookies, browser storage and similar technologies on lineapp.live and its localized pages. It should be read together with the Privacy Policy, which explains the personal data that may be processed through these technologies.
For questions about cookies or privacy, contact [email protected].
2. What cookies and similar technologies do
A cookie is a small value stored by a website in a browser. Session cookies support a visit and are normally removed when the session expires; persistent cookies remain until their expiry or deletion. Similar technologies can include browser storage, pixels, scripts and requests to external resources that allow a provider to receive technical information when a page or image is loaded.
LineApp does not put a password or an OAuth access token in a browser cookie. Cookie values can still be personal data when combined with other information, so they are handled according to the Privacy Policy and applicable law.
3. Cookie types grouped by purpose
LineApp groups cookies by their purpose instead of listing every individual parameter. Names, lifetimes and purposes can change with a release or environment configuration; the browser’s developer tools show the storage actually used for a particular visit.
| Cookie type | General purposes | Category | Typical retention |
|---|---|---|---|
| Essential and security | Keep sessions, authentication, CSRF protection and requested account actions working. | Necessary / security | Session lifetime; currently up to 120 minutes of inactivity. Security tokens are short-lived. |
| Functional preferences | Remember language, selected public location, theme and related interface choices. | Functional / preference | Usually up to 365 days, depending on the setting and environment. |
| Approximate-location suggestion state | Avoid repeated lookup or display of the same approximate-location suggestion and remember the relevant choice. | Functional / approximate location | State normally about 30 minutes; a dismissal normally about 30 days. |
| Consent record | Remember your choices for optional cookie categories and the version of the consent notice; keep a limited server-side record of the choice. | Consent / necessary | Browser choice usually up to 180 days; server journal currently up to 730 days. |
| Analytics technologies | Measure visits and product usage through Google Analytics, Yandex Metrica or other tags configured in Google Tag Manager after consent. | Optional / analytics | Varies by provider and configured tag; the relevant provider controls its own retention. |
| Third-party technologies | Support CAPTCHA, maps, address search, image delivery, OAuth pages and ticket links when those resources are used. | Third-party; necessary or optional depending on the service | Varies by provider; the relevant provider controls its own retention. |
4. Cookie categories
- Necessary and security cookies are used for sessions, authentication, CSRF protection, consent state, core navigation and requested account functions. Removing them can prevent LineApp from working.
- Functional preference cookies remember choices such as language, public location and theme. The approximate-location suggestion uses the Location choice in the consent settings. These cookies are not used to store passwords or OAuth tokens.
- The Analytics category is optional. When it is not allowed, LineApp does not load Google Tag Manager and the analytics tags configured inside that container do not receive a visit.
- Marketing is not currently active in the consent manager. If this changes, the relevant technologies and choices will be described before they are used.
5. Approximate location suggestions
When the feature is enabled and you allow the Approximate location category, LineApp may use the request IP address briefly to estimate a city or area for a first-visit suggestion. A short-lived cache may retain a hash-derived lookup key and coarse result to avoid repeated database work. Without that choice, the automatic lookup is not performed. The application does not store the raw IP in the GeoIP mapping table, public experience event record, account data or consent journal, and the result is not intended to identify an exact address, household or person.
This feature uses GeoLite2 data created by MaxMind, available from https://www.maxmind.com. The GeoLite2 database incorporates geographical data from GeoNames, made available under the Creative Commons Attribution 4.0 License.
6. Third-party scripts and resources
After you allow the Analytics category, the website loads Google Tag Manager. The configured container can load analytics or other third-party tags, and the resulting cookies or requests depend on that container’s contents. Google reCAPTCHA may load on enabled registration, sign-in or password-reset forms as a necessary anti-abuse security control. LineApp uses it only for that security purpose; it is not connected to analytics, advertising, profiling or recommendations, and LineApp does not store reCAPTCHA tokens or results in account data. The browser and request IP may be sent to Google for verification, subject to Google’s own notices and terms. Map tiles, address search, image delivery, OAuth pages and ticket links can also cause the relevant provider to receive ordinary technical request information or set its own storage outside LineApp’s control.
Third-party providers decide their own cookies, retention and purposes. Their independent processing is governed by the relevant provider’s privacy and cookie notices.
7. Consent and your choices
The first notice offers Accept all, Only necessary and Settings with equal visibility. Necessary and functional technologies remain active because they support the requested website and account functions; Approximate location and Analytics are off until you enable them.
The site stores your category choices and the consent-policy version in a first-party consent record and may keep the limited server-side journal described in the Privacy Policy. You can reopen Cookie Settings from the site and change or withdraw optional choices. Withdrawal stops future loading of the relevant LineApp-controlled technologies; it cannot undo processing that already occurred or delete storage controlled by an independent third-party provider.
You can also delete or block cookies through your browser. Blocking necessary cookies may prevent login, account actions, location selection or other features from working.
8. Updates and contact
We may update this policy when cookies, providers, consent controls or legal requirements change. The new version and date will be published on this page. Questions or requests can be sent to [email protected].
Contact
If you have any questions, please contact us at [email protected].
See also: Terms & Conditions, Privacy Policy, Cookie Policy.