Privacy Policy
Our privacy principle
Reseed is a local-first project workspace and file manager. Projects, file operations, the journal, reading, search indexes, and production AI features run on your device. Reseed has no analytics, advertising SDK, or account server, and production builds do not send your content to an AI provider.
Some features connect directly to services you choose, such as cloud storage, network shares, web feeds, model downloads, or weather. Those connections are described below so “local-first” is not mistaken for “never uses a network.”
1. Information and permissions
1.1 Core Projects and Files features
On Android, Reseed requests all-files access because broad file management is a core feature. This lets you browse project folders across shared storage and copy, move, rename, search, organize, and delete their contents. The app does not upload those files to Reseed, run analytics over them, or use them for advertising. Files leave your device only when you explicitly use sharing, cloud storage, a network connection, or another network feature.
Project metadata, file indexes, journal entries, reading history, chat history, embeddings, tags, and settings are stored locally in app databases or files. No Reseed account is required.
1.2 On-device AI and voice
Production builds include no cloud AI. Chat, semantic search, tagging, summarization, flashcard generation, and related AI features use on-device models. Messages and attached files are not sent to OpenAI, Anthropic, Google, or another AI provider.
Voice input requires microphone permission. Android voice input uses Android's on-device recognizer only; it is unavailable on Android versions or devices without an installed on-device recognizer. iOS voice conversation uses Apple's on-device SpeechAnalyzer. Audio and transcripts are processed locally.
Optional AI, translation, and dictionary models may be downloaded from Google Play, Hugging Face, Google ML Kit, or Reseed's static site. A download request exposes normal connection metadata such as IP address and user agent to the host. After installation, inference and lookups run locally.
1.3 Cloud and network connections
When you connect Google Drive, OneDrive, Dropbox, Box, MEGA, SMB, WebDAV, FTP, SFTP, or another storage service:
- Authentication tokens and saved credentials are stored on your device using Android Keystore or iOS Keychain where supported.
- Browsing and transfers occur directly between your device and the provider or server you selected. Reseed does not proxy or retain the content.
- The selected provider receives the files, credentials, and normal connection metadata required to fulfill your request under its own privacy terms.
The Web Clipper, RSS reader, OPDS browser, and article reader likewise contact the URL you ask them to open. That server sees normal request metadata.
If you add a Jellyfin media server, Reseed signs in to the server address you entered with the username and password you provide, keeps the resulting session token and password encrypted on your device with the same Keystore key as cloud credentials, and browses, streams, downloads, and shows library artwork directly from that server. Your server sees the same requests any Jellyfin client sends; Reseed does not relay them. On Android TV the app opens on this screen, and the optional screensaver shows photos from the same server.
If you add an Audiobookshelf or calibre server, the same applies: Reseed signs in to the address you entered with the username and password you provide, keeps them encrypted on your device with that Keystore key, and browses, streams, and downloads directly from your server. For Audiobookshelf, Reseed also sends your listening position back to the server while a book or podcast plays, so your account's progress stays in step. Books fetched from a calibre server are saved under Download/Reseed/Calibre on your device.
Subtitle and film lookups in the video player are optional and off until you enter your own API key. With a key entered, the player sends the video's file name, a hash of its contents, and the title and year it guesses from the name to OpenSubtitles (to find subtitles) or The Movie Database (to identify the film). Those services receive that query, your key, and normal connection metadata under their own terms. Without a key no request is made.
Casting sends the address the media is playing from, with its title and artwork, to the Cast device you choose on your local network; that device fetches the stream from the address itself. Nothing is sent to Google's servers by Reseed for this.
If you turn on the Agent Bridge, Reseed keeps an outbound HTTPS connection to a relay server whose address and key you entered, and serves file listings, contents, moves, deletions-to-trash, and name searches to any client that presents a token you issued in the app, limited to the folders you shared. The relay you chose sees that traffic and normal connection metadata; Reseed does not operate a relay for you. You can instead, or in addition, serve the same API to apps on the same phone at a loopback address that no other device can reach; that traffic never leaves the phone. A log of every agent request is kept on your device and can be cleared in the app.
If you install the Reseed watch app on a Wear OS watch paired with your phone, the phone sends it what Reseed is playing (title, artist, position, cover art) and what the glasses viewer is showing (its screen, the rows of a folder list, and a small copy of the picture on the glasses), and the watch sends back the buttons you press. This travels over the Bluetooth link between your phone and your watch through Google Play services' Wear Data Layer, which is scoped to your own paired devices; nothing goes to a server, and nothing is stored beyond the latest state. It is only active while a watch is connected.
1.4 Optional location, weather, news, photos, and calendar features
If you ask Reseed to add context to a journal entry, it may request coarse or precise location permission, store the resulting coordinates with the local entry, and send those coordinates to Open-Meteo to retrieve weather. This means location data is transmitted to and shared with Open-Meteo for app functionality. Open-Meteo also receives normal connection metadata. You can deny location permission or leave journal context off.
The same optional context feature can fetch the public Google News RSS feed. Google receives normal connection metadata, but Reseed does not add your journal text, location, or identity to that request.
When you allow photo access, Reseed reads local photo/video metadata, including dates and available EXIF coordinates, for Activity views, maps, search, and “On This Day.” It does not upload that metadata unless you explicitly share or transfer the file.
Calendar access is requested only when you choose a calendar-based day summary. Events are read from the device calendar store and summarized on-device; Reseed does not call a calendar web API for this feature.
1.5 Camera, USB, notifications, and foreground work
The optional USB-camera viewer can access a connected camera only when you open that feature and grant access. Camera frames remain on-device unless you save or share them. USB-camera hardware is not required to use Reseed.
The Elsewhere window (Files, overflow menu, Elsewhere) uses the front camera to follow your head so the scene's perspective shifts as you move. Frames are analysed on-device by a local face detector and discarded immediately; no image or face data is stored, uploaded, or used to identify anyone. The camera runs only while that screen is open and you have granted camera access; without it the window shows a still view. Photos you add to the window through the system photo picker are copied, reduced in size, into Reseed's private storage together with a depth map computed on the device; they are not uploaded, and removing a photo from the window deletes that copy while leaving your gallery untouched.
The Elsewhere website (reseed.net) is the same window in a web browser. If you allow camera access there, frames from your camera are analysed in your browser by a face-landmark model and are never uploaded, recorded, or shown; the camera stops when you turn tracking off or leave the page. The model and its runtime are downloaded once from public content-delivery hosts (jsDelivr for the runtime, Google's model storage for the model), which see the usual connection data for that download, such as your IP address, but never your camera frames. Your settings on that page (screen size, camera field of view, mirror and inversion switches, chosen scene) are kept in your browser's local storage and nowhere else. The site has no accounts or cookies. It keeps one aggregate count on its own server of page views and scenes opened (which page, nothing about you), with no personal data, no identifiers, and no third party involved. Scene images, when any are offered, are fetched from the site's content host as ordinary downloads. Two test scenes in the Elsewhere window (Train and Room, in the app and on the website) are public research captures downloaded from Hugging Face the first time you choose them; the app keeps the file in its private storage, and the download is the only network use the window has.
Notifications and foreground services are used for user-visible playback, read-aloud, voice conversation, file transfers, FTP serving, the Agent Bridge connection, and audio analysis. They are not used for tracking.
1.6 Purchases
Google Play or the Apple App Store processes in-app purchases and provides Reseed with product and entitlement status. Reseed does not receive your full payment-card details. The store's privacy policy governs its processing.
2. How data is used
| Purpose | Data | Where it goes |
|---|---|---|
| Projects, file management, reading, journal, search | Files and local metadata | Stays on device unless you choose a transfer |
| Production AI features | Selected local content | Stays on device |
| Voice input | Microphone audio and transcript | Stays on device; unavailable without on-device recognition |
| Cloud/network storage | Credentials and files you select | Directly to your selected provider/server |
| Journal weather | Coarse or precise coordinates | Open-Meteo, only when requested |
| Journal news | Public feed request | Google News RSS |
| Jellyfin media server | Sign-in and library/playback requests | Your own server |
| Audiobookshelf or calibre server | Sign-in, library and playback requests, listening progress | Your own server |
| Subtitle and film lookup (optional, your API key) | Video file name, content hash, guessed title and year | OpenSubtitles or The Movie Database |
| Casting | Media address, title, artwork | The Cast device you chose on your network |
| Model/dictionary downloads | Download request metadata | Google Play, Hugging Face, Google ML Kit, or Reseed's static host |
| Purchases | Product and entitlement information | Google Play or Apple App Store |
Reseed does not sell personal data, use data for behavioral advertising, or track you across apps and websites.
3. Storage, security, and retention
Local app data remains until you delete it, clear app storage, or uninstall the app. Files placed in user-visible storage remain until you delete them. Cloud providers and servers retain transferred data under their own policies.
Network connections use TLS when the selected service supports it. Dictionary pack downloads are SHA-256 integrity checked. No system can be guaranteed perfectly secure; keep device security and backups appropriate to your files.
4. Your choices
- Deny or revoke optional microphone, location, calendar, photo, camera, or notification permissions in system settings.
- Disconnect cloud accounts in Reseed and revoke the grant in the provider's connected-app settings if necessary.
- Delete local conversations, projects, indexes, and files through the app or your device. Clearing app data removes Reseed's private databases and tokens, but not files you placed in shared storage.
- Use Projects, Files, reading, journal, and on-device AI without connecting a cloud storage account. Network-only features naturally require a connection.
5. Children's privacy
Reseed is not directed to children under 13, and we do not knowingly collect personal information from children. Store accounts and purchases are subject to Google Play or Apple age and family rules.
6. Changes to this policy
We will update this policy before a release materially changes where data goes, including before any optional cloud-AI service becomes available. The date at the top identifies the current version.
7. Contact
For privacy questions or concerns, email support@reseed.net. Reseed does not operate a user-account or analytics database from which it can retrieve or delete a profile; use the controls above for on-device and provider-held data.