Privacy Policy

1. Overview

Snippbot is self-hosted software that runs entirely on your machine (or your own server). This privacy policy explains what data Snippbot stores, where it's stored, and how third-party integrations work.

2. Data Stored by Snippbot

All data is stored locally in ~/.snippbot/ on your machine:

• config.toml — System configuration and preferences
• snippbot.db — Main application database (projects, tasks, conversations)
• auth.db — Authentication (bcrypt-hashed passwords, SHA-256 hashed API tokens)
• profile_settings.db — User profile preferences
• memory.db — Episodic memory and embeddings
• knowledge.db — Knowledge graph (entities and relations)
• Agent workspace files (personas, history, artifacts)
• User uploads and attachments

3. Where Data is Stored

Exclusively on your local machine or your self-hosted server. Snippbot does not transmit any data to Snippbot-operated servers. There is no cloud sync, no backup service, no data replication.

4. No Telemetry

Snippbot does not collect usage analytics, crash reports, or telemetry of any kind. There is no phone-home behavior. The software does not make any network requests to Snippbot servers, except a bug report or a report about an AI response that you choose to send us.

5. Third-Party API Calls

When you use AI features, your messages are sent directly from your machine to your chosen LLM provider (Anthropic, OpenAI, Google, etc.) using your API key. Snippbot does not:

• Proxy your API calls through our servers
• Log or store API call content beyond your local conversation history
• Share your API keys with any third party

Review your LLM provider's privacy policy for how they handle your data.

If you turn on push notifications for the Snippbot mobile app, your Snippbot server sends notification content through Expo's push notification service and Google's Firebase Cloud Messaging so it can reach your phone. See Section 6.

6. The Snippbot Mobile App

The Snippbot app for Android, published by Snippai LLC, is a remote control for the Snippbot server you run yourself. It has no Snippbot account and no Snippai LLC server behind it: it talks to your server, which you pair it with. Optional third-party services and purchases are described in 6.4; reports you choose to send us are described in 6.5.

6.1 Where your data goes

• Your messages, the files and photos you attach, your voice recordings, and your settings changes are sent from the app directly to the Snippbot server you paired it with, and stored there. Snippai LLC never receives them, except for a response you report to us (6.5).
• The app reaches your server either on your local network or through an address you set up, such as a tunnel. On your local network it can use plain HTTP when your server does not offer HTTPS; that traffic, including the app's access token, is not encrypted. Use an HTTPS address when you connect from outside your home network.
• If the app crashes, it sends a crash report (the error, where it happened, your phone model and Android version) to your own server only.

6.2 Data stored on your phone

• Your server's address and the access token issued when you paired, kept in Android's encrypted storage.
• App preferences, such as app lock and notification choices.

Disconnect Device in the app's Settings removes the address and token. Uninstalling the app removes everything it stored on the phone.

6.3 Permissions

• Camera: to scan the pairing QR code, and to take a photo when you choose to attach one to a chat. QR codes are read on your phone and never leave it; photos you attach are sent to your server.
• Microphone: only while you record a voice message. The recording is sent to your server to be transcribed. Your server may pass it to a speech-to-text provider you configured there, under that provider's policy.
• Notifications: to show alerts from your server, only if you turn them on.
• Biometrics: to unlock the app with your fingerprint or face if you turn on app lock. Android handles the check; the app never sees your biometric data.

6.4 Services the app uses

• Push notifications (optional). When you turn on notifications, the app gets a push token from Expo's push notification service (operated by 650 Industries, Inc.), which uses Google's Firebase Cloud Messaging. To issue it, Expo receives your phone's Firebase token and an identifier for this installation. The app then registers the push token with your server. When your server sends you a notification, its content passes through Expo and Google to reach your phone. See Expo's privacy policy and Google's privacy policy. You can turn notifications off at any time in the app or in Android settings.
• Supporter purchases (optional, in builds with billing enabled). Opening Support Snippbot connects to RevenueCat and your app store. RevenueCat receives a random billing identifier, purchase history and receipts or purchase tokens, and app/device information needed to validate purchases and restore your badge. Snippai LLC can view billing records in RevenueCat. Once billing is used, the app refreshes billing status when you return to Settings or Support Snippbot. We do not send your conversations, daemon address, pairing credentials, name, or email to RevenueCat. The store processes payment details; Snippbot does not receive your card details. RevenueCat provides purchase validation, entitlement management, and billing analytics. See RevenueCat's privacy policy.
• Billing data and deletion. RevenueCat keeps billing records separately from your daemon and phone; disconnecting or uninstalling does not delete these records. To request deletion, email [email protected] with the Billing support ID shown on Support Snippbot. We may request purchase verification before deleting records. Store transaction records remain subject to the store's retention requirements. Deletion does not refund a purchase; restoring a purchase creates billing records again.
• App updates. Each time it starts, the app asks Expo's update service whether a newer version of its code is available. That request includes a random identifier for this installation, the app version, and the platform. It contains no personal information and none of your content.

