Who we are
RepoScape is provided by Edge Marketing And Design, LLC, 1301 11th Avenue, Suite B, Helena, Montana 59601. Questions and privacy requests may be submitted through the support form.
Local processing
RepoScape reads local Codex task records and user-approved project folders to organize projects, inspect Git repositories, show recent tasks and commits, render Markdown, and calculate personal token analytics. Tags, cached project metadata, Team credentials, and token indexes are stored in the Mac user's Application Support directory.
The free Local features do not require a RepoScape account and do not send this local project index to our Team server.
Optional mobile companion
When you pair your iPhone or iPad, the Mac and mobile app exchange project metadata, selected conversation history, usage information and chat requests through an encrypted connection relayed by Cloudflare. Pairing credentials authorize the connection; the Mac approves a new device. The relay handles encrypted message payloads and connection metadata, including pairing identifiers, access status and connection times. It is separate from Team sharing.
The mobile app keeps pairing credentials in protected local storage and may cache received project and conversation data on your device. Disconnect a device in the Mac’s Paired Devices panel to revoke its access; use Forget This Mac on the mobile device to remove its saved pairing. Personal mobile billing is managed through Stripe on the Mac, and eligible Team members receive access through their Team membership. Provider requests run through your Mac and your existing Codex or Claude account.
Optional GitHub connection
You can connect GitHub to find repositories available to your account and clone them into a folder you choose. RepoScape requests repository access, which GitHub's OAuth permissions also allow for writing; RepoScape uses this connection to list and clone repositories, not to change repositories on GitHub. Organization approval may be required.
GitHub sign-in, token renewal, and revocation pass through our Cloudflare-hosted service. The service does not persist your GitHub access or refresh tokens. The app stores those tokens locally with owner-only file permissions. Repository lists and cloned files travel directly between GitHub and your Mac. You can disconnect in RepoScape or revoke access in GitHub Settings.
Optional Team sharing
When Team features are enabled, RepoScape sends only the information needed to match shared repositories and coordinate work. This may include:
- Team and display names, device identifiers, app version, and membership role.
- Team-specific repository fingerprints and, for repositories shared by at least two devices, repository name, branch, commit identifier, and activity time.
- Changed relative file paths, Git change counts, processing state, short work summaries, and recent commit titles.
- Project-level lifetime and weekly token totals, weekly contribution percentage, and estimated plan value.
Codex conversations, responses, complete task history, thread identifiers, raw source code, and raw Git diffs are not sent to the RepoScape Team server.
Codex-generated summaries
To create a short teammate-safe work summary, the app may run the Codex command included with the Codex or ChatGPT desktop app. It supplies a bounded portion of the latest request, changed-file information, Git diff evidence, and selected untracked text. This processing occurs through the user's existing Codex/OpenAI installation and account. Only the resulting short summary is sent to the RepoScape Team server. OpenAI's handling of that request is governed by the user's agreement and privacy settings with OpenAI.
Billing
Stripe processes Team subscription checkout, payment methods, invoices, and cancellation. We receive Stripe customer and subscription identifiers, plan selection, subscription status, billing interval, and renewal date. RepoScape does not receive or store full payment-card numbers.
Infrastructure and security
Cloudflare hosts the Team API, encrypted Team records, operational logs, and application downloads. Connections use HTTPS or secure WebSockets. Team credentials are random, revocable, and stored locally with owner-only file permissions. Cloudflare automatically encrypts Durable Object data at rest and in transit within its network.
We maintain aggregate counts of successful RepoScape download requests to understand product adoption. These counts are not linked to a person, device, account, or Team.
RepoScape automatically reports selected operational failures and connection recoveries so we can repair Team, GitHub, update, and project-loading problems. Current apps send a random installation identifier, app and macOS versions, fixed event codes, and, for recoveries, the observed interruption duration. They do not send free-form error messages or Team display names. The diagnostic service also accepts older apps' reports but discards their free-form messages, names, and macOS details rather than storing them. Diagnostic storage contains fixed issue groups, app versions, counts, timestamps, recovery durations, and short-lived pseudonymous installation identifiers, not conversations or source code.
No internet service is completely secure. Team members are responsible for protecting Team Keys and securing their Macs.
Local Claude integration
Claude Code sessions are discovered on your Mac and grouped by folder. Local usage records provide token analytics. RepoScape installs lifecycle hooks and a status-line wrapper while preserving existing Claude settings and keeping a backup. These local records track activity and completion without storing prompts or tool inputs. Reported account balances may be requested through the installed Claude tools; your provider account terms apply. Claude conversations are not sent to teammates through Team sharing.
Retention and deletion
- Recent Team commit events are retained for approximately 24 hours.
- Last-reported project activity remains until the device reports a newer state, the installation is removed, or the Team is deleted.
- Unpaid checkout directories expire automatically, and abandoned unpaid Team-room data is scheduled for deletion after checkout expiration.
- Billing records are retained by Stripe according to legal, tax, fraud-prevention, and account requirements.
- Diagnostic installation details cover the last 7 UTC calendar days; daily grouped totals cover the last 30 UTC calendar days. Scheduled daily cleanup removes expired records. Storage and rate limits may reduce diagnostic coverage; cleanup delays can temporarily extend retention.
- A sole Team owner can delete the Team from the app after other members have left or been removed.
Website data
When you request an app download, we collect your name and email to record the request. Download requests are separate from aggregate download counts. You can request deletion through our support form.
We may enable optional analytics, advertising, remarketing, session-insight, or error-monitoring technologies to understand website use, improve RepoScape, measure campaigns, and reach interested audiences. Depending on the services enabled, providers may include Google Analytics or Google Ads, Meta Pixel, AdRoll, Microsoft Clarity, and Sentry. These providers may process information such as IP address, device and browser details, pages viewed, referring URLs, interactions, campaign information, and provider identifiers according to their own privacy terms.
When optional analytics or marketing tags require a choice, the website displays privacy controls before loading them and lets you accept, decline, or select categories. A first-party consent cookie records those choices for up to six months. You can reset the choice by clearing this website's cookies. Essential hosting and security logs may still process standard request information such as IP address, browser type, requested URL, and timestamps regardless of optional tracking choices.
When you submit the support form, we collect the name, email address, subject, and message you enter to review and respond to your request. We do not ask you to submit Team Keys, credentials, source code, or other secrets.
Your choices
You can use Local features without enabling Team sharing. Team owners and admins can remove installations, and members can leave a Team. You may contact us to request access, correction, or deletion of information associated with the Team service, subject to identity verification and legal retention requirements.
Changes
We may update this policy as RepoScape changes. The effective date above will be revised when material changes are published.