The Next Beacon ("Lorenly", "we", "us") is committed to protecting your personal data. This Privacy Policy explains how we collect, use, share, and retain personal data in connection with our booking platform - as a controller for our own purposes, and as a processor for the businesses that use Lorenly (see section 1).
Which law applies. We are established in the Netherlands, in the European Union, so our processing is governed by the EU General Data Protection Regulation (GDPR) and the Dutch GDPR Implementation Act (Uitvoeringswet AVG). Where we process the personal data of people in Switzerland, the Swiss Federal Act on Data Protection (FADP) can apply in addition. Nothing in this policy reduces the rights you hold under any of them.
1. Who we are (data controller)
The data controller for the personal data we process for our own purposes - the accounts of businesses using Lorenly, their subscription billing, visitors to our website, and the security of the platform - is:
The Next Beacon
the Netherlands
Chamber of Commerce: KVK 42184444
VAT ID NL005564273B97
Contact: [email protected]
Establishment in the EU. The data controller is established in the European Union (in the Netherlands), so the GDPR applies to us directly and no representative under GDPR Article 27 is required. You can contact us directly about any matter concerning your personal data.
Where you book with a business that uses Lorenly (a "Tenant"), that business is the data controller for your booking data and any payment you make to it; Lorenly processes your booking data on the business's behalf as its processor. Please refer to that business's own privacy policy for its data practices, and contact it to exercise your rights over that data.
2. What we collect
Account data
When you create a Lorenly account: name, email address, phone number, business name, and billing details. Necessary to provide the Service.
Usage data
How you interact with the platform: pages visited, features used, device type, browser, OS, IP address, and session timestamps. Used to improve the Service and diagnose issues.
Booking data
When a client books through Lorenly: their name, email, phone number, and booking details (service, date, time, notes, and answers to intake questions). This data may be provided through a Lorenly booking page or by an AI assistant acting at the client's request. We process it as a processor on behalf of the selected business (the Tenant), which is its controller, so that business can provide the appointment.
Payment data
Subscription payments. When a business pays for its Lorenly subscription, the payment is processed by Stripe (PCI DSS Level 1). We are the controller for this billing data. Lorenly does not store full card numbers or CVV codes; we receive only transaction identifiers and non-sensitive metadata.
Payments to a business. Deposits and other payments that clients make to a business are processed by that business's own payment provider account. Lorenly does not receive or hold those funds and does not store card numbers; we keep only the payment status and reference the provider returns, so the business can see whether a booking is paid.
3. How we use your data
- To provide, operate, and maintain the Lorenly platform
- To bill businesses for their Lorenly subscription and manage those subscriptions
- To send transactional communications (booking confirmations, reminders, account alerts)
- To respond to support requests
- To analyse usage and improve the Service
- To comply with our legal obligations under EU and Dutch law (for example tax and accounting rules)
- To detect, investigate, and prevent fraud and abuse
Legal bases: performance of contract, legitimate interests (security, fraud prevention, service improvement), legal obligation, and where required, consent.
4. Sharing your data
We do not sell personal data. We share data only with trusted processors:
- Stripe - processing of Lorenly subscription payments
- Cloud infrastructure providers - hosting and storage
- Email delivery providers - transactional emails
- Microsoft Clarity - how the Lorenly mobile app is used (taps, scrolling, screens), to improve it; all on-screen text is masked, so it never sees your clients' details
- AI model providers - only when a client chooses to book by chatting with a business's AI booking assistant: the chat messages are processed by the AI provider that business has configured (Anthropic, OpenAI or Google Gemini) to answer the client and make the booking. Google user data (section 5) is never sent to an AI provider
All third-party processors are bound by data processing agreements. We disclose data to public authorities only where required by law.
5. Google user data
A business can connect Google services to Lorenly. Each connection is optional, is started by a signed-in member of the business, and asks Google only for the narrowest permission the feature needs:
-
Google Calendar sync (scopes
https://www.googleapis.com/auth/calendar.app.createdandhttps://www.googleapis.com/auth/calendar.freebusy) - a staff member connects their own Google Calendar. Lorenly creates a separate "Lorenly bookings" calendar in their account and adds, updates and removes an event there for each of their Lorenly bookings. It can read and change only that calendar. From the rest of their calendar it reads only free/busy times (start and end), so those times are not offered to clients; it never sees event titles, descriptions, attendees or locations. We store those busy times as "Busy (calendar)". -
Google Meet links (scope
https://www.googleapis.com/auth/calendar.app.created) - a business connects one Google account to create a Google Meet link for each online appointment. Lorenly creates a separate "Lorenly online appointments" calendar in that account and adds each online appointment there with a Meet link, stores the link with the booking and includes it in the booking confirmation. This permission cannot read the account's other calendars, email or meetings.
How we use it. Google user data is used only to provide these user-facing features to the business that connected the account. It is not used for advertising, not sold, not used to build user profiles, and not read by people, except with the business's explicit permission for a support request, where needed for security or to comply with the law.
No AI training. Google user data is never sent to an AI or machine-learning provider, and is never used to create, train or improve any AI or machine-learning model - ours or anyone else's. The only effect a connected calendar has on the AI booking assistant is that busy times are not offered as open slots.
Limited Use. Lorenly's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
Disconnecting. A business can disconnect Google Calendar or Google Meet at any time in Settings - Integrations. Disconnecting Google Calendar also removes the "Lorenly bookings" calendar Lorenly created. Lorenly then revokes its access token with Google and deletes the stored tokens, the event mappings and the busy times it pulled in. You can also remove Lorenly's access from your Google Account at myaccount.google.com/permissions.
6. How we protect your data
We treat Google user data, payment references and our users' and their clients' personal data as sensitive, and protect it with these measures:
- Encryption in transit - every connection to Lorenly and to the services we call uses TLS 1.2 or higher; unencrypted connections are refused.
- Encryption at rest - databases, file storage and backups are encrypted with AES-256. OAuth access and refresh tokens, API keys and other credentials are additionally encrypted at the application level before they are stored, with keys kept separately from the data.
- Tenant isolation - each business's data is separated from every other business's data at both the application and the database layer (row-level security).
- Access control - role-based permissions inside each business; administrative access to production systems is limited to authorised personnel, requires multi-factor authentication and is logged.
- Data minimisation - we request the narrowest permissions and keep only the fields a feature needs (for example, busy times without event details).
- Backups and retention - daily encrypted backups kept for 30 days in a separate location; deleted data leaves the backups when they expire.
- Incident response - suspected security incidents are investigated promptly, and affected businesses and supervisory authorities are notified as the GDPR requires.
More detail is on our Security page.
7. Where your data is stored, and international transfers
Our application servers and primary database are hosted in Switzerland. Files you upload (such as images) are stored with our cloud storage provider in the following region: Western Europe.
Switzerland is recognised by the European Commission as providing an adequate level of data protection (an adequacy decision under GDPR Article 45), so hosting our servers there does not require additional transfer safeguards. Where a processor we use processes data outside the EU/EEA and Switzerland, we rely on an adequacy decision of the European Commission or on the European Commission's Standard Contractual Clauses, together with any supplementary measures required by GDPR Chapter V.
8. Retention
We retain personal data for as long as your account is active. After termination we retain data for 90 days to allow reactivation or data export requests, then securely delete or anonymise it. Some data (e.g. billing records) may be retained longer where required by tax and accounting law (Dutch tax law generally requires business records to be kept for seven years).
9. Your rights
Under the GDPR (and, where it applies, the Swiss FADP) you have the right to:
- Access - request a copy of the data we hold about you
- Rectification - request correction of inaccurate data
- Erasure - request deletion, subject to legal obligations
- Portability - receive your data in a structured, machine-readable format
- Restriction - limit processing in certain circumstances
- Objection - object to processing based on legitimate interests
- Withdraw consent - where processing is based on consent, withdraw it at any time
To exercise these rights, contact us. We will respond within 30 days.
Complaints. Our lead supervisory authority is the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) (https://autoriteitpersoonsgegevens.nl/). Under GDPR Art. 77 you may also lodge a complaint with the supervisory authority of the EU/EEA country where you live or work, or where the alleged infringement took place.
10. Cookies
We use cookies and similar technologies to operate and improve the Service. For details see our Cookie Policy.
11. Contact
For privacy-related questions or data subject requests, use the details on our Contact page. For data deletion requests, include "Data deletion request" in your subject line.