PRIVACY POLICY

Your privacy,
in plain words.

Your individual recipe book stays on your device. Shared recipes and photos are also stored online for both members. Imports use online services. Here is what is processed and what you can do.

Updated November 16, 2026 · miam and this website

Publisher and data controller

Arthur Bouder publishes miam, directs publication of this website and is responsible for the processing described here.

Individual publisher based in France.

35 rue du Docteur Bretonneau, 37000 Tours, France

Telephone : +33 7 70 35 51 92

arthurbouder.dev@gmail.com

This website is hosted by Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. French contact telephone: +33 1 73 01 52 44. Cloudflare contact details. The separate import server is hosted by Railway.

On your device

No sign-up, email address or password is required. The individual recipe book stays local; versions offering a shared book synchronize it between its owner and invited member. It stores titles, ingredients, steps, tags, dates and, when available, the source link, caption, public author name and image URL. Preferences, onboarding progress, pending imports, drafts and received share links are also stored locally. Edits in the individual book stay local; edits in a shared book are sent to the server for the other member. Availability depends on the installed version.

Sharing an Instagram or TikTok post to miam requests its import. The link is saved on your device, then sent to the server once onboarding is complete. You still review and save the draft yourself.

Instagram images are loaded directly from Meta servers and may be cached. miam may also request the post’s public Instagram embed page to find a cover without a Play symbol, without sending sign-in cookies. Meta receives the requested URL, your IP address and connection information. Deleting a recipe does not necessarily clear image caches. Device or browser backups may contain copies, depending on your system settings.

Shared recipe books and purchases

Once Premium access is confirmed, the owner’s recipes are copied to an online book. The miam server on Railway receives recipes, edits and compressed photos and stores them in a Supabase database and private file storage. The free individual book and its photos are not uploaded to Supabase for sharing.

Data includes recipe content and provenance, dates, identifiers for the book and its two installations, owner or guest roles, invitation information and synchronization identifiers. Both members can read, add, edit and delete all recipes. The guest explicitly accepts an invitation without merging their personal recipes into the shared book.

The invitation link contains a temporary access token: send it only to your chosen person. It lasts seven days and can be used once; the server stores its fingerprint. Opening the page sends its URL and connection information to Cloudflare and does not automatically accept the invitation.

Each device retains a copy of the recipes and downloaded photos. In the updated version, offline access lasts at most seven days after the last successful access verification, without exceeding the owner’s known subscription expiry. Older versions may apply a shorter period. Synchronization runs at startup, when returning to the app and every thirty seconds while it is in the foreground. Revocation applies at the next connection; it cannot instantly remove a disconnected copy.

RevenueCat receives an installation identifier used for purchases, technical information and transaction information needed to verify access. The server checks the owner’s rights to grant access to both members. Recipe content and photos are not sent to RevenueCat. Development versions may use its Test Store without real payments. RevenueCat information.

Shared storage, invitations and purchase verification provide the service you request, on the basis of performing that service. Access checks and synchronization receipts serve the legitimate interest of securing the service and preventing duplicate processing. Sharing is optional; using it requires the recipe-book data and technical identifiers. Supabase information and its data processing agreement.

When you import a recipe

The app sends the public Instagram URL, a request identifier, its creation time and the installation secret to the miam API over HTTPS. Tracking parameters are removed from the link. The server derives an installation fingerprint without storing the secret itself. Jobs, caches and usage limits are separated by installation.

miam / Railway
The server retains the source and draft to resume imports and avoid repeated processing. The hosting provider may process connection information, including IP addresses.
Supadata
Receives the Instagram or TikTok URL to retrieve its caption, public author, image and media details. If the caption is incomplete, video analysis may retrieve a transcript.
OpenAI
Receives the caption and, when needed, the video transcript from the miam server. It proposes a title, ingredients, steps and tags. Your full recipe book, local edits and installation secret are not included.

Captions can contain personal information about their authors or other people. Processing the link and necessary text provides the service you request. Protecting access, applying quotas and preventing duplicate processing serve our legitimate interest in security and preventing abuse. Keeping public author information serves the legitimate interest of documenting recipe provenance. Do not submit private content or sensitive personal data; public availability does not authorize every form of reuse. Imports produce drafts that you should check.

TypeSafe/Jev is not enabled on the import server. Extraction requests remain separate from recipe-book synchronization.

How long data is kept

Local data: recipes remain until you delete them or erase the app’s data. Expiry of offline access blocks the shared book without automatically deleting its content. Revoked guests lose their shared copy at the next connection. Images, secure storage and system backups have separate lifecycles.

Online shared book: recipes remain until removed from the book. The book, access rights and photos are erased when its owner uses “Supprimer mes données”. When a guest uses this action, their access is removed and the common book is kept. Subscription expiry blocks access without an automatic purge. Photo files from a removed recipe may remain in private storage until the whole book is deleted.

Revocation records, deletion receipts and purchase identity links are retained separately to prevent deleted access from reappearing and to preserve purchase rights. They contain no recipes; these records currently have no automatic purge. Deletion does not cancel a subscription or recall copies exported outside miam or provider backups.

