Privacy Policy
Pursuant to Art. 13, 14 GDPR | Last updated: 17 November 2026 | Version 2.0
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, labels & team members using the Client Center, as well as booking agencies and tour managers using the Booking Client Center), guests on shared portals, 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 Digital Services Data Protection Act (TDDDG).
Table of Contents
- Controller
- Data Protection Officer
- Competent Supervisory Authority
- Principles of Data Processing
- Categories of Personal Data Processed
- Purposes and Legal Bases of Data Processing
- Registration and User Account (Firebase Authentication)
- Onboarding, Artist Profile, Additional Workspaces, Client Center & Booking Client Center
- AI-Powered Features (Google Gemini API / Google AI Studio)
- Support Ticket System, Customer Support & Bug Reports
- News Section, Release Notes, Product Updates & Announcements
- Download Section, Asset Management & Self-Service GDPR Data Export (CSV / JSON)
- Analytics & Social Media Data (OAuth Connections & Streaming Impulse Radar)
- Server-Side Retrieval of Public Artist Profiles (No Third-Party Scraping Providers)
- Google Drive Integration
- Lead Generation and Email Verification
- Newsletter (Mailchimp)
- Payment Processing (PayPal) & Statutory Tax Retention (§ 147 AO / § 257 HGB)
- Hosting and Infrastructure (Google Cloud / Firebase / GoDaddy)
- Cookies, Web Analytics and Local Storage (TDDDG & GDPR)
- Contact
- Disclosure of Data to Third Parties
- Data Transfers to Third Countries
- Retention Periods, Account Deletion & Statutory Storage Obligations
- Your Rights as a Data Subject (incl. Access & Self-Service Export)
- Data Security
- Amendments to this Privacy Policy
- Right to Lodge a Complaint with the Supervisory Authority
- Additional Processing: Copilot, Vault Inspection, 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.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
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 & onboarding status: Name, email address (including verification status), password (encrypted in Firebase Auth), unique account identifier, profile picture URL, and individual onboarding progress
- Artist profile data (Artist App), Achievements & Additional Workspaces: Artist name, genre, biography, target audience, release dates, monthly listener goal, print specifications, unlocked platform milestones (Achievements), and isolated additional project workspaces
- Client Center, Booking Client Center, Team communication & Manager data: Manager name, agency/label name, managed artist profiles, two-step artist link requests, invited team members' email addresses (including abuse-protected SHA-256 invitation hashes), assigned role permissions, internal team and artist chat channels, comments, briefings, as well as tour, show, crew, rider, and venue records in the Booking Client Center
- Social media, streaming & impulse data: Profile URLs, monthly profile checks, streaming impulse signals, and public or authenticated metrics from Spotify, YouTube, YouTube Music, Instagram, Facebook, TikTok, X (Twitter), 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 procedure
- AI interaction, Copilot, contract & job data: Chat messages, requests and generated responses within the AI assistants and the 30+ music AI Smart Tools, audited contracts and AI risk/clause analyses, Release Agent configurations, proactive Copilot insights, Brand Voice preferences, asynchronous AI job payloads, and aggregated token budget counters
- Planning, catalog, Content Hub, Release Vault & project data: Structured release and track catalog metadata (incl. ISRC, UPC/EAN, GEMA work numbers, splits, and credits), release plans, playbooks, roadmaps, milestones, projects and moodboards, content ideas and social posts, Kanban tasks, calendar entries (incl. attachments and 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 including technical specification, loudness (LUFS, True Peak dBTP), and optional AI cover artwork inspection - Financial, statement & receipt data (Revenue Planner & Statement Inspector): Financial and budget plans, uploaded receipts and invoices (including optional AI receipt OCR), imported distributor and collecting society statements (from GEMA, GVL, Spotify, Apple Music, etc.), GoBD period locking attributes, and DATEV exports
- Support, bug report & feedback data: Support tickets (including public support requests submitted without a user account), isolated internal support notes, technical bug reports, and feedback submitted via Guest Portals
- 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 (in server/security logs or as a truncated 16-character SHA-256 hash in the consent audit trail), browser/device information, login and activity timestamps, session data, documented legal and cookie consents, article views in the news section
- Communication data: Transactional emails via our Google Workspace transactional email service (team invitations, replies to public support requests, trial/comp expiration reminders, contract and payment notices about your subscription) 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, subscription, Add-on & retention data: Billing address, VAT ID, subscription status, booked Add-on packages (for extra artist slots, extra storage space, and extra team members incl. quantities and scheduled end-of-period reductions), scheduled billing cycle changes, payment failure grace periods, confirmed billing periods, one-time trial eligibility status (including an irreversible cryptographic HMAC-SHA256 digest of the payment provider's payer identifier for abuse prevention), transaction ID, and accounting records archived for statutory tax retention upon account deletion. Payments are processed via PayPal; we do not store payment card or bank 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, connecting third-party platforms via OAuth, using optional AI features such as receipt OCR or cover artwork checks, 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, two-step artist linking, 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/portability rights under Art. 15, 20 GDPR)
- Art. 6(1)(f) GDPR – Legitimate interests: Processing in pursuit of our legitimate interests (e.g. operation, protection and IT security of the platform, abuse prevention, enforcing verified email addresses for team permissions, resolving technical bugs via the support and bug report system, providing the news and release notes sections)
7. Registration and User Account (Firebase Authentication)
Registration is required to use the protected areas of 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.
During registration and sign-in, Firebase Authentication processes your account identifier, email address, email verification status, display name, profile picture URL (for Google sign-in), account creation and last sign-in timestamps, and technically required connection data (such as the IP address in Firebase Authentication security logs). In Google Firestore (NoSQL database, region: europe-west10, Berlin, Germany), your user or management profile and your documented legal acknowledgements (storing a truncated 16-character SHA-256 hash of your IP address in the audit trail without storing plaintext IP addresses in the profile document) are created. Email-based team and collaboration permissions strictly require a verified email address to prevent unauthorized access via unverified email registrations.
Legal basis: Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(f) GDPR (account security). Google/Firebase's privacy policy is available at https://firebase.google.com/support/privacy and https://policies.google.com/privacy.
8. Onboarding, Artist Profile, Additional Workspaces, Client Center & Booking Client Center
After registration, you may use the platform as an individual artist (Artist App), across multiple project workspaces, or as a manager, label, agency, or booking team (Client Center & Booking Client Center):
a) Artist App, Artist Profile, Catalog & Achievements
When creating and using an artist profile, your project records are stored in Google Firestore and uploaded media files are stored in Google Cloud Storage:
- Required fields: Artist name, genre
- Optional fields: Biography, target audience, focus goals, release and catalog data (album, EP, single, music video, track metadata, ISRC, UPC/EAN, GEMA work numbers, splits), tour dates, monthly listener goal, social media links, planning preferences, contracts, and print specifications
- Growth Roadmaps, Playbooks, Milestones & Achievements: Automatically or manually generated strategy roadmaps and release playbooks as well as unlocked milestones and achievements (Achievements) with completion timestamps
b) Client Center (Managers, Labels, Team Management & Two-Step Artist Linking)
For managers, labels, and agencies, the Client Center provides enhanced collaboration and management features:
- Manager master data: Manager, label, or agency name, specialization, contact information
- Two-step consent workflow for artist linking: A management, label, or booking account only gains access to an artist account after the respective artist has actively confirmed the link request. Both the artist and the management can sever the link at any time (Artist entkoppeln / decouple artist); the artist's own data remains completely intact
- Team member management & communication: Inviting team members by email, assigning granular role and module permissions (Admin, Manager, Member, Booking roles, scoped artist or tab access), and collaborating via project chat channels and task/release comments
c) Additional Workspaces (Multi-Project Management)
Users can create additional isolated artist workspaces under one main account. 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. 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, replies to public support tickets, trial or comp access expiration reminders, and contract and payment notices about your subscription, e.g. confirmation of a cancellation including the access end date, withdrawal of a cancellation, failed payments, subscription pauses or payment reversals), we use our Google Workspace transactional email service (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 rate-limit log, without retaining plaintext recipient email addresses.
Delivery queue: To ensure that these notices, as well as internal notes to our support team about your account, arrive even during temporary delivery problems and are not sent twice, we place them in a delivery queue before sending. An entry contains your user identifier, the type of notice, its content and the delivery status and timestamps, but not your email address; the address is read from your user account only at the moment of sending. We make no more than five delivery attempts within 48 hours. As soon as a notice has been sent or has finally failed, we delete its content. A delivery record without content (type of notice, status, timestamps) is kept for 30 days to prevent duplicate messages and is then deleted automatically. When your user account is deleted, all related entries are deleted immediately.
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 (Google Gemini API / Google AI Studio)
esc/ctrl continuously utilizes current AI models from the Google Gemini Series (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
- Proactive AI Copilot (Insight Engine), Streaming Impulse Radar & 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, as well as a monthly Social Media Profile Check inspecting public profile bios and pre-save/smart links. Technical engine execution logs are automatically deleted after 30 days
- 30+ Specialized Music AI Smart Tools & Contract Analysis: Domain-specific tools (including Contract Analyzer for clause and risk analysis of stored contracts, GEMA Assistant, EPK Builder, Mastering QC, Split Sheet Generator, press text, pitch and storytelling assistants, merch and tour budget calculators), AI-powered receipt OCR in the Revenue Planner, and optional AI visual compliance checks for cover artworks in the Release Vault
- Growth Roadmap, Release Agents, Content Generator & Release/Tour Planner: AI-assisted generation and optimization of custom growth roadmaps, release agent workflows, 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; aggregated token consumption per account and period 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 application server to the Google Gemini API. User inputs and external content are bounded as data and action suggestions are validated. Complete prevention of prompt injection and factual errors cannot be technically guaranteed.
- 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.
- High Availability: The system uses current Google Gemini models with automated fallback mechanisms to ensure service reliability.
In addition, at your request we process uploaded documents, contracts, and statements including embedded images for optical character recognition (OCR) and analysis. Optional Google Search grounding and URL context may transmit search queries or public URLs to Google. Avoid confidential information in search queries. AI outputs are suggestions and not verified measurements or binding legal/tax advice. Image features use current Gemini image models. Provider: Google Ireland Limited / Google LLC, privacy notices at https://policies.google.com/privacy and API terms at https://ai.google.dev/gemini-api/terms.
Legal basis: Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(a) GDPR (consent for optional usage).
10. Support Ticket System, Customer Support & Bug Reports
To handle technical enquiries, customer service requests, and bug reports, we operate an integrated Support and Reporting System.
Data Collected & Operation:
- Signed-in Users (In-App Support & Bug Reports): Account identifier (always associated with your main account even when submitted from an additional workspace), name, email address, enquiry category (e.g. Authentication, API Error, Billing, Feature Request), subject, detailed issue description, priority, optional attachments, and the communication history inside the ticket. Replies from our support team are delivered directly within your in-app ticket inbox.
- Public Support & Contact Requests (without a user account): Via the public Support page ('/support'), you can submit enquiries without registering. We process your name, email address, subject, message, processing status, and timestamps. Submitting an email address never grants access to an existing user account; replies to public enquiries are sent by email via
support@wmit.work. - Separation of Internal Support Notes: Internal administrative support notes are stored separately and are technically isolated from the user inbox.
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; upon account deletion, your account-bound support tickets and bug reports are deleted in accordance with Section 24. Legal basis: Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(f) GDPR (legitimate interest in platform stability, abuse prevention, and effective support).
11. News Section, Release Notes, Product Updates & Announcements
On our platform, we provide a publicly and internally accessible News Section ('/news') as well as public Release Notes ('/release-notes'). Here, we publish platform updates, documented feature changes, music industry best practices, and system announcements. Our public Release Notes and legal documents are governed by a strict policy never to contain internal administration data, security-sensitive internals, or unauthorized personal data.
Data Processing in the News Section:
- When viewing news articles, anonymized view counters are updated to measure content relevance.
- If you are a logged-in user, we process your session data 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 (under “Account & Privacy” in the Artist App, Client Center, and Booking 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, unlocked achievements (Achievements), contracts, billing & tax records, revenue plans including all accounting entries, receipts, activity logs, and 7-day signed download links for uploaded receipt files, connected platforms, roadmaps, playbooks, tasks, calendar entries, booking tours/crew/riders, chat histories, AI job inputs, guest feedback, documented consents, and a cryptographic completion manifest. All timestamps are normalized to ISO-8601 format. 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. For quality assurance, esc/ctrl automatically inspects audio and image files against technical distributor specifications:
- Inspected parameters: Sample rate, bit depth, channels, file format, image resolution, aspect ratio, color space, and—for complete PCM audio files—integrated loudness (LUFS) and true peak level (True Peak dBTP) according to ITU-R BS.1770 / EBU R 128 (truncated or incomplete audio streams are rejected so that partial measurements are never reported as full loudness values).
- Processing & Optional AI Cover Inspection: Technical 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. Optionally, cover artwork images can be checked via the Google Gemini API against distributor visual guidelines (e.g. prohibited URLs, social handles, or third-party logos).
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, receipts, and imported royalty statements:
- Receipt upload & signature verification: Uploaded invoices and receipts are verified against binary file signatures (PDF, JPEG, PNG, WebP, HEIC) and stored in Cloud Storage; direct browser access is blocked and access is mediated exclusively through authenticated server endpoints.
- Optional AI receipt recognition (OCR): Upon your action, AI 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. Public artist summary fields are served exclusively via a filtered server interface without exposing email addresses. When accessing a password- or token-protected Guest Portal, a strictly necessary HttpOnly session cookie (valid for up to 8 hours) is set. - Smart Links & Pre-Save Pages (
/l/:slug,/s/:slug,/presave/:slug): Published release landing pages 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 & Streaming Impulse Radar)
A central feature of esc/ctrl is the aggregation of streaming and social media metrics from various platforms as well as the detection of organic reach impulses:
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 with AES-256-GCM encryption in our database and used by a server-side synchronization service to refresh metrics regularly. You can revoke a connection at any time in Settings; tokens will be deleted immediately upon revocation.
b) Public profile retrieval & data integrity (OAuth-first)
Whenever an active OAuth connection exists for a platform, metrics are retrieved exclusively through the provider's authenticated official API. Only if no OAuth connection is active for a platform, and you have saved a public artist profile URL in your settings, our server retrieves publicly visible baseline metrics via a multi-stage procedure (see Section 14). Non-public or unavailable values are never fabricated or treated as zero. During the monthly profile check, month-over-month comparisons are only performed when a verified reading from the immediately preceding calendar month exists for the identical profile ID; switching to a different platform profile starts a fresh measurement series. 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).
- Meta Data Deletion Callback (
/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, and imported Meta analytics/social data, and provide a confirmation code and status page at/data-deletion-status(without exposing internal account IDs; status logs expire automatically after 90 days).
14. Server-Side Retrieval of Public Artist Profiles (No Third-Party Scraping Providers)
Where no OAuth connection is active for a supported platform (YouTube, YouTube Music, Instagram, Facebook, TikTok, X/Twitter, Spotify, Apple Music, Amazon Music, or Deezer), but you have explicitly saved a public profile URL in your settings, our application server collects exclusively publicly visible baseline metrics of your designated artist profile in up to three stages:
- Stage 1 – Official Public Platform APIs: Where the platform exposes public catalog or channel statistics without user login, metrics are retrieved directly from the official public endpoint.
- Stage 2 – Direct Server-Side Metadata Retrieval: If Stage 1 does not supply the metric, our server fetches the configured public profile URL directly via HTTPS and parses structured page metadata (such as OpenGraph or Schema.org tags). No external third-party scraping providers are used, and no login or access barriers are bypassed.
- Stage 3 – Source-Grounded Web Search (Google Search Grounding via Google Gemini API): If metrics cannot be determined via Stages 1 and 2, a source-grounded web lookup may be performed via the Google Gemini API with Google Search enabled. Only your configured public profile URL and artist name are submitted; figures are accepted exclusively when literally backed by cited public web sources. Your account identifier and email address are never included in search queries.
Only publicly visible profile data of the artist profile configured by you is processed; private third-party data is never collected. Legal basis: Art. 6(1)(b) GDPR (provision of requested analytics features under your contract) and Art. 6(1)(f) GDPR. The Google provider details in Section 9 apply accordingly.
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.
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: Server-validated and rate-limited storage as an unverified lead in our database and dispatch of a confirmation email
- 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/
Legal basis: Art. 6(1)(a) GDPR.
18. Payment Processing (PayPal), Add-on Packages & Statutory Tax Retention (§ 147 AO / § 257 HGB)
Payments for paid subscriptions (Artist, Label, Management, Booking) as well as recurring Add-on packages (extra artist slots, extra Vault storage, and extra team members) 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, booked Add-on packages including quantities and scheduled end-of-period quantity reductions, scheduled switches between monthly and annual billing, confirmed payment periods, one-time 7-day Artist trial status (including an irreversible cryptographic HMAC-SHA256 digest of the payment provider's payer identifier to prevent multiple redemptions of the one-time free trial period), and technical idempotency keys to prevent duplicate payment booking. We do not store payment card or bank details ourselves. Access to paid features is determined strictly by confirmed paid billing periods or an active one-time trial period.
- Contract and payment notices: We automatically inform you by email, sent to the address of your user account, about essential events of your subscription (confirmation of a scheduled or completed cancellation, withdrawal of a cancellation, failed payments, subscription pauses, payment reversals) (Art. 6(1)(b) GDPR). For details on sending, see Section 8 e).
- One-time trial and abuse prevention: Under our Terms of Use, the free trial is available once per user account; circumventing this through additional accounts is not permitted. To enforce this, when a trial starts we store a record linked to your user account (user identifier, identifier of the trial subscription, timestamp). For the PayPal payment account used, we store only an irreversible cryptographic hash value (HMAC-SHA256) of the payer identifier (Payer ID) transmitted by PayPal, together with the time of the first trial and, for as long as the user account exists, the identifier of the trial subscription. We do not store the payer identifier itself in plain text. If another trial is requested from a different user account with the same PayPal payment account, we automatically cancel the newly created trial subscription with PayPal, do not grant free access and inform you that you can take out the subscription directly without a trial. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in preventing abusive repeated use of the trial). For the retention period, see Section 24 d).
- Payment Failure (7-Day Grace Period), Suspension & Reactivation: If a recurring debit fails, the system records a payment issue with a 7-day grace period. If a subscription is temporarily suspended by PayPal, booked Add-on packages remain preserved with their configuration intact and can be reactivated after updating the payment method via self-service reactivation in the subscription settings or upon successful payment capture, which automatically clears the dunning flag.
- 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 archive completely locked against client access pursuant to Art. 17(3)(b) GDPR.
PayPal Privacy Statement: https://www.paypal.com/de/webapps/mpp/ua/privacy-full. Legal basis: Art. 6(1)(b) GDPR (contract performance), Art. 6(1)(c) GDPR (legal obligation), and Art. 6(1)(f) GDPR (legitimate interest in protecting against abuse of free trial periods).
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. 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, receipts, and user uploads 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.
A Data Processing Agreement (DPA) pursuant to Art. 28 GDPR is in place. Firebase information: 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 Session Cookie: Strictly necessary HttpOnly and SameSite=Lax session cookie when accessing shared Guest Portals (
/guest/:token), valid for up to 8 hours. - Consent Storage: Retains your chosen cookie preferences, consent ID, schema identifier, 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, CMS & Interface Preferences: Preserves your light/dark mode, language, and active workspace settings as well as a non-personal local warm cache for public texts, FAQs, and templates in Local Storage to accelerate page rendering.
- 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. Accept and reject options are equally accessible in the banner.
- Automatic URL Path Redaction: Before page views are sent to GA4, confidential token segments in URLs (specifically on public share links, Guest Portals, and deletion status pages) are automatically redacted.
- SHA-256 Hashed User-Provided 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 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.
- 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 our database so that any revocation immediately stops server-side Measurement Protocol events. In addition, legal declarations (Terms acceptance, Privacy Policy acknowledgment, optional marketing emails) including the effective date and document version are logged in an audit-proof atomic transaction with an audit trail (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', browser tracking is disabled, existing first-party analytics cookies (_ga, _ga_*, _gid, _gat, _gcl_*) are actively deleted, and the revocation is persisted server-side. The lawfulness of processing carried out prior to revocation remains unaffected.
21. Contact
When contacting us via email or the public support/contact form, your details (name, email address, subject, 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, Mailchimp, PayPal)
- To connected third-party platforms at your explicit request (OAuth / Google Drive export)
- 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/receipt 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 & Add-ons: If a paid main subscription or an active Add-on package is active, account deletion is only possible after you have cancelled the subscription or Add-on packages to the end of the billing period. This prevents further PayPal charges from 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 and tracks, playbooks, roadmaps, milestones, tasks, calendar entries, achievements (Achievements), contracts, all files stored in the Release Vault, Revenue Planner, and user/project folders in Cloud Storage, tool results, AI jobs and token counters, analytics, streaming impulse, consent and social media data, chat histories, channels and comments, 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: 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, locked against all client access, 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 System and Copilot Run Logs: Erased automatically after 30 days.
- Meta Data Deletion Status Logs: Erased automatically after 90 days.
- Server-Side Analytics Consent: 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.
- Abuse prevention for the one-time free trial period: The record linked to your user account (user identifier, identifier of the trial subscription, timestamp) is deleted when your user account is deleted. The hash value (HMAC-SHA256) of the PayPal payer identifier, together with the time of the first trial, remains stored after an account deletion so that no further free trial can be obtained through a new account using the same PayPal payment account; we remove the identifier of the trial subscription at that point. The hash value is deleted automatically 24 months after the start of the first trial. It is pseudonymised: without the original payer identifier, neither that identifier nor your identity can be derived from it. The legal basis is Art. 6(1)(f) GDPR. You can object to this processing on grounds relating to your particular situation pursuant to Art. 21(1) GDPR.
- Delivery queue for system emails: The content of a notice is deleted as soon as it has been sent or has finally failed after the last delivery attempt. The delivery record without content is deleted automatically after 30 days, and immediately upon 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 storage for OAuth tokens, binary file signature verification for receipt uploads, isolated worker threads for document parsing, mandatory email verification checks for team and collaboration access, 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 and Version / Acknowledgment Rules
We reserve the right to amend this Privacy Policy when introducing new platform features, updating technical infrastructure, or adapting to amended legal or regulatory requirements.
- Mandatory Update of Version Number and Effective Date ("Last Updated"): Whenever this Privacy Policy (or the Terms of Service) is amended, both the version number and the effective date ("Last updated" / "Stand") are mandatorily updated in the Platform's central legal configuration and displayed synchronously in the document header, footer, and downloadable text files.
- Single-Step Confirmation of the Latest Version Only After Multiple Updates: Registered users are informed of updates in the Platform's update dialog upon their next sign-in. If multiple consecutive updates to the Privacy Policy or Terms of Service have been published since a registered user's last sign-in, the user only ever needs to acknowledge / confirm the single latest version currently in effect once upon sign-in (and never all intermediate prior versions sequentially), as the current version consolidates all preceding revisions.
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).
29. Additional Processing: Copilot, Vault Inspection, 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, complete 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: 17 November 2026 | Version: 2.0 | Platform: esc/ctrl (escctrl.wmit.work and escctrl.de) | Operator: wemakeITwork, Malte Schröder, Berlin
Contact for data protection enquiries: support@wmit.work