Local-first by design

Many web apps send every keystroke to a server. DailyLogic was built differently: the tools you use for budgeting, cooking, and shopping are designed to run in your browser.

That architectural choice is not an afterthought — it is central to how we protect your personal information.

When you open a DailyLogic tool, the calculation logic downloads to your browser as part of the page. As you enter amounts, servings, or prices, JavaScript processes them on your device and displays results immediately.

Because this processing happens client-side, DailyLogic does not need a database of your budgets, recipes, or shopping lists to function.

Like any website, your browser makes network requests to load pages, styles, and scripts from our hosting provider. Those requests may include standard technical metadata (such as IP address and user agent) required to deliver content.

We do not transmit the numbers and personal inputs you enter into our calculators to DailyLogic servers for processing or storage.

If you email us, only the information you include in your message is shared with us.

Some features — such as remembering your language, recent calculations, or favorite tools — store small amounts of data in your browser's local storage.

This data remains on your device until you clear it. It is not synced to our servers.

You can remove it at any time through your browser's privacy or site-data settings.

DailyLogic is served over HTTPS, which encrypts data in transit between your browser and our hosting infrastructure.

We keep our software dependencies updated and follow hosting best practices, but no online service can guarantee absolute security. We design the product to limit sensitive data exposure in the first place.

Use DailyLogic on a device and browser you trust, especially when entering financial information.

Clear site data when using a shared computer.

Remember that screenshots or exports you create are under your control — share them only with people you trust.

For legal details, see our Privacy Policy. To reach the team directly, visit the Contact page.