Privacy

What we collect when you look at the retreat, choose a room, register your interest in ARIA, ask a question (here or through our form on Instagram) or start a booking, why, and how to have it removed.

Who is responsible

Aria retreat SA is responsible for the details you give us on this site. Questions and requests: privacy@ariaretreat.com.

What we collect, and why

We answer your question, and handle a booking you start, because you asked us to. Analytics, advertising, aggregate counting and existing visit records are separate systems described below, with their respective choices. Registering is never a booking, and no payment details are asked for or stored.

Choosing a room and sending us a question work without any of these permissions. Choosing a room does not hold it and is not a booking.

The base statistics description below remains applicable outside the separately configured new window or when the new collection is off. For the proposed, active or retained description of the updated retreat screens, see their aggregate counting section.

Counting for everyone, on our server — from 16 November 2026, 11:50 until 30 November 2026, 11:50 (Athens time)

Between these two dates only — no visit of yours is counted before or after them — every page our server sends is counted: which page, whether it loaded, whether it was a fresh visit, a reload or a return, which room the address named when you opened the room screen or the question page, whether a form you sent was saved or failed (a category, never its content) and how long our server took. To do this we read the technical details every request carries — your IP address, your browser's description, the site the link came from — for a moment only, to leave out automated visits and to sort requests into a few classes: which browser engine, whether the link came from Instagram, which of our own campaign links, a reload. None of that is stored; what we keep is a count per day, with no visit number and no identifier. We count on the basis of our legitimate interest in making the page work and understanding where it fails people (GDPR Art. 6(1)(f)); you may object at any time while it runs — under Privacy choices, or by writing to privacy@ariaretreat.com, and we reply with how to turn counting off in your browser (the counts hold nothing by which we could find yours) — and a browser that has said “No thanks” or turned counting off is left out of these page counts as a courtesy (a form you send is always recorded: it is your own request to us and has a business record regardless). Day totals are kept for 13 months, then as weekly totals for up to 25 months.

Counting in the page, unless you object — from 16 November 2026, 11:50 until 30 November 2026, 11:50 (Athens time)

Between these two dates only, when the retreat page, the room screen or the question page opens, a small script of ours notes, in the page's own memory, a set of yes/no facts about that one visit to the page: that it was shown, how you reached it (a fresh visit, a reload, back or forward — also from your browser's memory of the page — or a move inside the site) and whether it opened out of sight, how long it stayed on screen while in use (10 and 30 seconds), how far you scrolled, which sections came into view, whether each stayed on screen for five seconds and which you came back to, which prices and buttons were on screen, which buttons you tapped and whether you tapped one control several times in quick succession, which questions you opened and whether each stayed open on screen for five seconds, whether you chose or changed a room, whether the form was started, sent or refused by the browser's own checks, how fast the page loaded and whether a script error occurred, and a few combinations of these in the same visit (for example, a price seen and then a button tapped, or the rooms looked at without a choice). It sends those facts, as yes/no marks only, to our own statistics server, which adds each one into a day's total — and counts any mark it refuses, by the reason — and keeps nothing else: no identifier, no time of day, no order of events, no text, no address, no cookie, and no record of the individual send. The first send happens as soon as the page appears; a few more follow while you read, when you switch to another app or tab, and when you leave — and the marks note whether such a send went while you read and when you switched away. Your IP address and browser description are used for seconds to drop automated traffic and to note the browser engine, then discarded. These totals never reach Meta or PostHog, are never combined with your registration or question, and are never used for adverts. We do this on the basis of our legitimate interest in improving the page (Art. 6(1)(f)). You may object at any time while it runs: turn “Aggregate counting” off under Privacy choices, or use this link if scripts are off (before 16 November 2026, 11:50 and after 30 November 2026, 11:50 that page only says when the counting runs or ran). The objection takes effect at once in this browser; marks already added to a day's total cannot be taken back. The setting is kept in this browser's choice cookie.

Aggregate counting on the updated ARIA retreat pages

The following describes the configuration for the experience, Ensuites & Prices and inquiry screens for the September 2027 retreat. It replaces the older page-specific examples only during the new enabled window on those three screens; other pages retain their existing definitions. The configured window is from 2026-11-16 11:50:00+02:00 (Europe/Athens) until 2026-11-30 11:50:00+02:00 (Europe/Athens), with the end excluded. A configured window does not mean that collection ran throughout it: collection also needs its server switch, matching content and your counting choice, and stops outside the window.

