Privacy notice

This page is a translation of the German original. Deutsch

1. Controller

The controller for the processing of personal data on this website is Usama Ibrahim Zagout (NextAppLab), Paulsborner Straße 21A, 10709 Berlin, Germany, e-mail: kontakt@nextapplab.net.

2. What this is about

At your request, MediaLink prepares a media file from a public link so that you can download it to your device. There are no user accounts and no registration, no advertising, no analytics or tracking tools and no third-party fonts or scripts; fonts and scripts are hosted on our server. This notice states which data is processed in the process, for what purpose, on what legal basis, who receives it and how long it is kept.

3. Visiting the website, technical connection data

When you visit the website, your browser and your network operator transmit technical connection data, including your IP address, time, requested address, status code, data volume and browser identifier (user agent). The website is delivered via Cloudflare (see section 9); the data therefore flows first through Cloudflare to our server.

On our server, the following applies:

• The web server proxy writes an access log without IP address and without the query part of the address; parts of share links are made unrecognisable in it. It contains time, method, path, status code, data volume, duration and user agent.
• To protect against overload and abuse, the proxy limits the number of requests per visitor. For this it holds the IP address only transiently in working memory and does not write it to its log.
• The server's firewall (ufw, log level “low”) records rejected connections with the sender's IP address, time and port in the server's systemd journal. The journal is rotated by storage size; no fixed retention period is configured.
• The containers' logs are rotated by size (at most three files of 10 MB per container). There is no time-based deletion period for them; when a container is recreated (for example during updates), the old container's logs are removed.
• The application itself does not store any IP address.

Retrieving the finished file. To retrieve the finished file, your browser connects directly to a download server of our own (not via Cloudflare); our server sees your IP address as the connection source. As with the proxy above, it is held only transiently in working memory to limit requests and simultaneous downloads and is stored neither in the access log nor in the error log; in the access log, the file's access key is also made unrecognisable. The download server's certificate is issued by Let's Encrypt; only the server name is transmitted in the process, no visitor data. In addition, the statement on the firewall log above applies unchanged. The legal basis is Art. 6(1)(f) GDPR.

Purposes: technical provision of the website, stability and security, protection against overload and abuse. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation).

4. Jobs: link, metadata, files

When you check a link or prepare a file, we process the link you entered (it may contain identifiers or other personal data), the metadata read from it (for example title, duration, available formats, preview image), the job status and the prepared file. The job is accessible, by means of access keys, to the browser that started it. The file becomes accessible to others only if you expressly create a share link (section 8). For the actual retrieval of the file, your browser also receives a download permission limited to 120 seconds (section 13).

Purpose: providing the service you requested. Legal basis: Art. 6(1)(b) GDPR (use of the service at your request), alternatively Art. 6(1)(f) GDPR.

Storage and deletion. Job data is held in the working memory of a database (Redis). Its persistence is switched off: no snapshot or journal files of the database are created, and a restart of the database empties it. To be distinguished from this is swapping: the server has an active swap file, and the operating system kernel can move working memory contents, including those of the database, to it. Files and preview images are located in the server's file system. Retrievability, database entries and files end in different ways:

• Retrievability. 30 minutes after a job is created, the server refuses new requests for the file, the preview image and the job. A transfer that started before is not interrupted by this.
• Database entries. The entries for a job have a lifetime of at most 32 minutes after creation (30 minutes plus 2 minutes buffer); after that, the database removes them by itself. As a rule, the cleanup service deletes expired jobs even earlier, on its next run.
• Files. A cleanup service runs every minute and deletes the files and preview images of expired jobs in the file system, as a rule within the following one to two minutes. It removes the files of failed and cancelled jobs already on the next run; the associated database entries expire as described above.
• Failure of the cleanup service. If it fails, files remain blocked for new requests but are deleted only after it restarts. We therefore do not promise deletion at a specific point in time.
• Failed deletion. If the cleanup service cannot delete a directory (for example because of a file system error), it notes this in its log only with the number and type of error, without file names, paths, links or identifiers, and tries again on every further run (every minute), even if the job entry in the database has already been removed. After a restart of the cleanup service, it finds such remnants again as soon as a directory has been unchanged for more than two minutes. A deletion error does not make any file retrievable again. We cannot promise how long a persistent error will last.
• Remnants. Deletion takes place in the file system (files) and in the database (job data). The disk areas and the swap file are not overwritten; swapped-out remnants may remain there until they are overwritten.
• No media library, no recovery. We do not create any backups of this data of our own (no backup job, database without persistence). In the hoster's customer area, there were no snapshots for this server when we viewed it on 4 November 2026. We do not know whether the hoster creates internal copies of the infrastructure beyond that; its terms and conditions exclude backups of customer content without a special agreement.

