Skip to content

Abilasha Devi · Lina Amad

Privacy policy

Last updated 30 September 2026

This page explains which personal data abilashadevi.com collects, why, who else handles it, how long it is kept, and what you can ask for.

1. Who is responsible

Lina Amad, who teaches as Abilasha Devi, is responsible for your personal data (the “controller” under the EU General Data Protection Regulation, GDPR). For anything about your data, write to her at alflina68@yahoo.com.

2. What is collected, and why

Writing to Lina (contact form)

Your name, email address, message and the topics you tick. Lina uses them to reply to you. The legal basis is your consent, given with the checkbox; you can withdraw it at any time.

Asking for a session

The practice, format, number of people, preferred time of day and language, a date and a place if you give them, your name, your email address or WhatsApp number, and your note. Lina uses them to arrange the session with you. Legal basis: steps you ask for before an agreement (Art. 6(1)(b) GDPR).

Reserving chairs at the communal table

Your name, email address, the evening and chairs you choose, and any allergies or preferences you write. They are used to keep your chairs and prepare the meal. Legal basis: the reservation you make (Art. 6(1)(b)).

Booking a session online (once online booking opens)

The session, format, date and time, your name, email address and note, and the place for a session in person. They are used to make the booking, to send you the calendar invitation (with a Google Meet link for online sessions), and to let you cancel through a private link. Legal basis: the booking (Art. 6(1)(b)).

Health information

If you tell Lina about an injury, a health condition or an allergy, it is used only to adapt the session or the meal. You give your explicit consent by writing it (Art. 9(2)(a)), and you can ask for it to be deleted at any time. Please share only what is needed.

Technical data

As with any website, the servers that deliver these pages receive your IP address and browser details, to send you the pages and protect the site from abuse. The site’s own code does not store your IP address. When you book online, a scrambled code derived from your IP address, never the address itself, is kept for up to 24 hours to stop repeated abuse.

The site uses no analytics, no advertising, no tracking pixels and no social-media plug-ins. Its fonts and its map are served from the site itself, so visiting it does not contact Google or any social network.

3. Cookies and browser storage

The site stores only what its own features need, so it does not ask for cookie consent:

  • NEXT_LOCALE: a cookie that remembers the language you choose with the EN/IT switch. It is deleted when you close the browser.
  • lina-theme: browser storage that remembers light or dark.
  • lina-intro-v2: browser storage that plays the opening animation once per visit. It is cleared when you close the tab.

There are no third-party cookies.

4. Who else handles your data

Lina uses these services to run the site. They handle data on her behalf, or under their own terms where stated.

  • Netlify, Inc. (United States) hosts the website, receives the forms, stores table reservations and emails Lina a notification of each message or reservation.
  • Railway Corporation (United States), with servers in the Netherlands, runs Lina’s admin and the database where messages and bookings are kept.
  • Yahoo provides Lina’s email account, where those notifications arrive.
  • Google (Google Calendar and Google Meet): for sessions booked online, the booking is added to Lina’s Google calendar with you as a guest, and Google sends you the invitation, the Meet link and any change. Google handles this under its own privacy policy.
  • Hostinger registers the domain name and keeps a backup of the previous website, including messages sent through its contact form.

If you contact Lina on WhatsApp or by phone, that conversation happens outside this website and WhatsApp’s own terms apply.

Some of these companies are based outside the European Union. Where your data leaves the EU, the transfer relies on the safeguards the GDPR recognises, such as the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses.

Your data is never sold and never used for advertising.

5. How long it is kept

  • Messages and session requests: up to 2 years after your last contact.
  • Reservations and bookings: up to 2 years after the date booked, or longer where the law requires it (for example accounting records for a paid booking).
  • A chair or time held while you fill in your details: deleted when its 10 minutes run out.
  • The anti-abuse code derived from your IP address: 24 hours.

6. Your rights

You can ask Lina to show you the data she holds about you, correct it, delete it, limit its use, object to its use, or give it to you in a common format. Where you gave consent, you can withdraw it at any time; this does not affect what was done before. Write to alflina68@yahoo.com; you will get an answer within one month.

If you think your data has been handled wrongly, you can complain to the data protection authority where you live or work. In Italy that is the Garante per la protezione dei dati personali (garanteprivacy.it).

7. The Google Calendar connection

Lina’s admin connects to one Google account, the one whose calendar holds her sessions. With that account’s permission it:

  • reads the account’s email address, to show which account is connected;
  • checks when the calendar is busy (free or busy only, with no event titles or details), to offer only free times. Busy times are kept in memory for about a minute and never stored;
  • creates, reads and cancels the calendar events of bookings made on this site, with the guest invited.

It stores the email address, the list of permissions granted, an encrypted access key and the identifiers of the events it creates, and nothing else from Google. Data received from Google is not shared with anyone, not sold, not used for advertising and not used to train AI models. Disconnecting in the admin revokes the access at Google and deletes the stored key. Access can also be removed at any time in the Google account’s settings (myaccount.google.com/permissions).

The use and transfer of information received from Google APIs by this website adheres to the Google API Services User Data Policy, including the Limited Use requirements.

8. Changes

This page changes when what the site does changes. The date at the top shows the current version.