Last updated: August 29, 2026
This Cookie Policy explains cookies and similar technologies in the context of fareora.com. It describes Fareora’s active Travelpayouts affiliate-attribution and Meta Pixel measurement technologies separately from tools that may be enabled later.
1. What cookies and similar technologies are
A cookie is a small text value a website asks a browser to store on a computer, phone or other device. Cookies can help a website remember a session or preference, protect a form, measure activity or recognize that a visitor arrived through a particular link.
First-party cookies are associated with the website being visited. Third-party cookies are set or read by another service used on or reached from that website. Session cookies usually expire when the browser session ends. Persistent cookies remain until their stated expiry or until the user deletes them.
Similar technologies can include local storage, pixels, tags, device or server identifiers and link parameters. This policy uses “cookies” as a convenient term when the same explanation applies to those technologies.
2. Fareora’s current cookie usage
Fareora uses Travelpayouts Drive and related affiliate-attribution technology after a visitor accepts Advertising / Marketing. Travelpayouts or participating travel partners may use cookies, link parameters or similar identifiers to analyze content and visitor interactions, recognize a referral, and attribute qualifying clicks, searches, bookings or other actions.
Fareora also uses Meta Pixel, provided by Meta Platforms, Inc. and relevant Meta entities, after Advertising / Marketing consent to measure website visits and interactions, support advertising attribution and performance analysis, and create or measure aggregated advertising audiences where applicable.
Essential technical processing may also occur through WordPress, the hosting environment, email delivery, security systems or the content-delivery network when needed to serve pages, administer the site, protect forms or respond to suspicious traffic.
Administrative users who sign in to WordPress can receive login and preference cookies. Those administrative cookies are not used to track ordinary visitors for advertising. Security providers may also apply short-lived technology in response to abuse or a verification challenge.
The contact form uses server-side security validation, anti-spam checks and temporary rate limiting. Contact messages are sent by email and are not stored as WordPress contact records. Fareora does not currently use Google Analytics, Google Tag Manager or a separate advertising-platform tracking integration beyond the Meta Pixel and Travelpayouts technologies described in this policy.
3. Consent categories and necessary cookies
Fareora provides three categories: Necessary, which is always enabled; Analytics, which is optional; and Advertising / Marketing, which is optional and includes Meta Pixel and Travelpayouts Drive. Optional categories are off by default for a new visitor and are not preselected in the preferences panel.
Necessary technologies support functions such as secure page delivery, form protection, traffic routing, fraud prevention, administrative authentication and storage of privacy choices. Disabling them can prevent a page, login or security control from working properly.
Fareora stores the visitor’s consent version, necessary, analytics and advertising choices, and timestamp in a first-party cookie named fareora_consent. The preference is retained for up to 180 days, after which Fareora may request a new choice. It does not contain a visitor’s name, email address or travel-search details.
4. Measurement technologies
Measurement technologies can help a website understand visits, traffic sources, device categories and navigation patterns. Travelpayouts Drive analyzes content and visitor behavior as part of Fareora’s affiliate monetization setup.
Fareora also uses Meta Pixel under Dataset ID 1042823911716262. Meta Pixel may process page visits and configured interaction events to support website measurement, interaction measurement, advertising attribution, advertising performance analysis, and audience measurement where applicable. The provider is Meta Platforms, Inc. and relevant Meta entities. Meta may receive technical and browser information, page and referring information, cookie or similar identifiers, and configured event information according to Meta’s own terms and privacy policies.
Fareora’s configured Meta events use general page and feature labels. They are not configured to send names, email addresses, phone numbers, exact rental locations, travel dates or other information entered into Fareora forms or the GetRentacar widget.
Fareora does not currently use Google Analytics or Google Tag Manager. If another analytics service is enabled, Fareora will identify the relevant service and available choices as appropriate. Information may be aggregated or pseudonymous, but technical identifiers can still be treated as personal information under some rules.
5. Affiliate and attribution cookies
Fareora participates in Travelpayouts. Some outbound links, widgets or automatically inserted travel tools may contain a partner or referral identifier. Travelpayouts, its technology providers, or participating travel partners may set or read cookies or similar identifiers to determine whether a click, search, booking or other qualifying action followed a Fareora referral.
Attribution periods vary according to the relevant travel program. Travelpayouts documentation states that the Partner ID may be stored in a cookie for up to 30 days where applicable, unless a particular program uses different terms. Fareora does not invent or list cookie names that have not been verified. A provider may also apply its own cookies after you interact with its tool or visit its website.
Participation in Travelpayouts does not mean Fareora has an active integration with every travel brand in the network. No KAYAK integration is currently active.
6. Advertising and marketing cookies
Advertising cookies and pixels can measure campaigns, attribute visits or actions, create or measure audiences and help analyze advertising performance. Fareora uses Meta Pixel for these purposes where applicable. Meta may set or read cookies or similar identifiers under its own policies when the Pixel loads.
Fareora does not currently use a separate behavioral-marketing or advertising-platform integration beyond Meta Pixel and the Travelpayouts monetization technology described above. If additional marketing technology is introduced, Fareora will update this policy and provide applicable information or choices before treating that technology as active.
7. Third-party cookies
Meta Platforms, Travelpayouts, participating travel partners, hosting, security, embedded services or external providers may operate under their own cookie policies. When a third-party technology loads or you interact with a travel tool or provider, the relevant third party may process identifiers and apply its own privacy and cookie terms. Fareora cannot delete a cookie stored by another domain.
8. Cookie duration categories
Cookie duration depends on purpose:
- Session: generally lasts until the browser session ends.
- Short-lived: may last minutes or hours for security, traffic routing or temporary state.
- Preference: may persist longer so a choice can be remembered.
- Affiliate attribution: the applicable Travelpayouts or travel-program terms determine the period; the Partner ID may be stored for up to 30 days where applicable, while specific programs may use different terms.
- Meta measurement and advertising: duration depends on Meta’s applicable technology, user settings and policies.
- Future analytics or advertising: if enabled later, duration would be defined by the relevant service.
Fareora does not publish invented cookie names or expiry periods. More specific information may be supplied through this policy, a consent interface or the relevant provider’s documentation when verified.
9. Browser and device controls
Most browsers allow you to view, delete or block cookies and to restrict third-party cookies. Controls differ by browser and device. Blocking every cookie can interfere with security, logins or form functions. Deleting cookies may remove saved choices or attribution identifiers.
You can usually find controls under privacy, security, site data or cookie settings. Browser “private” modes may limit persistence but do not necessarily prevent every request or identifier. Device and operating-system settings can provide additional advertising or tracking controls. Visitors can also review Meta’s Privacy Center, Accounts Center and advertising-preference settings.
10. Consent choices and current loading behavior
New visitors receive equally available choices to Accept All, Reject Non-Essential or Manage Preferences. Necessary is always on. Analytics and Advertising / Marketing are off until affirmatively enabled. Fareora uses this privacy-safe default worldwide because it does not rely on unverified regional geolocation.
Meta Pixel and Travelpayouts Drive are assigned to Advertising / Marketing. Fareora does not download Meta’s Pixel library, initialize the Pixel, fire configured Meta events or load Travelpayouts Drive before that category is accepted. The GetRentacar search widget and AirHelp flight-compensation eligibility tool are separate user-facing travel functions and remain available before optional consent. Their official embedded scripts include provider or affiliate parameters, so GetRentacar, AirHelp or their technology providers may process technical, interaction or attribution information when a tool loads or is used.
Use “Cookie Settings” in the footer to reopen the preferences panel. If Advertising / Marketing is withdrawn, Fareora stops future Meta event firing immediately and stores the denied preference; Travelpayouts Drive will not load on subsequent pages. Withdrawal cannot guarantee removal of third-party cookies or information already processed by Meta, Travelpayouts, GetRentacar, AirHelp or another provider.
Deleting or blocking relevant cookies may prevent advertising or affiliate attribution but does not necessarily delete information already processed by an external provider. Consult Meta, Travelpayouts or the relevant provider’s privacy controls where applicable.
11. Do Not Track and similar signals
Browsers and devices may send privacy preference signals. There is not one universal response required in every location or supported by every service. Fareora will describe its response if future technology makes a particular signal relevant to active analytics or advertising functionality.
12. Changes to this Cookie Policy
Fareora may update this policy when website functionality, service providers or cookie practices change. The current version will display its “Last updated” date. The policy will not be used to imply that a future tool is already active.
13. Contact
Questions about cookies or current website technology can be sent to [email protected]. Include the page and browser involved if reporting a technical issue.