Data classification
Customer, end-customer, recipe, financial, credential and operational data are treated according to sensitivity and purpose.
Security & Trust
Sensitive restaurant data deserves deliberate protection.
SousFounder is being designed to handle operational information responsibly—from customer and recipe information to financial records and connected-account grants.
Our approach
NeuraConnect applies risk-based technical and organizational safeguards designed to protect the confidentiality, integrity and availability of Customer Data. Controls are selected according to the sensitivity of the information, the connected service and the operational risk.
Tenant boundaries
Authorization and data access are designed to be tenant-scoped, with role-based permissions and explicit resource selection.
Protected credentials
OAuth grants and connector credentials are encrypted before storage and are not returned to the browser after connection.
Least-privilege integrations
We request only the provider scopes needed for the enabled function and prioritize read-only access for initial integrations.
Transport protection
Production web traffic is required to use HTTPS. Provider webhooks must be authenticated and fail closed when verification is unavailable.
Auditability
Connector runs, approvals and material system actions are designed to retain attributable status and failure information.
Secure development
Changes are reviewed through automated tests, dependency controls, environment separation and risk-based deployment verification.
Incident readiness
We maintain an incident-response process and will notify affected customers when required by law or contract.
AI processing
Zero Data Retention is a release gate.
Production Customer Data may be sent to an AI model provider only through an approved enterprise or API arrangement configured for Zero Data Retention. Providers may not use that data to train their models. SousFounder must still retain limited information within its own service when needed to provide requested features, maintain business records, secure the service or meet legal obligations.
External connections
The account owner remains in control.
Where supported, restaurant owners authorize their own provider accounts through OAuth or an approved app-install flow. A connection is not represented as healthy until authorization, resource selection and a basic provider call succeed. External changes should not be represented as executed without provider confirmation.
Customer transparency
Understand every external data relationship.
Authorized customers receive provider-specific disclosures before connecting an external account. The authenticated Trust Centre maintains current subprocessor details, Connected Service data flows, provider policy links and versioned legal records for the workspace.
Report a security concern
Please do not include passwords, access tokens or sensitive Customer Data in your initial message. We will provide a secure channel when needed.
Contact securityAlso review our Privacy Policy and Data Deletion instructions.