5. Session cookie ml_sid

As soon as you check a link or prepare a file for the first time (not already when you merely open the pages), your browser stores the cookie ml_sid. It contains a random, signed identifier. It assigns your jobs to your browser and serves to limit the number of simultaneous jobs and requests per session. On the server, we store only a hash value of the identifier. The identifier is a pseudonymous identifier; it is linked to the session's jobs, which may contain the link you entered, and is therefore treated as personal data.

The cookie is valid for 24 hours, HttpOnly, Secure and SameSite=Lax. You can delete it in your browser at any time; after that, jobs already started no longer belong to your browser. A consent banner is not provided because the cookie is necessary for the service you expressly requested (Section 25(2) no. 2 TDDDG). There is no other storage in the browser (no local storage) as long as no advertising is displayed.

Legal basis for processing the identifier: Art. 6(1)(b) GDPR and (f) GDPR (assigning jobs, fair use and protection against overload).

6. Rate limiting and slots

Checks, preparations and simultaneous jobs are limited per session and overall (for example at most 10 checks per 10 minutes and session). The counters are tied to the hash value of the session identifier and are held in the database's working memory; they expire after the respective time window. Legal basis: Art. 6(1)(f) GDPR.

7. Retrieval from the target platforms

Your link is retrieved from the respective platform not by your device but by our server (via a proxy that allows only approved platform addresses). The platform thereby receives the internet address of our server and the request with the link you entered. The platform does not receive your IP address in this way. However, the link itself may contain identifiers or other personal data that you thereby pass on to the platform. Depending on the link, this is Dailymotion, TikTok, Pinterest, YouTube, Instagram, Facebook, X, Reddit, Vimeo or Twitch. We use no account and no cookies of the platforms.

The platforms are controllers in their own right; their privacy notices apply to them:

• TikTok (according to its notices for the EEA: TikTok Technology Limited, Ireland): https://www.tiktok.com/legal/page/eea/privacy-policy/en
• Pinterest (Pinterest Europe Ltd., Ireland): https://policy.pinterest.com/en/privacy-policy
• YouTube (Google Ireland Limited, Ireland): https://policies.google.com/privacy
• Dailymotion (Dailymotion SA, France): https://legal.dailymotion.com/r/privacy?lang=de
• Instagram and Facebook (Meta Platforms Ireland Limited, Ireland): https://www.facebook.com/privacy/policy
• X (for users in the EEA: X Internet Unlimited Company, Ireland): https://x.com/en/privacy
• Twitch (Twitch Interactive, Inc., USA): https://legal.twitch.com/legal/privacy-notice/
• Reddit: https://www.reddit.com/policies/privacy-policy · Vimeo: https://vimeo.com/privacy

Purpose: fulfilling your request. Legal basis: Art. 6(1)(b) GDPR, alternatively (f) GDPR.

Third countries. Whether data reaches a third country during a retrieval depends on the platform and on the group to which it passes the data on; the platforms decide that. We transmit to the platform the internet address of our server, the link you yourself entered, and the technically usual details of every request (such as the identifier of the retrieval program), and only because you request this retrieval.

8. Share link (QR code)

If you want to transfer a file to another device, we create a share link that is hard to guess. It is valid for at most 10 minutes and never longer than the file; you can revoke it beforehand. Whoever has the link can download the file as long as it is valid. After expiry or revocation, the server refuses new requests; a transfer that started before is not interrupted by this. The link key is made unrecognisable in our logs. Legal basis: Art. 6(1)(b) GDPR.

9. Cloudflare (delivery, encryption, tunnel)

