Last updated: 7 September 2026
Atablio is a private household meal-planning app for the Lesieur home (Quebec, Canada). The household administrator is the data controller. Contact: [email protected].
This version has no advertising analytics, no in-app purchases, and no server push notifications.
To provide your account, share the menu with authorised household members, generate a local meal plan, and let you import/edit recipes.
Data is stored on a family computer (Mac mini) at home. It is not hosted in a third-party database cloud. If public HTTPS is enabled, encrypted traffic may transit a relay (Tailscale Funnel or Cloudflare Tunnel) that is not used as a recipe-storage service.
No sale, rental, or third-party advertising. Only household members and the administrator can access data, within the sharing level you choose (private / household / instance-public).
Photo text recognition runs locally on iPhone/iPad. This version does not send your recipes to a remote AI vendor.
Account data is kept while the account exists. You can delete the account in the app (password + confirmation): immediate removal of the account, private recipes, import photos and sessions. Server backups retain history until they rotate; that backup window is not yet published.
Password authentication, versioned tokens, private import photos, quotas and EXIF stripping. The admin panel is not exposed on the public Internet.
The app is for the household. It is not designed to collect children’s data for commercial purposes.
Questions, access or deletion: [email protected].
When you create a shared meal, invited people can see its title, date, place, recipe, participants and shared notes. After accepting, each person can reserve ingredients and add a contribution note. Private recipe notes and guests’ personal food profiles are not shared automatically. Completed meals remain in participants’ history.
To protect accounts, we keep sign-in, password reset, account lock and recovery events for 90 days: time, outcome, affected account, observed IP address and reported browser/app and operating-system family/version. These clues do not prove someone’s identity. Excessive attempts are logged with rate limiting. Passwords, secret links and request bodies are not stored in this journal. Administrators can review it; expired entries are purged on the next write. Recovering a locked account requires an independent identity check in person or by calling a previously known number, followed by a private one-use link. This form does not collect identity documents.