Data Captry handles
Captry handles content you choose to save, including text, links, images, voice notes, reminders, collections, and notes. The app may create OCR text, transcripts, titles, summaries, categories, extracted details, and search data from that content.
Storage and processing
Your content, settings, and search data are stored in Captry's private storage on your device. The database and capture files are encrypted at rest. OCR, transcription, search, and AI-assisted features run on your device.
Captry does not upload your captures to Captry Labs, apart from what passes between your phone and computer when you turn on Captry on your computer, as described below, which is encrypted so Captry Labs cannot read it. The app has no account system, advertising, or developer-operated analytics.
If you send a bug report or feature request from Settings > Support, Captry sends the message you wrote and, if you leave the option on, the app version, Android version, and device model to Captry Labs. A bug report can also include the app’s own recent log lines if you turn that on; the log is shown in full first. The report shows you exactly what will be sent before you send it. Reports go to a Captry Labs endpoint hosted on Cloudflare and are forwarded to Captry Labs' issue tracker or support mailbox. They do not include your captures, notes, searches, or generated results, and they are not linked to an account. Sending is off until you turn it on, and Settings > Network lists every feature that can use the network and lets you turn each one off.
If you turn on Captry on your computer, what passes between your phone and captry.app/desktop goes through a Captry Labs endpoint hosted on Cloudflare: captures and edits you make on the desktop page, and the changes you make to your captures on the phone, such as a new capture, an edit or a deletion, so the page stays current. Each is sealed on the device that makes it with a key only your phone holds, so the endpoint stores data it cannot read. It is held under an identifier derived from that key. Captures and edits for the phone are deleted when the phone collects them; the phone's changes are kept for 14 days for any of your computers to read; nothing is kept longer than 14 days. The endpoint sees ordinary connection data, such as your IP address, and the time and rough size of each message (each is padded before it is sealed, so its exact size does not show), and nothing that identifies you or links the identifier to you. Private captures are never sent. Edits from the desktop never delete anything outright and never touch private captures, and the phone lists each one with Undo. If you pair a computer from Settings > Network, the phone scans a code on the computer’s screen. Once you tap Pair it sends that computer a key made for paired computers, separate from the one that protects the phone's own storage, sealed so only it can open it, and your captures apart from private ones, with small copies of pictures, sealed the same way. They pass through the same endpoint and are deleted once the computer has them, and within an hour regardless. A full-size picture is sent the same way when you open it on the computer. Reset key in Settings > Network replaces that key, so every paired computer loses access until it pairs again. While Captry is open on your phone, it keeps one connection to the endpoint so it hears at once that something is waiting; the endpoint only ever says that, never what, and the connection closes when you leave the app. Captry on your computer is off until you turn it on.
You can check that captry.app/desktop is a published release. Its source and the
SHA-256 of every release are public at
github.com/captrylabs/captry-desktop,
one commit per release, and the page pins every script it runs by its SHA-384, so
your browser refuses a script that was changed. To check the page itself, compare
the output of curl -s https://captry.app/desktop/ | shasum -a 256 with
the newest entry in that repository's desktop/releases.json, or run its
verify.mjs.
If you turn on Read saved webpage links, Captry visits each link you save, once, and keeps the page’s title, description, author, date, readable text and preview picture on your phone so the link is searchable and named. The request goes directly to the site the link points at and carries the same ordinary connection data a browser sends: your IP address, a user agent that names Captry, and your language. It carries no cookies, no sign-in and nothing else you have saved. The site can see that the address was visited. A saved link’s screen also offers to read that one page while the switch is off; that is a button you press for one address. Read saved webpage links is off until you turn it on, and you can choose to read pages only on Wi-Fi.
Third-party services
Captry uses Google ML Kit for on-device features. Google states that feature inputs and outputs are not sent to its servers, but ML Kit may collect limited technical data for diagnostics and usage measurement. Google Play and Play services also handle app installation, updates, and some system model downloads.
If you enable Smart search, Captry downloads EmbeddingGemma. If you enable Advanced understanding when Nano Prompt is unavailable, Captry downloads Gemma 4 E2B. If you enable Translation downloads, Captry downloads a language pack through Google Play services. Those requests may share ordinary connection data, such as your IP address and user-agent, with the download host. They do not include your captures, notes, searches, or generated results.
Permissions and sharing
Captry uses internet access for optional model downloads, for bug reports and feature requests you choose to send, for collecting captures you send from your computer when you turn that on, and for reading the pages behind links you save when you turn that on. It requests microphone access for voice features and notification access for reminders. It does not request broad photo-library access. It asks for the camera the first time you use the Camera button, Grab text or the scanner that pairs a computer; photos are still taken by your phone’s camera app, and Grab text and the scanner read from the live view without storing a picture.
“Where was this” (Settings > Privacy, off by default) keeps the place a photo already carries in its own data and, with the coarse location permission you grant there, compares it with the phone’s position when For You opens. The position is used for that comparison and not stored. Places Captry keeps go into your exports and backups, as they already do inside the photos. Turning the setting off stops both and removes every place Captry kept; the photos themselves are not changed.
Captry sends content to another app, website, export, or backup only when you choose that action. Readable exports are not encrypted. Encrypted backups are protected by your recovery code. Data sent elsewhere is governed by the destination you selected.
Retention and deletion
Your data remains on your device until you delete it, use Delete everything, clear the app's storage, enable an applicable automatic deletion option, or uninstall the app. Archived captures remain until deleted. Copies you exported, shared, or backed up must be deleted separately.
Security
Captry uses Android private storage, encryption, and the Android Keystore. You may also enable a PIN and biometric app lock. Captry does not store your PIN, fingerprint, or face data.
Children, changes, and contact
Captry is not directed to people under 18. This policy may change when the app's data practices change; the effective date will be updated.