Privacy Policy

1. Controller

The controller under Art. 4(7) GDPR is:

Represented by Jan Burzinski and Benoît Jaenisch. Email: info@bejanic.de, phone: +49 155 66800465. Security reports: security@bejanic.de.

We are not legally required to appoint a data protection officer. Send privacy requests to the address above.

2. Principles and legal bases

We process personal data only as needed to run a working, secure service. Content you upload is private by default. We do not analyze it for advertising, sell data, or use advertising networks.

We rely on:

• Art. 6(1)(b) GDPR — performing the user contract: account, service delivery, uploads, playback, sharing, billing, and support.
• Art. 6(1)(f) GDPR — legitimate interests: security and abuse prevention, technical logging, error diagnosis, sparse reach measurement, and product development.
• Art. 6(1)(a) GDPR — consent: waitlist signup, optional diagnostics with feedback, and push notifications you enable in the OS and the app. You may withdraw consent at any time for the future.
• Art. 6(1)(c) GDPR — legal obligations, including commercial and tax retention.

3. Visiting the website and server logs

When you load tapedeck.stream, our infrastructure processes technically necessary connection data: IP address, date and time, requested URL, HTTP status, bytes transferred, referrer, and browser/device details (user agent). This is required to deliver the page, fend off attacks and overload, and fix outages.

The legal basis is Art. 6(1)(f) GDPR. Transport is TLS-encrypted. Rate limiting briefly processes features derived from IP address and account identifier.

4. Account and sign-in

Using tapedeck requires an account. You can sign in with Sign in with Apple, Google, email and password, or — on the web — a one-time code sent to your email. Password hashes, where used, are stored by our authentication provider, not in tapedeck’s application database.

Registration and sessions run through Clerk. Processed data include email address, optional name, username and profile photo, sign-in times, method used, and technical session and security data. Inside tapedeck, your display name and photo are shown to members you share folders or tracks with.

The legal basis is Art. 6(1)(b) GDPR, and Art. 6(1)(f) GDPR for securing sign-in.

5. Using tapedeck

When you use tapedeck we process data created by your work in the product. The legal basis is Art. 6(1)(b) GDPR.

Content

Uploaded audio and cover images, project and folder names, titles, artist, detected tempo and key, filename, size and type, version history, and comments, replies, reactions, and timestamps. Comments are visible to people who have access to that track.

Audio processing

Original uploads are stored encrypted in Cloudflare R2. A processing service we run on Railway creates a playback rendition and technical features such as tempo and key. Playback uses short-lived signed URLs; audio is not left openly on the internet.

Activity

To show how your music is received, we log plays inside shared folders, including who played, when, and for how long. Folder owners control whether that activity is visible to other members.

Synchronization

To keep devices current we keep a short-lived list of change events (for example “track added”, “access revoked”) and a per-device sync cursor. Your device stores a local copy of your library.

6. Sharing, invitations, and share links

You decide who gets access. When sharing we process roles (owner, editor, viewer), member permissions, and grant/revoke times.

Email invitations process the address you provide so we can deliver the invite. For share links we store a link identifier, optional expiry, use limits, a use counter, and — if you set link protection — the password in a protected form. Invite only people who expect to receive that material; you are responsible for choosing recipients.

Legal bases are Art. 6(1)(b) GDPR and our legitimate interest in securing shares under Art. 6(1)(f) GDPR.

7. Notifications and email

We send transactional email required for the service: sign-in codes, invitations, confirmations, and — if you enable them — activity summaries. Delivery uses Resend. Legal basis: Art. 6(1)(b) GDPR.

In the mobile app you can enable push notifications. We then process a device token, platform (iOS or Android), last-used time, and delivery status. Delivery uses Expo and Apple or Google system push. Legal basis: your consent under Art. 6(1)(a) GDPR, which you can withdraw in app settings or system settings.

In-app notifications (for example new comments) are stored with trigger, affected folder or track, and read state so they stay consistent across your devices.

8. Subscriptions and payments

tapedeck has a free tier. For paid plans we process your plan, its term and status, and usage of included allowances.

