Start Free
×
FoodDroneShampooScribe

Quick Answer: KitchenWeather encrypts your records in transit and at rest, does not sell your data, does not share records with health authorities, and treats your data as yours. You can export your complete Trust Memory at any time.

TS行政書士
Expert-supervised by Takayuki SawaiGyoseishoshi — Licensed Administrative Professional, Japan

KitchenWeather Data Privacy and Security: Your Records, Your Control

When you use a digital system to store your kitchen's safety records, the question of where that data goes and who can see it matters. This article explains exactly what KitchenWeather does with your data — and, as importantly, what it does not do.

Your Data Is Yours

The most important principle of KitchenWeather's data approach: the records you create belong to you. Your morning check completions, temperature logs, findings, and Trust Memory history are your operational records. KitchenWeather stores them on your behalf — it does not claim ownership of them or use them for purposes beyond providing the service to you.

Encryption

Data is encrypted in two states:

In Transit

All data transmitted between your device and KitchenWeather's servers uses TLS encryption (HTTPS). When you submit a morning check, enter temperature readings, or access your dashboard, the connection is encrypted. Intercepting this data in transit would require breaking standard transport layer security.

At Rest

Data stored in KitchenWeather's infrastructure is encrypted at rest. Your records are not stored as readable plain text in the database. The encryption applies to all stored data, not just passwords.

Access Control

KitchenWeather uses Supabase as its database infrastructure. Row-level security (RLS) policies govern data access — meaning the system is designed so that queries can only return data belonging to the authenticated user. One kitchen account cannot access another kitchen's records, even if both are in the same database.

KitchenWeather's team does not routinely access individual kitchen records. Support requests may require examining account-level information, but access to operational records requires active intervention, not passive visibility.

What KitchenWeather Does Not Do

To be direct:

Third-Party Services

KitchenWeather uses a small number of third-party services to deliver its functionality:

These services are chosen for their security standards and reliability. The data shared with each is limited to what is necessary for their specific function.

GDPR Awareness

KitchenWeather was designed with data minimization and user control principles consistent with GDPR, even for users outside the European Union. This means:

What You Control

You can:

Frequently Asked Questions

If DOHMH requests my records, does KitchenWeather share them?

KitchenWeather does not proactively share records with DOHMH. Like any service, we would need to comply with a valid legal order, but routine inspection record requests are yours to fulfill or not.

Where are my records stored?

KitchenWeather uses Supabase cloud infrastructure. Data is stored in encrypted form in secure cloud environments.

What happens to my data if KitchenWeather shuts down?

In the event of service discontinuation, we would provide advance notice and data export capabilities before shutdown.

Can I use KitchenWeather's data to train my own systems?

Your records are yours to use as you see fit, including exporting them for your own analysis or systems.

Sources

🟢 SAFE TODAY

Your kitchen is ready to serve. Start your morning shield.

Start Free — 0 setup fees

Founding Member pricing forever. Cancel anytime.