1. Cookies and Similar Technologies

Cookies are small pieces of information stored by a browser. Similar technologies include local storage, session storage, authentication tokens, device identifiers, native application storage, cached settings, service-worker storage, and related mechanisms used to operate an online or mobile service.

This page uses “cookies” as a convenient term for these technologies even when the information is stored through a different browser, app, device, or authentication mechanism.

2. Strictly Necessary and Core Service Technologies

Blocking required technologies can prevent sign-in, break protected features, interrupt uploads, remove saved device state, or make Loombus unable to confirm your account permissions.

• create, maintain, refresh, and end authenticated sessions;
• keep protected account, Room, message, billing, support, and administrative pages limited to authorized users;
• complete email, Google, Apple, and other supported sign-in or account-recovery flows;
• protect against cross-site request forgery, unauthorized access, fraud, spam, abuse, and security threats;
• remember routing, account state, consent state, feature state, and technical information required to deliver the service;
• support database, storage, file, notification, and API operations that depend on a valid session.

3. Preferences and Interface State

Clearing local storage or application data may reset preferences, sign you out, remove locally remembered interface state, or require you to complete certain setup steps again.

• appearance choice, including Light, Dark, or System mode;
• supported navigation, onboarding, composer, filter, search, and workspace state;
• dismissed notices, selected tabs, draft-related state, and device-specific feature preferences;
• notification permission prompts, saved-session choices, and local biometric-unlock preference where supported by the native app.

4. Search, Local, and Discovery State

Loombus may temporarily store a search term, filter, category, location selection, radius, remote status, event date, pagination state, or recent destination to provide consistent navigation and reduce repeated input.

Stored location-related preferences are not the same as continuous GPS tracking. A specific device-location feature would request the applicable permission before using device location when required.

5. AI, Usage Limits, and Cached Feature State

Cookies or similar state may help associate an authenticated request with the correct subscription, AI usage allowance, cached output, feature bucket, rate limit, or abuse-prevention control.

The substantive prompts, source content, outputs, and usage records connected to AI features are described in the Privacy Policy. They are not necessarily stored inside a browser cookie.

6. Billing, App Stores, and Purchase State

Loombus and its payment or app-store providers may use cookies, tokens, transaction identifiers, or application storage to initiate checkout, return from a billing flow, restore purchases, confirm entitlement, prevent duplicate fulfillment, and manage subscription access.

Payment providers and app stores use their own technologies under their own terms and privacy notices. Loombus generally receives transaction and entitlement information rather than a complete card number or bank login.

7. Push Notifications and Native Application Storage

The mobile applications may store a push-notification registration token, permission state, app version, device platform, saved session, and local settings needed to deliver supported notifications and maintain account access.

A push token identifies an application installation for notification delivery. It is not a biometric template and is not the same as your advertising identifier.

8. Security, Fraud Prevention, and Rate Limiting

Loombus may use cookies, tokens, browser identifiers, network information, and server-side logs to recognize suspicious sign-in patterns, enforce rate limits, prevent repeated abuse, secure support forms, detect automated activity, and protect accounts and infrastructure.

These controls can change without notice because publishing detailed security rules could make them easier to evade.

9. Diagnostics, Reliability, and Performance

Loombus may use technical identifiers and similar technologies to diagnose crashes, failed requests, slow loading, broken routes, notification failures, upload problems, session errors, and other reliability issues.

Diagnostic information may be connected to an account when needed to reproduce a problem, investigate abuse, or provide support.

10. Third-Party Service Providers

Authentication, hosting, database, storage, email, push, payment, app-store, mapping, geocoding, security, diagnostics, file-processing, and AI providers may set or read their own cookies, tokens, SDK state, or similar information while providing services to Loombus.

Loombus does not control every technology used by an external provider. The provider’s own terms and privacy notices govern its independent practices.

11. Advertising and Cross-Site Tracking

As of the effective date, Loombus does not operate a cross-site behavioral advertising network and does not use undisclosed advertising pixels to follow members across unrelated websites for targeted advertising.

Loombus may measure its own service reliability, acquisition, and feature use. If Loombus introduces materially different advertising or cross-context tracking, the applicable notices and consent controls will be updated as required.

12. Managing Cookies and Stored State

Restricting required technology may cause loss of functionality. Browser “Do Not Track” signals are not a substitute for required session and security storage and may not have a uniform legal or technical meaning.

• use browser settings to view, block, or delete cookies and site data;
• clear local or session storage through browser or device controls;
• manage app storage, notification permissions, and biometric-unlock settings through the device operating system or Loombus settings where supported;
• use private browsing for a shorter-lived session, understanding that some protected features may not work as expected;
• sign out when using a shared device.

13. Retention of Cookie and Similar Data

Session technologies may expire when a session ends, while persistent technologies may remain until their expiration, sign-out, deletion, application reset, or manual clearing. Server-side records associated with a token or identifier may follow different security, billing, audit, or retention schedules.

14. Related Policies

Read this page with the Privacy Policy and Terms of Service. The Privacy Policy explains the broader categories of information Loombus processes and the purposes for that processing.

15. Cookie Questions

Submit a question through Loombus Support or email support@loombus.com.

Document status

Effective date: July 18, 2026

Last reviewed: July 18, 2026

This public explanation describes the current Loombus service and may be updated as features, operational practices, or legal requirements change.