Purchase on the web

Web subscriptions are handled by Autumn together with Stripe. You enter payment details with the payment provider; we do not receive or store card data.

Purchase in the mobile app

iOS and Android purchases run through Apple In-App Purchase or Google Play Billing. Checkout, payment methods, and invoicing sit with Apple or Google as independent controllers; we do not receive payment data.

So a store-bought plan applies on every device and on the web, we use RevenueCat. We process your account identifier (the same as your tapedeck account), the product bought, status, start, renewal, expiry or refund, purchase platform, and the receipts and device/country signals Apple or Google send. RevenueCat reconciles that status with Autumn, which decides your allowances. We do not use this for advertising or cross-app tracking.

Manage and cancel App Store or Google Play subscriptions in that store’s settings. Deleting your tapedeck account does not cancel those subscriptions.

Legal bases are Art. 6(1)(b) GDPR and, for retaining invoices, Art. 6(1)(c) GDPR.

9. Contact form, feedback, and waitlist

Contact

If you use the contact form or write to us, we process your name, email, topic, and message to reply. The form includes a hidden field for spam detection that humans should leave empty. Legal basis: Art. 6(1)(b) GDPR for contract-related requests, otherwise Art. 6(1)(f) GDPR.

In-product feedback

Feedback from the app processes your message with your account identifier. You may optionally attach technical details about version, device, and recent technical events. Diagnostics do not include audio files or extra message content. Legal basis: Art. 6(1)(f) GDPR for handling feedback; Art. 6(1)(a) GDPR for optional diagnostics.

Waitlist

For the waitlist we store your email, signup origin, and confirmation times. Signup uses double opt-in: we send a time-limited confirmation link and only then add you. Legal basis: Art. 6(1)(a) GDPR. Unsubscribe via the link in each email or by writing to us.

10. Reach measurement and product analytics

Databuddy on public pages

Marketing pages measure reach with Databuddy. It uses no cookies and no cross-site identification. We collect aggregated items such as page, referrer, approximate origin, device type, and load times. The script and measurements stay on our domain; visitor IP addresses are not sent to Databuddy. Signed-in areas such as dashboard, projects, tracks, and account are excluded. Legal basis: Art. 6(1)(f) GDPR.

PostHog in the web app

In the web app we use PostHog on European infrastructure to find errors and understand a small set of core product flows. Session replay is off, we do not autocapture clicks or inputs, and events are cleaned before send — email addresses, access tokens, signed media URLs, and object identifiers are removed or replaced. We mainly capture error reports, upload and processing status, and that an account was active on a given day. Legal basis: Art. 6(1)(f) GDPR.

PostHog in the mobile app

The mobile app sends data to PostHog only after your explicit consent under Art. 6(1)(a) GDPR. That includes technical errors, upload and processing status, and that an account was active on a given day. Processing runs on European infrastructure. Session replay is off; events are cleaned and do not include audio or comment bodies, email addresses, access tokens, or signed media URLs. Withdraw consent anytime under Settings → Share analytics. Withdrawal applies going forward. Optional diagnostics in a feedback message stay separate and are sent only if you choose that when submitting.

11. Operations logs and security

For stable, secure operation we log technical events from our API and processing service: time, route, status, duration, request id, and error messages. Logs are kept at Axiom. They are used for debugging, security incidents, and proving system security; we do not analyze your music from them. Legal basis: Art. 6(1)(f) GDPR.

12. Mobile app

The iOS and Android app processes the same data as the web app. In addition:

• Camera, microphone, photos, and files permissions are requested only when you use a feature that needs them — for example taking a project cover, picking cover art, or recording an idea. You can revoke permissions in system settings.
• Optional Face ID or fingerprint unlock is checked only on your device. Biometric data are not sent to us or to third parties.
• Credentials and session tokens sit in the device’s secure storage; library data are cached locally so the app can work offline.
• The app is distributed through the App Store or Google Play. Apple and Google are independent controllers for their store processing.

13. Cookies and local storage

We do not use advertising or tracking cookies and do not embed services that recognize you across unrelated sites. We store only technically necessary information:

