Orar application

Application Privacy Policy

Version 2026-10-17 · Last updated 17 October 2026 · Permanent version link

Read this alongside the App Terms of Service, Data Processing Agreement, and Impressum (Legal Notice). Acknowledging that you have read this notice is not consent to every processing activity.

1. Who decides how information is used

Shpend Kajmaku, Karlsplatz 3, 42103 Wuppertal, Germany, is the controller for its own account administration, contractual records, abuse prevention, support and service-security purposes. Contact support@orar.pro about personal data and support@orar.pro for service assistance.

The business or tester whose booking page you use determines why customer and staff booking information is collected and how appointments are managed. For that information the business is the controller and Orar processes it on its documented instructions under the DPA. A business must establish its own lawful basis and provide its own notice to its clients. Orar does not choose a business's legal basis by supplying a scheduling form.

If you are a booking customer, contact the booking business first about access, correction, deletion, cancellation or rescheduling. You may also contact us to help identify the responsible business or route a request; this does not remove your statutory rights.

2. Account and business information

Email/password registration sends credentials to Firebase Authentication. Google sign-in uses Google's authentication service and provides the account information needed to sign you in, such as an identifier, email address and available display name. We use authentication identifiers and tokens to associate sessions with authorized users. Application database records do not contain account passwords. Managers who create staff accounts supply an initial password to the account-creation function, which passes it to Firebase Auth.

Business records are created during workspace setup and subsequent use. They include the business name, public booking name and slug, timezone, service descriptions and prices, staff names and emails, roles, schedules, time off, booking questions, image URLs and notification-template settings.

Agreement records associate the authenticated account UID with document versions, a server timestamp, terms and DPA acceptance, and privacy acknowledgement. Business setup follows account registration. The signup receipt does not collect business identification information or a separate business-authority confirmation, and does not separately duplicate email, IP address or user agent. Infrastructure and abuse-protection functions separately process technical request information as described below.

3. Appointment information and sources

A public booking collects name and email, a phone number when provided or required by the business, the service and professional selected, appointment time and status, and answers to the business's configured questions. Staff may also enter bookings and customer details on someone's behalf. Information therefore comes from the individual, the business's authorized users, authentication providers and operation of the service.

Appointment records can contain internal titles, service and staff references, booking source and change history. Historical snapshots retain the relevant customer name/email, staff and service names, previous and current times, status, actor and event time. Notification records contain recipient addresses, message subjects and full text/HTML, processing attempts, status and provider/error references.

Do not submit special-category data under Article 9 GDPR (including health, genetic, biometric identification, political, religious, trade-union or sex-life information) or criminal-conviction/offence data under Article 10 GDPR. Such processing is outside the permitted service scope. A service name or free-text answer can itself reveal sensitive information; do not enter medical or sensitive details into free-text fields. Payment-card information and identity-document copies are not requested by the booking flow.

4. Purposes and legal grounds

For its controller activities, the operator uses necessary information to provide accounts, communicate about the service, administer the free early-access evaluation and agreements, answer support requests, protect access and prevent automated abuse. Performance of a contract or requested pre-contractual steps (Art. 6(1)(b) GDPR) applies where the individual is personally a contracting party. For business representatives, staff, and security/anti-abuse measures, the legal ground is legitimate interests in administering the workspace relationship and maintaining a secure service (Art. 6(1)(f) GDPR). Specific legal obligations (Art. 6(1)(c) GDPR) may require retaining particular records.

For customer booking data, the business selects and explains its legal grounds, including whether information is necessary for an appointment or a separate optional purpose. Orar's processor activities do not depend on a blanket privacy checkbox. No advertising or audience-analytics purpose is implemented in the application.

5. Information made public or shared

A published booking page exposes the business's public profile, service choices, staff display names and relevant availability. The public availability response contains time intervals, staff identifiers, scheduling types and service buffers; it excludes private calendar titles and customer contact details. Businesses should treat public labels and images as public material, avoid personal information in availability labels, and review their page before sharing it.

Authorized owners and administrators can manage their workspace. Staff access to appointment records and booking history is restricted to their assigned bookings; workspace membership also exposes relevant team information. Operational access by the operator or providers is limited to authorized support, maintenance and security purposes.

Booking email delivery is prepared for Scaleway Transactional Email in Paris, France. When live sending is enabled, that provider receives the recipient's address and the message subject and full body. Booking messages may identify the customer, business, service, professional, time, status and reference. The customer, assigned staff member and workspace owners receive separate messages; identical recipient addresses are deduplicated. In preview mode (the default during local and unconfigured testing), messages are recorded in the workspace queue for review and are not transmitted externally. Provider acceptance does not guarantee inbox delivery.

