Privacy Policy

Last updated: September 14, 2026

Textuoso never sends your messages, media, call log, or contacts to any server, not the developer's and not any third party's, unless you choose to use a third-party cloud service for your backups. They stay on your own devices, where the app processes them. The developer (StittHub, LLC) never receives or stores the contents of your messages, your attachments, your call history, or your contacts, so there is none of it to read, mine, or sell.

Which parts of this policy apply to you:

If you use only the Textuoso Android app: Part A and Part B.
If you use the Textuoso Web app or the Textuoso website (textuoso.com): Part A and Part C.

Part A. Both apps

How your data moves between your devices

Textuoso has two parts: the Textuoso Android app (installed on your phone) and the Textuoso Web app (which runs in a web browser on your own computer or device). When you move data between them, it travels directly from your phone to the browser on your own device over an encrypted, peer-to-peer connection across your local network. Both devices must be on the same local network (for example, the same Wi-Fi); Textuoso does not support connections between separate networks. Your data is not uploaded to a website, relayed through a server, or stored in the cloud. "Sent to your browser" refers to a browser running on a device you own, such as Textuoso open on your own computer, and nowhere else.

The signaling service used to connect your devices

To establish that direct connection, the two devices first have to find each other. Textuoso uses a signaling service (operated for Textuoso by Cloudflare) for this: when you scan the QR code, it relays the connection-establishment information the two devices need to find each other and set up their direct, encrypted link, and then takes no further part. It never receives your messages, media, files, call log, or contacts.

The signaling service keeps no database. It holds the two ends of a pairing in memory only for as long as they are connecting, and keeps nothing once they have. It is protected by rate limiting applied by Cloudflare, which counts recent requests from the same IP address, the way any website's protection against automated traffic does. The developer does not receive, store, or use your IP address from it.

Optional backups to third-party services

Textuoso produces backup files, and you may choose to keep those files in a third-party storage or cloud service (for example, Google Drive, OneDrive, or Dropbox). If you do, the backup is stored by that service under your own account and is handled according to that service's own privacy policy and terms. It is no longer solely on your device, and that service may be able to access its contents. Whether to use such a service, and which one, is entirely your choice.

Security

The connection between the Textuoso Android app and the Textuoso Web app is established directly between your devices, through QR-code pairing, and is encrypted. Textuoso's device-to-device transfer does not send your backups through the developer's servers. The account service described in Part C uses encrypted connections, stores no passwords, keeps sign-in codes only as hashes, and stores phone identifiers only as keyed one-way hashes.

Children

Textuoso is a general-purpose tool for managing data on your own devices and is not directed at children. Textuoso accounts (Part C) are only for people 18 and older.

Changes to this policy

This policy may be updated from time to time, and the "last updated" date above reflects the most recent version. If the policy changes materially, you will be asked to review it again in the app or the Web app before continuing.

Who is responsible, and how to contact us

Textuoso is provided by StittHub, LLC. Our Privacy Officer is responsible for this policy and for privacy questions and requests, and can be reached at our contact email.

Part B. The Textuoso Android app

What the app accesses on your phone

To do its job, the app accesses the following on your phone, only to provide the features you ask for, and only locally:

SMS, MMS, and RCS messages: their text, attachments (photos, video, audio), timestamps, and addresses, including Samsung Messages RCS chats and their attachments where present.
Call log: phone numbers, dates, durations, and call types.
Contacts: the full contact record (names, phone numbers, email and postal addresses, organizations, nicknames, notes, websites, events, relations, photos, and any app-specific fields your other apps store on a contact), used to label conversations and calls, and (when you choose to) to back up and restore your contacts to your device.
Your device's phone number: used so group conversations are grouped and restored correctly.
Your device's country: read from your SIM or mobile network (the two-letter country code only, never your location), used to display phone numbers in the right national format.
A device identifier (Android ID): used to tag a backup with the phone it came from, so that a delete or modification is never applied to the wrong phone. It stays on the phone unless you register the phone to a Web app account (Part C).

This information is used solely to display, search, clean up, back up, transfer, and restore your messages, call log, and contacts at your direction.

