Security
This page says where customer data lives, how it is protected, who can reach it and what we do not claim. It is written for the person at a customer who has to approve a new vendor, and it describes only what is in place or dated.
What we hold, and what we don't
| WanderingWU | A Kitchen Society | |
|---|---|---|
| Purpose | Theoretical food cost, purchasing and sales for multi-kitchen operators | Recipes, costing and allergen review for kitchens and home cooks |
| Customer data | Distributor invoices and order guides, POS item-sales exports, daily sales totals, menus, recipe costs | Recipes, ingredient price lists, invoice-derived item prices, recipe photos |
| Personal data | Name and work email for sign-in; role assignments | Name and email for sign-in; role and organization membership |
| Not held | Protected health information, payment card numbers, bank details, government identifiers, patient or student records | |
| Who owns it | The customer. We process it to produce their reports and delete it when they leave | |
Classification: business-confidential (invoices, sales, recipes) plus basic contact information. Both are treated as confidential.
Hosting and data protection
Both applications run in the United States. Production is moving from managed hosting (SmarterASP.NET) to Microsoft Azure in November 2026; this page is updated the day the move completes.
| Control | Today | From the Azure move (November 2026) |
|---|---|---|
| Region | United States | Azure East US 2; data does not leave the US |
| In transit | TLS 1.2+, HTTPS only | Same, plus HSTS |
| At rest | SQL Server on managed hosting | Azure SQL Transparent Data Encryption and encrypted storage |
| Backups | Daily host backups | Point-in-time restore, 14 days; weekly long-term retention, 12 months; restore tested quarterly |
| Isolation | One database and one web application per product; customer data separated by account and organization inside each | |
| Files (invoice PDFs, photos) | Application storage on the host | Azure Blob Storage, private containers, encrypted at rest |
| Infrastructure certifications | Provider's | Inherited from Microsoft Azure (SOC 1/2/3, ISO 27001) |
Subprocessors
| Subprocessor | Used for | Data it sees |
|---|---|---|
| Microsoft Azure | Hosting, database, storage, logs | All customer data, encrypted |
| Microsoft 365 | Business email; invoices customers forward to an ingestion address | Emails sent to us, with attachments |
| Kroger Developer API | Retail shelf prices for home-cook costing in A Kitchen Society | Ingredient search terms and a store location; no customer or account data |
No other third party receives customer data. No analytics or advertising trackers run on signed-in pages.
Access
- Accounts. Email and password (ASP.NET Core Identity; passwords are hashed, never stored). Accounts are created by invitation: a customer administrator invites their own staff. There is no open sign-up.
- Roles. WanderingWU: site, organization and account-level roles that limit what each person can read or file, checked on every request. A Kitchen Society: organization roles plus per-user permissions an administrator controls.
- Two-factor sign-in. WanderingWU: a verification code emailed on sign-in from a new device, required for administrator roles. A Kitchen Society: authenticator app (time-based codes) with recovery codes, available to every account.
- Single sign-on. Not offered yet; Microsoft Entra ID / SAML sign-in is planned for the first enterprise customer that requires it.
- Platform administration. Hosting and cloud consoles behind multi-factor authentication, limited to named administrators; no shared accounts. Secrets live in hosting configuration, never in source code.
- Support access. We open a customer's data only to resolve a request they made, and say so in the reply.
Operations
| Monitoring | Application logging with 90-day retention; after the Azure move, Application Insights with availability tests on both sites |
|---|---|
| Availability | Platform provider SLA 99.9% today, 99.95% on Azure App Service. No contractual uptime commitment at this stage; planned maintenance is announced by email |
| Changes | Developed and tested against a copy of production data before publishing; database changes run as reviewed scripts; staging slot after the move |
| Incidents | Security contact admin@wanderingwu.com. Affected customers notified within 72 hours of a confirmed incident involving their data: what happened, what was affected, what changed |
| Retention and deletion | Data kept for the life of the subscription; exported on request and deleted within 30 days of termination or request; backups expire on their schedule |
| Portability | Invoices, sales, recipes and cost reports export to CSV or PDF from the application at any time |
| Vulnerabilities | Framework and dependency updates monthly and on advisory; reports to the security contact acknowledged within 2 business days |
| Continuity | Code in a private repository; a database is restorable from backup to a new host within one business day |
What we do not claim
WanderingWU LLC holds no SOC 2 report or HIPAA attestation of its own and does not process the data that would require one. Infrastructure certifications are Microsoft Azure's, inherited for hosting, database and storage. We are an early-stage vendor; everything above is in place or carries a date, and nothing is described that is not.
Questionnaires (HECVAT, SIG, or your own form) are welcome: send them to admin@wanderingwu.com. Our Privacy Policy covers personal information.