miam server: completed or failed jobs are deleted after seven days from creation. Source and extraction caches expire seven days after caching, without renewal on a read. Purging runs at startup and at most one minute apart during service activity; outages delay it. Technical usage counters and duplicate-request receipts are retained for 35 days. They include installation fingerprints, request identifiers, dates, usage units and a source fingerprint, not caption text. They are not anonymous.

Backups: a daily SQLite copy is made on the server volume. Previous days’ copies are removed after a successful new backup during the hourly check. Failures can leave an older copy. Deleting an import from the active database does not erase existing backups. Off-volume Railway snapshots were not enabled in the latest hosting check. Private manual exports are scheduled for deletion within seven days by the operator; we do not promise one global deletion deadline across all providers.

OpenAI: miam uses store:false, which does not mean zero retention. OpenAI normally retains abuse-monitoring logs for up to 30 days, subject to legal and security exceptions and separate cache rules. No zero-retention arrangement is confirmed for miam. OpenAI data documentation.

Supadata: single-job results are available for one hour, batch results for 24 hours. Public content may be cached without one published expiry period for all caches. Removal can be requested with its URL. API request logs have separate retention during the customer relationship. Supadata policy. Hosting providers retain technical logs according to their security obligations and terms; the miam deadlines do not apply to every provider copy.

This website and support

The website adds no advertising, analytics, forms, accounts or cookies. Fonts and images are hosted with the pages. External policy links contact those websites only when opened. Cloudflare processes connection information to serve and protect the website. Cloudflare policy.

If you email us, Google Gmail processes your email address, optional name, message and attachments so we can answer. A contact link opens your email app; viewing this page sends no email. Do not send passwords, secrets or your entire recipe book. Ordinary support correspondence is kept while resolving the request, then for 6 months after resolution, before deletion from the publisher’s mailbox, including trash. Necessary evidence may be kept longer for a justified legal obligation or dispute, with a separate deadline. Copies in your own mailbox and Google’s technical deletion and backup periods are separate. Google privacy · Google retention.

Support and website security rely on the legitimate interest of answering requests and providing a safe service. Rights requests are processed to comply with data-protection obligations. Providing information is optional, but a reply address and sufficient detail may be needed to answer you.

Security and international transfers

The API uses HTTPS and checks access to each import and shared book. Shared photos are private, with temporary download links. Provider keys remain on the server. This does not guarantee that every local datum is encrypted or that incidents are impossible. Providers may process data outside France and the EU. A European server region does not guarantee that all processing, logs and subprocessors stay in Europe.

The published data-processing agreements of Railway, Cloudflare, Supadata and OpenAI provide for EU standard contractual clauses or applicable adequacy decisions. Contact us for available information on applicable safeguards and copies of the clauses.

Your rights and choices

You can use saved recipes without new imports, edit them or delete them. See deletion instructions for the differences between local and remote data.

Under applicable conditions, you can request access, correction, erasure, restriction and portability, object to processing based on legitimate interests for reasons relating to your situation, and withdraw consent where processing relies on it. Withdrawal does not undo prior processing.

arthurbouder.dev@gmail.com

Describe your request and provide enough information to locate the relevant data. Additional identity verification is requested only where reasonably needed; do not send an identity document unsolicited. We normally reply within one month. Complex or numerous requests may require up to two additional months; we will explain the extension within the first month. You may complain to the CNIL or the supervisory authority competent for your situation.

This policy grants no rights to reuse Instagram content and does not replace the terms of the services concerned.

Optional analytics and feedback

Analytics is on by default for new installations. Previously saved choices are preserved. You can stop or enable it in Settings. miam sends app-open events, onboarding progress (Welcome, Premium presentation, demo and completion), an installation identifier and limited app and system information to PostHog. This helps us understand usage. Recipe content, photos, source links and secrets are excluded. There are no targeted ads, screen recordings or access to GPS location.

Sending feedback is a separate action. Only the message you submit, its category, app version and platform are sent to the miam server. The server forwards them to our EU-hosted PostHog project with an identifier for that message. This helps us address problems and improve the app. Avoid sensitive information. An unsent draft stays on your device.

The server removes the text after PostHog acknowledges it, or after seven days without a successful delivery. A technical receipt remains for thirty-five days. Deleting miam data does not automatically remove events already sent to PostHog. Contact support for deletion, with the approximate date and content of your feedback. For analytics, contact us before removing the installation so we can help identify it.

miam has not configured automatic deletion of PostHog events. The provider’s query windows do not guarantee deletion. See PostHog retention and its privacy policy. You can turn off analytics sharing at any time. Voluntary feedback is processed to handle your request and improve the service.

From app version 0.1.5, usage statistics also include opening and closing Premium offers, their entry point (onboarding, free limit, settings or shared notebook), the annual or monthly plan and the purchase attempt outcome. Test purchases are marked. These events contain no payment receipt, amount or transaction identifier. You can turn these statistics off in Settings.

Statistics in the next app version also include the start of an import attempt, its terminal failure, saving a new recipe and the number of non-demo recipes in the notebook after saving. Only the source platform (Instagram or TikTok) is included, without the link or recipe content.

From app version 0.1.5, the country of use will be estimated from the IP address received by PostHog. Only the country code and name will be stored, without the IP address, city, region, postal code or coordinates. No location permission is requested. Travel or a VPN can change this estimate. The same usage-statistics setting controls this measurement.