Privacy Policy
Last updated:
Tearleads, LLC operates Command Snippets. This policy explains how we handle information when you use our website, web app and API or contact us.
Snippets and tags start private. You choose what to publish. Private content is stored and processed to run the service; “private” does not mean it is inaccessible to the service operator.
1. Information we collect
- Account information. When you sign in with Google or GitHub, we receive a verified email address and use it to find or create your account. GitHub also provides a username; for Google we derive an initial username from your email address. We store your username, account identifiers, account status, sign-in counts and activity dates. We do not receive your Google or GitHub password.
- Your content. We store snippet subjects and bodies, tags, their order and relationships, visibility settings, creation and update dates, and saved versions of your data. Copying your own snippets records reuse counts and timestamps, which are part of your account data.
- Technical information. Requests to the service expose information such as IP addresses, request paths and browser details to our hosting provider. Authentication records and administrative audit records help us operate and protect accounts. Click analytics are described separately below.
- Communications. If you email us, we receive your email address and whatever you include in the message and attachments.
2. How we use information
We use information to authenticate you, save and synchronize your content, provide search, backups and reuse history, display content you make public, respond to support requests, investigate failures or abuse, and meet legal obligations. We use limited click analytics to understand which parts of the website and app are used and to improve them.
We do not sell personal information or use snippet content for targeted advertising. We do not send snippet text to the click analytics collector.
3. Public sharing and service providers
A snippet is publicly available when both the snippet and at least one tag containing it are public. Public pages can expose your username, public tags and snippet content to anyone who visits them, along with creation and update dates, tag activity dates, ordering, and counts of public tags and snippets. Your reuse history is not shown on public pages. Other people can copy public content; making it private later cannot recall copies or remove it from someone else's device.
Cloudflare hosts our website, application, API and database and processes information needed to deliver and secure them. Google or GitHub processes your sign-in under its own privacy policy. Our support email provider processes messages you send us. Authorized administrators can access account information and stored content for support, security and administration. CT, our click analytics service, is also operated by Tearleads, LLC and hosted on Cloudflare.
We may disclose information when reasonably necessary to comply with legal requirements, protect people's rights or safety, or investigate misuse. Information may also transfer as part of a merger, acquisition or transfer of the service, subject to applicable law and notice of material changes.
4. Cookies and data on your device
Authentication cookies keep you signed in and normally expire after 28 days unless renewed. Browser storage remembers your account and preferences. The app also keeps a local database of snippets, tags and pending edits so you can work offline, and caches application files for faster loading. Sign-in uses temporary browser storage to complete the authentication flow.
Signing out normally removes the signed-in account's local data. If changes have not reached the server, the app can keep them on that device for your next sign-in or let you discard them. Public-page caches and downloaded backup files are separate. Clearing site data removes browser storage, but can also destroy unsynchronized edits; it does not delete your server account or files you downloaded. Blocking cookies or storage may prevent sign-in or offline features from working.
5. Click analytics and your choices
CT records click times, element types, the application and environment, and public website paths such as /about/. Web app clicks use a generic page identifier so usernames and tag names in routes are not collected.
The collector also records the IP address and available approximate location, such as country, region and city. Click records are retained for up to 90 days and are available only to authenticated CT administrators. We do not send snippet text, form values, link destinations, query strings, account identifiers or persistent visitor identifiers with these events. Editable fields are excluded from click collection.
CT honors the browser's Do Not Track setting. You can also disable CT using the CT browser extension in each browser or profile you use. Global Privacy Control does not disable this click collection. Opting out of click analytics does not disable the authentication and storage needed to use the app.
6. Retention and deletion
We keep account data and content to provide the service while your account remains open. Deleting a snippet or tag hides it from normal use but can leave a deletion record and its content on the server for synchronization. Restoring a backup creates a new data version and preserves earlier versions; it does not erase them. You can delete inactive versions through Data Versions.
Contact us to request account deletion or removal of retained content. Deactivation or marking an account for deletion is not the same as completed erasure. We may retain information needed for security, dispute resolution or legal obligations, and copies may remain in recovery backups until those backups expire. Administrative audit records can retain usernames after an account is removed. Retention depends on the information's purpose and these obligations; the specific 90-day limit above applies to CT click records.
7. Your controls and privacy requests
You can edit or delete snippets and tags, change their visibility, export a backup, and manage saved data versions in the app. To request access, correction, deletion or help exporting other account information, email support@tearleads.com. Tell us the account username and the request; do not send passwords, authentication tokens or sensitive snippet content. We may ask for information to verify that the account is yours before acting.
Depending on where you live, applicable law may also give you rights to restrict or object to processing, withdraw consent where processing relies on it, appeal a decision about a request, or complain to a privacy regulator. Contact us to exercise applicable rights or appeal our response. We will respond within the period required by applicable law and will not discriminate against you for exercising those rights.
8. Security and international processing
The service uses HTTPS and account access controls. It is not an end-to-end encrypted vault, and no storage or transmission system is completely secure. Avoid putting passwords, access tokens or other secrets in snippets, and protect the devices and identity-provider accounts you use to sign in.
Our service providers operate internationally, so information may be processed outside the country where you live. Privacy protections can differ by country. Contact us with questions about processing locations or safeguards applicable to your information.
9. Children
Command Snippets is for people aged 18 and older and is not directed to children. We do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has provided information, contact us so we can investigate and arrange its removal as appropriate.
10. Updates and contact
We will update the date on this page when this policy changes. For material changes, we will provide additional notice through the service or another appropriate channel and obtain consent when required by law.
The operator responsible for this policy is Tearleads, LLC. Send privacy questions or requests to support@tearleads.com. Our Terms of Service describe the rules for using Command Snippets.