Security
How StormKeep handles access, delivery workflows, data handoff, and responsible security communication.
Security topics at a glance
- Scoped delivery projects and agreed access
- Customer-controlled destinations and handoff notes
- Operational safeguards and least-necessary access
- Responsible security communication
- Where to contact the team
Scoped delivery by project
StormKeep works on scoped delivery projects. Access methods, source lists, and destinations are agreed per engagement so the handoff stays practical and predictable.
Access and handoff
- Customer-provided source lists and destinations are handled according to project scope.
- No public upload portal or self-serve credential collection is implied on this page.
- Delivery methods are aligned before work begins.
Delivery and storage
- Delivery is typically handed off to customer-controlled cloud storage or an agreed destination.
- Outputs may include files, metadata, manifests, and transcripts/captions where available.
- Retention and storage details depend on the engagement.
Least necessary access, documented handoff
Project-specific access
Access is limited to what the engagement needs, and the workflow is scoped around the agreed delivery outcome.
Handoff documentation
Delivery notes, manifests, and transfer details are kept practical so teams can review what landed and where it was sent.
No formal claims by default
This page does not claim certification, legal guarantees, or formal compliance commitments unless they are explicitly documented elsewhere.
Questions or concerns?
For security questions, contact [email protected]. This page is not a bug bounty program unless one is explicitly agreed for a specific engagement.
Talk through the delivery scope before you build it in-house
A short walkthrough usually clarifies the source list, the output package, and whether managed delivery is the better operating model.