6.5 Reporting a response

Each AI response in the app has a Report button for flagging harmful or offensive content. The app sends a report only after you tap Send report. A report contains:

• the full text of the response you are reporting;
• the reason you picked and any note you add;
• the app version, the platform (Android), and whether you sent it from the demo.

It does not include the rest of your conversation, your server's address, your access token, or any account or contact details. A response can repeat things from your conversation, so check it before you send. Reports go to our issue tracker at issues.snippbot.com, where only Snippai LLC can read them. We use them to review harmful or offensive responses and to improve the safeguards that ship with Snippbot. To limit abuse, the tracker counts reports from each network using a one-way hash of your IP address, not the address itself. Reports are anonymous, so to have one deleted, email [email protected] with roughly when you sent it and what it said.

6.6 Demo mode

A new installation opens in test mode ("Explore the demo" also starts it), which uses sample data built into the app. Nothing you do in test mode is sent anywhere, except a report you choose to send (6.5) and app-update checks. Sending chats and Supporter checkout are turned off in test mode; theme previews there do not contact the store or RevenueCat.

6.7 What the app does not do

• No advertising or cross-app tracking SDKs. Optional purchases use RevenueCat for purchase validation and billing analytics.
• We do not sell your data. The service providers described above process data needed for their services. Snippai LLC does not receive your conversations, files, or recordings, other than a response you report (6.5).
• No access to your location or contacts, and no access to your photo library beyond the photos you pick to attach.

To delete data held by your server, including devices you have paired, use your server (Section 8). Questions about the app: [email protected].

7. This Website

The snippbot.com marketing site:

• Does not use cookies beyond essential functionality
• Does not use third-party analytics or trackers
• Is a static site with no server-side data collection

8. Your Rights

You have full control over your data:

• View — All data is in readable SQLite databases and text files in ~/.snippbot/
• Export — Use snippbot config show or access files directly
• Delete — Run snippbot reset to remove all data, or manually delete ~/.snippbot/
• No account needed — Snippbot works without creating any external account

9. Singularity Marketplace

If you use the Singularity Marketplace (www.singularitymarketplace.com) to discover, download, or install Packages, the Marketplace has its own Privacy Policy governing data collected by that platform (publisher accounts, package analytics, etc.). Packages installed through the Marketplace run locally on your machine — Snippbot does not share your local data with the Marketplace or with Package publishers. However, individual Packages may have their own data collection behaviors; review each Package's documentation before installation.

9.1 Data Deletion (including Facebook / Google sign-in data)

If you signed up for a Singularity Marketplace publisher account using Sign in with Google or Sign in with Facebook, the Marketplace stores your email address (received from the provider), your linked provider account ID, and your Marketplace publisher profile. To request deletion of all data Snippai LLC has stored about your account — including any data received from Google or Facebook — email [email protected] from the email address on file. We will confirm receipt within one business day and complete deletion within 30 days. Deletion is irreversible; once it completes, your Publisher name, Packages, license history, and provider links cannot be restored.

Alternatively, if you want to remove a connected social account (Google or Facebook) without deleting your Marketplace account, sign in and go to Settings → Connected accounts and click Disconnect. This revokes Snippai LLC's access token through the provider's permissions API (Google: oauth2.googleapis.com/revoke; Facebook: DELETE /me/permissions) and removes the link from our database, but keeps your Marketplace account, Packages, and license history intact.

For data stored locally by the Snippbot desktop application (not the Marketplace), see Section 8 above — local data deletion is under your direct control via snippbot reset or removing ~/.snippbot/.

10. Future Hybrid/Cloud Mode

If cloud features are introduced in the future (Phase 6-7), they will be strictly opt-in. Local-only mode will always remain available and free. No data will ever be sent to cloud services without explicit user consent.

11. Children

Snippbot is not directed at children under 13. We do not knowingly collect data from children.

12. Changes

We may update this privacy policy. Changes will be posted on this page with an updated date. Since Snippbot is self-hosted, privacy policy changes do not affect your local installation — they only apply to this website and future software releases.

13. Contact

Privacy questions: [email protected]