DepositoLive privacy policy – website and app
Updated 22 November 2026. This privacy policy explains the processing of personal data when using the DepositoLive website and app. The information applies to the features you use; optional provider features are described separately.
Controller and contact
ProWebSolutions GmbH, Aurelienstraße 48, 04177 Leipzig, DE
recht@depositolive.de
Request deletion of your account or individual data
In the app, open Account and choose account deletion; on the website, use Account & Privacy. Confirm your identity and then the deletion request. Without signing in, email the privacy contact above with the subject “DepositoLive: delete account”. To remove individual data without deleting your account, use “DepositoLive: delete data” and identify the content. We verify identity before changing another person’s account data. The exceptions below for necessary contractual, financial and security records also apply.
Account and sign-in
We process your email address, password hash for password accounts, Google identity link if selected, profile, roles, language, adult confirmation and session data to provide and secure your account (GDPR Article 6(1)(b) and (f)). On the website, standard sessions last 24 hours, or seven days with “Stay signed in”. In the app, “Stay signed in” is enabled by default: sign-in lasts 30 days from the last authorised use and renews with continued use. The session key rotates at the next app connection after seven days. Without this option, sign-in lasts 24 hours; signing out or revocation ends it earlier. The adult confirmation does not collect a date of birth.
Profiles and community
Profile names, images, descriptions, posts, comments and interactions are shown according to visibility settings. Follows, hearts and the feed priority you choose are processed to provide these functions (Article 6(1)(b)). Private profiles and posts remain subject to access controls. Your email address is not used as a public profile name.
Music and tickets
Account, purchase and entitlement references, tracks, playback/usage events, ticket and QR identifiers, event details and where applicable seat or check-in data are processed for access, delivery and existing licensing/usage reporting (Article 6(1)(b) and (c)). These events are not automatically anonymous.
Local app storage
Native session data use Android Keystore-protected storage. Embedded DepositoLive pages receive a Secure/HttpOnly session cookie only for our own HTTPS domain and have no Capacitor bridge. Library and ticket-wallet data may be stored locally; music files are stored offline only when authorised. Signing out removes account-bound local music, library and ticket data. Uninstalling or clearing app data removes local app storage. Android cloud backup is disabled. Necessary local storage serves the requested function (section 25(2) German TDDDG).
Hosting, email and security
The operator confirmed on 12 November 2026 that the platform and its own mail server are hosted by Hetzner at Helsinki, Finland. No additional external email relay is configured. Requests generate IP addresses, times, resources, status and technical device/error data for delivery, diagnosis and abuse prevention (Article 6(1)(b) and (f) GDPR). The infrastructure provider receives data as necessary to operate hosting. Logs remain for necessary diagnosis, incidents or specific evidence; no uniform automatic deletion period is configured for all logs.
Google, Stripe and recipients
Optional Google sign-in sends authentication data to Google; we receive the verified identity and email. Google maps/place searches load only when explicitly requested and may send IP addresses and search/address data; manual entry remains available. Stripe handles ticket payments and seller onboarding, receiving the necessary order, payment, contact and verification data. Our app does not collect card details. Sellers/organisers receive buyer and ticket data needed to fulfil the contract. Chosen authentication/payment functions rely on Article 6(1)(b); optional maps rely on consent under Article 6(1)(a). External providers may process data internationally; recipients and safeguards are described under “External providers and international processing”.
Messages and retention
Verification, security, order and ticket messages serve account or contract purposes. Social emails follow your preferences and are off by default. Account/content data are generally retained until deletion or the end of use, subject to continuing purposes or retention duties. Orders, invoices, consent and accounting records follow applicable legal duties or necessary legal claims (Article 6(1)(c) and (f)). Reports and moderation decisions are kept as needed for handling, evidence and legal defence.
Your rights and account deletion
Subject to applicable conditions, you can request access, correction, erasure, restriction and portability, withdraw consent for the future, object on grounds relating to your particular situation to legitimate-interest processing, and complain to a supervisory authority. Use the contact above. In-app account deletion requires renewed identity verification and a separate confirmation. It hides the profile without erasing legally required evidence or other customers’ acquired rights. Required account, entitlement and order data are necessary for the related functions. No automated decision producing legal or similarly significant effects is made.
One profile and visibility
Each account has one profile with optional artist and organiser capabilities. New profiles start public; fans can change visibility later. Artist profiles remain public during active public use. Profiles with unchanged placeholder names are excluded from search. Public details can be seen by users, visitors and search engines. Follower/following list visibility is separately configurable; your own feed priority is not public. Processing provides the requested profile/community function (Article 6(1)(b) GDPR).
Image processing and face framing
When you voluntarily upload a post image we validate type, size and decoding and create display variants. The platform sends the image over an encrypted connection to its own restricted image-processing worker for framing. SCRFD detects face regions only, retaining dimensions, count, rectangle and relative focus coordinates. It performs no identity matching, face gallery or storage of biometric recognition features. Without a detected face we use the centre. This provides the requested post display (Article 6(1)(b)). Focus data is retained with the content; analysis creates no new public identity.
Image metadata
Newly rendered profile, post and comment variants omit source EXIF/GPS metadata. Album covers also retain an unchanged original in protected music storage; metadata removal from that original is not established. Upload only images you intend to publish. Originals, derivatives and links remain for requested display and existing access rights and are cleaned according to reference-dependent deletion rules (Article 6(1)(b)).
Camera, photos and ticket scanning
The camera is used only when you choose to take a photo or perform an authorised ticket scan. You select individual photos; your entire photo library is not uploaded. A post photo is uploaded only when submitted. Admission scanning validates the recognised ticket token against the event and scanner permission; camera frames are not sent to the server for this. The basis is the requested function (Article 6(1)(b)). You can revoke Android permission in system settings.
Device image and music storage
Discovery music and artist covers share a 10 MiB image cache; feed images have a separate 5 MiB cache. Older files are evicted at the limit. Library covers remain account-bound. Authorised audio is stored in protected app storage subject to your download limit. A permitted track being played can be saved; whole albums use your Wi-Fi/download choice. Permanent and time-limited rights are checked separately; downloading a pass does not make it permanent. Offline usage events wait locally for synchronisation. This storage provides playback and requested offline access (section 25(2) TDDDG and Article 6(1)(b) GDPR).
Cookies and browser session storage
deposito_session provides the necessary website session for 24 hours, or seven days with Remember me. Persistent app sign-in uses a 30-day period renewed with use and key rotation after seven days; deposito_locale retains language for up to one year. HTTPS cookies are Secure, HttpOnly and SameSite=Lax; CSRF data stays in the session. The server session-file cleanup threshold of 32 days is not a guaranteed deletion deadline. sessionStorage can retain edited event drafts and audio upload session references until save, discard, completion or tab-session end. Our web code does not use localStorage. Google/Stripe pages you explicitly open may use their own storage. Necessary storage relies on section 25(2) TDDDG.
Usage reporting and accounting
Music access and licensing reports use track/album reference, usage type, time, country and, where relevant, a temporary order link. Music usage events do not retain a permanent listener identifier or IP address; technical server logs can contain IP addresses. Short-lived playback/download sessions are cleaned after expiry and a technical grace period; the separate reporting-to-order link expires after 30 days. Necessary usage and accounting evidence remains for contracts, licences and statutory evidence. Recipients can include involved rightsholders, collecting societies or their reporting agents where the actual licence/reporting operation requires it (Article 6(1)(b), (c) and (f)).
No advertising or device surveillance
The app uses no advertising ID or third-party advertising/analytics service. It requests no contacts, microphone or precise device location access. Event addresses and a country processed for tax/usage are not GPS tracking. There is no hidden recommendation based on advertising or engagement profiles. Reports and reasoned moderation decisions are access-controlled and kept as necessary for handling, statutory evidence or legal defence.
Deletion and retention details
Deletion requests are available under Account in the app and Account & privacy on depositolive.de; without signing in you can use the contact above. After identity re-verification and separate confirmation, the account is disabled, session access revoked and profile hidden; subsequent cleanup removes or anonymises data/content no longer needed. Orders, invoices, consents and security evidence remain restricted for outstanding contracts, statutory retention and necessary legal defence. Deletion does not cancel orders or destroy other customers’ acquired rights. Unconfirmed registrations are cleaned no sooner than 72 hours where no required references exist. Used/expired verification and reset tokens are technically cleaned. Immediate deletion of every financial or backup record is not promised.
External providers and international processing
For Google sign-in and Google user services, Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, is generally the data controller in the EEA. Google LLC in the USA participates in worldwide processing. This is distinct from the contracting entity for Google Cloud billing. Google explains its transfer mechanisms at policies.google.com/privacy/frameworks, including the EU-US Data Privacy Framework for certified US recipients and standard contractual clauses. Our payment platform uses ProWebSolutions GmbH’s German Stripe business account. Stripe names Stripe Payments Europe, Limited and, for relevant payment services, additionally Stripe Technology Europe, Limited, Ireland, for European business customers. Stripe acts partly on our instructions and partly as an independent controller, for example for statutory checks and fraud prevention. The account-related Stripe Privacy InfoPack describes US hosting, international processing and DPF or standard contractual clauses. Further information: stripe.com/privacy and stripe.com/legal/dpa. Contact our privacy contact for information about applicable safeguards and a copy of available guarantees. We do not promise exclusively European processing by external providers.
Artists, organisers and sales reports
When you offer music or events, we process the seller details, business/invoice email, address, country and any tax information you provide, rights declarations, music files, covers and event information for publication, contracts and accounting (Article 6(1)(b) and (c) GDPR). Seller details and tax profiles are managed separately; missing information is not fabricated. Selected contact details are transferred when you request Stripe onboarding. You enter bank, identity-document and additional verification information in the Stripe process; DepositoLive processes the account, capability and settlement references Stripe returns. Individual sales messages and optional scheduled ticket reports follow seller settings. If you add a second report address, the report and its sales information are also sent there. Only enter an authorised recipient. PDF/CSV exports and original documents are available to authorised accounts.