• Session cookies from our sign-in provider so you stay signed in and requests stay protected.
• Browser or device local storage for settings, the cached library, and changes not yet uploaded.

This storage is strictly necessary to provide the service you requested (§ 25(2) no. 2 TDDDG) and does not require consent. You can clear local data in browser settings or by signing out.

14. Recipients and processors

We work with a small set of processors under Art. 28 GDPR:

• Cloudflare, Inc. (USA / EU) – Hosting and delivery of the website and API, attack protection, and encrypted storage of uploaded audio and images (R2).
• PlanetScale, Inc. (EU) – PostgreSQL database that holds account and content metadata.
• Clerk, Inc. (USA) – Registration, sign-in, and session management, including email one-time codes, email/password, Google, and Sign in with Apple.
• Resend (Plus Five Five, Inc.) (USA / EU) – Transactional email such as invitations, confirmations, and summaries.
• PostHog, Inc. (EU) – Product analytics and error diagnosis in the app and web (EU instance).
• Databuddy (EU) – Cookie-free reach measurement on public marketing pages.
• Axiom, Inc. (USA / EU) – Retention of technical operations and security logs.
• Railway Corp. (USA / EU) – Audio processing service that converts uploaded files for playback.
• Autumn (Useautumn, Inc.) and Stripe, Inc. (USA / EU) – Subscription and payment processing on the web.
• RevenueCat, Inc. (USA) – Managing and reconciling subscriptions purchased in the mobile app through the App Store or Google Play.
• Expo (650 Industries, Inc.) (USA) – Push notification delivery to the mobile app via Apple and Google push services.

We disclose data further only with your consent, if required by law, or to enforce our rights. Content you share is available only to people you authorize.

15. Transfers outside the EEA

Some providers are based in the United States or process data outside the EU/EEA. Where that happens we rely on an adequacy decision — for example the EU-US Data Privacy Framework if the provider is certified — or Standard Contractual Clauses under Art. 46(2)(c) GDPR plus measures such as encryption and data minimization.

Database and product analytics run on European infrastructure. Even with those safeguards, access by authorities in third countries cannot be fully ruled out. We will provide copies of the relevant safeguards on request.

16. Retention and deletion

• Account and content: while your account exists. Deleting an object removes it including related audio; final storage removal follows a cleanup pass.
• Account deletion: you can delete your account in Settings. We then remove folders, tracks, uploads, comments, shares, notifications, account settings, and your profile at the sign-in provider. Cancel App Store or Google Play subscriptions there as well.
• Sync events: typically 72 hours, then automatic removal.
• Operations logs: typically no longer than 30 days, unless needed for a security incident.
• Waitlist: until you withdraw consent or the program ends.
• Requests and feedback: until handled and thereafter where legal retention applies.
• Billing records: six or ten years under German commercial and tax law.

17. Your rights

You have the right to:

• access the data we hold about you (Art. 15 GDPR)
• rectification of inaccurate data (Art. 16 GDPR)
• erasure (Art. 17 GDPR)
• restriction of processing (Art. 18 GDPR)
• data portability (Art. 20 GDPR)
• withdraw consent with effect for the future (Art. 7 GDPR)

Right to object under Art. 21 GDPR: you may object at any time, on grounds relating to your particular situation, to processing we base on Art. 6(1)(f) GDPR. We will then stop unless we demonstrate compelling legitimate grounds that override your interests, or the processing is for legal claims.

To exercise these rights, write to info@bejanic.de. You may also lodge a complaint with a supervisory authority (Art. 77 GDPR). Ours is:

18. Children, mandatory information, and changes

tapedeck is not directed at children. You must be at least 16 to create an account. If we learn an account exists contrary to that rule, we delete it.

Your email address is required to run an account; without it we cannot provide the service. Other details are optional. We do not use automated decision-making including profiling under Art. 22 GDPR.

We update this notice when the service or the law changes. The version on this page applies. Technical protections are described under Trust & Security, provider details in the Imprint, and product rules in the Terms of Service.