What the app does not do

It has no account and does not send your personal information to the developer.
It does not send your messages, media, files, call log, or contacts to the developer or to any server, unless you choose a third-party cloud service for your backups.
It contains no advertising and no analytics, crash reporting, or tracking.
It does not sell or share your personal information.

Permissions and why they are needed

Read SMS / Receive SMS, MMS and WAP push / Read cell broadcasts: to read and back up your messages, and so Android lets the app act as the default SMS app during a restore, which is the only way to write messages back to the device.
Read / Write Call Log: to back up and restore your call history.
Read / Write Contacts: to show names instead of bare phone numbers, and to back up and restore contacts.
Phone state: to read your device's own phone number for correct grouping.
Camera: to scan the pairing QR code shown by the Web app.
Internet, network and Wi-Fi state, local network: to establish the encrypted, direct connection to the browser on your own device.
Foreground service, wake lock, notifications: to keep a long backup or restore running reliably and to show its progress.
Exact alarms, run at startup: to start scheduled backups on time, and to re-arm them after the phone restarts.

The content accessed through these permissions is processed on your own devices and is not transmitted to the developer.

Where backups are kept, and how to delete them

Backups you make on the phone, whether you start them yourself or schedule them, are written to the location you choose, on the device or in a third-party cloud service you have connected. They stay there until you delete them.
A backup pushed from the Web app is kept as one staged file so you can restore it. It stays on the device until a newer push replaces it, or you remove it.
To delete: delete individual backups from within the app; delete backups kept in Google Drive, OneDrive, or Dropbox from within the app or in that service; or clear the app's storage in Android settings, or uninstall it, to remove all Textuoso data on the device, including the staged file.

Part C. The Textuoso Web app and the Textuoso website

Your account: what is stored, why, and for how long

Using the Textuoso Web app requires an account. Unlike your messages, an account does involve information the developer stores:

Your email address: so the account exists and you can sign in. There is no password: you enter your email, are sent a short-lived sign-in code, and that code signs you in. Kept until you delete your account.
Sign-in codes: stored only as a hash. Expire after 10 minutes.
Sessions: a random identifier that keeps you signed in. Up to 60 days, or until you sign out or delete your account.
Registered phones: a one-way keyed hash of the phone's Android ID (never the ID itself), with its brand and model, any label you give it, and when it was registered and last seen. This ties a phone to your account and counts it against your allowance. Until you remove the phone or delete your account.
Free trials: the same keyed hash of a phone's Android ID with the date its trial began, so one phone cannot start the trial repeatedly. The hash cannot be turned back into the identifier. Kept after account deletion, with no email address attached, so a trial cannot be restarted by making a new account.
Which documents you accepted: the versions of the Terms of Service (including your confirmation that you are at least 18), this Privacy Policy, and the early-access notice that you accepted, and when. For as long as the account exists.
Your country: a two-letter country code, so numbers are formatted correctly. Until you change it or delete your account.
Purchases and receipts: if you buy anything, what was bought, the quantity, the amount, any tax, the currency, any refund, the seller, and the payment processor's references. Kept after account deletion for accounting, tax, fraud prevention, and transaction-record purposes, for as long as reasonably necessary or required by law.
Service logs: short-lived operational records, such as a sign-in code being sent or a purchase completing, used to diagnose problems. They identify an account only by a shortened one-way hash of its email address, never the address itself. Kept by Cloudflare for no more than 7 days.

None of this is advertising, analytics, or tracking, and none of it is sold. Your messages, media, call log, and contacts are not part of any of it.

Why this information is used

To provide the account and service you asked for: your email address, sign-in codes, sessions, registered phones, trials, accepted documents, and country.
For accounting, tax, and fraud prevention: purchase and receipt records.
To keep the service working and safe: rate limiting, bot checks, and service logs.
With your consent: the advertising tag, outside the United States (see Advertising measurement below).

Companies that handle this information, and where

