Privacy Policy
Last updated: November 20, 2026
This Privacy Policy explains how Natla s.r.l. processes personal data in connection with TheBooking website, WordPress plugin, customer area, licensing and platform services, subscription workflow, Envato migration programme, and support service.
It is intended to provide the information required by Articles 13 and 14 of Regulation (EU) 2016/679 (the "GDPR"). It does not treat acceptance of this Policy as consent to processing that relies on another legal basis.
1. Data Controller and Scope
The data controller is Natla s.r.l., with registered office at Via del Crocifisso 51, 00165 Rome, Italy ("Natla", "we", "us" or "our").
This Policy applies when you:
- visit thebookingplugin.com or use its customer area;
- purchase or manage a TheBooking subscription;
- activate or use TheBooking and its remote licensed features;
- request an Envato customer migration or related discount; or
- contact our support service.
If you operate a website using TheBooking, you normally determine the purposes and means of processing your own customers' booking and contact data. This Policy does not replace the privacy information that you must provide to those individuals.
Where Natla processes personal data contained in a functional service payload only to return a result on behalf of a business customer, that customer remains the controller and Natla acts as its processor. Any such processing must be governed by data processing terms that meet Article 28 GDPR.
2. Where We Obtain Personal Data
We obtain personal data directly from you, automatically from your browser or WordPress installation, from Paddle in connection with subscriptions, and from Envato when we verify an eligible purchase. We may combine these data only where necessary for the purposes described below.
3. Data, Purposes and Legal Bases
3.1 Website Delivery, Logs and Security
When you visit the Website, our hosting and network infrastructure may process your IP address, request date and time, requested URL, response status, referrer, browser and device information, and security or diagnostic events.
We process these data to deliver the Website, maintain availability, investigate faults, prevent abuse, and protect our systems. The legal basis is our legitimate interest in operating and securing the Website and services under Article 6(1)(f) GDPR.
3.2 Website Analytics
If you select "Accept analytics" in the cookie banner, we use Google Analytics 4 to understand Website use. Analytics data may include online identifiers, pages viewed, session events, approximate location derived from the IP address, and browser, device, and interaction information.
With the same consent, we record analytics events for key actions on the Website: opening the Paddle checkout, starting a free trial or completing a purchase, requesting a customer-area sign-in link, signing in, generating a download link and its version number, redeeming an Envato migration discount, and selecting a support email link. For checkout events, we send only the plan, Paddle price identifier, product name, billing interval, currency, amount excluding tax, tax amount, and Paddle transaction identifier. The transaction identifier prevents the same order from being counted twice. Because it could be matched with Paddle records to link an analytics session to an order, we treat it as personal data. We do not send your name, email address, billing address, payment details, licence identifiers, or authentication tokens to Google Analytics.
The legal basis is your consent under Article 6(1)(a) GDPR and the applicable rules on storing or accessing information on a device. Google Analytics is not activated if you decline. We do not use Google Ads through the Website.
3.3 Checkout, Subscriptions and Billing
Paddle.com Market Ltd acts as Merchant of Record and independent data controller for checkout, payment, invoicing, tax, fraud-prevention, and billing activities. You provide Paddle with data such as your name, email address, billing address, tax information, and payment details. Natla does not receive or store your full payment card details.
For licensing and subscription administration, Paddle provides Natla with limited customer and transaction information, including a Paddle customer identifier, subscription identifier, plan, subscription status, renewal dates, scheduled changes, and discount information. We may retrieve the customer name and email address when necessary to deliver a licence, send service communications, or provide access to the customer area.
We process these data to take steps at your request and perform the service contract under Article 6(1)(b) GDPR; to meet tax, accounting, and other legal obligations under Article 6(1)(c); and to prevent fraud and establish, exercise, or defend legal claims under Article 6(1)(f).
3.4 Licensing, Customer Area, Downloads and Updates
Our licensing systems process identifiers linked to your Paddle customer and subscription, the licence identifier and status, plan and entitlement data, renewal or scheduled-change dates, and cryptographic hashes of licence tokens.
When the Plugin is activated, validates a licence, checks for updates, downloads a release, or uses a licensed platform function, it may send the licence token, installation URL or domain, Plugin and file version, WordPress and PHP versions, locale, release channel, multisite and environment indicators, request time, source IP address, endpoint, result, and diagnostic information. We store the activation URL, activation time, development-site indicator, and last-seen time where needed to enforce the one-site licence and provide the service.
The customer area uses short-lived, passwordless links and session tokens. We process these data to authenticate customers, provision and validate licences, enforce entitlements, supply updates and downloads, operate licensed functions, prevent misuse, and troubleshoot faults.
The legal bases are performance of the contract under Article 6(1)(b) GDPR and our legitimate interests in service security, licence enforcement, and fraud prevention under Article 6(1)(f).
3.5 Slot Segmentation Service
Some Plugin functions send availability rules to our slot segmentation service. The payload may include licence claims, pseudonymous internal identifiers for services, providers and availability records, time zones, date ranges, durations, capacity limits, constraints, overrides, and related scheduling rules.
The service is not designed to receive booking content, customer or attendee names, email addresses, phone numbers, payment data, or calendar event content. The functional payload is processed in memory to calculate a response and is not stored in the service's application database. Limited request, error, and infrastructure metadata may be recorded for security and troubleshooting.
For licence, network, security, and diagnostic metadata that Natla uses for its own service purposes, the legal bases are performance of the contract under Article 6(1)(b) GDPR and our legitimate interest in maintaining a secure and reliable service under Article 6(1)(f). If a functional payload contains personal data, the customer determines the relevant legal basis and Natla processes those data on the customer's documented instructions to provide the calculation.
3.6 Envato Purchase Migration
If you request migration from an eligible Envato purchase, we process the purchase code and email address you submit. We send the purchase code to Envato for verification and may receive or record the Envato buyer username, item identifier, sale date, support expiry, purchase count, and validation outcome. We also record the Paddle discount, redemption status, relevant dates, and resulting subscription identifier.
These data are used to verify eligibility, issue and administer the migration offer, prevent duplicate or fraudulent redemptions, and resolve related claims. The legal bases are steps taken at your request and performance of the resulting contract under Article 6(1)(b) GDPR, and our legitimate interests in fraud prevention and defence of claims under Article 6(1)(f).
3.7 Support
When you request support, we process your email address, subject, message, selected topic, site URL, licence or account identifiers, and any information you choose to include. If you choose to include environment details, these may contain Plugin, WordPress and PHP versions, locale, multisite and environment indicators, and active-theme information.
Support messages are sent through our mail infrastructure and managed in our customer-support service. We use them to respond, troubleshoot, maintain service history, and defend claims. The legal bases are performance of the contract under Article 6(1)(b) GDPR and our legitimate interest in providing an effective and secure support service under Article 6(1)(f).
Please do not include special-category data, credentials, payment card data, booking-customer data, or other personal data that is not necessary for your request.
3.8 Legal Compliance and Claims
We may process and disclose relevant data where necessary to comply with a legal obligation, respond to a competent authority, prevent unlawful conduct, or establish, exercise, or defend legal claims. The legal bases are Article 6(1)(c) and Article 6(1)(f) GDPR, as applicable.
4. Cookies and Browser Storage
The Website uses the following browser storage:
- tbk_analytics_consent_v1: a necessary first-party cookie that records whether optional analytics were accepted or rejected. It expires after 184 days, approximately six months. We use it to honour your choice and avoid repeatedly showing the banner.
- _ga and _ga_<container-id>: Google Analytics cookies set only after consent to distinguish browsers and maintain session state. They are configured to expire 184 days after creation and not to renew their lifetime on each page view.
- thebooking-theme: a local-storage preference used to remember the light, dark, or system theme selected on your device. It remains until you change it or clear browser storage.
- thebooking.portal.session: session storage used only after passwordless authentication to keep the customer-area token in the current browser tab. The client limits it to 60 minutes, clears it on sign-out or expiry, and the browser removes it when the tab session ends.
Google Analytics user-level and event-level data are configured with the default two-month retention period. Advertising features and advertising-personalisation signals are disabled, and we do not use Google Ads. The retention setting does not necessarily remove aggregate reports that no longer directly identify a user.
You may withdraw analytics consent at any time. The control below disables further analytics collection, removes accessible Google Analytics cookies, clears the consent choice, and reloads the Website so that you can choose again. The same control is available as "Cookie settings" in the footer of every page. You can also delete cookies through your browser settings.
Website fonts and application code are served locally and do not require a browser connection to a public font or JavaScript CDN. When you open a page or dialog that shows subscription prices, such as the home page, the product pages and the trial dialog, the Website loads Paddle software to display prices localised for your country, including the applicable currency and taxes. Paddle software also loads a script from Paddle's ProfitWell service (public.profitwell.com). When you select a checkout action, the same Paddle software opens the checkout. In each case, Paddle and its delivery infrastructure receive technical network data such as your IP address, user agent, requested resource, time, and pricing or checkout integration context. Paddle uses your IP address to estimate your country for price localisation. Before you enter details in the checkout, the Website does not send Paddle your name, email address, or other identifying details.
The preference and session storage described above are necessary to provide functions requested by you or to maintain the security and usability of the Website. The legal bases are performance of the requested service under Article 6(1)(b) GDPR and our legitimate interests under Article 6(1)(f). We load Paddle to display localised prices on the basis of our legitimate interest in showing accurate prices, currencies, and taxes for your location under Article 6(1)(f) GDPR, and to open the checkout to take steps requested by you before entering into a contract under Article 6(1)(b).
5. Recipients and Service Providers
Personal data may be disclosed, only as necessary for the relevant purpose, to:
- IONOS SE, which provides the European-region virtual server used to operate our application services, including licence management and customer support;
- DreamHost LLC, which provides Website hosting in the US-East region and US-based mail and mailbox infrastructure. Support messages are managed through our customer-support service hosted on IONOS infrastructure;
- Paddle.com Market Ltd and its group and service providers, acting as Merchant of Record and independent controller for price localisation, checkout, billing, tax, invoicing, and related compliance;
- Google and its service providers, for Google Analytics only after consent;
- Envato and its group or service providers, acting as an independent controller of its marketplace data, when we verify a migration request;
- professional advisers, auditors, insurers, and public or judicial authorities where access is necessary and legally permitted.
Providers that process data on our documented instructions are appointed under Article 28 GDPR where required. Their personnel and our authorised personnel receive access only according to their duties.
6. International Data Transfers
The IONOS virtual server is configured in a European region. DreamHost processes Website and mail data in the United States. Paddle, Google, Envato, and their service providers may also process data in the United Kingdom, the United States, or other countries outside the European Economic Area.
Where Chapter V GDPR applies, transfers are based on an applicable European Commission adequacy decision, including the EU-US Data Privacy Framework for participating recipients where available, or on appropriate safeguards such as the European Commission's Standard Contractual Clauses, together with supplementary measures where required. You may contact us for information about the safeguard applicable to a specific transfer and how to obtain a copy.
7. Retention
We retain personal data for no longer than necessary for the stated purposes. The following periods apply unless a legal hold, dispute, or mandatory law requires a longer period for the data concerned:
- Website, API, proxy, and application logs: 30 days. Events isolated for investigation of a security incident may be retained for up to 180 days.
- Customer, subscription, licence, plan, and status records used to operate the service: for the contractual relationship and 24 months after it ends.
- Minimal contractual evidence, transaction identifiers, and legally required accounting records: 10 years from the relevant transaction or for any longer period required by law.
- Activation URL and last-seen information: while the licence is active and for 90 days afterwards.
- Licence-token hashes: while the token is valid; hashes of revoked tokens are retained for 90 days.
- Passwordless links and customer-area sessions: links expire after 15 minutes and session tokens after 60 minutes. The current customer-area token is kept in the browser's session storage and is cleared by the client on sign-out or expiry; the browser also removes it when that tab session ends.
- Detailed Envato migration data, including the raw purchase code: until the request is completed or expires and for 12 months afterwards. Minimal redemption evidence, including a one-way hash of the purchase code, item identifier, dates, and outcome, may be retained for 10 years from redemption.
- Customer-support requests: 24 months after closure. Data needed for a dispute or legal claim may be retained until the claim is finally resolved and, where necessary, for up to 10 years.
- Messages in the DreamHost mailbox after successful import into our customer-support service: 30 days.
- Data submitted for on-demand service processing: only for the time needed to process the request and return the result. Related limited technical logs follow the 30-day log period above.
- Encrypted rolling backups: 30 days, after which they are overwritten according to the backup cycle.
- Google Analytics: user-level and event-level data for two months; analytics cookies for 184 days from creation, as described above.
- Cookie consent choice: 184 days.
- Theme preference: until you change it or clear local browser storage.
Paddle, Envato, and other independent controllers determine their own retention periods for data they process for their purposes. Their privacy policies provide further information.
8. Whether Data Are Required
Analytics consent is optional and declining it does not prevent access to the Website. Providing the information required for checkout, licence provisioning, activation, authentication, and subscription management is necessary to enter into or perform the service contract; without it, we cannot supply the relevant service. Envato migration is optional, but we cannot verify or grant that offer without the requested purchase information.
Support information is voluntary, although we may be unable to investigate or answer a request if essential details are missing.
9. Your GDPR Rights
Subject to the conditions in the GDPR, you may request access to your personal data, correction of inaccurate data, erasure, restriction of processing, or data portability. You may object at any time to processing based on legitimate interests, including by explaining circumstances specific to you.
Where processing is based on consent, you may withdraw consent at any time without affecting processing carried out before withdrawal. You also have the right to lodge a complaint with the Italian supervisory authority, the Garante per la protezione dei dati personali, or with another competent supervisory authority.
We normally respond within one month. We may request information reasonably necessary to confirm your identity and may extend the response period where permitted by the GDPR.
10. Automated Decisions
Natla does not use the personal data covered by this Policy to make decisions based solely on automated processing that produce legal effects or similarly significant effects on you. We do not use Google Ads on the Website.
11. Security
We use technical and organisational measures appropriate to the risk, including access controls, encrypted communications, token hashing, restricted administrative access, backups, monitoring, restrictive browser security headers, removal of passwordless tokens from the visible URL before third-party analytics can run, and procedures for managing security events. No internet transmission or storage system can be guaranteed to be completely secure.
12. Children
The service is a commercial WordPress product intended for adults and organisations. It is not directed to children, and we do not knowingly collect children's personal data through the service. If you believe that a child has provided personal data to us, please contact us so that we can investigate and take appropriate action.
13. Third-Party Services and Links
The Website and Plugin may link to or integrate with third-party services. Those parties may act as independent controllers and apply their own terms and privacy policies. We encourage you to review them before providing personal data.
14. Changes to This Policy
We may update this Policy when our processing, providers, or legal obligations change. We will publish the revised version here, update the date above, and provide a prominent notice or direct communication where the change materially affects individuals.
15. Contact and Rights Requests
For questions, GDPR requests, or complaints concerning Natla's processing, contact us by email: Send email