Public notice and consent management
Cookie Policy
Cookies, similar technologies, and user choices
Effective date: 10 July 2026
Last updated: 14 July 2026
Version: 1.0
Implementation rule
- Analytics, non-essential preference, and advertising cookies are blocked before the user makes a choice.
- The first layer of the banner offers equally prominent options: “Accept all”, “Reject non-essential”, and “Customise”.
- The exact list of active technologies must be visible in the “Cookie settings” panel and match the actual implementation.
2. Who uses the technologies
The Platform is operated by Rentify SRL. Some technologies are supplied by third parties, including Google and Meta. On the Paynet page, the payment processor controls its own cookies and security measures under its own notices.
3. Cookie categories
| Category | Purpose | Consent |
|---|---|---|
| Strictly necessary | Session, authentication, security, fraud prevention, basket, booking, cookie choice, and checkout. | No, where indispensable to the requested service. |
| Preferences | Language, display, options, and settings that are not indispensable. | Yes, where not strictly necessary. |
| Analytics | Measurement of visits, errors, and Platform use, for example through Google Analytics. | Yes. |
| Advertising and conversions | Conversion attribution, campaign measurement, and remarketing, for example through Google Ads and Meta Pixel. | Yes. |
4. Register of active technologies
For each active technology, the “Cookie settings” panel must show its name, provider, purpose, category, duration, and whether it is a first- or third-party cookie. The register in the panel is updated whenever the implementation changes materially.
The examples below describe technologies that may be used only if they appear in the live register and are configured in accordance with this Policy:
| Provider / example | Purpose | Indicative duration | Category |
|---|---|---|---|
| Rentify – session and security | Authentication, booking, security, and remembering cookie choices. | Session or the technically necessary period. | Strictly necessary |
| Google Analytics – _ga / _ga_<ID> | Statistics and session state. | Up to 2 years, depending on configuration. | Analytics |
| Google Ads – _gcl_au and similar | Conversions and advertising. | Normally up to 3 months. | Advertising |
| Meta Pixel – _fbp and similar | Conversions, analytics, and Meta advertising. | Normally up to 3 months. | Advertising |
| Paynet | Security and payment processing on the Paynet page. | According to Paynet's notice. | Controlled by Paynet |
Names and durations may be changed by providers or through Rentify's configuration. If the live register cannot be kept accurate, the relevant non-essential technology must be disabled until it is updated.
6. Tag blocking and Consent Mode
Rentify's standard configuration blocks in advance: analytics and advertising tags do not load or transmit signals before consent. If Rentify later adopts an advanced configuration that sends cookieless signals before consent, that change must be legally assessed, clearly described here, and reflected in the banner before activation.
7. Evidence and duration of the choice
Rentify may retain evidence of the choice, including the consent identifier, date and time, categories, banner and Policy versions, and a minimal technical identifier. The choice is normally requested again after 6 months, after a significant change to providers or purposes, or if the evidence is no longer available.
8. Withdrawing and changing the choice
The user may change or withdraw the choice at any time through the permanent “Cookie settings” link in the Platform footer. Withdrawal stops future activation of refused categories to the extent technically possible and is as simple as giving consent.
9. Browser settings
Cookies may also be deleted or blocked in the browser. Blocking strictly necessary cookies may prevent authentication, preservation of a booking, or payment. Browser settings do not replace the Rentify panel for controlling tags that do not use traditional cookies.
10. Data sent to third parties
With the user's consent, Google and Meta may receive device, IP, page, event, and online identifier data and combine it under their own policies. Rentify does not include document data, full payment numbers, passenger names, detailed routes, or free-text fields that may contain sensitive information in URLs, event names, or parameters.
11. Audit and updates
Rentify scans cookies and tags before launch and after relevant changes to the site, tag manager, or providers. Any unidentified technology is investigated and, if not strictly necessary, blocked until it is classified and disclosed.
12. Changes and contact
The Policy may be updated when technologies or legal requirements change. Questions and requests: support@rentify.md, +373 60 650 806.