We use Cloudflare for DNS, TLS encryption, forwarding and the tunnel to our server. In the process, Cloudflare processes technical connection data such as the IP address and routing data. Cloudflare, Inc. (101 Townsend Street, San Francisco, CA 94107, USA) acts for this processing, by its own account, as a processor and, for some purposes of its own, as a controller (privacy policy: https://www.cloudflare.com/privacypolicy/). Cloudflare does not state a fixed retention period for these logs; storage follows its statements.

Purpose: secure and high-performance delivery. Legal basis: Art. 6(1)(f) GDPR. Transfer to the USA: see section 11.

10. Hosting (netcup)

The server is located with netcup GmbH, Emmy-Noether-Straße 10, 76131 Karlsruhe, in the Nuremberg data centre (according to the customer area). netcup provides the infrastructure and in the process processes the server's data on our behalf. We access the server's contents after an SSH login for maintenance purposes. Legal basis: Art. 6(1)(f) GDPR.

11. Recipients and transfer to third countries

Data is not passed on to any other third parties unless we are legally obliged to do so.

12. Contact by e-mail

If you write to kontakt@nextapplab.net, Cloudflare Email Routing receives the message and forwards it to a private mailbox of the operator at Google (Gmail, Google Ireland Limited). In the process, your e-mail address, subject, content and attachments are processed. According to Cloudflare's documentation, the service checks sender authentication (SPF, DKIM, DMARC) and rejects messages in case of failures; forwarding takes place in real time.

Email Routing forwards only kontakt@nextapplab.net. Messages to all other addresses of the domain are discarded (catch-all rule "Drop"); Email Workers are not set up. In the Email Routing activity log, Cloudflare shows a message's status (for example forwarded, rejected, delivery failed) and the authentication results; the documentation does not state a retention period for this. Cloudflare keeps forwarding statistics for 31 days.

We store messages only for as long as is necessary to handle your request or retention obligations exist. Legal basis: Art. 6(1)(b) GDPR (request) or (f) GDPR.

13. Retention periods at a glance

14. Your rights

You have the following rights against us: access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). Where we process data on the basis of legitimate interests (Art. 6(1)(f)), you may object at any time on grounds relating to your particular situation. We currently do not rely on any consent; withdrawal is therefore not necessary.

How to reach us. Write to kontakt@nextapplab.net. Please note: a simple e-mail is not end-to-end encrypted, and it runs via Cloudflare Email Routing to a mailbox at Google (section 12). Therefore do not write to us more than necessary.

What you should not send us. Never send us the content of your cookie ml_sid, a share link or a job's access key. Whoever knows these values can access the jobs; we do not need them, and we never ask for them.

Access and erasure concerning jobs, and their limits. We keep no accounts and cannot reliably determine who started a job. The link entered and a point in time are therefore not enough for us to give you job data (link, metadata, files) or to delete it at your request: otherwise anyone who knows a link could obtain or have deleted the data of other people's jobs. We therefore do not release any job data on the basis of these details alone. We can confirm to you in general which data we process and for how long (this notice), and we examine requests case by case, including whether additional details for identification are needed (Art. 11(2) and Art. 12(6) GDPR). A procedure that reliably assigns a job to a person without that person revealing a cookie or an access key does not currently exist.

What you can do yourself. You can cancel running jobs in the application; a cancelled job is removed on the next cleanup run. You can revoke share links there yourself; this prevents new requests, and a transfer that has already started is not interrupted (section 8). Otherwise, jobs end by themselves: after 30 minutes new requests are refused, and the deletion of database entries and files takes place after that as described in section 4, without our promising a fixed point in time. You must request information on IP addresses and connection data at Cloudflare, netcup and Google from those providers; we have no access to their logs, unless they can be viewed in the operator's account.

15. Right to lodge a complaint

You can lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is: Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59–61, 10555 Berlin, telephone +49 30 13889-0, e-mail mailbox@datenschutz-berlin.de, https://www.datenschutz-berlin.de/ (complaint: https://www.datenschutz-berlin.de/buergerinnen-und-buerger/beschwerde/).

16. Obligation to provide data, automated decisions

You are not obliged to provide personal data; however, without the connection data mentioned and the link entered, the service cannot be used. There is no automated decision-making, including profiling.

17. Version and changes

As of: November 5, 2026. We adapt this notice when operations change, for example if advertising or analytics were introduced.