For processing within a workspace, Customer means the person or business on whose behalf an authorized account holder creates that workspace. The Processor is Shpend Kajmaku, Karlsplatz 3, 42103 Wuppertal, Germany. This DPA supplements the App Terms and takes precedence for its subject matter. GDPR terms have their statutory meanings; the Customer acts as controller and the Processor acts as processor under Article 28 GDPR.
1. Subject matter, scope and duration
The Processor provides appointment-scheduling software during the early-access validation phase and processes Customer Personal Data only to deliver that service and assist the Customer as described below. Annex A specifies the data categories, data subjects, operations and purposes. Processing lasts for the active workspace relationship and the period required to complete return or erasure under Section 10.
Individual account registration records acceptance of this DPA; workspace setup follows afterward. An account holder acting for another entity must have authority to instruct processing on its behalf. Separate operator-controlled account administration, abuse prevention, and contractual records are described in the App Privacy Notice. If the Customer acts as a processor for another controller, the Customer warrants that its instructions and notices are authorized by that controller.
2. Documented instructions and Customer duties
Documented instructions comprise this DPA, the Customer's workspace configuration, authorized booking operations and further written directions from designated Customer contacts. The Processor will not sell Customer Personal Data, use it for advertising, or process it for unrelated purposes.
The Customer determines lawful purposes and legal grounds for its client bookings, supplies required privacy notices and provider identification (Impressum), limits collection to necessary fields, and assesses whether the early-access service is suitable for its use case. Special-category data (Art. 9 GDPR, including health data) and criminal-offence data (Art. 10 GDPR) are prohibited.
The Processor will immediately inform the Customer if it considers an instruction contrary to the GDPR or applicable EU or German data-protection law. If EU or Member State law requires processing beyond instructions, the Processor will inform the Customer before processing unless that law prohibits notification for important public-interest reasons.
3. Personnel confidentiality and access
The Processor ensures that any person authorized to process Customer Personal Data is bound by confidentiality commitments or an appropriate statutory duty, and that access is restricted strictly to what is necessary for support, maintenance, and operation of the service.
4. Security of processing
The Processor implements technical and organizational measures appropriate to the risk under Article 32 GDPR, taking into account the state of the art, implementation costs, and the nature, scope, context and purposes of the early-access scheduling service, as detailed in Annex B.
The Customer is responsible for managing its staff roles, credentials, public profile content and custom booking questions responsibly, and for maintaining independent backups of critical business schedules during early access.
5. Subprocessors and changes
The Customer grants general written authorization for the subprocessors listed in Annex C. The Processor maintains written terms imposing data-protection obligations under Article 28(3) GDPR on its infrastructure subprocessors and remains responsible to the Customer for their performance.
The Processor will give at least 14 days' advance notice (or 30 days where practicable) before adding or replacing a subprocessor handling Customer Personal Data, identifying the provider, function and location. The Customer may object on reasonable data-protection grounds; if an objection cannot be resolved, the Customer may terminate the workspace and request immediate deletion of its data without penalty.
6. International transfers
The regional backend (Data Connect/PostgreSQL and Cloud Functions) is configured for Frankfurt, Germany (europe-west3), and live booking email delivery targets Scaleway's Paris, France region. Hosted Firebase Authentication processes account sign-in in the United States and Firebase Hosting operates via a global CDN. Applicable 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)..
7. Assistance with data-subject rights
Taking into account the nature of the processing, the Processor assists the Customer by appropriate technical and organizational measures in fulfilling requests for access, correction, erasure, restriction, portability, and objection under Chapter III GDPR. If a booking client contacts the Processor directly about a Customer booking, the Processor will promptly forward the request to the Customer and will not independently delete or alter Customer booking records without Customer instruction unless legally required.
Customer assistance requests should be sent to support@orar.pro identifying the workspace and relevant booking reference. Because self-service bulk export and permanent record purging are not yet automated in the UI, the Processor fulfills export and erasure instructions manually within statutory deadlines.
8. Personal data breaches and impact assessments
The Processor will notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data, providing the known nature of the breach, affected categories and approximate number of records, likely consequences, and remedial measures taken or proposed.
The Processor will contain and investigate the incident and assist the Customer with its obligations under Articles 32 to 36 GDPR (security, breach notifications, data-protection impact assessments, and prior consultation), taking into account the nature of processing and information available to the Processor.
9. Information and audits
The Processor will make available to the Customer information necessary to demonstrate compliance with Article 28 GDPR and allow for and contribute to proportionate audits, including inspections, conducted by the Customer or an auditor mandated by the Customer. Audits starts with documentary review of system architecture and provider certifications; any further inspection requires reasonable advance notice, confidentiality protections, and strict protection of other tenants' data and infrastructure security.
10. Return and erasure of data
At the Customer's choice upon workspace closure or termination of the evaluation service, the Processor will return Customer Personal Data in a structured, commonly used machine-readable format (such as JSON or CSV) and/or delete all existing copies in the application database, including appointments, customer details, questionnaire answers, reservation holds, history snapshots and queued/sent notification records, unless EU or Member State law requires storage.
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.. Within the live application UI, cancelling an appointment or removing a staff member preserves historical records for workspace auditability; complete erasure is executed operationally by the Processor upon workspace termination or specific Customer instruction to support@orar.pro.
Annex A. Description of processing
- Data subjects: booking clients, prospective clients submitting booking requests, business owners, staff members and authorized workspace users.
- Categories of personal data: names, email addresses, optional phone numbers, staff identifiers and roles, appointment dates/times/status, selected services, answers to non-sensitive booking questions, change-history snapshots and transactional email contents/delivery status.
- Processing operations: collection, validation, storage, availability calculation, display to authorized workspace staff, publication of business availability intervals, transactional email transmission (when enabled), export and deletion.
- Purpose: providing and securing the business appointment-scheduling software in accordance with Customer configuration.
- Excluded data: Article 9 GDPR special-category data (such as health/medical records), Article 10 offence data, payment card details and government ID copies are strictly excluded.
Annex B. Technical and organizational security measures
Application-level controls implemented in code:
- Tenant and role isolation: authenticated UID and workspace role checks on Data Connect queries and Cloud Functions; staff members are restricted to viewing and managing their own assigned appointments and histories, while owners/admins manage the workspace.
- Server-controlled booking integrity: public booking holds and confirmations execute through server-side Cloud Functions with input validation, transactional conflict checks, and optimistic version checks.
- Cryptographic reservation tokens: temporary 10-minute reservation holds use randomly generated credentials stored only as SHA-256 hashes in the database.
- Abuse and bot protection: public booking and account-onboarding endpoints enforce hidden honeypot validation and in-memory burst rate limiting (keyed by authenticated UID or truncated SHA-256 IP digest for 10 minutes). Optional Firebase App Check (reCAPTCHA) remains disabled by default during validation so visitors are not subjected to third-party CAPTCHA profiling.
- Secret & XSS protection: email provider API credentials are held server-side via Secret Manager; dynamic fields in generated HTML booking emails are HTML-escaped; iframe embed messaging validates origin, window reference, and channel tokens.
- Immutable agreement ledger: legal acceptance receipts are written via server transactions in Firestore with client read/write access completely denied by security rules.
Infrastructure and operational measures: TLS encryption in transit across all HTTPS endpoints; encryption at rest provided by Google Cloud / Scaleway infrastructure; least-privilege administrative access to cloud consoles; and manual verification before executing destructive data erasure or export requests.
Annex C. Authorized subprocessors and external recipients
- Google Ireland Limited / Google LLC (Firebase / Google Cloud):
- Data Connect & Cloud SQL for PostgreSQL: stores workspace, staff, service, appointment, history and email-queue records. Configured region:
europe-west3(Frankfurt, Germany). - Cloud Functions for Firebase: executes booking, onboarding, legal-receipt and email-queue logic. Configured region:
europe-west3(Frankfurt, Germany). - Cloud Firestore: stores immutable operator legal-acceptance receipts (`legalAcceptances`).
- Firebase Authentication: manages user sign-in, session tokens and verification emails (documented by Google as processed in the United States under the Firebase Data Processing and Security Terms, EU-U.S. DPF and SCCs).
- Firebase Hosting: serves static web application assets via global CDN infrastructure.
- Firebase App Check / Google reCAPTCHA (optional): only active if configured via environment keys for bot mitigation.
- Data Connect & Cloud SQL for PostgreSQL: stores workspace, staff, service, appointment, history and email-queue records. Configured region:
- Scaleway SAS (Scaleway Transactional Email, conditional): processes recipient email address, subject and booking notification body in Paris, France (`fr-par`, EU) only when live email delivery (`EMAIL_MODE=scaleway`) is enabled. In default `preview` mode, no data is sent to Scaleway.
- External user/customer-triggered features (not core subprocessors): displaying a booking QR code requests an image from
api.qrserver.comusing the public booking URL; customer-configured logo/background URLs are fetched directly by visitors' browsers from the customer's chosen image host; clicking WhatsApp or email share links opens the user's chosen external application.
Statutory references: GDPR Articles 28, 32–36 and Chapter V and the European Commission's Standard Contractual Clauses.