# Privacy Policy **Pursuant to Art. 13, 14 GDPR | Last updated: 5 November 2026 | Version 1.5** **Notice:** This Privacy Policy provides comprehensive information about how we collect, process, and use personal data in connection with the use of the platform **esc/ctrl** (accessible at escctrl.wmit.work and escctrl.de). It applies to all users (artists using the Artist App, managers & team members using the Client Center), visitors, and prospective users of this platform and fulfills the legal requirements of the General Data Protection Regulation (GDPR), the German Federal Data Protection Act (BDSG), and the Telecommunications Telemedia Data Protection Act (TDDDG). ## Table of Contents 1. Controller 2. Data Protection Officer 3. Competent Supervisory Authority 4. Principles of Data Processing 5. Categories of Personal Data Processed 6. Purposes and Legal Bases of Data Processing 7. Registration and User Account (Firebase Authentication) 8. Onboarding, Artist Profile & Client Center (Managers & Team Members) 9. AI-Powered Features (Gemini 2.5 API / Google AI Studio) 10. Support Ticket System, Customer Support & Bug Reports 11. News Section, Product Updates & Announcements 12. Download Section, Asset Management & Self-Service GDPR Data Export (CSV / JSON) 13. Analytics & Social Media Data (OAuth Connections) 14. Web Scraping Service (Apify) 15. Google Drive Integration 16. Lead Generation and Email Verification 17. Newsletter (Mailchimp) 18. Payment Processing (PayPal) & Statutory Tax Retention (§ 147 AO / § 257 HGB) 19. Hosting and Infrastructure (Google Cloud / Firebase / GoDaddy) 20. Cookies, Web Analytics and Local Storage 21. Contact 22. Disclosure of Data to Third Parties 23. Data Transfers to Third Countries 24. Retention Periods, Account Deletion & Statutory Storage Obligations 25. Your Rights as a Data Subject (incl. Access & Self-Service Export) 26. Data Security 27. Amendments to this Privacy Policy 28. Right to Lodge a Complaint with the Supervisory Authority 29. Additional Processing: Copilot, Support and Consent ## 1. Controller The controller within the meaning of the General Data Protection Regulation (GDPR) and other national data protection laws as well as other data protection provisions is: **Operator / Company:** wemakeITwork **Name:** Malte Schröder **Postal Address:** CAYA Postbox 890308, 96035 Bamberg, Germany **Registered Office:** Planufer 92b, 10967 Berlin, Germany **Phone:** +49 30 16 63 95 84 **Email:** support@wmit.work **Platform URL:** [https://escctrl.wmit.work](https://escctrl.wmit.work) · [https://escctrl.de](https://escctrl.de) **Studio Website:** https://nyr.studio The platform **esc/ctrl** is operated by wemakeITwork, sole trader Malte Schröder, a sole proprietorship based in Berlin, Germany. For all data protection enquiries, please contact us directly by email or phone at any time. ## 2. Data Protection Officer The appointment of a Data Protection Officer (DPO) is currently not mandatory for our business pursuant to Art. 37 GDPR in conjunction with § 38 BDSG, as we regularly employ fewer than 20 persons engaged in the automated processing of personal data as a sole proprietorship. We nevertheless take data protection very seriously and are available at all times for any data protection-related enquiries (see Section 1). ## 3. Competent Supervisory Authority The competent data protection supervisory authority for our business is: **Authority:** Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit) **Postal Address:** Friedrichstr. 219, 10969 Berlin, Germany **Visitor Entrance:** Puttkamer Straße 16–18 (5th Floor), Berlin **Phone:** +49 30 138 89 0 **Email:** mailbox@datenschutz-berlin.de **Website:** [https://www.datenschutz-berlin.de](https://www.datenschutz-berlin.de) ## 4. Principles of Data Processing We process personal data in strict compliance with the principles set out in Art. 5 GDPR: * **Lawfulness, fairness and transparency:** Data is processed only on the basis of a valid legal ground and in a comprehensible manner. * **Purpose limitation:** Data is collected for specified, explicit and legitimate purposes and not processed in a manner incompatible with those purposes. * **Data minimisation:** Only the data necessary for the respective purpose is processed. * **Accuracy:** Data is kept factually accurate and up to date; inaccurate data is deleted or corrected without delay. * **Storage limitation:** Data is not retained for longer than necessary for the respective purpose. * **Integrity and confidentiality:** Data is protected against unauthorised access, loss or destruction by appropriate technical and organisational measures. * **Accountability:** As controller, we are able to demonstrate compliance with all of the above principles. ## 5. Categories of Personal Data Processed Depending on the features used, the following categories of personal data may be processed in connection with the use of esc/ctrl: * **Master data:** Name, email address, password (encrypted), user ID, profile picture URL * **Artist profile data (Artist App) & Additional Workspaces:** Artist name, genre, biography, target audience, release dates, monthly listener goal, and isolated project workspaces (`_`) * **Client Center, Booking Client Center & Manager data:** Manager name, agency/label name, managed artist IDs, invited team members' email addresses (including abuse-protected SHA-256 invitation hashes), assigned role permissions, as well as tour, show, crew, rider, and venue records in the Booking Client Center * **Social media & streaming data:** Profile URLs, monthly profile checks (*socialProfilStand*), and public or authenticated metrics from Spotify, YouTube, Instagram, Facebook, TikTok, Apple Music, Amazon Music, Deezer, SoundCloud * **OAuth tokens & Meta deletion status:** Access tokens for connected third-party platforms (stored with AES-256-GCM encryption), refresh tokens, and status records of the automated Meta Data Deletion Callback * **AI interaction, Copilot & job data:** Chat messages, requests and generated responses within the Gemini 2.5 AI assistants and the 30+ music AI Smart Tools, proactive Copilot insights (*actionableInsights*), Brand Voice preferences, asynchronous AI job payloads (*aiJobs*, *aiJobPayloads*), and token budget counters (*aiUsage*) * **Planning, Release Vault & project data:** Release plans, playbooks, roadmaps, moodboards, Kanban tasks, calendar entries (including public ICS calendar feeds), Smart Link / Pre-Save pages, public share links (`/share/*`), Guest Portals (`/guest/:token`), and audio masters, artworks, and videos stored in the Release Vault (*vaultItems*) including technical specification and loudness inspection (LUFS, True Peak dBTP) * **Financial, statement & receipt data (Revenue Planner & Statement Inspector):** Financial plans (*revenuePlans*, *revenuePlanSettings*), uploaded receipts and invoices (including optional AI receipt OCR), imported distributor and collecting society statements (GEMA, GVL, Spotify, Apple Music, etc.), GoBD period locking attributes, and DATEV exports * **Support & feedback data:** Support tickets, issue descriptions, attachment files, resolution status, and feedback submitted via Guest Portals (*guestFeedback*) * **Download & export logs:** Generated GDPR data exports (CSV/JSON including export manifest and temporary receipt download links), downloaded asset packages, download timestamps * **Usage, consent & news data:** IP address (or truncated SHA-256 hash in the consent audit log), browser/device information, login timestamps, session data, documented legal and cookie consents (*legalConsents*, *analyticsConsents*), article views in the news section * **Communication data:** Transactional emails via Google Workspace SMTP (team invitations); in-app support replies and reminders as well as emails in the context of lead generation and verification processes * **Google Drive export:** The title and text of a document that you explicitly choose to export from esc/ctrl * **Payment & billing data:** Billing address, VAT ID, transaction ID, and subscription tiers (payments processed via PayPal; we do not store credit card details ourselves) ## 6. Purposes and Legal Bases of Data Processing We process your personal data on the basis of the following legal grounds under the GDPR: * **Art. 6(1)(a) GDPR – Consent:** Processing activities for which you have given your explicit consent (e.g. newsletter subscription, connection of third-party platforms, use of opt-in AI features, analytics and marketing cookies pursuant to § 25(1) TDDDG) * **Art. 6(1)(b) GDPR – Performance of a contract:** Processing necessary for the performance of the user agreement (provision of the platform for Artist App, Client Center, and Booking Client Center users), registration, support handling, and delivery of contracted services * **Art. 6(1)(c) GDPR – Legal obligation:** Processing required by applicable legal provisions (in particular statutory retention obligations under tax and commercial law pursuant to § 147 AO / § 257 HGB and access rights under Art. 15, 20 GDPR) * **Art. 6(1)(f) GDPR – Legitimate interests:** Processing in pursuit of our legitimate interests (e.g. operation and IT security of the platform, abuse prevention, resolving technical bugs via the support system, providing the news section) ## 7. Registration and User Account (Firebase Authentication) Registration is required to use esc/ctrl. Authentication is handled via **Google Firebase Authentication** (Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA), a separate service within Google’s infrastructure. Our Firestore database region does not determine where Firebase Authentication processes data; exclusively German or European processing is not guaranteed for this service. ### Sign-in Options You can register and sign in via two methods: * **Email & Password:** You provide an email address and a self-chosen password. The password is stored by Firebase in encrypted form. We never have access to your plaintext password. * **Google Sign-In (OAuth 2.0):** You sign in with your existing Google account. This transfers your Google account data (name, email address, profile picture) to Firebase. Authentication is conducted via an OAuth 2.0 token flow. The following data is processed during registration and stored in **Google Firestore** (NoSQL database, region: **europe-west10, Berlin, Germany**): User ID (UID), email address, display name, profile picture URL (for Google sign-in), account creation date, last sign-in timestamp, and IP address at the time of registration. **Legal basis:** Art. 6(1)(b) GDPR (performance of a contract). Google/Firebase's privacy policy is available at [https://firebase.google.com/support/privacy](https://firebase.google.com/support/privacy) and [https://policies.google.com/privacy](https://policies.google.com/privacy). ## 8. Onboarding, Artist Profile & Client Center (Managers & Team Members) After registration, you may use the platform as an individual artist (Artist App), across multiple project workspaces, or as a manager/agency/booking team (Client Center & Booking Client Center): ### a) Artist App & Artist Profile When creating an artist profile, data is stored in Google Firestore (collection *artistProfiles*): * **Required fields:** Artist name, genre * **Optional fields:** Biography, target audience, focus goals, release dates (album, single, music video), tour dates, monthly listener goal, social media links, planning preferences, and print specifications * **Growth Roadmaps & Playbooks:** Automatically or manually generated strategy roadmaps and release playbooks (collections *growthRoadmaps*, *playbooks*) ### b) Client Center (Manager & Team Management) For managers, labels, and agencies, the **Client Center** provides enhanced collaboration and management features. Data is stored in Google Firestore (collections *managerProfiles*, *teamMembers*, *clientBriefings*, *artistQuickNotes*, *linkRequests*): * **Manager master data:** Manager/agency name, specialization, contact information * **Managed artists:** Linking artist IDs to the manager account to grant access to dashboard views, daily briefings, and roadmaps * **Team member management:** Inviting team members by email, assigning granular role and tab permissions (Admin, Manager, Member, Booking roles). Invited members receive notifications to activate their access ### c) Additional Workspaces (Multi-Project Management) Users can create additional isolated artist workspaces under one main account (collection *workspaces*, identifier `_`). Each additional workspace stores its own profile, release, Vault, task, and financial records separately from the primary project. Both the self-service GDPR data export (Section 12b) and account deletion (Section 24) automatically include all additional workspaces owned by the main account. ### d) Booking Client Center & Tour / Live Management For booking agencies, tour managers, and promoters, esc/ctrl provides the **Booking Client Center** (`/booking-client-center`). This module processes tours, show dates, daily itineraries, routing and venue intelligence, crew assignments, and technical/hospitality riders (collections *bookingTours*, *bookingCrew*, *bookingRiders*, *bookingVenues*). Where personal data is involved (such as contact details of crew members, stage managers, or local promoters), processing takes place to perform tour and live event planning. ### e) Transactional System Emails & Team Invitation Abuse Protection To dispatch operational transactional emails (team invitations), we use **Google Workspace SMTP** (`smtp.gmail.com`, sender address `support@wmit.work`). For rate-limiting and abuse protection of team invitations, we store only a cryptographic **SHA-256 hash** of the invited email address and daily organisation counters in the collections *teamEinladungen* and *teamEinladungsZaehler*, without retaining plaintext recipient email addresses in the rate-limit log. **Legal basis:** Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(f) GDPR (legitimate interest in efficient collaboration across management, team, and booking structures as well as spam and abuse prevention). ## 9. AI-Powered Features (Gemini 2.5 API / Google AI Studio) esc/ctrl continuously utilizes current AI models from the **Google Gemini 2.5 Series** (e.g. 'gemini-2.5-pro' and 'gemini-2.5-flash' by Google DeepMind / Google LLC), provided via **Google AI Studio**, for the following core capabilities: * **AI Assistant (Copilot) & Brand Voice Context:** Chat-based assistant answering questions regarding release strategy, marketing, and content creation using your stored artist concept and Brand Voice profile (*artistConcepts*, *copilotKontext*) * **Proactive AI Copilot (Insight Engine) & Monthly Social Media Profile Check:** Automated evaluation of upcoming release deadlines, pitch windows, technical Vault specifications, budget anomalies, and measured streaming impulses to generate actionable recommendations (*actionableInsights*), as well as a monthly Social Media Profile Check (*socialProfilStand*) inspecting public profile bios and pre-save/smart links. Technical engine execution logs (*copilotEngineRuns*) are accessible solely to platform administrators and are automatically deleted after 30 days * **30+ Specialized Music AI Smart Tools:** Domain-specific tools (including Contract Analyzer, GEMA Assistant, EPK Builder, Mastering QC, Split Sheet Generator, press text, pitch and storytelling assistants, merch and tour budget calculators) as well as AI-powered receipt OCR in the Revenue Planner * **Growth Roadmap, Content Generator & Release/Tour Planner:** AI-assisted generation and optimization of custom growth roadmaps, social posting schedules, release timelines, and tour schedules * **Asynchronous AI Job Queue & Token Budgeting:** Long-running AI tasks are processed through a server-side job queue (*aiJobs*, *aiJobPayloads*); aggregated token consumption per account and month (*aiUsage*) is recorded for fair resource allocation and cost control **Data Processing & Security Measures:** When using AI features, your artist profile (name, genre, goals, release dates), chat prompts, and context data are transmitted server-side via our secure Node server ('server.ts') to the Google Gemini API. All inputs pass through server-side prompt injection protection and are encapsulated in XML structures. * **No Model Training:** Pursuant to commercial API terms of Google AI Studio, submitted prompts and data are **not** used to train public Google AI models. * **Fallback Architecture:** The system primarily uses 'gemini-2.5-pro' and 'gemini-2.5-flash' with automated fallback mechanisms to ensure high availability. **Legal basis:** Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(a) GDPR (consent for optional usage). Further information on data processing by Google AI: [https://ai.google.dev/gemini-api/terms](https://ai.google.dev/gemini-api/terms). ## 10. Support Ticket System, Customer Support & Bug Reports To handle technical enquiries, bug reports, and user feedback, we operate an integrated **Support Ticket System** (collections *supportTickets*, *feedback* in Firestore). **Data collected:** * User ID, name, email address * Enquiry category (e.g. Authentication, API Error, Billing, Feature Request) * Subject, detailed issue description, priority * Optional: Uploaded screenshots or attachment files * Ticket status, timestamps, communication logs with support staff **Purpose & Retention:** Processing your support request, resolving technical bugs, and maintaining platform stability. After ticket closure, support records are retained for the duration of the standard statutory limitation period (§ 195 German Civil Code - BGB: 3 years to the end of the calendar year) to handle any follow-up questions. **Legal basis:** Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(f) GDPR (legitimate interest in platform stability and effective support). ## 11. News Section, Product Updates & Announcements On our platform, we provide a publicly and internally accessible **News Section** ('/news'). Here, we publish platform updates, new features, music industry best practices, and system announcements. **Data Processing in the News Section:** * When viewing news articles, anonymized view counters are updated in Firestore to measure content relevance. * If you are a logged-in user, we process your session ID to mark articles you have already read. * If you subscribe to product updates via the news section, your email address is processed in accordance with Section 17 (Newsletter). **Legal basis:** Art. 6(1)(f) GDPR (legitimate interest in transparent information sharing regarding platform features). ## 12. Download Section, Asset Management & Self-Service GDPR Data Export (CSV / JSON) esc/ctrl offers comprehensive tools for file management, financial and royalty statement inspection, external sharing, and exporting your personal data: ### a) Download of Templates & Asset Packages In the download section ('/downloads'), you can download pre-formatted checklists, release guides, branding assets, and contract templates. Download timestamps and anonymized counters are recorded to optimize our content offerings. **Legal basis:** Art. 6(1)(f) GDPR. ### b) Self-Service GDPR Data Export (CSV / JSON) under Art. 15 & 20 GDPR You can download a full, streamed export of all your stored data at any time from your account settings ('Settings.tsx' or 'Account & Privacy' in the Client Center) in standard **CSV format** (including UTF-8 BOM for Microsoft Excel and Apple Numbers) as well as **JSON format**. * **Export Content:** Master personal data, artist/manager profiles, all additional workspaces (*zusatzWorkspaces*), billing & tax records, revenue plans including 7-day signed download links (*dateiLink*) for uploaded receipt files, connected platforms, roadmaps, playbooks, tasks, calendar entries, booking tours/crew/riders, chat histories, AI job inputs (*aiJobInputs*, excluding internal worker lease tokens), guest feedback, documented consents (*legalConsents*, *legalConsentAuditLog*, *analyticsConsent*), and a cryptographic completion manifest (*exportManifest*). For memberships in third-party teams, only your own membership entry is exported. * **Transparency & Portability:** This self-service export fulfills your data subject rights to access (Art. 15 GDPR) and data portability (Art. 20 GDPR). **Legal basis:** Art. 6(1)(c) GDPR (compliance with legal obligations to uphold data subject rights). ### c) Release Vault & Technical Specification / Loudness Inspection In the **Release Vault**, you store audio masters (WAV, FLAC, MP3, AIFF), cover artworks, and music videos in Google Cloud Storage (`vault//...`, collection *vaultItems*). For quality assurance, esc/ctrl automatically inspects audio and image files against technical distributor specifications (*specPruefung*): * **Inspected parameters:** Sample rate, bit depth, channels, file format, image resolution, aspect ratio, color space, and—for audio files—integrated loudness (**LUFS**) and true peak level (**True Peak dBTP**) according to ITU-R BS.1770 / EBU R 128. * **Processing:** Analysis runs locally in your browser or via bounded server-side header/stream inspection without sharing your unreleased works with external third-party audio profiling services. ### d) Revenue Planner, Statement Inspector, AI Receipt OCR, GoBD Locking & DATEV Export In the **Revenue Planner** and **Statement Inspector**, we process your financial planning, income/expense items (*revenuePlans*, *revenuePlanSettings*, subcollections *positionen* and *belege*), and imported royalty statements (*royaltyStatements*, *royaltyLineItems*): * **Receipt upload & signature verification:** Uploaded invoices and receipts are verified against binary file signatures (PDF, JPEG, PNG, WebP, HEIC) and stored in Cloud Storage (`revenuePlanBelege//...`). * **Optional AI receipt recognition (OCR):** Upon your action, Gemini 2.5 extracts invoice date, gross/net amount, tax rate, currency, invoice number, and issuer from a receipt as an editable booking suggestion. * **Statement Inspector:** Imported statement files (CSV, PDF, Office formats from GEMA, GVL, Spotify, Apple Music, DistroKid, etc.) are parsed inside isolated worker threads with strict size and page limits and matched against your catalog. * **GoBD locking & DATEV export:** Locked accounting periods are stamped with an immutable lock timestamp and an 8-year statutory retention marker and can be exported in standardized **DATEV format (EXTF 700)** for your tax advisor. ### e) Public Share Links, Guest Portals, Smart Links & ICS Calendar Feeds * **Public Share Links (`/share/*`) & Guest Portals (`/guest/:token`):** You can share selected content (such as roadmaps, EPKs, moodboards, split sheets) via token links. When accessing a password- or token-protected Guest Portal (*guestLinks*), a strictly necessary HttpOnly session cookie (`guest_session`, valid for up to 8 hours) is set; submitted guest feedback is stored in *guestFeedback*. * **Smart Links & Pre-Save Pages (`/l/:slug`, `/s/:slug`, `/presave/:slug`):** Published release landing pages (*smart_links*) publicly display the streaming links and artwork configured by you and count page views and streaming service clicks in aggregated form. * **Public ICS Calendar Feeds:** When you enable calendar synchronization, a cryptographic feed token is generated so external calendar applications can subscribe to your release and tour dates in iCalendar (`.ics`) format. You can revoke or regenerate the token at any time. **Legal basis for c) to e):** Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(a) GDPR (consent for optional public shares and AI OCR). ## 13. Analytics & Social Media Data (OAuth Connections) A central feature of esc/ctrl is the aggregation of streaming and social media metrics from various platforms: ### a) OAuth 2.0 Connections You can connect your accounts on the following platforms directly via standardized **OAuth 2.0 protocol**: * **Spotify:** Read access to profile, email, top tracks, playlists. Scopes: 'user-read-private', 'user-read-email', 'user-top-read', 'playlist-read-private', 'playlist-read-collaborative' * **Google / YouTube:** Read access to YouTube channel and Analytics. Scopes: 'userinfo.profile', 'userinfo.email', 'youtube.readonly', 'yt-analytics.readonly', 'analytics.readonly' * **Facebook / Instagram:** Read access to Pages and Instagram Business Insights. Scopes: 'email', 'public_profile', 'pages_show_list', 'pages_read_engagement', 'instagram_basic', 'instagram_manage_insights' * **TikTok:** Read access to basic user info and video stats. Scopes: 'user.info.basic', 'video.list', 'user.info.profile', 'user.info.stats' OAuth access tokens and refresh tokens are stored in encrypted form in Google Firestore (collections *oauthConnections* / *userConnections*). The tokens are used automatically by a server-side polling service (*oauthPoller*) to refresh metrics regularly. You can revoke a connection at any time in Settings; tokens will be deleted immediately upon revocation. ### b) Public profile fallback For platforms without an active OAuth connection, public profile pages are retrieved by our server. Optional AI extraction checks literal evidence for the metrics used. Non-public values are not invented. Historical Apify values remain marked as archived; new queries use our own server-side retrieval. Only publicly available metrics are processed. **Legal basis:** Art. 6(1)(a) GDPR (OAuth) and Art. 6(1)(b)/(f) GDPR. ### c) Active OAuth Token Revocation & Automated Meta Data Deletion Callback * **Active token revocation at the provider:** When you disconnect a platform integration in Settings or delete your account, stored OAuth tokens are not only deleted from our database but also actively revoked via the respective provider's revocation endpoint (Google, Meta, TikTok, Spotify; *revokeProviderTokens*). * **Meta Data Deletion Callback (`/api/social/meta/data-deletion` & `/data-deletion-status`):** In compliance with Meta Platforms Ireland Limited requirements, we provide an automated data deletion callback endpoint. If you remove the esc/ctrl app in your Facebook or Instagram account settings, Meta sends an HMAC-SHA256 signed deletion request to our server. We automatically delete all associated OAuth connections, link records (*metaAccountLinks*), and imported Meta analytics/social data, and provide a confirmation code and status page at `/data-deletion-status` (without exposing internal user IDs; status records in *metaDeletionRequests* expire automatically after 90 days). ## 14. Web Scraping Service (Apify) Earlier fallback data queries used **Apify** (Apify Technologies s.r.o., Václavské nám. 808/66, 110 00 Prague, Czech Republic). Those historical queries transmitted public profile URLs and your user ID. New profile queries no longer use Apify. Historical values and provenance remain available until deleted under our retention policy. Apify processes data in accordance with its privacy policy: [https://apify.com/privacy-policy](https://apify.com/privacy-policy). **Legal basis:** Art. 6(1)(b) and (f) GDPR. ## 15. Google Drive Integration esc/ctrl offers an optional **Google Drive export** for documents created in the AI Copilot and results from the Smart Tools. Google authorization with the `https://www.googleapis.com/auth/drive.file` permission starts only when you select “Google Drive” for a document. After you grant access, your browser sends the displayed document title and text to Google through the Google Drive API and creates a new **.txt file** in your Drive. No destination folder is currently selected. This export does not list existing Drive files or read the content or metadata of other files. It does not request full access to your Drive or establish persistent server-side Drive access. The exported file stays in your Google Drive until you delete it there; deleting your esc/ctrl account does not automatically remove it. You can revoke the Google permission in your Google account. **Legal basis:** Art. 6(1)(a) GDPR (consent). Google Privacy Policy: [https://policies.google.com/privacy](https://policies.google.com/privacy). ## 16. Lead Generation and Email Verification On the public landing page, visitors can request the *Release Strategy Guide* by entering their **name and email address**. Data collection uses a secure double opt-in procedure: * **Step 1:** Input in form * **Step 2:** Stored as unverified lead in Firestore (collection *leads*) and confirmation email sent * **Step 3:** Clicking the confirmation link verifies the lead and enables the guide download **Legal basis:** Art. 6(1)(a) GDPR (consent). ## 17. Newsletter (Mailchimp) For sending platform updates, industry news, and offers, we use **Mailchimp** (The Rocket Science Group LLC, 675 Ponce de Leon Ave NE, Suite 5000, Atlanta, GA 30308, USA). * **Data processed:** Email address, first name, last name * **Opt-in & Unsubscribe:** Double opt-in process. Unsubscribe anytime via link in any email or by contacting support@wmit.work * **Third country transfer:** Certified under the EU-US Data Privacy Framework and EU Standard Contractual Clauses (SCCs). Info: [https://mailchimp.com/legal/privacy/](https://mailchimp.com/legal/privacy/) **Legal basis:** Art. 6(1)(a) GDPR. ## 18. Payment Processing (PayPal) & Statutory Tax Retention (§ 147 AO / § 257 HGB) Payments for paid subscriptions (Artist, Label, Management, Booking) are processed via **PayPal (Europe) S.à r.l. et Cie, S.C.A.**, 22-24 Boulevard Royal, L-2449 Luxembourg. * **Data processed:** Name, email address, billing address, VAT ID, transaction ID, subscription plan. We do **not** store payment card or bank details ourselves. * **Statutory Retention Obligation:** Invoices, payment receipts, and tax-relevant transaction records are subject to an **8-year statutory retention period** under § 147(3) sentence 1 German Tax Code (AO) and § 257(4) German Commercial Code (HGB). Even upon account deletion, these accounting records remain stored in a separate, access-protected archive pursuant to **Art. 17(3)(b) GDPR**. PayPal Privacy Statement: [https://www.paypal.com/de/webapps/mpp/ua/privacy-full](https://www.paypal.com/de/webapps/mpp/ua/privacy-full). **Legal basis:** Art. 6(1)(b) GDPR (contract performance) and Art. 6(1)(c) GDPR (legal obligation). ### Technical security, fonts and providers Firebase App Check uses reCAPTCHA v3 by Google Ireland Limited / Google LLC to protect accounts, stored data and paid APIs against automated abuse. Google processes IP addresses, browser/device information and interaction signals for this purpose. App Check tokens are temporary. This necessary security processing is based on our legitimate interest (Article 6(1)(f) GDPR); strictly necessary device storage/access serves this protection (section 25(2)(2) TDDDG), rather than optional marketing. Google services may process data in the US; transfer safeguards are described in section 23. See https://policies.google.com/privacy and https://firebase.google.com/support/privacy. Fonts are delivered through the esc/ctrl domain with server-side caching. Your browser does not contact Google Fonts directly for font delivery; its IP address and browser cookies are not forwarded to Google for this purpose. On your request, uploaded documents, contracts, statements and embedded images may be sent to Gemini for OCR and analysis. Optional Google Search grounding and URL context send search queries or public URLs to Google. Avoid confidential information in search requests. AI output is a fallible suggestion, not a measured platform value or binding legal/tax advice. Inputs and action suggestions are constrained; complete prevention of prompt injection is not guaranteed. Connected providers include Spotify AB (Sweden, https://www.spotify.com/legal/privacy-policy/), Meta Platforms Ireland Limited (Ireland, https://www.facebook.com/privacy/policy/) and TikTok Technology Limited (Ireland, https://www.tiktok.com/legal/page/eea/privacy-policy/en). These independent providers process connected account data under their respective notices; these describe international transfers as well. ## 19. Hosting and Infrastructure (Google Cloud / Firebase / GoDaddy) * **Google Cloud Run:** The application’s production server runs in **us-west1 (Oregon, USA)**. Requests to this server are therefore processed in the USA. * **Google Firestore:** The production database is stored in **europe-west10 (Berlin, Germany)**. * **Google Cloud Storage / Firebase Storage:** The storage bucket used for Vault files is located in **US-WEST1 (Oregon, USA)**. Uploaded files are stored there. * **Google Firebase Authentication:** Sign-in is processed by a separate Google service. It is not bound to the Firestore database region; exclusively German or European processing is not guaranteed. * **GoDaddy LLC:** Domain registration (*wmit.work*) and DNS management. Info: [https://www.godaddy.com/en/legal/agreements/privacy-policy](https://www.godaddy.com/en/legal/agreements/privacy-policy). A Data Processing Agreement (DPA) pursuant to Art. 28 GDPR is in place. Firebase information: [https://firebase.google.com/support/privacy](https://firebase.google.com/support/privacy). **Legal basis:** Art. 6(1)(b) and (f) GDPR. ## 20. Cookies, Web Analytics and Local Storage (TDDDG & GDPR) esc/ctrl uses cookies and similar storage technologies (such as Local Storage and Session Storage) in full compliance with § 25 TDDDG and the GDPR. On our legal pages (Privacy Policy, Legal Notice, Terms of Service), the document text remains freely readable at all times without a blocking full-screen overlay before you make a cookie choice. ### a) Technology Categories * **Strictly Necessary / Essential Technologies (§ 25(2) No. 2 TDDDG, Art. 6(1)(b) and (f) GDPR):** * *Firebase Auth Tokens & Session Storage:* Encrypted tokens for secure authentication and authorization of your user session. * *OAuth State Token:* Temporary protection against Cross-Site Request Forgery (CSRF) during API platform connections (expiry: 10 minutes). * *Guest Portal Cookie ('guest_session'):* Strictly necessary HttpOnly and SameSite=Lax session cookie when accessing shared Guest Portals (`/guest/:token`), valid for up to 8 hours. * *Consent Storage ('cookie_consent' & 'analytics_consent'):* Retains your chosen cookie preferences, consent ID, and timestamp in Local Storage for a maximum of 12 months. After 12 months or upon an update of the consent schema, stored preferences expire automatically and consent is requested anew. * *Theme, Language & Interface Preferences:* Preserves your light/dark mode, language, and active workspace settings. * **Statistics & Reach Measurement (§ 25(1) TDDDG, Art. 6(1)(a) GDPR – explicit Opt-in):** * *Google Analytics 4 (GA4):* Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland / Google LLC, USA. * *Google Consent Mode v2:* We implement Google Consent Mode v2. All optional signals ('analytics_storage', 'ad_storage', 'ad_user_data', 'ad_personalization', 'personalization_storage') default to **'denied'** on page load. Google Analytics is only initialized after you actively grant consent in the Cookie Banner. * *URL Path Redaction ('sanitizeAnalyticsPath'):* Before page views are sent to GA4, confidential token segments in URLs (specifically under `/share/.../[redacted]`, `/guest/[redacted]`, and `/data-deletion-status/[redacted]`) are automatically redacted. * *SHA-256 Hashed User-Provided Data ('user_data') & Server-Side Measurement Protocol:* Only if you have explicitly consented to both “Statistics & Analytics” and “Marketing”, normalized user data (such as email address or address fields) may be hashed locally in your browser via the Web Crypto API as a **SHA-256 digest** (pseudonymized, not anonymized) before transmission to Google (never in plaintext). Likewise, our server only dispatches subscription lifecycle events (e.g. PayPal webhook events) via the **GA4 Measurement Protocol** if an active, non-revoked analytics consent record with a pseudonymous client ID (no older than 180 days) exists in your account (*analyticsConsents*). * **Marketing & Campaign Conversions (§ 25(1) TDDDG, Art. 6(1)(a) GDPR – explicit Opt-in):** * Controls the signals 'ad_storage', 'ad_user_data', 'ad_personalization', and 'personalization_storage' to measure the effectiveness of announcements and release campaigns. ### b) Account-Scoped Consent Synchronization & Audit Trail When signed in, your analytics consent choice is synchronized along with a pseudonymous client ID and a monotonically increasing sequence number in Firestore (collection *analyticsConsents*) so that any revocation immediately stops server-side Measurement Protocol events. In addition, legal consents (Terms, Privacy, optional marketing emails) are logged in an audit-proof manner in the collection *legalConsents* and its *auditLog* subcollection (storing a truncated 16-character SHA-256 IP hash and user agent pursuant to Art. 5(2), Art. 7(1) GDPR). ### c) Revocation, Cookie Cleanup and Subsequent Modification (Art. 7(3) GDPR) You can **revoke or adjust your consent** for individual or all optional cookie categories **at any time with future effect**: * via the **“Cookie Settings”** link in the footer of any public page, * via the action button on this Privacy Policy page, or * inside your account under **Settings** (“Legal” tab) as well as in the Client Center and Booking Client Center under **“Account & Privacy”**. Upon revocation, Google Consent Mode v2 signals are immediately updated to **'denied'**, the browser-wide disable flag (`window['ga-disable-...'] = true`) is set, existing first-party cookies (`_ga`, `_ga_*`, `_gid`, `_gat`, `_gcl_*`) are actively deleted, and the revocation is persisted server-side in *analyticsConsents*. The lawfulness of processing carried out prior to revocation remains unaffected. ## 21. Contact When contacting us via email or contact form, your details (name, email address, message text) are processed to handle your enquiry. **Legal basis:** Art. 6(1)(f) GDPR or Art. 6(1)(b) GDPR. ## 22. Disclosure of Data to Third Parties Data is disclosed to third parties exclusively: * To audited data processors under Art. 28 GDPR (Google Cloud/Firebase/Google Workspace SMTP, Mailchimp, Apify, PayPal) * To connected third-party platforms at your explicit request (OAuth) * In case of statutory or official obligations * **No Sales:** We never sell personal data to third parties. ## 23. Data Transfers to Third Countries Where service providers process data outside the EEA (e.g. Google, Mailchimp, GoDaddy in the USA), an adequate level of data protection is guaranteed via: * Certification under the **EU-US Data Privacy Framework** * Execution of **EU Standard Contractual Clauses (SCCs)** pursuant to Art. 46(2)(c) GDPR The production infrastructure spans the USA (application server and Vault file storage) and Germany (Firestore database). Processing therefore does not take place exclusively within the EU; individual locations are listed in Section 19. ## 24. Retention Periods, Account Deletion & Statutory Storage Obligations ### a) How account deletion works You start the deletion of your account yourself in the settings. Re-authentication is required to confirm your identity. * **14-day period:** After your request, your account remains active for 14 days. During this time you may revoke the deletion at any time and without giving reasons. Each time you sign in, we show you the deletion date and the option to revoke. * **Taking your data with you:** Until the period expires, you can download your data as JSON and CSV files (Art. 20 GDPR). * **Final deletion:** Once the 14 days have elapsed, your data is deleted automatically and irreversibly. Signing in with your previous credentials is no longer possible thereafter. * **Active subscription:** If a paid subscription is active, deletion is only possible after you have cancelled it. This prevents further charges being taken after deletion. ### b) What is deleted Once the period expires, the following are removed completely and irreversibly: your user account (Firebase Authentication), your artist or management profile, all additional workspaces (`_`), releases, playbooks, tasks, calendar entries, files stored in the Release Vault and Revenue Planner in Cloud Storage, tool results, AI jobs and token counters, analytics, consent (*analyticsConsents*) and social media data, chat histories and messages, guest links and guest feedback, support tickets and bug reports, as well as all connections to linked platforms (including active OAuth token revocation at the respective providers). Your account is also removed from any organisations you were linked to via the Client Center. * **Specific rule for Booking records (*bookingTours*, *bookingCrew*, *bookingRiders*):** If a booking agency deletes its account, all tours, crew entries, and riders created by that agency are completely deleted. Conversely, if an artist linked to an agency deletes their own account, the agency's business tour and rider records remain intact while the personal reference to the deleted artist is automatically anonymized to “Gelöschter Artist” (Deleted Artist). ### c) What is retained for statutory reasons Pursuant to **Art. 17(3)(b) GDPR** in conjunction with **§ 147(3) sentence 1 AO** and **§ 257(4) HGB**, we are required to retain accounting-relevant records. The following are therefore not deleted: * Email address, date of registration and date of account deletion * Billing address * Subscription and payment history including invoice numbers Upon deletion, this data is transferred to a **separate archive** that is isolated from the platform's live operation and accessed solely in fulfilment of tax or commercial law obligations. It is **no longer** processed for platform use, analytics or advertising purposes. After the retention period of **8 years**, calculated from the end of the respective calendar year, this data is deleted as well. ### d) Further retention periods * **Server Logs:** Erased automatically after a maximum of 7 days. * **Technical Copilot Engine Run Logs (*copilotEngineRuns*):** Erased automatically after 30 days. * **Meta Data Deletion Status Logs (*metaDeletionRequests*):** Erased automatically after 90 days. * **Server-Side Analytics Consent (*analyticsConsents*):** Considered for the server-side GA4 Measurement Protocol for a maximum of 180 days from grant and immediately disabled or deleted upon revocation or account deletion. * **Newsletter subscriptions and enquiries submitted via our contact and lead forms:** Stored independently of any account deletion on the basis of the consent given in each case, and revocable separately at any time (see sections 16 and 17). ## 25. Your Rights as a Data Subject (incl. Access & Self-Service Export) You have the following rights under the GDPR: * **Art. 15 GDPR – Right of Access:** Right to obtain confirmation and a copy of stored data concerning you. * **Art. 16 GDPR – Right to Rectification:** Right to correct inaccurate data. * **Art. 17 GDPR – Right to Erasure:** Right to have your account deleted. You can start the process yourself in the settings at any time; section 24 describes the exact procedure and the statutory exceptions. * **Art. 18 GDPR – Right to Restriction of Processing.** * **Art. 20 GDPR – Right to Data Portability:** Right to receive your data in a structured, standard format (use our self-service **CSV / JSON export feature** in settings). * **Art. 21 GDPR – Right to Object** against processing under Art. 6(1)(f) GDPR. * **Art. 7(3) GDPR – Right to Withdraw Consent.** Exercise your rights by emailing **support@wmit.work** (Subject: Data Protection). Requests are processed within 30 days. ## 26. Data Security We implement state-of-the-art technical and organizational measures (TOMs): HTTPS/TLS 1.3 encryption, AES-256-GCM encrypted Firestore storage for OAuth tokens, binary file signature verification for receipt uploads, isolated worker threads for document parsing, Firebase Auth with strong password hashing, and multi-layered prompt injection filtering for AI queries. The locations of the production infrastructure are listed in Section 19. ## 27. Amendments to this Privacy Policy We reserve the right to amend this Privacy Policy to reflect new features or legal updates. Registered users will be notified of material changes. ## 28. Right to Lodge a Complaint with the Supervisory Authority You have the right to lodge a complaint with the competent supervisory authority: **Berlin Commissioner for Data Protection and Freedom of Information** (Puttkamer Straße 16–18, 10969 Berlin, [https://www.datenschutz-berlin.de](https://www.datenschutz-berlin.de)). ## 29. Additional Processing: Copilot, Support and Consent The rule-based Copilot checks release deadlines, assigned content, budgets and technical file properties. Findings may be aggregated into a portfolio overview for the Client Center account responsible for its roster. These are recommendations; releases are not rescheduled automatically. Public profile and link checks process configured platform URLs and available profile data. Unavailable metrics remain marked as missing. Server-side Vault checks read file headers and, for supported PCM audio, audio blocks from existing storage. Cover images may be sent to the Google Gemini API for optional visual checks. Technical measurements and findings are stored with the file. AI findings may be incorrect and do not replace human approval. The legal basis for these product functions is Art. 6(1)(b) GDPR; the AI provider information in Section 9 also applies. Public support requests do not require an account. We store name, email address, subject, message, processing status and timestamps to handle the request; email matching does not grant access to an existing user account. Public requests are answered by email, authenticated requests within the ticket. Internal support notes remain separate from the user inbox. The legal basis is Art. 6(1)(b) GDPR for contract-related requests, otherwise Art. 6(1)(f) GDPR for handling requests and preventing abuse. Google Analytics is loaded only after valid website analytics consent. Statistical identifiers are pseudonymous, not necessarily anonymous. Sending hashed contact data (such as an email address) for Google matching additionally requires the separate marketing choice; hashing does not make these data anonymous. Withdrawal stops further browser use and clears accessible analytics cookies. It does not retroactively delete previously lawfully transmitted data. Choices apply per browser and domain; switching between escctrl.de and escctrl.wmit.work may require a separate choice. Legal basis for optional processing: Art. 6(1)(a) GDPR and Section 25(1) TDDDG. --- **Date of this Privacy Policy:** 5 November 2026 | **Version:** 1.5 | **Platform:** esc/ctrl (escctrl.wmit.work and escctrl.de) | **Operator:** wemakeITwork, Malte Schröder, Berlin Contact for data protection enquiries: support@wmit.work