Privacy
Privacy at SnippetGraph
SnippetGraph is designed to act as a pass-through workspace. We do not store user data as a product asset, data broker feed, or training dataset. Content you choose to publish is forwarded to GitHub or another destination exactly as you send it, without rewriting, reselling, or repackaging it.
You stay in control of when a workspace is created, used, connected, disconnected, or deleted. If you no longer want a workspace, you can remove it and stop using the service on your own terms.
What this page covers
This page explains the basic privacy expectations for SnippetGraph, including what we collect, how data moves through the product, and what controls you have over your workspace.
The short version: SnippetGraph is built to forward your content to the destination you select, not to keep, mine, or commercialize that content for itself.
User data handling
We do not store user data for profiling, ad targeting, or resale. We do not alter your content before forwarding it to GitHub or another configured destination.
Content flows through SnippetGraph as a delivery layer so you can publish knowledge to your chosen system as-is. Ownership and control remain with you and your team.
Workspace control
You decide when to create a workspace, when to connect destinations, when to publish, and when to delete a workspace. Those actions are initiated by you, not by automatic redistribution.
Deleting a workspace is your control point for removing work you no longer want managed through SnippetGraph.
Destinations and third parties
When you connect GitHub or another destination, your content is sent only to that configured destination so the workflow you selected can complete.
Third-party platforms such as GitHub apply their own terms, privacy policies, and retention rules once the content reaches them.
General privacy principles
We aim to follow a simple privacy model:
- Collect as little information as possible to operate the workspace you requested.
- Do not sell user data.
- Do not use your content as a marketing dataset.
- Keep publishing behavior transparent so you know where your work is going.
- Give users direct control over workspace usage and deletion.