Security And Data
What ShipFoundry stores, how integration data is bounded, and what security claims are intentionally avoided.
ShipFoundry stores the product, stack, evidence, brief, integration, billing, and outcome data needed to explain recommendations and support agent handoffs.
When To Use This
Use this page when evaluating whether ShipFoundry is appropriate for a product, repository, account, or agent workflow.
This page is not a legal policy. It is the operational trust boundary for the launch product.
How It Works
ShipFoundry separates public source intelligence from private account and project data.
Public source intelligence can be reused across accounts. Account and project records are private to the account and protected by membership checks and database access controls.
What ShipFoundry Stores
| Data Type | Purpose |
|---|---|
| Account and user records | Membership, access, and preferences. |
| Audit events | Action history and traceability. |
| Billing records | Subscription state and entitlements. |
| Product context | Product summary, goals, constraints, important repo areas, external tools, and tracked stack. |
| Global Intelligence | Public update summaries, tags, match signals, and source evidence. |
| Repo evidence | Focused read-only evidence tied to selected repositories and specific updates. |
| Briefs and task packets | Generated investigation and handoff artifacts. |
| Outcomes | User or agent decisions that improve future matching. |
| Integration metadata | Connection state and selected configuration for GitHub, Linear, MCP, billing, email, analytics, and observability. |
Step-By-Step
- Add only the product context needed for useful matching.
- Choose optional integrations deliberately.
- Select GitHub repositories instead of granting broad repo scope.
- Review trust states before acting on recommendations.
- Keep provider credentials out of prompts and generated task packets.
- Record outcomes so uncertain or wrong recommendations improve over time.
What ShipFoundry Does
- Keeps feature code behind internal service facades.
- Uses account membership checks for account-scoped product data.
- Uses encrypted storage for sensitive integration tokens where implemented.
- Keeps MCP OAuth and fallback token flows scoped.
- Treats GitHub repo evidence as read-only and selected-repository first.
- Records Linear exports as explicit attempts tied to briefs.
What ShipFoundry Does Not Do
- It does not ask MCP clients to handle GitHub, Linear, OpenAI, Supabase, Stripe, or Resend provider tokens.
- It does not commit code or open PRs from GitHub repo evidence.
- It does not promise secret scanning unless that capability is explicitly implemented and documented later.
- It does not broadly mirror repositories by default.
- It does not use Linear as a broad source of truth for all project state.
Access Tokens
OAuth and token flows should keep raw credentials out of prompts and generated packets. MCP OAuth is preferred when supported. Manual MCP bearer tokens are an advanced fallback and should be stored in environment variables or a secret-backed local store that is not checked into source control, not pasted into chat.
Deletion Boundary
Subscription cancellation stays in Billing through Stripe Customer Portal and does not delete the account. Single-owner personal accounts can use Account settings to delete the account after cancellation is completed or scheduled. Deletion removes account-scoped product data through the local account cascade, deletes local integration credentials, anonymizes retained operational records, and hard-deletes the Supabase auth user after billing and local cleanup succeed. Team, multi-owner, admin, unverified-storage, or content-reassignment cases are blocked from self-serve deletion and require support review.
Troubleshooting
If a generated brief includes too much context, review the product profile and integration scope.
If repo evidence appears for the wrong repository, check selected repositories and project settings.
If an agent asks for provider credentials, stop and use the ShipFoundry MCP or integration flow instead.
Related Pages
- Read-only repo evidence: GitHub Repo Evidence
- Example artifact: Sample Engineering Spike
- Agent workflow: Agent Workflows
- MCP integration: MCP
- Linear export boundary: Linear
- Product CTA: Start 7-Day Trial
Was This Page Useful?
Send a short note if this page is unclear, overclaims a capability, or is missing the proof you expected.
Send Docs Feedback for Security And Data