During this window the specific definitions below apply to these screens only when the new collection is enabled and its binding is valid.

We keep totals to understand whether the pages work and which information is useful: sections and prices shown, questions opened, gallery and programme controls used, en-suite comparisons, and forms started or submitted. We also count image problems and broad page-speed, layout and response bands. This layer creates no visitor identifier, stores no typed values or individual journey, is kept apart from inquiries and visit records, and is not sent to Meta or PostHog or used to choose adverts. Turn it off to stop further browser collection and server page counting; unsent marks are discarded. A request already in transit may still arrive, and an individual contribution already in a total cannot be located or removed. Separate operational counts can still record a form response or committed inquiry. Your choice is saved in this browser's existing choice cookie.

We also keep separate totals showing whether the opening and later content appeared on screen, whether our privacy notice appeared and its choices were opened, and whether it remained unanswered when the page was first hidden. Progress past the opening counts only actual page text visible outside the notice and other fixed overlays; no answer is not refusal. Browser attempts, answers received by the server and newly saved permission records are separate totals, with analytics and advertising answers kept apart. Receiving an answer is not proof of a valid permission or a successful save. Saving a privacy choice, including its yes/no answers, can still be counted as a separate operation when browser counting stops; we do not create a visitor identifier or join these totals to inquiries. The existing choice to stop aggregate browser counting still applies.

For loads where aggregate counting remains enabled, a single aggregate snapshot at the first page hide or screen end combines each privacy-choice state with whether content after the opening was seen by then. Analytics and advertising choices remain separate. Unanswered is not refusal, and unavailable choices are kept separate. A counting-off load produces no behavioural snapshot. These are observed load totals, not unique people, final choices or proof that agreeing causes engagement.

Separately, we keep coarse device, operating-system and explicit app-browser categories as independent weekly document totals, without joining them to activities, campaigns or geography. Browser descriptions are used transiently for these estimates, not retained as descriptions. Only fixed, complete weeks are exported. Small cells and related totals are suppressed; percentages are withheld for small samples. These rules reduce disclosure risk but do not guarantee anonymity.

Each page can add a presence mark for a closed category, not an event stream: visible and active time, scrolling, section exposure and dwell, FAQ use, actual button exposure and taps, prices seen, deliberate en-suite comparisons, gallery and programme use, visible-image state, observed interface results, and broad initial-window performance or error categories. First-hide and final states are separate observations, not a way to identify why someone left. Repeated price locations are capped per option. Comparing an option is separate from following its inquiry link. No price is inferred on the experience screen.

Server totals distinguish document requests, in-site requests and excluded or unknown request types; they are not confirmation that a person saw a page. Arrival tags use a fixed campaign list plus missing and other categories. The server uses technical headers transiently, without keeping raw user-agent, referrer URLs or IP-derived identifiers in this aggregate layer. Missing or lost observations are not treated as no activity.

Base daily totals keep the existing limits of up to 13 months, and weekly totals up to 25 months. New opening, privacy-notice, gallery, programme, comparison, image, observed interface, initial-performance and response-health families have daily totals up to 30 days and closed-week totals up to 90 days. Coarse context, when enabled, is weekly from its first storage and kept up to 90 days. Daily and weekly copies are never added together. Staff, demo and burst categories keep their existing shorter legacy limits. The separately configured early outcome recorder keeps its own stated deletion date.

Operational save/response counts are a separate population, with no browsing, campaign or context join. A successful HTTP response is different from a committed inquiry; a replay is different from a new inquiry. A recorded email-channel acceptance is not inbox delivery. Dated email-attempt and final-failure totals are unavailable where the source cannot support them. This does not change inquiry records, their retention, or permission to send marketing.

PostHog analytics and Meta advertising remain separate permission choices. Restored section reporting goes to PostHog only with analytics permission; the Pixel does not run on name/email screens. Existing visit records remain a separate disclosed system, and are not joined to the new aggregate totals. Use Privacy choices or turn aggregate counting off.

Measuring our Instagram adverts with Meta, and choosing who sees them — only if you allow it

