Privacy policy
Current policy effective October 13, 2026.
Location analytics update prepared October 21, 2026. The planned collection described below is not active yet. It will take effect with a future release, only after Scope verifies the PostHog privacy settings and notifies account holders by email or in the product in advance. Scope will publish the effective date when that release is scheduled.
Scope is a version control service at scopevcs.com, run by Adam Blumoff as an individual. This policy explains what personal data Scope handles, why, who processes it, how long it is kept, and what you can do about it. Questions and requests go to hello@scopevcs.com.
What Scope collects
Account data. When you sign up, Clerk handles sign-in and passes Scope your verified email address and a Clerk account identifier. Scope stores your handle, email address and that identifier. If you sign in with another provider through Clerk, Clerk receives the profile data that provider shares.
Content you add. Repositories you push, including commit author names and email addresses recorded in Git history; requests, revisions, discussions and replies; media attachments; ratings; and repository invitations, including the invited email address.
CLI sessions. When you sign in from the Scope CLI, Scope stores a hashed session token, a session label, and when the session was created, last used, expires and was revoked.
Workflow runs. Logs and results from workflows that run on your repositories.
Product analytics. The website records page views, error types and performance measurements. The API records outcomes such as pushes, submitted requests and completed workflow runs. Events use a random page-memory ID for signed-out visitors and an opaque internal user ID for signed-in users, never your name or email. Signed-in events can be associated with your Scope account. Events captured before sign-in in the same page can be linked to that user ID. These IDs are pseudonymous. Events exclude names, email addresses, repository names, source code, file paths, request titles and discussion content. The website keeps its analytics ID in page memory only. Nothing is written to cookies or browser storage for analytics. Browser analytics stops completely if your browser sends Do Not Track or Global Privacy Control.
Planned approximate location analytics. After the update takes effect, Scope will use the IP address of browser analytics requests to estimate country, region and city. Scope's web proxy will temporarily send the visitor IP address provided by its trusted hosting proxy to PostHog in the United States. PostHog will derive the approximate location and discard the raw IP address from stored analytics events. Latitude, longitude and postal codes will also be removed. Scope will not request browser GPS or other device location access. Approximate location will be associated with the analytics IDs described above, including the internal user ID when signed in. Backend analytics events will continue to have IP-based location enrichment disabled. The browser analytics storage and Do Not Track and Global Privacy Control protections above will still apply.
Operational logs. Scope's servers log request paths, timing and errors to operate and secure the service. These logs, and traces of how long each step of a request took, are sent to PostHog. Log lines can include repository names, file paths and error details. Railway, Scope's hosting provider, also records your IP address in its HTTP logs. Until the planned location analytics update takes effect, the analytics proxy removes your IP address before events are sent to PostHog. The planned update does not change Railway's HTTP logging.
Scope does not sell or share personal data for advertising, and does not use advertising cookies. The website stores only what it needs to work: Clerk's sign-in cookies, your theme preference, a cookie remembering whether you collapsed the requests sidebar, and, for the current tab only, unsent attachment drafts and one-time notices.
Why Scope uses it
- To provide the service you signed up for: hosting repositories, running workflows, and sending the invitations you ask Scope to send. For users in the EU and UK, the legal basis is performance of a contract.
- To keep the service secure and working, and to understand which features are used so they can be improved. Once the planned update takes effect, this will include understanding where visitors use Scope at an approximate country, region and city level. The legal basis is legitimate interest. You can opt out of browser analytics with Do Not Track or Global Privacy Control.
- To meet legal obligations, such as responding to valid legal requests.
Who processes it
Scope uses these service providers. Each receives only what it needs for its job.
| Provider | Purpose | Location |
|---|---|---|
| Clerk | Sign-in and account identity | United States |
| Railway | Application hosting, database and file storage | United States |
| Amazon Web Services | Workflow runners and encrypted database backups | United States |
| PostHog | Product analytics, planned approximate location enrichment, application logs and traces | United States |
| Resend | Sending invitation emails | United States |
Scope stores data in the United States. If you use Scope from elsewhere, your data is transferred to the United States.
Repository content is visible to the people you give access to, and public repositories are visible to everyone.
How long it is kept
| Data | Retention |
|---|---|
| Account data | Until you delete your account |
| Repositories and their requests, discussions and attachments | Until the repository is deleted |
| Workflow runs and logs | 30 days after the run finishes |
| Repository invitations, including the invited email | 30 days after the invitation is accepted, revoked or expires |
| Database backups | 42 days |
| Server and hosting logs, including IP addresses | Railway's log retention period |
| Application logs and traces in PostHog | 14 days |
| Analytics events, including approximate location after activation | Deleted on the retention schedule of Scope's PostHog project |
| Browser IP addresses sent for planned location enrichment | Processed temporarily by PostHog to derive location; discarded from stored analytics events |
Deleting your account
You can delete your account from your account page. Scope then deletes your account data, CLI sessions and the repositories you own. Deleted data leaves backups within 42 days.
If you own a repository that other people are members of, delete it before deleting your account. Work you contributed to other people's repositories, such as requests and discussion replies, stays in those repositories and shows "Deleted user".
Git history is different. Commit author names and email addresses are part of each commit, so they remain in other people's repositories and in any clones made before deletion. Scope cannot remove them from copies it doesn't control.
Your rights
Depending on where you live, you can ask to access, correct, delete or export your personal data, object to or restrict its processing, and withdraw consent where processing relies on it. Email hello@scopevcs.com from the address on your account and Scope will respond within 30 days. You can also export your repositories at any time by cloning them.
California residents have the right to know, delete and correct personal information, and to opt out of its sale or sharing. Scope does not sell or share personal information. Scope will not discriminate against you for exercising these rights.
If you are in the EU or UK and believe Scope has mishandled your data, you can complain to your local data protection authority.
Children
Scope is not for children under 13. You must be at least 13, or older where your country's law requires, to use it. If Scope learns that it holds an account for a child under 13, the account is deleted.
Security
Connections to Scope use TLS. Session tokens are stored hashed, and backups are encrypted. To report a security problem, see the security policy.
Changes
When this policy changes, the effective date above changes. For significant changes, Scope will notify account holders by email or in the product before the change takes effect.