What Reins collects: nothing about your work.

Who we are

Reins is made by Enraio, an independent software studio in Goa, India. Enraio decides how the data described here is used. Our registered office address is available on request at hello@enraio.com.

What Reins collects

Nothing about your work. There is no account, and no analytics, crash reporting, advertising or tracking in the app or the daemon. Your sessions, commands, transcripts and files go between your phone and your own machine; they never pass through a server we run. A few features do involve a server, ours or someone else’s, and each is described below: push alerts, buying Reins Pro, voice input, and this website.

Where your work goes

The phone bootstraps over SSH and then holds an encrypted connection to the daemon on your machine. Transcripts, commands and working-directory paths are read from your own disk by a daemon running as you. Your phone keeps a capped local cache of recent sessions, commands and decisions so history survives a restart. Revoking a machine does not clear that cache; deleting the app does.

Photos. You can attach a picture from the camera, your photo library or the clipboard to a message. Like anything you type, it goes only to your machine.

Push alerts

Alerts work on Android today, and are on by default; iPhone follows when Apple’s push service is wired up. To deliver them, the app asks Google’s Firebase Cloud Messaging for this phone’s push address and seals it, through our relay at reins-push.enraio.com, into a ticket only the relay can open. Your machine keeps the ticket, valid for up to 180 days, and never sees the address. When an agent needs you and the phone isn’t connected, the machine asks the relay to wake the phone, and Google delivers a notification that says only “An agent needs you”.

The relay has no database and never sees what the agent asked. Like any web service it sees your IP address, which it uses to rate limit requests and which Cloudflare, its host, keeps briefly in its logs. Requests also carry a Firebase App Check token, which lets Google confirm they came from the genuine app. You can point the daemon at a Firebase project of your own instead of the relay. To turn alerts off, switch them off in Machine, then This phone, or deny the notification permission; the app then stops registering with Firebase and the relay.

Buying Reins Pro

Reins Pro is sold through Google Play, and through the App Store on iPhone, as a monthly or yearly subscription or a one-time lifetime purchase. The store takes the payment and handles receipts, cancellations and refunds. We never receive your card details, and the store doesn’t give us your name or email address; its sales reports show us at most your country or region.

To know whether you have Pro, the app uses RevenueCat, the subscription service we use. RevenueCat gives the app a random ID with no link to your name or email, and keeps it with the store’s receipt for your purchases (what you bought, when, the price and store country) and basic app and device details such as the app version and operating system. Like any web service it also sees your IP address. It sees nothing about your machines or sessions. A free user’s app also talks to RevenueCat, to learn that it isn’t Pro.

Because there is no account, Pro belongs to your Google or Apple account rather than to us. On a new phone, Restore purchases asks the store for your receipts and moves Pro across. A purchase on Android does not give you Pro on iPhone, or the other way round. For help with a purchase, send us the order ID from the store’s receipt email; that is the only way we can find it.

Voice input

The microphone button turns speech into text using your phone’s own speech recognition: Google’s on Android, Apple’s on iPhone. The app asks for microphone permission the first time you use it, and listens only while the button is active. Depending on your phone and its settings, recognition may happen on the phone or on Google’s or Apple’s servers, under their privacy policies. Reins itself never records, stores or uploads the audio; only the finished text goes to your machine, like anything you type. Voice input is on by default; switch it off in Machine, then This phone, or deny the microphone permission.

Other things worth knowing

• Camera. Besides photos, pairing can scan the QR code your machine shows. The code is read on the phone and the camera image is not stored or sent.
• mDNS. The daemon announces itself on your LAN as _reins._tcp, and the pairing screen browses for it with a multicast query while it is open. Run the daemon with --advertise=false to turn the announcement off.
• Webhooks. If you configure webhooks in the daemon, it sends agent events to the addresses you choose. Nothing is sent unless you set one up.
• Apple Watch. On iPhone, the app can pass alerts and your replies to your paired Apple Watch over Apple’s watch connection.
• Your network. If you reach your machine over Tailscale or a VPN, that provider is in your network path.
• App distribution. Apple and Google sign and distribute the app and see the install, as with any app.

This website and the early-builds list

This site is hosted on Vercel, which keeps standard request logs (IP address, page and time) for a short period. It loads no third-party scripts, fonts or analytics and sets no cookies. The early-builds form sends your email address to a small service we run on Cloudflare. We use it only to send you a build link, and delete it when you ask or once the list is no longer needed.

Who processes data for us

These providers handle data only to run the features above: Google (Play, Firebase Cloud Messaging, App Check and speech recognition, and Google Play), Apple (the App Store and speech recognition), RevenueCat (Pro status), Cloudflare (the push relay and the early-builds list) and Vercel (this website). They may process it in the United States and other countries, under their own data-protection terms. We don’t sell or share personal information, or use it for advertising or tracking.

How long data is kept

• Push relay: nothing stored; Cloudflare’s logs are short-lived. Tickets on your machine expire after 180 days.
• RevenueCat: while your purchase is active, and afterwards for as long as tax and accounting rules require.
• Early-builds list: until you ask us to remove your address, or the list is retired.
• Everything else about your work stays on your phone and your machine, under your control.

Why we may use it

Where privacy law asks for a reason: Pro status is needed to provide what you bought; push delivery and abuse protection serve our legitimate interest in a working, secure service you have chosen to use; and the early-builds list relies on your consent, which you can withdraw at any time.

Your rights

Depending on where you live, you can ask to see, correct or delete the data we hold about you, to object to its use, or to withdraw consent. Email hello@enraio.com and we will reply within 30 days. If you are not satisfied, you can complain to your data-protection authority.

Deleting your data

There is no account to delete. To remove everything on your phone, delete the app; to remove what is on your machine, uninstall the daemon. To have your RevenueCat purchase record erased, email hello@enraio.com with the order ID from your store receipt; to leave the early-builds list, email us from that address. We confirm when it is done. The stores keep their own records of your purchases under their policies.

Children

Reins is a developer tool and isn’t directed at children under 16.

Changes

If this policy changes in a way that matters, we will update the date at the top and say so in the app’s release notes.

Questions

Email hello@enraio.com. For the technical detail behind this page, see Security, how it works and Free and Pro.