Privacy policy — La Babiole

This is a translation of the Korean original. Where they differ, the Korean original prevails.

1. What we collect

Account details — your nickname, your password (stored only as an irreversible hash) and, if you sign up, your email address.
Ledger — ledgers, accounts, categories, entries, memos, sharing settings and their change history. Stored on the server and shown according to each signed-in member's access to a ledger.
Kitchen — kitchens and their members, recipes (ingredients, steps, photos), stock (name, amount, where it is kept, use-by date), meal plans and what was eaten. A recipe you make public, and its photos, can be seen by anyone, signed in or not.
Photos — photos you upload for receipts, recipes or making a recipe. The screens and the AI features use only a converted copy with location and other metadata removed; the original is kept as it was. An original may contain where it was taken, or what a receipt shows, such as part of a card number, the shop or a name.
AI keys — API keys for AI providers (Anthropic, OpenAI, Google) that you register. They are encrypted with a server secret and only their last four characters are shown. Usage per key, per service and per member (tokens and jobs) is recorded too.
Email hashes — so that a request to delete original photos can be checked as yours, each time you sign up or change your email we keep an irreversible value (HMAC) made from the address and a server secret.
Game records — scores, when they were set, and the play data used to rank them. We also collect game completion dates, completion counts, achievements and the times they were earned.
Activity records — only for things you do yourself, such as signing up, logging in, submitting a record or posting: the time, the request path, the result, your IP address (IPv4 or IPv6) and browser information (User-Agent).
Notifications — when another user mentions you (@nickname), or comments on or likes your post, we record who did it, when and on which post, and show it to you as a notification. All of it comes from public posts. If you ask for deletion, notifications are kept as deleted too; a notification you have read is deleted automatically 180 days after you read it.
Contact messages — the type, name (optional), reply email (optional) and text you enter in the contact form, and the IP address it was sent from. If you are signed in, your account is recorded too.
Bot check — logging in, asking for a sign-up code, password reset or email change, sending a contact message and posting a record without an account use Cloudflare Turnstile to check you are a person. Cloudflare processes your IP address and browser information for this; this site only receives the result.
Cookies — an authentication cookie to keep you logged in, a cookie that remembers your language, and third-party cookies used to identify you for ads. The game visitor cookie (lb_game_visitor) binds an unsigned-in visitor’s game round to this browser to prevent another person from taking it over and limits the daily challenge to one result per day. It is signed, inaccessible to JavaScript, and retained for 30 days.

Simply viewing a page is not recorded, and secrets such as passwords and authentication tokens are never part of an activity record. What you type into the sales tax calculator is processed only in your browser. Ledger entries are stored on the server when you save them, and amounts and memos are not included in general activity logs.

2. Why we use it

To identify your account, keep you logged in and run the leaderboards
To block fake records and keep the service stable
IP addresses and activity records are used only to detect abuse, such as bots, multiple accounts or rigged rankings, and to establish the facts if a dispute arises.
To show ads and improve the service
Original photos are kept as training data for improving the AI features in future.

3. How long we keep it, and what happens when you leave

Accounts, ledgers, game records, posts, comments and notifications are soft-deleted when you ask: they are kept marked as deleted. Deleted data is excluded from normal viewing and use of the service but is not physically destroyed straight away. Activity records, including IP addresses, are deleted automatically 90 days after they are collected.

Before deleting your account you must delete any ledger you own or hand it to someone else. When you leave, your access to ledgers is withdrawn, your account, posts and records are soft-deleted, and remaining activity records are pseudonymised: the account identifier is replaced with an irreversible random value and your nickname and IP address are removed, so general activity records no longer point directly to your account. The records themselves are not deleted at once so that repeatedly deleting and re-creating accounts cannot be used for abuse; they too are deleted after 90 days. The email address and password hash left on a closed account are erased 30 days after its deletion finishes; the nickname stays reserved only, so nobody else can take it.

What administrators do (the audit log) is kept separately so that it can be checked that it was done properly. It contains none of your secrets.

Contact messages are kept for 1095 days from the day they arrive and then deleted automatically.

Original photos are kept even after the entry, recipe or kitchen is deleted or you close your account. They are deleted without delay if you ask (6. Your rights). A converted copy linked to nothing is deleted after a set time, and deleting an entry or a kitchen deletes its converted copies. The email hashes used to check deletion requests are kept after you leave. Registered AI keys are deleted at once when you leave, and any sharing ends with them. Kitchen data is kept while the kitchen exists; leaving ends your membership of it.

Game completion dates, completion counts, achievements and their earned times are deleted when you close your account. Daily challenge records are automatically deleted after the configured retention period of 90 days (90 days by default).

4. Ads and cookies

This site shows ads through Google AdSense. Third-party vendors, including Google, may use cookies to show ads based on your earlier visits. You can turn off personalised ads in Google's ad settings, and you can refuse cookies in your browser settings.

5. Sharing with third parties

We do not sell or give your personal information to third parties, except where the law requires it, following the proper procedure.

When you use an AI feature (reading a receipt, drafting ingredients from a dish name, translating a recipe, making a recipe from text or photos), the converted copies of the photos and the text it uses are sent to the AI provider of the key you registered or that was shared with you (Anthropic, PBC; OpenAI, L.L.C.; Google LLC, United States). This is a transfer abroad, and the provider handles it under its own policy. Nothing is sent if you do not use the AI features.

Photos of public recipes are served from a public address (a CDN) that anyone can open. Making the recipe private or deleting it deletes the public copy.

The bot check uses Turnstile from Cloudflare, Inc. The information it needs is processed under Cloudflare's privacy policy.

6. Your rights

You can ask at any time to see, correct or delete your personal information, or to have its processing stopped. Send the request through the contact page; it is handled within 10 days. To have original photos deleted, use the contact page with the "privacy" type. Even after you leave, a request from an address you signed up with is matched to your photos through its email hash.

7. How we protect it

Passwords are hashed with scrypt, so the original cannot be recovered. All traffic is encrypted with HTTPS, and authentication tokens are kept in cookies that JavaScript cannot read. Only a fixed list of fields can be written to activity records, so passwords and tokens never reach them. Only authorised administrators can read the records, and every read or change is kept in the audit log. AI keys are encrypted with AES-256-GCM. The photo store is not public, and every time an administrator opens, deletes or downloads a photo it is kept in the audit log.

8. Contact

For questions about personal information, use the contact page.

Guest posts, comments and retention

For guest posts we store a nickname, a scrypt hash of the editing/deletion password and an IP prefix. Only the first two IPv4 sections or IPv6 groups are shown. The full IP and a blocking HMAC are stored separately from content for 90 days. We never store the original password. After the full-IP record expires, the password hash and blocking HMAC remain for editing, deletion and enforcement of blocks. Guest posts and comments use Cloudflare Turnstile. Guests cannot upload photos, vote or earn activity points.

Contact messages are kept for 1095 days, audit records for 365, board management records for 365, activity-point display history for 365, and the recent game record feed for 3. Shorter periods apply to existing records through a bounded daily cleanup; longer periods apply to new records. Anti-duplication ledgers and necessary service state are maintained separately from display history.

Social sign-in

Enabled providers: Google. We receive a provider-specific ID, email and its verification status. Only an email the provider has verified is kept on the account; an unverified one is discarded. Apple may supply a relay email. Names are used only to suggest a nickname. We never receive or store the provider password. Existing accounts with the same email are not linked automatically.

When you enable push notifications, we store push subscription information (device endpoint and encryption keys). It is used only to deliver notifications and deleted when you disable notifications on that device or close your account.