Storage and browser technologies
This policy explains the limited browser storage used by Airbip, what is necessary for the service and how to manage optional technologies if they are introduced.
Cookies are small data files stored by a browser and returned to a website on later requests. Similar technologies can include local storage, pixels or identifiers used to maintain state or understand interactions.
They may be first-party, set for the Airbip domain, or third-party, set through an external service. They may expire at the end of a session or remain for a defined period.
The current public Airbip frontend does not include advertising cookies or third-party audience analytics. The application uses necessary session and security mechanisms when a visitor submits a form, requests an invitation, signs in or uses a protected area.
Cookie names may vary by environment or deployment configuration. The functional purpose, rather than only the technical name, determines the category.
| Technology | Purpose | Duration criterion | Status |
|---|---|---|---|
| Airbip session identifier | Maintain a secure session, form state, authentication and referral context | Session or configured inactivity period; renewed when the session is used | Necessary |
| Request-verification token | Help verify that forms and authenticated actions originate from the expected session | Session or short technical lifetime | Necessary |
| Interface preference, if enabled | Remember a choice explicitly requested by the user, such as a display preference | Limited to the useful life of that preference | Necessary when requested by the user |
Necessary cookies support a function expressly requested by the user or are required to transmit, secure or maintain the service. They can be used without optional-consent controls where the applicable rules permit.
Blocking them may prevent forms, login, language continuity, invitation requests, checkout or customer-area functions from working correctly.
If Airbip later introduces non-essential measurement, personalisation or advertising technologies, they will not be activated before the required information and consent controls are available.
Accepting optional cookies will not be bundled with acceptance of terms, privacy information or account creation. Rejecting optional cookies will be offered in a way that does not make it harder than accepting them.
Any updated inventory will identify the provider, purpose, duration and whether information is transferred to a third country.
Where consent is required, it must be a clear affirmative choice based on understandable information. Silence, inactivity or continuing to browse is not treated as consent for optional cookies.
A user can withdraw or change a choice at any time through the available preference control. Withdrawal applies to future use and does not make earlier consent-based processing unlawful.
Browsers allow users to inspect, block and delete cookies for one site or all sites. Private browsing and automatic deletion can further limit persistence.
Browser settings operate independently from Airbip consent controls. Deleting cookies may sign a user out, clear form state or require preferences to be selected again.
A link to a third-party website does not place that site’s cookies on Airbip. If external content is embedded in the future, its provider may set its own technologies and must be identified before optional activation where required.
Applications deployed for customers have their own administrators, configuration and cookie responsibilities. This website policy does not automatically describe cookies used inside a separately hosted customer application.
A cookie identifier, IP address or interaction record may be personal data when it relates to an identifiable person. The privacy policy explains legal bases, recipients, retention criteria and rights.
Questions about a technology observed on Airbip can be sent through the contact form with its name, domain and the page where it appeared.
We review this policy when website functionality or providers change. A newly introduced optional technology must be reflected in the inventory and consent interface before it is used where consent is required.
The review date on this page identifies the current version.
This public information is completed by the specific order, service description and any data-processing agreement accepted by the customer.