PRIVATE HOUSEHOLD RECIPE PLANNER · UPDATED 18 OCTOBER 2026

Privacy policy

Dinner Garden at dinner.lazytitan.cc is a privately operated recipe collection, meal planner, and grocery tool intended for the operator and people personally known to them. This page explains the information handled by this installation.

Who operates the service and how to contact them

The service is operated by the individual who maintains dinner.lazytitan.cc and invited you to use Dinner Garden. For questions, access requests, corrections, exports, or deletion requests, contact that person directly using your existing communication with them. Household administrators can help identify the operator. No public contact email has been designated. If you do not know the operator, do not submit personal information or connect your Google account.

Information the app handles

• Google account information: your Google account identifier, verified email address, display name, and profile-picture URL.
• App content: recipe titles, ingredients, cooking steps, source links, cooking times, servings, categories, a food photo if provided, planned meals and activities, groceries, household membership, invitations, and preferences.
• Authentication information: a server session identifier, a request-verification token, and a Google refresh credential so the app can maintain the Drive connection. Google handles your Google password; Dinner Garden does not receive or store it.
• Technical information: the server, reverse proxy, browser, and service providers necessarily handle connection information. Access logs may contain IP addresses, request URLs, timestamps, response codes, and browser information, depending on the operator’s server settings.

How Google data is used

Your Google identity is used to sign you in, show your profile, identify the account invited to a household, and authorize access to your household data. Your email address is used to match invitations. Google account data is used only to provide the app’s user-facing features. It is not sold, used for advertising, or sent to an AI model for training.

Dinner Garden requests the openid, email, and profile permissions and the Google Drive drive.file permission. The implemented Drive integration creates and maintains recipe files in a Dinner Garden folder in your own Drive. It does not scan or import your unrelated Drive files. The app can update its recipe copies and move them into Drive Trash when their recipes are deleted in the app. Access is limited by the permissions you grant to Google.

Where information is stored

Signed-in account information, household content, preferences, invitation records, sessions, and synchronization jobs are stored on the operator’s server. Recipe copies, including their food photos, are also stored in each connected member’s own Google Drive. Meal plans and groceries remain on the app server; the automatic Drive copy contains recipes, not a complete account backup.

Google refresh credentials are encrypted in the server database using a separately configured key. The server database’s recipe and household content is not encrypted by the application at the field level. The operator controls the host, its access permissions, logs, and backups. Authorized household members can see shared household content, and the operator has technical administration access; this is not end-to-end encryption.

In device mode, recipes, photos, plans, and groceries are saved in your browser rather than synchronized to an account. The browser also stores personal theme preferences and caches app interface files. Signed-in sessions use an essential HttpOnly cookie. No advertising or analytics service is intentionally integrated into the app.

Sharing and external services

• Your household: joined members can view and edit the shared recipes, planner, and groceries. Member names and email addresses are shown within the household. A recipient must sign in with the invited Google account and accept before joining.
• Google: Google handles sign-in, consent, profile-image hosting, and Drive storage under its own policies. Your Drive copies belong to your account.
• Recipe websites: when you import a URL, the server contacts that website and the selected photo host to download recipe data. Those services can receive the server’s connection information.
• Listonic: only after you choose to export ingredients does the app load Listonic’s button and pass the selected ingredient text and any preferred list name to Listonic. Listonic manages its own login, destination selection, storage, and cookies. Dinner Garden does not obtain your Listonic password or verify that Listonic is using the same Google account.
• Invitation email, when configured: an email service can receive the recipient address, inviter identity, household name, and invitation message. Without email-service configuration, invitations appear inside the app only; no invitation email is sent.

The Android APK opens the same website using the phone’s browser engine. It does not implement an independent Google credential store or collect additional native-device information.

Retention and deletion

Content is retained while the operator keeps this installation and its records. There is no automatic account-erasure or fixed backup/log-retention schedule in this version. Ask the operator to remove your server-side account data, access credentials, membership, logs where applicable, or backups where feasible. Signing out ends the current session; it does not erase your account or revoke Google consent.

Deleting a recipe queues its app-created Drive copies for current household members to be moved into Google Drive Trash. This occurs during synchronization and may be delayed or fail while Google access is unavailable. Copies still used by another joined household and copies held by former members are retained. Older app versions did not queue Drive deletion, so earlier leftover copies require manual removal. Independently downloaded, exported, or backed-up copies are not remotely erased. Google’s own Trash retention rules apply.

You can delete your own Drive copies in Google Drive, clear local browser data, export a backup in Settings, or revoke the app’s access from Google account connections. Revoking Google access prevents future authorized Google operations but does not automatically erase existing server or Drive data.

Your choices and changes to this policy

Connecting Google and exporting to Listonic are optional choices. The person operating this installation can assist with reviewing, exporting, correcting, or deleting your information. Do not upload information you do not want household members or the operator to access. If the app’s data practices change, this page should be updated with a new revision date before the changed practices are introduced.