Springbase Data Security & Privacy One-Pager

📚

Context-based access

Contexts organize approved knowledge sources such as docs, PDFs, URLs, meetings, live sources, and app data.^[4]

🔐

Encryption controls

Springbase security messaging includes AES-256-GCM encryption for sensitive data.^[12]

🧑‍⚖️

Privacy rights

Security messaging includes DSAR support, helping customers manage privacy requests.^[12]

🛡️

No model training

Customer data is used to provide the requested workspace experience — not to train AI models.

How data flows through Springbase

1. Add trusted sources

Teams upload or connect documents, PDFs, URLs, meetings, saved contexts, projects, and connected files into Springbase Contexts.^[4][9]

→

2. Retrieve only authorized context

Springbase retrieves from the relevant Context so answers are grounded in the customer’s selected knowledge base, not free-floating AI improv.^[3][4]

→

3. Produce client-ready output

Outputs can become reports, dashboards, diagrams, HTML pages, markdown docs, and other Canvas artifacts for review, reuse, and sharing.^[9]

How Contexts protect client knowledge

Contexts act as Springbase’s memory layer: knowledge bases that make AI responses grounded, specific, and organization-aware.^[4]

✓ Private collaboration: context owners can invite trusted contributors by email while keeping the context off public/community surfaces.^[8]
✓ Controlled visibility: context visibility supports private, unlisted, public, enterprise, or team settings.^[5]
✓ Source visibility controls: public/link contexts can control whether source documents are visible.^[5]
✓ Revocable access: owners can revoke collaborator access after an engagement ends.^[5]

Security & privacy controls

Springbase’s security posture is designed around access control, sensitive-data protection, and operational safeguards.

✓ Row-Level Security: included in Springbase’s security messaging for access isolation.^[12]
✓ AES-256-GCM encryption: used for sensitive data in Springbase’s security messaging.^[12]
✓ CSRF protection and rate limiting: included in security messaging to help protect platform endpoints.^[12]
✓ Audit and accountability: Springbase references audit-related security messaging for operational visibility.^[12]

🛡️

Zero training on customer data.

Springbase does not use customer documents, meetings, Contexts, prompts, or outputs to train AI models. Customer data is used to serve the customer’s requested workflow, ground responses, and generate outputs inside the customer’s workspace.