How ZapBridge handles your data

In short

• ZapBridge runs locally on your phone. We don't receive, store or see your texts.
• Your texts go only where you send them: a backup file, your paired browser, or an automation's destination.
• No account, no ads, no analytics, no selling of data.

What the app uses on your phone

SMS. To back up and restore texts, show new SMS on your laptop, and run your automations. Asked for only when you start a feature that needs it.

Contacts (optional). Only if you turn on "Show contact names", to add a name next to a number in what ZapBridge sends.

Notifications. To tell you when a backup finishes or something couldn't be sent.

Restore. Android lets only the default SMS app write texts, so during a restore ZapBridge asks to be the default SMS app for a moment, then helps you switch back.

On the phone, ZapBridge keeps a queue of texts waiting to send, an activity log and battery-use figures. They never leave the phone unless you export them.

Where your texts go

Only to places you choose, directly from your phone:

• Backups: this phone, your Google Drive, a Google Sheet, or an email you send from your Gmail.
• Your laptop: encrypted on your phone and delivered through your browser's own push service (for example Google's for Chrome, Apple's for Safari). That service can't read them.
• Automations: the Slack channel, webhook address, Google Drive folder or email address you enter. Those services handle the texts under their own privacy policies.

Google account data

If you connect them, ZapBridge asks for Gmail: send email only (it can't read your inbox) and Google Drive: only files ZapBridge creates. These are used only to deliver what you asked for.

ZapBridge's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

This website and the laptop app

The laptop app at zapbridge.roshi.in saves texts only in that browser's storage. It removes them when you unpair, when the phone unpairs, or after 30 days with no new text. The site uses no cookies and no analytics. Our hosting provider keeps standard request logs (such as IP address and time) for security.

Security, and where our responsibility ends

Texts sent to your laptop are encrypted on your phone, Google sign-in uses Google's own protections, and the app can be locked with your fingerprint, face or screen lock. Because we never receive your texts, there is no copy of them on our side that could leak.

Once you send a text to a place you chose (a Slack channel, a webhook, an email address, a Drive folder, a paired browser), it is protected by that place and the people with access to it, not by us. Keeping your phone, computer and accounts secure is up to you. Our terms of use explain what we can and can't be held responsible for.

Deleting your data

• In the app: Settings › Turn off everything and sign out deletes everything ZapBridge kept on the phone and tells paired browsers to remove their texts.
• In a browser: Devices › Remove deletes that phone's texts from the browser.
• Files you saved to Drive, email or elsewhere stay there until you delete them.
• To revoke Google access: myaccount.google.com › Security › Third-party access.

Children

ZapBridge is meant for adults (18+) and isn't directed at children.

Governing law and disputes

This policy is governed by the laws of India, and any dispute about it is handled by the courts of Delhi, India, as set out in our terms of use. This doesn't take away any right you have under the data protection law where you live, including to complain to your local data protection authority.

Changes and contact

If this policy changes, the new version appears here with a new date. Questions: contact@roshi.in.