Privacy Policy · Deliver SMS.

Effective date: 25 October 2026

1.jbia ("we", "us") publishes the Android app Deliver SMS. (package name com.one.jbia.deliversms, the "app"; called 문자전달. in Korean). This policy explains what personal information the app handles and how.

It describes what the app actually does. The app has no server run by us, and the text of your messages is never sent to us.

A Korean version of this policy is published at privacy.html. Both describe the same practices.

1. The app has no server

This comes first because everything else follows from it. We do not run a server that stores your messages. Reading a message, checking it against your conditions and forwarding it all happen inside your own phone. A forwarded message travels only to the places you set up yourself — your mobile carrier (when forwarding by text) and the mail server of the account you entered (when forwarding by e-mail).

So we cannot see the content of your messages, do not hold it, and have no means of giving it to anyone else.

2. What is processed, and why

2-1. Kept on your phone only (never sent to us)

Item	Purpose	Kept
Sender and text of an incoming message	Checking it against the conditions you made, and composing the forward	The app stops using it once the forward finishes. The text travels as the forwarding job's input data, so it stays in the phone's own job store (Android's WorkManager database) until Android clears the finished job (the forward itself can take hours if quiet hours or a retry hold it back). Attachments are held in the app's private cache, and old ones are deleted when the next MMS is sent (anything over an hour old) and when the next chat picture arrives (anything over 24 hours old). Nothing is deleted on a timer, so on a phone with nothing more to send a file can outlive those windows
History	Letting you see what was forwarded and what failed	The sender, an 80-character preview of the text, where it was sent (the number or mail address), the condition's name, how it was sent, whether it succeeded or failed and why, and when it arrived and finished; the latest 200 entries
Your confirmed sender number	Showing whose phone a forward came from; noticing a SIM change	Until the app is uninstalled
SIM fingerprint	Telling whether the SIM has changed (the number is then confirmed again)	Until the app is uninstalled
Conditions	Which messages go where	Until the app is uninstalled
E-mail forwarding settings (SMTP server, account name, password)	Sending forwards through your own mail account	Until the app is uninstalled
Contact names	Putting the sender's name beside their number on a forward	Not stored. Looked up each time a message is forwarded

All of the above sits in the app's private storage on your phone. Other apps cannot read it, and neither can we.

About your mail password: the SMTP account details you enter are stored on your phone and used only to connect to the mail server you named. They are not sent to us. The password is stored encrypted with a device-bound key in the Android Keystore, which cannot be taken off the phone. Where your mail provider offers one, we recommend an app password rather than your account password.

About contacts: if you allow access to contacts, then when a message is forwarded the app looks up that one sender's number in your contacts to add a name. Chat (RCS) forwarding also looks up in the other direction (see "About notification access" below). Either way, it does not read your whole contact list, make a list of it, store it anywhere or send it anywhere. What is looked up is used to check your conditions and in the forwarded message, and then discarded. If you do not allow access, forwarding works just the same and shows the number only.

About notification access: this applies only if you switch on forwarding of chat (RCS) messages. Android gives chat messages to the default messaging app alone and offers no way for another app to read them, so the app reads the notification the messaging app shows to learn the sender and the text.

Only the notifications of two messaging apps are read (com.samsung.android.messaging and com.google.android.apps.messaging). Notifications from any other app are dropped straight away, without being read or stored.
The feature is off by default. It works only after you switch it on in the app's settings and also grant notification access yourself in Android's system settings. Without both, nothing is read.
If the notification carries a picture, that is read too. The permission to read it lasts only as long as the notification does, so the picture is copied into the app's private cache to be sent on (up to 12MB per picture). Cached pictures are deleted when the next chat picture arrives, which clears anything over 24 hours old. There is no timer, so if no further chat picture arrives a file can sit there longer than that.
Sometimes a notification gives the sender without a number. The app then looks in your contacts for a number to check your conditions against: first through the contact address carried in the notification (a content://com.android.contacts/… link to the person the messaging app has already matched), reading that one contact's numbers; and failing that, the one contact whose name matches exactly. If two contacts share the name, no number is used. When the notification carries the number itself, your contacts are not queried at all.
What is read is used only to check your conditions and to forward the message. It is not sent anywhere else, including to us. The history keeps no more than it does for a text message (the "History" row above). Where the notification gave the sender only as a name, that display name is what the history keeps instead of a number.
Turning off notification access, or the feature, stops it at once.

About backup files: backup and restore are started by you. A backup is a file you save to a place you choose; it holds your conditions and settings, including your mail password. The whole file is encrypted with a 4-digit PIN you choose, and it is not sent to us. Four digits can be worked out given time, so keep the file somewhere private. If you forget the PIN, the file cannot be restored.

2-2. What leaves your phone

Recipient	Data	Purpose	Basis
Your mobile carrier	The text of the message being forwarded, and the number you told the app to forward to	Forwarding by text	Your request
The mail server you set up	The text of the message being forwarded, and the address you told the app to forward to	Forwarding by e-mail	Your request
Google AdMob	Advertising ID, approximate location (country level), device and app information, app interaction, diagnostics	Showing and measuring ads	The ads SDK starts when the app is launched and cannot be switched off, with or without a pass; consent only where the law requires it (see section 3)
Google Play billing	Purchase record	Confirming your pass	Performing our contract with you
Our contact address	When you send us an enquiry or the app's log, what is in the e-mail draft	Answering you	Your choice

An enquiry or log is sent only when you tap the button that opens your mail app, and you can read and edit it before sending. The log includes the app and Android versions, the phone model and your plan; it leaves out message text and shortens recipient numbers and addresses. The app sends no error reports on its own.

Google processes the advertising and billing data above under its own policies, which may involve transfers outside your country. The only personal data we receive is an e-mail you choose to send us, which we handle from the Republic of Korea.

3. Advertising

The app uses one kind of ad: a rewarded ad. It plays only after you choose to watch it in a dialog that says what it gives you. There are no banner, interstitial or app-open ads, and no ad ever appears unannounced.

Ads are served by Google AdMob, which uses your Advertising ID. The Advertising ID is a resettable identifier that does not identify you directly.

Consent. Where the law requires consent for advertising — for example in the European Economic Area, the United Kingdom and Switzerland — the app shows Google's consent message before any ad is requested. There, and in US states whose privacy laws give you a right to opt out, the app's Settings screen includes Ad privacy options, where you can make or change your choice at any time. Declining does not stop the app from working.
You can reset or delete your Advertising ID in Android's settings (usually Settings → Privacy → Ads, or Settings → Google → Ads, depending on the phone).
How Google uses data from apps that use its services: https://policies.google.com/technologies/partner-sites
Google's advertising policies: https://policies.google.com/technologies/ads

4. Why the app asks for permissions

These are the permissions the app asks for and what each is used for. They are asked for when needed, not all at once. Sending text messages is not needed to finish setup and is not asked for there; it is asked for only on the screen where you create a condition that forwards by text. If you only forward to your own e-mail you never need it — though forwarding by e-mail works only during the free 7-day trial (no card needed) or with a pass, so without either one the text route is all that is left and the permission is needed for that.

Permission	Used for
Receive text messages (`RECEIVE_SMS`), receive multimedia messages (`RECEIVE_MMS`, `RECEIVE_WAP_PUSH`)	Checking an arriving message against your conditions
Read the received message (`READ_SMS`)	An MMS arrival broadcast carries no content; the body and attachments exist only after the platform has downloaded the message and written it to the store. To find the message whose arrival was announced, the app queries the MMS inbox newest-first, stops the moment it reaches a row older than the announcement (with a 2-minute allowance for device clock skew), and scans at most 20 rows. The SMS inbox is never queried, and past conversations are never browsed, indexed or copied. When a forward is delayed by quiet hours or a retry, the same message is read from the store again at sending time
Send text messages (`SEND_SMS`)	Forwarding by text. Asked for only when you create a condition that forwards by text
Phone number (`READ_PHONE_NUMBERS`)	Confirming this phone's sender number and noticing a SIM change
Read contacts (`READ_CONTACTS`)	Adding the sender's name to a forward by looking up only the one number being forwarded. With chat (RCS) forwarding switched on, a notification may give the sender without a number, so the lookup also runs in reverse — through the contact address carried in the notification (`content://com.android.contacts/…`), reading that one contact's numbers, or failing that the one contact whose name matches exactly — to get a number to check your conditions against (not used if two contacts share the name). The app works normally without it
Internet and network state	Forwarding by e-mail, purchases and ads
Show notifications (`POST_NOTIFICATIONS`)	Telling you a forward succeeded or failed
Notification access (`BIND_NOTIFICATION_LISTENER_SERVICE`)	Forwarding chat (RCS) messages only. Off by default; works only after you switch it on and grant it yourself in system settings. See "About notification access" in 2-1
Battery restriction exemption	Keeping forwarding going while the phone saves power

The app does not ask to become your default SMS app.

5. How long data is kept, and deletion

Everything stored on your phone is deleted when you uninstall the app. The history keeps only the latest 200 entries and removes older ones automatically. You can also delete conditions and the history yourself inside the app.

We keep no other information about you. E-mails you send us are kept for three years so we can follow up on them, and then deleted.

6. Your rights

You can ask to see, correct or delete your personal information, or to have its processing restricted or stopped. Because the app's information is all on your phone, the quickest way is to view and delete it inside the app. For anything else, write to the address in section 8 and we will act on it without undue delay.

If you are in the EEA, the UK or Switzerland, you have the rights of access, rectification, erasure, restriction, data portability and objection under the GDPR, the UK GDPR or Swiss data protection law. Where ads rely on your consent, you can withdraw it at any time under Settings → Ad privacy options; this does not affect what happened before you withdrew it. You also have the right to complain to the data protection supervisory authority where you live or work.

If you are in the United States: we do not sell your personal information, and we do not receive any to sell. Google may process your Advertising ID and device information to show and measure ads, subject to the privacy choices you make. Where your state's privacy law gives you the right to opt out of targeted advertising or the "sale" or "sharing" of personal information, you can make that choice at any time under Settings → Ad privacy options. We will not treat you differently for exercising any of these rights.

Children: the app is not directed at children. It is not intended for children under 13, or under 16 in the EEA and the UK (14 in the Republic of Korea), and we do not knowingly process their personal information. If you believe a child has sent us personal information, contact us and we will delete it.

7. How the information is protected

Your information is kept in the app's private storage, which other apps cannot access.
Your mail password is stored encrypted with a device-bound key in the Android Keystore.
Backup files are encrypted (AES-GCM) with the 4-digit PIN you choose.
Forwarding by e-mail uses an encrypted TLS/SSL connection by default (SSL on port 465, STARTTLS on other ports). You can turn encryption off in settings, but then the message and your account details travel unencrypted, so we do not recommend it.
A forward sent by text (SMS or MMS) is carried by your mobile carrier's network and is not encrypted by the app. Its protection on that leg is whatever the carrier's network provides.
Because we have no server holding your information, there is no server it could leak from.

8. Who is responsible, and how to contact us

Item	Details
Business name	1.jbia
Representative and person responsible for privacy	INAE YOUN
Business registration number (Republic of Korea)	168-38-01725
E-mail	1.jbia.studio@gmail.com

1.jbia is the controller of the personal information described in this policy that we process ourselves. Google is responsible for its own processing as described in its policies.

If you are in the Republic of Korea and need to report or discuss a privacy infringement, you can also contact:

Personal Information Infringement Report Center (privacy.kisa.or.kr / 118)
Personal Information Dispute Mediation Committee (www.kopico.go.kr / 1833-6972)
Supreme Prosecutors' Office, Cyber Investigation Division (www.spo.go.kr / 1301)
Korean National Police Agency, Cyber Bureau (ecrm.police.go.kr / 182)

Elsewhere, you can contact your local data protection authority.

9. Changes to this policy

If this policy changes, the changes and their effective date will be posted on this page. If a change is to your disadvantage, we will announce it 30 days before it takes effect.

Effective date: 17 September 2026 (first English version)
25 October 2026: what READ_SMS queries in the MMS store (section 4), how and when a message body and its attachments are actually cleared (2-1), what a history entry keeps (2-1), the caching of a picture from a notification and both contact lookups (2-1 and 4), what reaches AdMob and on what basis (2-2), what the send permission is for and what e-mail forwarding needs (4), and whether the text leg is encrypted (7) — all brought in line with what the app does