Privacy Policy
This policy explains what data Snippets handles today, where it is stored, and how limited service data is used to operate optional account, sync, calendar, payment, and support features.
Overview
Snippets is designed around a local-first model. In normal use, notes and related content are stored on the user's own device unless the user chooses an optional sync method.
We aim to keep data collection limited to what is required to operate the website, receive feedback, prevent abuse, and support optional features chosen by the user, including accounts, Snippets Cloud, Google Calendar, and paid licenses.
Data Storage and Optional Sync
Notes are stored locally on the user's device by default. Users may optionally enable synchronization using the local file system, a GitHub repository under their own GitHub account, or Snippets Cloud.
If GitHub sync is enabled, synced content is stored and processed by GitHub under the user's own GitHub setup and is subject to GitHub's terms and privacy practices.
Snippets Cloud is an optional cloud sync service currently in beta. Data for Snippets Cloud is hosted on Amazon Web Services. During the beta, Snippets does not guarantee that synced data will be stored safely, remain available, or be preserved with 100% durability. Users should keep their own backups of important data.
User Accounts
Users may sign up for a Snippets account, but accounts remain optional. An account may be used for features such as Snippets Cloud, license management, or related account-based services.
Account data may include information such as an email address, authentication identifiers, license status, service metadata, and similar records needed to provide and protect account features.
End-to-End Encryption
Snippets Cloud uses client-side end-to-end encryption for encrypted content. In short: a vault key is derived from the user's passphrase with libsodium password hashing, each item uses a random data key, keys are wrapped with XChaCha20-Poly1305 AEAD, and payloads are encrypted with random nonces.
Pro Licenses and Payments
Users may optionally buy a Snippets Pro license. Payments are processed by Lemon Squeezy, which handles payment details under its own terms and privacy practices.
Snippets may receive and store related transaction, license, customer, and subscription metadata needed to activate, manage, and support Pro licenses.
Network Requests and Feedback
The app uses a small number of backend endpoints, for example to submit feedback or similar service requests.
For those requests, the client's IP address may be processed to prevent abuse, apply rate limits, and protect service stability. Feedback content is stored as submitted so it can be reviewed and acted on.
Website Analytics, Cookies, and Trackers
The Snippets website uses limited first-party analytics to understand basic website usage and interest in downloads. In particular, the landing page may send events when it is visited, when a visitor scrolls substantially through it, when a download button is clicked, and when a browser referrer is available.
These analytics events are sent directly to a Snippets-owned backend endpoint. They are not used for advertising or cross-site behavioral profiling, and the website does not use cookies for analytics or marketing.
Like any standard web request, analytics requests may include technical information such as the client's IP address and request metadata processed by the receiving infrastructure.
Hosting and Sharing
Data collected through backend service endpoints is hosted on Amazon Web Services. Payment processing is provided by Lemon Squeezy. Data is not sold and is not shared with third parties except as needed to operate, secure, and support the service infrastructure, integrations, and payment systems used by Snippets, subject to the Google user data limits below.
Google Calendar
Connecting Google Calendar is optional. Through Google's OAuth consent screen, you grant Snippets permission to read all calendar information available to your account, including shared calendars, and write calendar changes. This includes event details and attendee information, used only to display your calendars and make changes through the app.
After you authorize access through Google OAuth, Snippets stores the resulting OAuth credentials locally on your device. Calendar data is loaded into memory to provide the calendar features; it is not saved to persistent local storage or to any Snippets database. Neither OAuth credentials nor calendar data are stored on Snippets servers or in Snippets Cloud.
Changes you make to your calendars are sent to Google and shared according to your calendar settings, subject to Google's Privacy Policy.
Google User Data Retention and Deletion
Google OAuth credentials are retained locally on your device until you disconnect Google Calendar in Snippets. To delete these credentials, click Disconnect for the Google Calendar connection in the app. This removes the locally stored credentials from your device.
Google Calendar data is held temporarily in application memory while the app is running and is discarded when the app exits. Snippets does not retain a persistent copy of this data on your device or in its databases, servers, or cloud backups. Discarding this temporary data does not delete your calendars or events from Google Calendar.
You can revoke Snippets' access at any time through your Google Account connections. Revoking access prevents Snippets from accessing your Google Calendar data again unless you authorize it again. Your calendars and events remain in your Google account, where you can manage or delete them directly through Google Calendar.
Changes to This Policy
This policy may be updated as Snippets evolves, including when product features, authentication, payment, sync, or additional online services change.