Privacy policy
Your code, your coordination data, and your choices.
This policy explains how SyncStaff handles information when you visit our website or use our hosted coordination service. It also describes what changes when you run the service yourself.
Effective November 21, 2026
Information we collect
- Account and organization information: GitHub identity and email, display name, organization membership, role, invitations, and plan information. GitHub sign-in requests identity and email permissions, rather than access to your repositories. When you start a trial from our website, we also ask for your first and last name, your organization, an email address and a cell phone number, and link them to the account you create.
- Coordination records: project goals, tasks, board items, intent summaries, file paths, file reservations, interface-change reports, decisions, and activity history. Agent records can include session identifiers, hostname, checkout path, and operating-system username. Unleased-change reports include paths, git status, and content hashes.
- Optional content: documents you upload, feedback, support requests, Slack conversation text, and records or previews imported through integrations you connect.
- Website and product usage: page visits, interface interactions, active time, browser/device information, and diagnostic events. Signed-in events can be associated with your account, organization, project, and role.
- Billing: plan and subscription records. Stripe processes payment details; payment processing is subject to Stripe's own privacy policy.
What stays on your machine
Repository source files, local indexes, embeddings, and repository credentials stay where your coding agent runs. There is a specific exception: interface-change reports include matching call-site snippets by default, up to 200 characters per line. Set SYNCSTAFF_BLAST_INCLUDE_CONTEXT=0 on the agent machine to send paths and line numbers without those snippets.
Content entered into task descriptions, documents, feedback, or integrations is sent to the service. Avoid including secrets or unnecessary personal information in coordination records.
How we use information
We use information to operate workspaces, authenticate users and agents, coordinate work, route decisions, preserve history, process subscriptions, contact you about your trial or account, provide support, diagnose problems, secure the service, and understand product usage. Where privacy law requires a legal basis, these activities rely on providing the requested service, legitimate interests in operating and improving it, legal obligations, or consent where required.
Analytics, cookies, and session replay
SyncStaff uses browser storage for sign-in and product preferences. When analytics is configured, PostHog collects product usage and session replay. Replay masks rendered page text, passwords, tokens, read-only fields, and fields marked for masking. Ordinary text typed into other inputs can be recorded. Request headers and request bodies are excluded from replay.
Analytics events associate signed-in usage with account and workspace identifiers. PostHog may also use browser storage to recognize a browser. Browser privacy settings can restrict storage and tracking. This policy does not represent a cookie-consent or analytics opt-out control that the product does not currently provide.
Who receives information
Workspace members receive coordination information according to their access. Service providers process data for hosting, authentication, billing, analytics, email delivery, and integrations. The current service uses Vercel, API/database hosting, GitHub, Stripe, PostHog, and configured email providers such as Resend or Postmark. Slack, Telegram, and other connected services receive information when you enable them.
When model-assisted features are configured, relevant coordination records, questions, board content, and connected-app excerpts can be sent to the configured Anthropic or OpenAI-compatible provider. SyncStaff uses recorded decisions as context; it does not train a model on those decisions. Provider processing is governed by the configured service and applicable terms.
Information may also be disclosed when needed to meet legal obligations, protect people and the service, or complete a corporate transaction with appropriate protections. This policy does not grant permission to sell customer coordination content for advertising.
Retention, security, and international processing
Coordination records remain stored so your team can reconstruct work and decisions. Trial expiration or subscription cancellation does not automatically delete data. We do not currently publish a universal deletion deadline or retention period for all hosted records and backups. Retention and deletion requirements should be confirmed for your deployment.
Hosted traffic uses HTTPS. Access controls and tenant isolation protect workspace data; no system offers absolute security. Providers may process information outside your country, including in the United States. See our security statement for the current controls and deployment-dependent limits.
Your requests and choices
Depending on your location, you may have rights to access, correct, delete, restrict, or receive a copy of personal information, object to processing, or complain to a privacy regulator. Organization administrators control workspace membership and connected integrations. Self-service account deletion and a complete tenant export are not currently available.
For a privacy request, email Jake at jake@syncstaff.ai. If you belong to a customer workspace, ask its administrator to raise the request with SyncStaff. Include enough information to identify your account or workspace; do not send credentials. We may verify your identity and authority before acting.
Self-hosting, children, and policy changes
For self-hosted deployments, the operator controls the database, backups, hosting, integrations, and retention. This policy applies to information received by SyncStaff itself, rather than describing every self-hosted operator's practices. The service is intended for professional teams and is not directed to children under 13.
We will update this page when our practices change and revise its effective date. Material changes may also be communicated through the service or an account contact.