Last updated: 5 October 2026
1. About this Cookie Policy
This Cookie Policy explains how Nebari uses cookies and similar technologies when you visit or use getnebari.com.
Nebari is operated by:
Dmitriy Perederenko
Self employed professional in Spain
NIF: Z0704881M
Calle San Jose 39, 2
San Juan de Alicante, 03550
Spain
Email: hello@getnebari.com
Website: getnebari.com
This Cookie Policy should be read together with the Privacy Policy.
2. What cookies are
Cookies are small pieces of information stored on your device by a website.
They can be used for purposes such as maintaining a login session, remembering technical settings, protecting accounts and providing website functionality.
Some similar technologies may perform comparable functions without using traditional browser cookies.
3. Cookies used by Nebari
The following list describes cookies observed during a production audit and the Nebari email-verification cookie specified below. Durations may be refreshed when cookies are used or renewed.
__cf_bm
Provider: Cloudflare. Purpose: security and bot protection. Duration: approximately 30 minutes of inactivity. Category: strictly necessary / security.
cf_clearance
Provider: Cloudflare. Purpose: stores the result of a Cloudflare security challenge so that it does not need to be repeated. Duration: approximately one year as observed in production; the actual duration may depend on Cloudflare configuration. Category: strictly necessary / security.
__Host-appgarden-visitor
Provider: OpenAI / ChatGPT Sites hosting platform. A technical cookie set by the hosting platform. Its exact platform-side purpose is not publicly documented in sufficient detail. Observed duration: approximately 90 days. It is not classified here as advertising, analytics or strictly necessary because its precise purpose and exemption status have not been confirmed.
__Secure-better-auth.session_token
Provider: Nebari / Better Auth. Purpose: authentication and maintaining the signed-in session. Duration: 7 days when Remember me is enabled. When Remember me is not enabled, the application uses a shorter, session-style authentication period according to its configuration. That unchecked case was not directly tested in the production browser audit, so no observed browser duration is claimed for it. Category: strictly necessary / authentication. This cookie is removed on logout.
bonsai-session
Provider: Nebari. Purpose: maintains the anonymous visitor identifier used to associate guest calendar data before login. Duration: approximately 365 days, refreshed when used. Category: functional / strictly necessary for guest data persistence. This cookie can remain after logout; it is not the signed-in authentication cookie.
nebari-verification-pending
Provider: Nebari. Purpose: remembers that email verification is pending so the requested registration flow can direct this browser to the verification screen. It contains only the value 1, not an email address, password, verification token or link, and does not grant access to an account. Scope: getnebari.com only (host-only; no Domain attribute), Path=/. Duration: up to one hour (Max-Age=3600), removed after successful verification, sign-in or logout. Attributes on HTTPS: HttpOnly, Secure and SameSite=Lax. Category: technical / registration-flow support; not used for analytics or advertising.
The hosting platform may set technical cookies outside Nebari's direct control. These cookies are disclosed here without assuming that every hosting cookie has been legally classified as exempt from consent.
4. Website analytics
Nebari does not currently install optional analytics cookies.
5. Product analytics
Nebari may collect limited product usage information directly within its own infrastructure.
This may include events such as account creation, creation of a tree, creation of a calendar activity, photo uploads or use of particular features.
This information is used to understand how Nebari is used and to improve the Service.
Nebari aims to avoid including unnecessary personal information or user generated content in product analytics events.
More information about this processing is available in the Privacy Policy.
6. Cloudflare security technologies
Cloudflare security cookies observed in production include __cf_bm and cf_clearance. Their purposes and observed durations are described above. The presence of cf_clearance alone does not establish which Cloudflare challenge or pre-clearance configuration issued it.
7. Consent
Nebari does not intentionally use advertising or marketing cookies and does not currently install optional analytics cookies.
Nebari does not currently display a cookie consent banner. This does not mean that every technical cookie set by the hosting platform has been legally classified as exempt. The precise purpose of __Host-appgarden-visitor remains insufficiently documented, as explained above.
If Nebari introduces optional cookies or similar technologies that require consent, they will not be activated until users have received the required information and given valid consent. Where required, users will be able to reject those technologies as easily as they can accept them.
8. Browser controls
Most browsers allow users to inspect, block or delete cookies through browser settings.
Blocking cookies that are technically necessary may prevent authentication or other parts of Nebari from functioning correctly.
9. Changes to this Cookie Policy
Nebari may update this Cookie Policy if the technologies used by the Service change or if applicable legal requirements change.
The current version will be published on getnebari.com and will show the date of the latest update.
10. Contact
Questions about cookies or privacy may be sent to: