LinkRelay ("the App", package name com.codingfeline.linkrelay) is an Android app that receives links you share to it and forwards them to an app you choose, according to rules you define. This policy describes what data the App handles, where it is sent, and the rights you have over that data.
In short: the App processes shared links on your device. It has no account, no advertising, and no analytics, and the developer runs no server of its own. Data leaves your device in three cases only: (a) crash and error reports sent to Firebase Crashlytics (§3.1), (b) requests to known link-shortening services to find where a short link leads, which you can turn off (§3.2), and (c) Android's own backup and device-to-device transfer, which the operating system performs and the developer never sees (§3.3).
The data controller is:
We respond to data subject requests within 30 days as required by GDPR Art. 12(3).
The following data is stored only in the App's private storage on your device. The developer has no copy of it.
The App reads the text you share to it, extracts the links, and removes tracking parameters using a list bundled with the App. It then opens the link in the app chosen by your rule or in the selection screen. The link is passed to that app because you asked the App to open it there. Apart from §3.2, the link is not sent anywhere else by the App.
To show you which apps can open a link, the App asks Android for the apps that can handle https links. This list is used on the device only and is never sent anywhere.
You can export your rules and settings to a JSON file and import them again. You choose where the file is saved and which file is read. Forwarding history is not included in the export. The App does not send the file anywhere.
The App uses Firebase Crashlytics to find and fix bugs. When the App crashes, or when it catches an unexpected error, a report is sent to Google. A report contains:
Firebase Crashlytics also includes the Firebase sessions library, which sends app and device metadata, the network connection type, and the time the App came to the foreground, so that crash-free rates can be calculated.
The App never writes the links you share into its logs. However, an error message that the App did not anticipate may contain part of a link, such as a host name, and such a message would be included in a crash report.
Google processes this data on the developer's behalf as a service provider. Crashlytics keeps crash stack traces and the associated identifiers for 90 days, then starts removing them (Firebase privacy and security). The App has no in-app setting to turn crash reporting off.
When a link you share belongs to a known link-shortening service (for example bit.ly or youtu.be), the App sends a request directly to that service to learn where the link leads, so that your rules can match the real destination. The request goes to the service that issued the link, not to the developer.
The App allows Android's automatic backup. If backup is turned on in your device settings, Android copies the App's data (including rules, settings, and forwarding history) to your Google account's backup, and to your new device when you transfer to one. The operating system performs this. The developer cannot access these copies. You can turn off backup in your device's settings, and manage or delete backups from your Google account.
| Permission | Purpose |
|---|---|
INTERNET | Expanding short links (§3.2) and sending crash and error reports (§3.1). |
POST_NOTIFICATIONS | Suggesting that you register a rule for a domain you forwarded (Android 13 and later). You can refuse it. |
ACCESS_NETWORK_STATE | Added by the Firebase libraries to check for a network connection before sending reports. |
For users in the EEA, the United Kingdom, and Switzerland, we rely on the following legal bases under GDPR Art. 6:
We do not engage in automated decision-making or profiling under Art. 22.
Crash and error reports are processed by Google LLC, which may process them in the United States or other countries. Requests to link-shortening services (§3.2) go to wherever those services operate.
You can ask Firebase to delete the crash report data sent from your installation of the App:
The App needs an internet connection for this. It shows whether the request succeeded, and if it failed, you can try again.
You have the right to request access to, rectification of, or erasure of your personal data, to request restriction of processing, to object to processing based on legitimate interest, and to data portability.
Most of the App's data is on your device and is under your control directly. For crash reports, note that the developer cannot tell which report belongs to whom: reports carry installation identifiers only, and the App has no account. You can delete the crash report data sent from your installation yourself, from the App (§7.1). For other requests, contact yshrsmz.ys+pp@gmail.com.
You also have the right to lodge a complaint with your local Data Protection Authority (Art. 77 GDPR).
The App is not directed to children under 13 (or the equivalent minimum age in your jurisdiction). The developer does not knowingly collect personal information from children.
The App's handling of user data follows the Google Play User Data policy. We do not sell user data, do not use it for advertising, and use it only for the purposes described in this document.
Crash and error reports and short-link expansion requests are sent over HTTPS. The App does not allow unencrypted HTTP connections, so a short link written with http:// is not requested and is forwarded as it is. Data on your device is kept in the App's private storage, which other apps cannot read.
If this policy changes in a way that affects what data is handled or where it is sent, we will publish the updated version at this URL with a new "last updated" date and a note in the changelog below.
This policy is published in English. A Japanese translation is available on request via the privacy contact above; in case of conflict, the English version controls.
last updated: September 25, 2026