Security
This page says where your recipes and price lists live, how they are protected, who can reach them and what we do not claim. It is written for the person 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
| Your data | Recipes and their versions, recipe photos, ingredient price lists (order guides you import, prices you type, Kroger shelf prices, and invoice prices when a kitchen is connected to WanderingWU), allergen and nutrition reviews |
|---|---|
| Personal data | Name and email for sign-in; role and organization membership. Invite requests: the name, email and organization the requester typed |
| Not held | Protected health information, payment card numbers, bank details, government identifiers, patient or student records |
| Who owns it | You, or your organization. We process it to cost your recipes and delete it when you leave |
Classification: business-confidential (recipes, prices) plus basic contact information. Both are treated as confidential. Home recipes are private to the person who wrote them unless they share them.
Hosting and data protection
A Kitchen Society runs 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 | Its own database and web application; data separated by organization, kitchen and person inside it | |
| Files (recipe photos, imported PDFs) | 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 and outside data
| Who | Used for | What it sees |
|---|---|---|
| SmarterASP.NET (Microsoft Azure after the move) | Hosting, database, file storage, email for sign-in and invitations | All customer data, and the emails we send |
| Kroger Developer API | Retail shelf prices for home-cook costing | Ingredient search terms and a store location; no customer or account data |
| Cloudflare Turnstile | Telling people from bots on the sign-up page (once public sign-up opens), with no puzzles | The visitor's browser and IP address while the sign-up page is open; no account data, and no cookies used for advertising |
| YouTube (Google), privacy-enhanced player | Playing the video on a story page that has one (youtube-nocookie.com) | The visitor's browser and IP address when the player loads; no account data |
| Google Fonts, cdnjs (Cloudflare), Quill CDN | The typefaces, icons and page scripts every page loads | The visitor's browser and IP address when a page loads; no account data |
| USDA FoodData Central, Open Food Facts | Nutrition and allergen facts for ingredients | Ingredient names and product codes we look up; no customer or account data |
No other third party receives customer data. No analytics or advertising trackers run on any page, signed in or not.
WanderingWU is a separate product of the same company. It connects to a kitchen only when that kitchen's administrator sets the connection up; then invoice prices flow in and recipe costs flow back. Without that connection nothing is shared, and A Kitchen Society works entirely on its own.
Access
- Accounts. Email and password (ASP.NET Core Identity; passwords are hashed, never stored). Accounts are created by invitation: an organization's administrator invites their own team, and home cooks request an invite. There is no open sign-up.
- Roles. Organization roles (Org Admin, Culinary, Head Chef and others) plus per-person permissions the administrator controls, checked on every request. Each kitchen's prices are visible only to that kitchen's members.
- Two-factor sign-in. 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 |
|---|---|
| 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 |
| Incidents | Security contact admin@akitchensociety.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 account; exported on request and deleted within 30 days of termination or request; backups expire on their schedule |
| Portability | Any recipe prints to PDF from the application at any time; a full export of recipes and price lists (CSV) is available on request |
| 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; the 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 the hosting provider'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.