The privacy notice asks about this separately from usage analytics. If you allow it, on the retreat page and the room-choice page we load Meta's measurement script (the Meta Pixel), and our server sends Meta a copy of the same events (Meta's Conversions API). Meta sets its own cookies on this site (_fbp, and _fbc when you arrived from an advert) and receives: that you viewed those pages, which room option you chose and for which retreat, the advert's click identifier, and your browser's technical description (its “user agent”). Because the script runs in your browser, Meta's servers also see your IP address, as with any request to a website. Our server does not send Meta your IP address, your name, email or phone number, or any price or payment amount. Meta's script is kept silent wherever you are asked for your name or email: it sends nothing beside the booking form or the question form, and on the retreat page it stops as soon as you start filling in the notice form.

When you send us a question with the question form, our server (not Meta's script, which does not run on that page) tells Meta only that a question was sent, for which retreat, from which page and which advert brought you, with the same Meta cookies and technical description as above. Never what you wrote, the room you asked about, your name, email or phone number. Nothing is sent if the question could not be stored.

We use this to see which adverts lead people to choose a room or ask a question, to improve our adverts, and to choose who sees them: for example, to remind people who chose a room but have not asked anything yet, and not to keep advertising to people who already asked us a question. For this, Meta puts visitors into groups — for example, people who viewed the retreat in the last 30 days without choosing a room — so that our adverts can be shown to them again, or no longer shown to people who have already asked us a question. Meta builds these groups from the events above and the identifiers those events carry: Meta's cookies (_fbp and _fbc), the advert's click identifier, your browser's technical description, our reference number for a room choice or a question sent (so that Meta counts each once) and, for what Meta's script sends from your browser, your IP address. Meta keeps these groups; we see only their approximate size. We do not upload lists of names, email addresses or phone numbers to Meta. Meta uses this data to show our adverts to people more likely to be interested, and also processes it under its own terms and privacy policy. If you do not allow it, Meta's script is not loaded and nothing about your visit is sent to Meta. You can withdraw at any time with “Privacy choices” at the foot of the page: the script stops at once, the Meta cookies on this site are deleted, nothing more is sent to Meta from that browser, and what our server had not yet sent to Meta from your current visit number is dropped. That reaches what was done under your current visit number, which lasts up to 24 hours (one set before 29 September 2026: up to 90 days); for what you registered, asked or booked before that, write to privacy@ariaretreat.com and we will apply your “no” to your registration (“Cookies and our records”). A request does not change the answer stored in your browser: in a browser that still says yes, what that answer allows — PostHog, Meta's script — runs again when you next visit, until you choose No under Privacy choices there. Unsubscribing from our emails is a separate choice; with it our server also stops sending advert measurement for what you registered, asked or booked (Meta's script in your browser follows the answer stored there).

Usage analytics and recordings — only if you allow them

If you allow it in the notice, PostHog records your visits — everything you type is hidden before it leaves your browser — and notes which parts of the page you reach, how far you scroll and any errors; you are known there by a random identifier only. With the same permission our server adds PostHog's identifier to the steps of your visit it records (a page opened, a form started, a room chosen), records whether the retreat page was in the foreground for ten seconds and whether the first room's price came into view (and that this was measured), and sends PostHog a copy of the steps it records (for example a room chosen, a question sent, a booking started, a deposit paid) under that identifier — with the page version, the kind of device, the room and, for a booking, the number of people and the price; never your name, email or a confirmation link. If you do not allow it, PostHog is not loaded, and none of these — PostHog's identifier on the steps, the foreground and price records, the copies for PostHog — is kept or sent; the steps themselves are recorded as “Cookies and our records” describes. Withdraw under Privacy choices: PostHog stops in your browser at once, and from then on our server adds none of these for that browser and drops the copies still waiting from your current visit number. That reaches what was done under your current visit number, which lasts up to 24 hours (one set before 29 September 2026: up to 90 days); for what you registered, asked or booked before that, write to privacy@ariaretreat.com and we will apply your “no” to your registration (“Cookies and our records”). A request does not change the answer stored in your browser: in a browser that still says yes, what that answer allows — PostHog, Meta's script — runs again when you next visit, until you choose No under Privacy choices there. What was already sent cannot be called back, and what PostHog already holds is not removed by withdrawing. Unsubscribing from our emails is a separate choice and does not change this permission. Details of how a withdrawal is applied

How a withdrawal is applied, in detail

If you do not allow it, PostHog is not loaded and our server records and sends none of this. You can change your mind at any time with “Privacy choices” at the foot of the page. If you withdraw it, PostHog stops in your browser at once, and from the moment our server receives your answer until your permission reaches it again, it records none of the above for that browser, makes no new copy for PostHog of anything done from it — including the confirmation of a registration made there, a confirmation link opened there, and a deposit paid for a booking started there — and does not send the copies still waiting to be sent. Allowing it again later does not send those either. An “Allow” you gave just before withdrawing that reaches our server after your no is ignored when our server can tell it came first; it may not be able to when the notice's own message of your no has not reached it before that “Allow”, when you said no on a page opened before our notice began numbering its answers on 24 September 2026, or when your device's clock was set back between the two, and that “Allow” then counts until our server next reads your answer from your browser. A no given to an earlier version of this notice still counts as a no. The copy of a registration's confirmation belongs to the browser you registered in and needs its permission: opening the link in another browser that has not answered this notice does not stop it, but opening it — the first time or later, even once the link has expired — in one that has said no does, unless the copy has already been sent, or is being sent, by then. In another browser, a no given only after the link was opened there stops the copy, if it has not been sent by then, only when that opening confirmed the registration or caused the copy to be made. A request our server suspects is automated — an email security scanner checking the link before you open it, for example, though some real browsers that send little about themselves are suspected too — confirms the registration but makes no copy; one can be made only when the link is later opened in a browser it does not suspect, under the same rules, and never once the browser the suspected request came from has said no. A copy already sent, or being sent, when your answer reaches our server cannot be called back, and withdrawing does not remove what PostHog already holds; what our own server has already recorded is kept.

What a “no” reaches

A “no” under “Privacy choices” applies at once to this browser and to what was done under its current visit number, which lasts up to 24 hours (one set before 29 September 2026: up to 90 days). For what you registered, asked or booked before that, write to privacy@ariaretreat.com and we will apply your “no” to your registration. A request does not change the answer stored in your browser: in a browser that still says yes, what that answer allows — PostHog, Meta's script — runs again when you next visit, until you choose No under Privacy choices there. Unsubscribing from our emails is a separate choice.

Cookies and our records

Cookies. aria_sid: a random visit number set by our server on your first visit to one of our pages, before you have answered anything (not on our privacy pages or a confirmation link). It lets us treat your requests as one visit in our records, keeps a record of the privacy answers given with it, remembers which version of a page you were shown, and limits abuse of the question form. With your advert-measurement permission, the reference number Meta receives for a room choice is worked out from it, so that Meta counts the choice once; with your usage-analytics permission, PostHog's random identifier is worked out from it. It cannot be read by scripts, is never itself sent to Meta or PostHog, and expires 24 hours after it is set (one set before 29 September 2026 lasts up to 90 days); your next visit then gets a new one. aria_consent: set only when you answer the notice, tick the optional box on the registration form, or turn aggregate counting off or on: your two answers, which version of the notice you answered and, if you made one, your aggregate-counting choice (a flag shared by everyone who made the same choice, not an identifier); 180 days. aria_internal: our own team's browsers only. Only with your permission: PostHog's identifier and session, stored in your browser by PostHog's script; Meta's _fbp, set by Meta's script, and _fbc, the advert's click identifier (90 days). Saying no to advert measurement deletes Meta's cookies at once. Aggregate counting sets and reads no cookie of its own.

Our records of a visit. Against the visit number our server keeps, for the retreat pages, the steps of a visit — a page opened (noted when the page's own script starts, which can be a moment before it appears on your screen, or without it ever appearing, for example when an app loads it ahead), a tap on the main buttons, a form started, a room chosen or changed — with the kind of device and whether an automated visit was suspected; which of our advert links brought you only with your advert-measurement permission; PostHog's session identifier only with your usage-analytics permission. From 29 September 2026, 30 days after each record is made the visit number is removed from it, with PostHog's session identifier and any advert click identifier; the same happens to our copies of what we sent to Meta and PostHog (a copy still waiting to be sent: once it is sent or dropped) and to our note of which version of a page you were shown. What happened stays. Two reference numbers that were worked out from the visit number stay too — the one Meta received for a room choice, and PostHog's identifier — so such a record can still be matched to a visit number we keep with a privacy answer (below). Records made before 29 September 2026 keep the visit number for now. Copies of these records are also kept in our server's database backups, on the same server. The backups are not encrypted. Each backup is deleted at the first nightly run after it is 14 days old.

A registration is kept with your email address, not with the visit number, except for: the record of the advert that brought you, with your advert-measurement permission (30 days); with your usage-analytics permission, the confirmation link we email you (until 30 days after it is used or expires) and our copies for PostHog (as above); the record of your confirmation, if our server suspected it came from an automated check and you had allowed usage analytics (30 days); and a record naming the visit number, when a privacy answer given with it reached your registration (kept with the permissions, below). A question is kept with the visit number for 30 days, like the other steps. A booking stays linked to the visit number of the browser it was started from for as long as the booking is kept, because the permissions given in that browser decide what is sent about the deposit and whether it counts as a test.

Withdrawing, and your visit number. Usage analytics, advert measurement and our emails are three separate choices. A “no” under Privacy choices applies at once to this browser and to what was done under its current visit number: what your browser and our server would still do for it, including copies still waiting to be sent, and what you registered, asked or booked with it. A visit number lasts up to 24 hours (one set before 29 September 2026: up to 90 days); after that your browser has a new one, and a “no” given then applies to your browser and the new number only. It does not reach what was registered, asked or booked under the old number, nor what our server still sends or copies under that number's permission: a copy whose earlier sending failed (within minutes for PostHog; for Meta, never more than 24 hours after a room choice or 7 days after a question), or a copy for PostHog of a deposit paid later, or of a registration confirmed later from a browser that has not said no. For those, write to privacy@ariaretreat.com: we apply your “no” — to usage analytics, advert measurement or both — to your registration, questions and bookings and to the visit numbers you used for them, and from then on our server sends PostHog and Meta nothing more about them; what was already sent cannot be called back. A request does not change the answer stored in your browser: in a browser that still says yes, what that answer allows — PostHog, Meta's script — runs again when you next visit, until you choose No under Privacy choices there. Unsubscribing from our emails is a separate choice; with it our server also stops sending advert measurement for what you registered, asked or booked, but not usage analytics, and it does not change the answer stored in your browser. So that a “no” and your request can reach across in this way, we keep only the pair “this visit number, this contact”, with nothing about the visit, for 90 days after the visit began: we cannot tell a 24-hour visit number from a 90-day one set before 29 September 2026, so we keep every pair that long.

The permissions you give in the notice or with a question are kept with the visit number they were given with, as the record of what you allowed and when. If we take a visit out of our figures (our own team's test visits, for example), its visit number stays on that list.

Who else handles your details

Our emails, both the automatic ones and our personal replies, are delivered by Resend. Email you send to our addresses reaches us through Forward Email, and we read and answer it in our Google (Gmail) mailbox; we keep what you send through our form on Instagram in a private Google spreadsheet. The site is hosted with DigitalOcean, and — only with your permission — usage analytics are processed by PostHog on servers in the EU. These act only on our instructions. Only with your permission, Meta receives the advert-measurement data described above and uses it partly under its own terms. When you use our form on Instagram, Meta collects the details for us and also handles them under its own terms. We do not sell or rent your details to anyone.

How long, and how to leave

Every automatic email from us has a link that stops all further contact at once, except the confirmation and reminders of a booking you have made; to stop those, write to us at the address above. Our personal replies are written by hand: answer one with “stop”, or write to us at the address above, and we stop at once. We keep what you send us through our form on Instagram for 12 months after our last exchange with you, unless you ask us to delete it sooner. You can also ask us at the address above to see, correct or delete what we hold, and we will do so. If you live in the EU or the UK you may also complain to your data protection authority.

Whole-house retreat enquiries

Our retreat hosting enquiry form is for organisers asking about exclusive use of the house. We store your name, email, preferred dates, date flexibility, number of nights, group size and message to answer your request and prepare a personal proposal. Your enquiry is forwarded to the ARIA team through Resend. This form does not reserve dates, take payment, subscribe you to marketing or start the September retreat’s email sequence.

For new enquiries, the current retention period in our website database is 180 days after receipt. Enquiries already sent follow the retention period shown when you contacted us; their website records are automatically removed when that period ends. Correspondence with our team is handled separately for your request and any agreed arrangements. You can ask us for earlier deletion using the contact address above.

The existing privacy choices apply to usage analytics and aggregate counting on this page. A separate random identifier lets us count browser visits separately from the scheduled retreat; its record is kept for up to the session lifetime described above, measured from the first visit to this page. The Meta Pixel does not run on this page, and ARIA does not send whole-house enquiry events to Meta.

You can ask us at the contact address above to access, correct or delete your enquiry. Personal replies are handled by the ARIA team.