← Back to specgit

specgit trust center

Security and data privacy

specgit is built around a simple promise: your documents stay in GitHub. We provide the editor, comments, realtime collaboration, and review workflow without keeping a separate long-term copy of your work.

Does specgit store my documents?

No. specgit reads documents from GitHub when you open them and saves edits back to GitHub through commits, branches, pull requests, and comments. Your repository remains the source of truth. Where docs are held is also a product question, not just a security one — we compare the approaches in Notion vs GitHub for product specs.

What happens during live collaboration?

Live collaboration uses temporary realtime state so multiple people can edit together. That state is deleted after publish or direct commit, and inactive rooms are swept after up to 7 days.

Does specgit track users?

No. specgit does not use product analytics, ad tracking, or third-party tracking scripts. Operational logs are used to keep the service reliable and are retained for up to 30 days.

How does GitHub sign-in work?

You sign in through GitHub directly, via the specgit GitHub App — there is no separate password and specgit never sees your GitHub credentials. The App uses fine-grained, least-privilege permissions and short-lived tokens, and it can only reach the repositories you (or your organization's admin) explicitly grant when installing it. GitHub access is used only to perform actions you request, such as reading files, saving edits, creating review branches, opening pull requests, and posting comments.

What access does the specgit GitHub App have?

Only fine-grained permissions on the repositories granted to the installation: contents (read/write), pull requests (read/write), and your public profile. Organization members who aren't admins can request the installation in one click, and an admin approves it once. Access is revocable at any time from GitHub's settings. Approving for an organization? There's a one-page brief for IT admins covering each permission and why it's needed.

specgit uses GitHub access to

  • list repositories you can access;
  • read Markdown and HTML files you open;
  • save edits as commits;
  • create review branches and pull requests;
  • post review comments; and
  • merge or publish when you choose to publish.

specgit's access cannot

  • change repository settings;
  • manage deploy keys;
  • manage webhooks through your account;
  • manage collaborators or invitations;
  • edit wikis; or
  • reach repositories outside the installation's grant — and specgit never copies your documents into a database.

How do the AI features handle my documents?

The AI features (the in-editor AI assistant, AI review comments, comment triage, and voice) are optional and only run when you invoke them. When you explicitly start an AI action, the document text (and its review comments, for review and triage) is sent to our AI model provider to generate the response; voice sessions stream conversation audio for the duration of the session. specgit keeps none of that content — only usage metadata (token counts, model, cost, and timestamps) that powers metering, spending limits, and your usage dashboard, plus anonymous accepted/dismissed proposal totals. The one exception is explicit consent: if you tick "share this conversation" when rating an AI response, that transcript is kept for up to 90 days and used only to diagnose and improve the AI. Nothing is sent for AI processing in the background or without an explicit request, your content is not used to train models, and every AI-proposed change requires your approval in the editor before it is applied or posted.

Our AI model provider is xAI. Per xAI's API terms, API inputs and outputs are not used to train xAI's models, and API request/response data is retained by xAI for up to 30 days for abuse monitoring, then automatically deleted.

What data does specgit retain?

  • Documents and comments remain in your GitHub repository.
  • Temporary realtime editing state is deleted after publish/direct commit or inactivity.
  • GitHub access tokens are stored server-side for active sessions only, encrypted at rest (AES-256-GCM), and deleted on sign-out or after 30 days of inactivity.
  • Account preferences (theme, editor layout, AI auto-approve settings) and your terms-of-use acceptance are stored with your GitHub identity so they follow you across devices — settings only, never document content. AI chat history stays on your device.
  • Operational logs are retained for up to 30 days.
  • AI usage records are metadata only — token counts, model, cost, and timestamps for metering and the usage dashboard; AI quality counters are anonymous daily approved/dismissed proposal totals with no account, document, or content attached.
  • AI feedback — ratings, optional notes, and conversation transcripts you explicitly chose to share — is retained for up to 90 days, then deleted.

Where can I read the full policy?

Read the full Privacy Policy and Terms of Use, or contact support.