Account-verification emails use Firebase Authentication separately from booking notifications. In local emulator mode, verification links are provided locally by the emulator instead of being emailed. A recipient's own email provider may process delivered messages outside the EU, regardless of the sending provider's location.

6. External features and embeds

Displaying a QR code contacts api.qrserver.com and supplies the public booking URL to generate that image. Business-supplied logo or background URLs cause the browser to contact the image host; those hosts receive browser connection information. Background images request no referrer. Businesses should select hosts and content they are entitled to use.

WhatsApp sharing opens wa.me with the business name and booking link only when clicked by the user. Email sharing invokes the user's email application. These sharing choices do not automatically enroll customers in WhatsApp messaging. Ordinary booking flows do not send automated WhatsApp notifications.

An embedded booking form runs on the Orar origin. Its host page receives iframe resizing messages and, after a successful booking, an opaque booking reference and status. Contact details and questionnaire answers are not included in that event. A host website can connect the event to its own analytics; its operator must provide the necessary notice and consent controls.

7. Browser storage, bot protection and technical records

Firebase Auth uses browser persistence, normally IndexedDB with localStorage or sessionStorage fallbacks, to maintain authentication. The application also stores the selected workspace under activeTenantId and the visual preference under theme in localStorage. Those preferences have no automatic expiry and can be cleared via browser storage settings. Booking drafts and temporary reservation tokens are held in page memory rather than application localStorage.

To protect booking pages and account onboarding from automated spam and abuse without third-party tracking, submission forms include hidden honeypot fields and backend callables apply short-term (10-minute) in-memory rate-limiting counters keyed by authenticated user ID or a truncated SHA-256 hash of the client IP address. Firebase App Check (Google reCAPTCHA) is disabled by default during this validation phase so no third-party CAPTCHA scripts or cookies load in normal operation. Hosting, authentication and function providers also process IP addresses, request times and device/request headers for delivery and security.

8. Locations and transfers

Local development uses emulators for authentication, application data, server operations and agreement records on the development computer.

The regional application backend (Data Connect/PostgreSQL and Cloud Functions) is configured for Frankfurt, Germany (europe-west3). Live Firebase Authentication is documented by Google as processing in the United States, while Firebase Hosting uses global CDN infrastructure. See Firebase's privacy and security information. The booking email integration targets Scaleway's Paris region, which Scaleway documents as hosted and processed within the EU in its service FAQ.

International-transfer safeguards: Core application backend services (Data Connect/PostgreSQL and Cloud Functions) are configured in Frankfurt, Germany (europe-west3), and transactional email delivery when enabled uses Scaleway in Paris, France. Firebase Authentication (processed in the United States) and Firebase Hosting (global CDN) are operated under the Google Firebase Data Processing and Security Terms, relying on the EU-U.S. Data Privacy Framework (DPF) and European Commission Standard Contractual Clauses (SCCs).. Ask support@orar.pro for further information on applicable transfer mechanisms.

9. Retention, cancellation and deletion

Retention schedule: Account, workspace, and booking records are retained while the evaluation workspace remains active and are deleted within 30 days of an erasure request, workspace closure, or termination of the validation project, unless mandatory statutory obligations require longer retention. Website privacy-notice acknowledgements in browser localStorage expire after 180 days; in-memory abuse-prevention rate-limit counters expire after 10 minutes.. Current early-access software does not yet implement an automated background purge or a self-service workspace-erasure button; instead, complete account or workspace deletion and data exports are handled operationally upon request to support@orar.pro.

Within an active workspace, cancelling a booking preserves its record and history so businesses can track schedule changes. Removing a service marks it inactive. Removing staff membership does not itself delete the underlying Firebase account. A temporary booking hold expires after ten minutes, though the expired reservation row remains until database cleanup or workspace deletion. Trial/evaluation end, sign-out and changes to question settings do not automatically erase stored workspace records without an erasure instruction or workspace closure.

10. Security, rights and updates

Implemented controls include tenant/role checks, validated server-side booking operations, transaction/version checks, hashed temporary reservation tokens, honeypot and rate-limit protections, and restricted server-side access to email-provider secrets. These reduce operational risks, though no internet service can guarantee absolute security.

Subject to statutory conditions, individuals may access (Art. 15 GDPR), correct (Art. 16), erase (Art. 17) or restrict (Art. 18) data, object to legitimate-interest processing (Art. 21), request portability (Art. 20) and withdraw any consent. We do not use the booking logic for profiling or solely automated decisions producing legal or similarly significant effects (Art. 22 GDPR).

Contact the relevant booking business or support@orar.pro. Requests will be verified proportionately and normally answered within one month (extendable by up to two further months for complex or multiple requests, with notice given within the first month). You may complain to a competent supervisory authority, including the LDI NRW in Germany or any authority listed by the EDPB. Material changes to purposes, providers or this notice will be identified through an updated version.