Cloudflare, Inc. (United States): hosts the Textuoso website, the Web app's account service, and the signaling service; stores account data; applies rate limiting; runs the Turnstile bot check at sign-in, which receives your IP address to tell a person from an automated attempt.
Resend (United States): delivers sign-in emails, and receives your email address to do so.
Stripe (United States): processes payments and is the seller for purchases (see Payment below).
Google LLC (United States): the advertising tag on the Textuoso website (see Advertising measurement below).

These companies handle information as described above and under their own contractual and legal obligations. The developer's account data is stored in the United States, and the companies above may also process information in other locations, as described in their privacy documentation. While information is in the United States, it may be accessible to courts, law enforcement, and national security authorities there under US law.

Protecting sign-in from abuse

The account service limits how many sign-in codes can be requested for one email address. That count is kept against a hash of the address, expires within the hour it covers, and involves no IP address. Requests are also rate limited by Cloudflare by IP address, as described for the signaling service in Part A. The developer does not store your IP address.

Payment

Payment is handled by Stripe, which is also the seller. Stripe acts as merchant of record: you buy from Stripe (shown as "Sold through Link"), and Stripe calculates, collects, and remits any sales tax, VAT, or GST and issues your receipt. Checkout happens in Stripe's own form, where you enter your card details, name, and billing address. The developer never sees or stores your card details. Your name and billing address are held by Stripe under its own privacy policy; the developer does not store them, and can look them up through Stripe when a purchase question requires it.

Advertising measurement

This section is about the Textuoso website and Web app only. The Android app loads no advertising tag, contacts no advertising service, and reports nothing to one.

Textuoso advertises on Google. To measure which ads bring people to Textuoso, the Textuoso website, including the Web app, can load Google's advertising tag.

What it does. When you arrive from one of our ads, the link carries an identifier Google generated for that click. The tag stores it in your browser, and if you later create an account, tells Google Ads a sign-up happened so Google can credit the ad. Only Google can resolve the identifier.
What it does not do. It never receives your messages, media, call log, or contacts, and it is not sent your email address or any other account detail. Google's "enhanced conversions" feature, which would upload a hashed copy of your email, is switched off.
When it loads. For visitors in the United States it loads by default. Everywhere else it loads only if you choose Allow when asked.
Changing your choice. Use Ad settings at the bottom of any page on textuoso.com, or Help, then Ad settings in the Web app, at any time. Choosing No thanks stops the tag and deletes the identifier it stored in your browser.

Blocking the tag with an ad blocker has no effect on Textuoso: everything continues to work.

Deleting your account

Delete your account yourself in the Textuoso Web app, from the account menu. Deleting it erases your email address, releases every phone registered to it, and ends your sessions immediately. It cannot be undone, and any registrations you paid for are not transferred to a new account.

Your purchase and receipt records are kept for accounting, tax, fraud prevention, and transaction-record purposes, for as long as reasonably necessary or required by law, and an emptied account record is kept with them so those purchases still refer to something. That remaining record holds no email address and no name, and nothing in it can be used to contact or identify you. A phone's free trial record is also kept, as described above.

Your rights, and how to use them

You can ask to:

get a copy of the account information we hold about you;
correct it if it is wrong;
delete it (you can also delete your account yourself, as described above);
withdraw consent, such as for the advertising tag (use Ad settings); and
object to how we use it.

To make a request, write to our Privacy Officer at our contact email from the email address on your account, so we can confirm the account is yours. We will respond within the time required by applicable law, and ordinarily within 30 days.

If you are not satisfied with our response, you can complain to the privacy regulator where you live, including:

Canada: the Office of the Privacy Commissioner of Canada.
Australia: the Office of the Australian Information Commissioner.
Singapore: the Personal Data Protection Commission.

Users in India

If you are in India, you have the rights given by the Digital Personal Data Protection Act, 2023: to access a summary of your personal data and who it was shared with; to have it corrected, completed, updated, or erased; to withdraw consent; to nominate someone to exercise these rights if you die or become unable to; and to have grievances addressed. To exercise any of them, write to our Privacy Officer at our contact email from the email address on your account. We will respond within the time required by applicable law, and ordinarily within 30 days. You can also delete your account yourself from the account menu in the Web app. If we do not resolve your grievance, you can complain to the Data Protection Board of India.

Back to Textuoso