Privacy Policy
Our Privacy Principle
Reseed is built on a simple idea: your files are yours. The core app runs entirely on your device with no cloud uploads, no tracking, and no data collection. The optional AI Workspace subscription introduces cloud AI processing — but only when you explicitly choose it, and only on the content you select. When you use it, your messages are routed through Reseed to the AI provider and are never stored by us.
1. Information We Collect
1.1 Core App (Free + AI Unlock) — No Data Collected
The core Reseed app, including all local file handling and the on-device AI (semantic search, auto-tagging, summarization, knowledge graph), operates entirely offline. We collect:
- No file data. Your files are never uploaded, scanned, or accessed by our servers.
- No usage analytics. We do not track which files you open, how often you use the app, or what you search for.
- No personal information. No account creation is required for the core app or the AI Unlock purchase.
- No advertising identifiers. Reseed contains no ads and no ad SDKs.
The on-device AI models (Gemma, Universal Sentence Encoder, MediaPipe Text Classifier) run locally on your device's processor. All indexing, embeddings, classifications, and knowledge graph data are stored in a local database on your device. No data leaves your device when using the core app.
1.2 AI Workspace Subscription — Cloud Processing (Opt-In Only)
If you subscribe to AI Workspace, the following data is processed:
| Data | Where It Goes | Why | Retention |
|---|---|---|---|
| Messages you send in AI Workspace chat | Reseed's AI proxy, which forwards them to the provider you select (OpenAI, Anthropic, or Google) | To generate AI responses to your questions | See Section 3 (per-provider policies) |
| Files you attach to a chat | Reseed's AI proxy, which forwards them to the provider you select | To provide file context for your conversation | See Section 3 (per-provider policies) |
| Subscription status | Google Play / Apple App Store | To verify your subscription and manage billing | Per Google/Apple policies |
| Token usage counts | Reseed auth service | To enforce your monthly token budget | Retained for the current billing cycle, then deleted |
| Voice transcripts (voice conversation mode) | Reseed's AI proxy, which forwards them to the provider you select | To answer your spoken questions | Per provider (Section 3) |
What we do NOT do with your AI Workspace content:
- Your chat messages and attached files are routed through Reseed's proxy to the AI provider. The proxy is a transient relay — it holds your content only in memory for the moment it takes to forward the request and stream the response back. We do not store, log, or retain the content of your messages, your attachments, or the AI's responses.
- We do not read or analyze the content of your conversations.
- We do not use your conversations or files to train any AI model, and our agreements with each AI provider prohibit them from training on your content.
Voice conversation: When you use voice mode, microphone
audio is transcribed on your device (Android:
android.speech.SpeechRecognizer; iOS:
SFSpeechRecognizer). Only the resulting text is sent — through
Reseed's proxy — to your selected AI provider; raw audio never leaves the
device. The provider's text response is then synthesized to speech locally
on-device.
1.3 Cloud Storage Connections (Google Drive, OneDrive, Dropbox, etc.)
When you connect a cloud storage account:
- Authentication tokens are stored locally on your device (Android Keystore / iOS Keychain).
- File browsing and transfers happen directly between your device and the cloud provider. Reseed servers are not involved.
- We do not store, cache, or access your cloud storage credentials on any server.
1.4 Other Features That Touch the Network or Device Sensors
These features are optional. The core app works without using any of them.
Photos library access. When you grant Photos permission, Reseed reads photo and video metadata (creation date, location EXIF tags, file path, dimensions) to populate the journal photo grid, "On This Day" view, and search index. Photo files themselves are accessed only locally — they are never uploaded to Reseed servers or any third party unless you explicitly attach a specific photo to an AI Workspace chat (Section 1.2) or share it via the system share sheet.
Journal context (location, weather, news headlines). If you enable context collection on a journal entry, Reseed may, with your permission:
- Read your device's current coordinates (Android:
ACCESS_COARSE_LOCATIONorACCESS_FINE_LOCATION; iOS: "When In Use" location authorization). Coordinates are stored locally with the entry. - Send those coordinates to Open-Meteo (
api.open-meteo.com) to retrieve current weather. Open-Meteo is a free service that does not require an API key. See open-meteo.com/en/terms. - Fetch the public Google News RSS feed (
news.google.com/rss) and extract the top five headlines. No personal information is included in the request; the feed host (Google) sees standard request metadata (IP, User-Agent).
You can disable journal context collection in Settings, or simply deny the location permission, in which case none of the above occurs.
Web Clipper, RSS reader, OPDS catalog browser. When you save a URL, add a feed, or open a catalog, your device fetches that URL directly from the third-party server you specified. The destination server sees standard request metadata (IP, User-Agent), exactly as it would for a normal web browser. No traffic is routed through Reseed servers.
Network protocols (SMB, WebDAV, FTP, SFTP). Connections are made directly from your device to the server you configure. No traffic is routed through Reseed servers.
2. How Your Data Is Used
| Purpose | Data Used | Legal Basis |
|---|---|---|
| Providing core local file features | None (all local) | N/A — no data collected |
| On-device AI features (search, tagging, summarization) | None (all local) | N/A — no data collected |
| AI Workspace chat responses | Messages and attached files routed through Reseed's proxy to your chosen AI provider | Your explicit consent (opt-in subscription) |
| Subscription management | Purchase/subscription status via app store | Contract performance |
| Token budget enforcement | Aggregated token counts (no message content) | Contract performance |
| Voice conversation | Microphone audio (transcribed on-device); resulting text routed through Reseed's proxy to your chosen AI provider | Your explicit consent |
| Journal weather context | Current device coordinates sent to Open-Meteo | Your explicit consent (per-entry toggle) |
| Journal news context | None personal — public RSS feed fetched | N/A — no personal data collected |
| Photos library access | Photo/video metadata read locally; no transmission | Your explicit consent (system Photos permission) |
| Web Clipper, RSS, OPDS, network shares | URL fetched directly from device to third-party server | Your explicit action |
3. Third-Party AI Providers (AI Workspace Only)
When you use AI Workspace, your messages and attached files are routed through Reseed's proxy to the AI provider you select, using Reseed's own business API account with that provider. Each provider has its own data handling practices, and Reseed configures the most privacy-protective commercial terms available:
OpenAI (ChatGPT / GPT-4o)
- API data policy: OpenAI does not use API inputs/outputs to train its models.
- Retention: Accessed under Reseed's business API account with zero data retention configured where available; otherwise inputs are retained only briefly for abuse monitoring, then deleted.
- Privacy policy: openai.com/policies/privacy-policy
Anthropic (Claude)
- API data policy: Anthropic does not train on API inputs/outputs.
- Retention: Retained only transiently as permitted under Anthropic's commercial terms; Reseed does not enable any optional data-sharing.
- Privacy policy: anthropic.com/privacy
Google (Gemini)
- API data policy: Gemini data is not used to train models when accessed via the paid API, which is how Reseed connects.
- Retention: Per Reseed's Google Cloud data-processing terms.
- Privacy policy: policies.google.com/privacy
Future Providers (xAI/Grok, DeepSeek, Meta/Llama)
- When additional AI providers are added to AI Workspace, this policy will be updated with their specific data handling practices before they become available.
- You will always be informed which provider is processing your data before sending a message.
Important: Reseed runs the proxy that relays your request to the provider and returns the response. We pass your content through to fulfill the request but do not store or retain it, and our agreements with each provider prohibit training on it. We encourage you to review each provider's privacy policy. The active provider is shown in the app's model selection screen before you send a message.
4. Data Storage and Security
Message Flow (AI Workspace)
When you send an AI Workspace message, it is transmitted over TLS to Reseed's AI proxy, which forwards it to the provider you select (OpenAI, Anthropic, or Google) using Reseed-managed credentials and streams the response back to your device. The proxy holds your message and the response only in memory for the duration of the request — it does not log, cache, or persist the content. Subscription verification and token-budget accounting use only metadata (an opaque subscription identifier and token counts), never the content of your messages.
On-Device Data
- All file indexes, embeddings, tags, knowledge graph data, and saved AI conversation summaries are stored in an encrypted local database (Room/SQLite) on your device.
- Saved AI Workspace conversations and summaries are stored as local files in a user-configurable folder. They never leave your device unless you explicitly share or export them.
- Cloud storage authentication tokens are stored in Android Keystore / iOS Keychain (hardware-backed encryption where available).
Credentials (AI Workspace)
- The AI provider API keys are held server-side by Reseed and used only by the proxy. They are never sent to or stored on your device.
- Your device authenticates to the proxy with a short-lived Reseed session token issued after your subscription is verified.
- You do not need to provide your own AI provider API key.
Network Security
- All API communications use TLS 1.2+ encryption.
- Certificate pinning is implemented for AI provider API endpoints.
5. Your Choices and Controls
| Control | How |
|---|---|
| Use Reseed without any cloud features | Simply don't subscribe to AI Workspace. The entire core app works offline with zero data collection. |
| Choose which files to share with AI | Files are only sent to AI providers when you explicitly attach them to a chat. No automatic file sharing ever occurs. |
| Choose your AI provider | You select which AI models are active. You control which provider processes each conversation. |
| Save or discard conversations | After each chat, choose to save the full conversation, save only a summary, or discard entirely. Nothing is saved without your action (unless you enable auto-save). |
| Delete saved conversations | Saved chats and summaries are regular files on your device. Delete them like any other file. They are also removed from the knowledge graph. |
| Cancel AI Workspace | Cancel anytime through Google Play or the App Store. Your locally saved conversations and knowledge graph data remain on your device. |
| Revoke connected cloud storage | Uninstalling Reseed removes OAuth tokens from your device, but the grant may persist in your provider account. To fully revoke, visit the provider's connected-apps page: Google, Microsoft, or Dropbox. |
| Delete all app data | Uninstalling Reseed or clearing app data removes all local databases, indexes, embeddings, and saved conversations permanently. |
6. Children's Privacy
Reseed is not directed at children under 13. We do not knowingly collect personal information from children. The AI Workspace subscription requires a Google Play or App Store account, which have their own age restrictions.
7. Data Transfers
- Core app: No data transfers occur. Everything stays on your device.
- AI Workspace: When you send a message, it is transmitted to Reseed's proxy and then forwarded to the AI provider's servers. Reseed's proxy and OpenAI's and Anthropic's servers are located in the United States. Google servers may be located in various regions per Google Cloud's infrastructure. By using AI Workspace, you consent to this transfer.
8. Changes to This Policy
We will update this privacy policy when new features (such as additional AI providers) are added. Material changes will be communicated through an in-app notification. The "Last Updated" date at the top of this document will always reflect the most recent revision.
9. Contact
For privacy questions, data deletion requests, or concerns:
- Email: support@reseed.net
Deleting your Reseed auth-service record. The Reseed auth service stores only your current-billing-cycle token count, keyed to an opaque subscription identifier. To delete this record, email support@reseed.net with the subject "Account deletion." We will purge the record within 30 days. Cancelling your subscription through Apple or Google does not by itself delete this server-side record.
Summary
| Feature | Data Leaves Your Device? | Who Processes It? |
|---|---|---|
| File browsing, viewing, organizing | No | Nobody — all local |
| On-device AI (search, tags, summaries, knowledge graph) | No | Nobody — all local |
| AI Unlock (one-time purchase) | No (except purchase verification) | Google Play / App Store |
| Flashcard Pack purchases | No (except purchase verification) | Google Play / App Store |
| Flashcard Pack content | No — downloaded and stored locally | Nobody — all local |
| AI Workspace chat | Yes — only the messages and files you choose to send | Routed through Reseed's proxy (held in memory, not stored) to the AI provider you select (OpenAI, Anthropic, or Google) |
| Voice conversation (microphone) | Audio stays on device; transcribed text is sent | Routed through Reseed's proxy to the AI provider you select |
| Saved conversations / summaries | No — stored locally | Nobody — all local |
| Cloud storage browsing (Drive, OneDrive, etc.) | Yes — to the cloud provider you connected | The cloud storage provider |
| Photos library access | No — metadata read locally; files stay on device | Nobody — all local |
| Journal weather context | Yes — current coordinates only | Open-Meteo |
| Journal news context | Yes — request only (no personal data) | Google News RSS |
| Web Clipper / RSS / OPDS / SMB / WebDAV / FTP / SFTP | Yes — direct fetch from your device | The third-party server you specified |
| Token usage counts (AI Workspace) | Yes — anonymously keyed to subscription identifier | Reseed auth service |