Privacy Policy
Last updated · 29 October 2026
In one sentence: Relay is an SMS app: on your phone it receives, shows and sends your text messages, and it forwards them only to destinations you set up yourself. We run no server that receives your messages, we show no ads, and we use no tracking or analytics. The only third parties in the app are Google Play billing for the optional Pro purchase, and Firebase Crashlytics, which receives a technical report if the app crashes and never any message content.
01 Who we are
Relay ("the App") is developed and operated by Livotov Labs Ltd. ("we", "us", "our"), P.O. Box 99, Varna 9002, Bulgaria, Company ID 202346120. For any privacy question, contact labs@livotov.eu. This Policy explains how the App and this website handle information.
02 Our core principle: on-device processing
Relay is designed so your message content never leaves your device except as texts you send and to the destinations you explicitly set up: another phone number you choose, your own email account or Postmark server, your own Telegram bot and chat, a web address you control, or an automation app on the same phone. There is no Relay cloud, no Relay account, and no intermediary server that receives, stores or reads your messages. This is true for every destination kind, email included.
03 Information the App accesses on your device
Relay is a messaging app with forwarding built in. To do that, the App accesses the following locally, on your device:
- Your text messages (SMS and MMS), only while Relay is your default SMS app, a role you grant in Android and can move to another app at any time. As the default SMS app, Relay receives incoming texts and picture messages, stores them in your phone's own message store, shows your conversations, and checks incoming texts against your forwarding settings (RECEIVE_SMS, READ_SMS, RECEIVE_MMS, RECEIVE_WAP_PUSH). The messages stay in your phone's message store, where they always were; we never receive a copy.
- Sending texts: Relay sends the texts you write, including replies from a notification, and, if you set up another phone number as a destination, forwards texts to it as ordinary SMS (SEND_SMS). Carrier charges may apply. The App never makes calls and does not request any call-log or phone-call permission.
- Contacts: read on the device to show names instead of numbers and to let you pick a recipient (READ_CONTACTS). Contacts are never copied off the device or sent anywhere. This is optional; without it the App shows numbers.
- If another app is your SMS app, Relay stops reading, receiving and sending SMS, and can instead read incoming texts from that app's notifications to keep forwarding, which requires notification access and no SMS permission.
- Notifications: to show incoming texts, with reply and mark-as-read actions, and to tell you when a text or a forward has failed (POST_NOTIFICATIONS).
- Network access: to deliver to Telegram, email and webhook destinations you configure, and to download picture messages from your carrier (INTERNET).
- Background work: to finish a delivery after a message arrives and to retry a failed one, the App schedules short background jobs and may ask you to exempt it from battery optimisation (REQUEST_IGNORE_BATTERY_OPTIMIZATIONS, RECEIVE_BOOT_COMPLETED).
We request only the permissions the feature you use needs, and the App works, with the feature disabled, if you decline.
04 Information stored on your device
Stored locally only:
- Your text messages, in the phone's own message store, as with any SMS app. Deleting a conversation in Relay removes it from that store.
- Unsent drafts, your rules, destinations and app settings.
- A capped activity log of forwarded, skipped and failed messages (sender and a short preview), so you can see what happened and retry failures. For a failed delivery the full text is kept for up to seven days so it can be resent, then deleted.
- Secrets, meaning a Telegram bot token, a webhook header value, a mail password or a Postmark server token, are held in your device's hardware-backed encrypted storage and are never written to logs or exports.
Clear the log at any time (Activity → Clear, or Settings → Your data). Uninstalling removes all locally stored data.
05 Information sent to third parties: only the destinations you choose
When a message is forwarded, automatically or because you chose to forward it, its content is transmitted from your phone directly to the destination(s) you configured. Those services have their own terms and privacy policies:
- Another phone: sent as an ordinary SMS through your mobile carrier to the number you chose.
- Telegram: delivered through the Telegram Bot API to the chat or channel you specify, using your own bot.
- Email: delivered either through the mail server and account you provide (SMTP) or through your own Postmark account using your server token. Either way the connection is made from your phone.
- Webhook: posted as JSON to the web address you provide.
- Automation app: handed to an app on the same phone (such as Tasker) by an Android broadcast. If you do not name a target app, any app on the phone that listens for that broadcast can receive it; the App warns you about this.
We neither control nor take responsibility for how those services process messages you route to them, and we never add ourselves as a recipient or intermediary.
06 Purchases and crash reports
Relay offers an optional "Pro" upgrade, as a one-time purchase or a monthly or annual subscription with a free trial. Payments are processed by Google Play; we never see or store your card details. The App asks Google Play on your phone which Pro purchase your Google account owns and keeps that answer on the device; no purchase data is sent to us or to anyone else, and there is no account with Relay. Manage or cancel subscriptions in Google Play; refunds follow Google Play policies.
If the App crashes, Firebase Crashlytics (Google) sends us a technical report so we can fix the fault: the stack trace, the app version, the Android version, the device model, free memory and storage, and a random installation identifier that Crashlytics generates. A report never contains a message, a phone number, a rule or a destination, because the App does not hand any of those to Crashlytics. Reports are kept by Crashlytics for 90 days. Crash reporting is switched off in development builds and there is no analytics or usage tracking (see Firebase's privacy documentation). Our legal basis is our legitimate interest in finding and fixing faults in the App (Art. 6(1)(f) GDPR). A report carries no name, number or account, and uninstalling the App or clearing its data resets the installation identifier.
07 What we do not do
- We do not operate a server that receives your messages.
- We do not sell, rent or share your data with anyone.
- We do not use advertising, ad networks or advertising identifiers.
- We do not embed analytics or tracking SDKs. The only components that talk to a network on our behalf are Google Play billing and the crash reporter described above, and neither ever receives a message.
- We do not require an account, an email address or a sign-up.
08 This website
This website uses no cookies, no trackers, no analytics and no third-party scripts. Nothing about your visit is collected or stored by us, so there is no cookie banner: there is nothing to consent to. The forms described below are the one exception, and only for what you choose to send. Fonts are loaded from Google Fonts solely to render the page, which means your browser requests them from Google's servers under Google's privacy policy. If the site is served through a hosting provider, that provider may keep ordinary server logs (such as IP addresses) for security and operation.
The support and early-access forms (only if you write to us)
The form at relaysim.app/support and the early-access form for Relay Business at business.relaysim.app ask for your name, your email address and your message. Each posts to our own function on its own domain, with no third-party form service, and that function relays it to our inbox and sends you a confirmation, both through Postmark (ActiveCampaign), our transactional email provider. We keep no database copy of your submission: nothing you wrote is stored on our infrastructure, and your IP address is written neither to the email nor to our logs. To keep the form from being abused to send spam, we count submissions against two limits, one per sender and one per day; the per-sender counter is keyed by a one-way, salted hash of your IP address, holds no other data, and is deleted automatically within an hour. Our legal basis for that counter is our legitimate interest in the security of our own infrastructure, and for handling your message our legitimate interest in answering people who contact us (Art. 6(1)(f) GDPR). What you send stays in our mailbox for as long as the correspondence and any legal retention duty require, and is used to acknowledge your message and to reply to you (for an early-access request, that includes telling you when early access opens), and for nothing else. The acknowledgement is automatic, plain text, carries no tracking pixel and quotes nothing you wrote. We never add you to a mailing list.
09 Transfers outside the EU
We are based in the EU, and most of what this Policy describes never leaves your phone. Three services we use are run by companies in the United States, so the personal data they handle for us may be processed there:
- crash reports, by Google (Firebase Crashlytics, section 06);
- emails from the support and early-access forms, by Postmark (ActiveCampaign, section 08);
- this website's hosting and its server logs, by Google.
These transfers rely on the EU–US Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission's standard contractual clauses in our data-processing terms with that provider. The forms' spam counters are kept in the EU.
10 Children
Relay is intended for adults and is not directed to children under 18. We do not knowingly collect information from children.
11 Your rights
Most of your data lives only on your device, and you control it there: view, edit or export the activity log, or delete everything by clearing it in the App or uninstalling. The personal data we hold ourselves is limited to the crash reports described in section 06 and any email you send us, through the forms or directly.
Under the GDPR you have the right to access that data, to have it corrected or erased, to restrict its processing, to object to processing based on our legitimate interests (which covers crash reports and handling your messages), and to data portability. To use any of these rights, write to labs@livotov.eu or use the support form; we answer within one month. Crash reports carry no name or number, so we can only find yours if you give us details that point to it, such as the time of the crash and your device model.
You also have the right to lodge a complaint with a data-protection authority, in particular in the EU country where you live or work. Our lead authority is Bulgaria's Commission for Personal Data Protection (cpdp.bg).
12 Security
We minimise risk by keeping data on your device, encrypting secrets in the Android Keystore and using encrypted connections (HTTPS, or TLS for mail) to every destination that supports them. No method is perfectly secure, but by design there is no central store of your messages to breach.
13 Changes
We may update this Policy for new features or legal requirements. Material changes update the "Last updated" date above and, where appropriate, are noted in the App.
14 Contact
Livotov Labs Ltd.
P.O. Box 99, Varna 9002, Bulgaria
Company ID 202346120
Email labs@livotov.eu