Docs / Security

ShipGlance is in early access. These pages describe the hosted product; sign-in opens when early access does. Join early access →

Security

How the hosted product protects your GitHub data. The privacy policy covers the data side; setup walkthroughs are in the guides.

Is GitHub access read-only?

Yes. The ShipGlance GitHub App requests read-only permissions: Actions, repository metadata and contents, and commit statuses. It cannot push, merge, open pull requests, or change anything in your repositories.

Repository access uses short-lived GitHub installation tokens, minted per installation. The App's private key never leaves our control plane.

What data does ShipGlance store?

• No source code contents. The board is built from workflow run and deployment metadata.
• No card numbers. Payment is handled by Stripe.
• No third-party trackers, fonts, or ad scripts. Analytics are first-party only.

Is my workspace isolated from other customers?

Yes. Every workspace runs as its own isolated instance with its own database file and its own subdomain. There is no shared database across customers, so no query can span workspaces.

How is sign-in handled?

Sign-in is GitHub OAuth. There are no passwords to store or steal. Stored credentials are encrypted at rest, and customer configuration never contains secrets (see Configuration).

Are share links safe to send outside my team?

Share links are redacted and expiring by design. They carry a stripped-down view for people outside your workspace, not a session into your board. Public status embeds (Team plan, see pricing) expose the same minimal surface.

What happens when I delete a workspace?

Your data is deleted within 30 days of workspace deletion, backups included. See Billing & plans for the full deletion rules.

How do I report a security issue?

Email hello@shipglance.com. Reports go directly to the people who wrote the code, and we respond promptly. If we discover a breach affecting your data, we notify affected account holders by email.