Public website

Website Privacy Policy

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

For account, workspace and appointment information, read the separate App Privacy Notice and our Impressum (Legal Notice). A business using Orar is responsible for its own customers' bookings; contact that business first about a booking or its use of your information.

1. Who is responsible

The website controller is Shpend Kajmaku, Karlsplatz 3, 42103 Wuppertal, Germany. Contact support@orar.pro about privacy and support@orar.pro about the website. Statutory provider identification is available in the Impressum.

2. What the public website processes

The marketing homepage introduces Orar as an early-access scheduling validation project and links to registration, login and documentation. It does not initialize the application's Firebase authentication or appointment database. No advertising pixels, audience analytics or cross-site marketing trackers are installed on the homepage.

Your browser sends technical information needed to request a page, such as an IP address, requested URL, request time, browser information and, depending on your browser's policy, a referring address. Hosting infrastructure processes connection, security and diagnostic records necessary to serve the pages and defend against abuse.

If you contact us, we receive the address you use and the information you choose to send. Please provide only what is needed and avoid sending appointment details or sensitive information in an initial website enquiry.

3. Privacy controls and browser storage

The website privacy control explains the absence of optional analytics and advertising. Choosing “Continue with necessary only” stores the notice version, acknowledgment time and expiry under orar.privacy-notice.v1 in localStorage for 180 days. Expired records are ignored on the next visit; no visitor identifier is stored in that preference. It does not activate an analytics service, and acknowledging this notice is not consent to unrelated processing.

You can reopen the privacy control and use your browser settings to clear site storage. Clearing storage may make the notice appear again. The authenticated application uses separate sign-in and preference storage, described in the App Privacy Notice. Google sign-in and other external services have their own storage behavior.

If optional tracking is ever introduced, this notice and the controls will be updated before activation. Where consent is required, refusing or withdrawing it will be as accessible as giving it, without preventing ordinary access to the public information pages.

4. Purposes and legal grounds

We use necessary request information to deliver the website, diagnose failures and protect it from misuse under Article 6(1)(f) GDPR (legitimate interest in operating a reliable, secure website). Enquiries are handled to respond to your request under Article 6(1)(b) GDPR (pre-contractual steps) or Article 6(1)(f) GDPR (responding to correspondence). A specific legal obligation under Article 6(1)(c) GDPR may require retaining particular records. We do not treat continued browsing as consent.

5. Hosting, recipients and international processing

The local website preview is served from the development computer. The hosted website uses Google/Firebase Hosting, which distributes pages through global CDN infrastructure. Providers receive technical request information necessary to deliver and protect their services. Authorized personnel may access relevant correspondence or diagnostics, and disclosures may be made when required by applicable law.

Visiting this marketing homepage does not connect to the application's authentication or appointment database. 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)..

6. How long information is kept

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.. Necessary records are kept only for their documented purpose, including justified security or legal requirements, and then deleted or anonymized. The notice preference in browser localStorage expires after 180 days.

7. Your choices and rights

Where the GDPR applies, you may request access (Art. 15), correction (Art. 16), erasure (Art. 17) or restriction (Art. 18); object to processing based on legitimate interests (Art. 21); and request portability where its conditions apply (Art. 20). If processing relies on consent, you may withdraw it at any time without affecting earlier lawful processing. These rights have statutory conditions and do not always require immediate deletion of every record.

Contact support@orar.pro. We may request proportionate information to identify the relevant records and verify your request. We normally respond within one month. Where complexity or the number of requests permits an extension of up to two further months, we explain the extension and reasons within the first month. You may complain to a competent supervisory authority, including the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (LDI NRW) or the authority in the EEA country where you live or work. See the EDPB authority directory.

8. Other pages and changes

Following a login, registration, booking or external link changes the service you are using. Read the relevant privacy notice there. We will identify material changes and update this notice's version; publication alone does not supply consent for a new purpose that requires it.