Closed-beta privacy notice

Margy Privacy Policy

This notice explains how the Margy closed beta handles account data, recipe workspaces, session history, local photos, Connected Agents, notifications, communications, diagnostics, and consented Google Analytics on the public landing page.

Data controller & contact

Mattia Michini, Teramo (TE), Italy, is the controller of the personal data processed through this application. For any privacy requests, please write to mattiamichini@gmail.com

Personal data Margy processes

  • Account and authentication data. Supabase Auth processes your user ID, email address, sign-in provider, authentication timestamps, and security records needed to operate your account. Margy does not receive your OAuth provider password.
  • Public landing analytics. After consent, Google Analytics 4 may process public landing page views, device or session information, and traffic sources. Internal and authenticated routes do not load analytics.
  • Workspace and recipe data. Margy stores account preferences, equipment, flours, preferments, starters, recipes, notes, session history, actuals, reviews, and public recipe snapshots. The app is local-first and synchronizes supported records to Supabase when you use an authenticated account.
  • Session photos. Optimized photo copies stay in IndexedDB on the device. Photo metadata may synchronize to your Supabase workspace. Image bytes are not uploaded by the current beta photo workflow. Clearing browser storage or deleting local copies can remove them.
  • Connected Agent data. For Model Context Protocol connections, Margy stores grant metadata, allowed scopes, token hashes, revocation state, and a limited audit record. External clients receive the synchronized data you authorize within those scopes.
  • Security and diagnostic data. Margy processes request identifiers, timestamps, error types, release information, and allowlisted technical context to secure and troubleshoot the beta. If a Sentry data source name is configured, redacted error events are sent to Sentry. Without it, no Sentry event is sent.
  • Messages and newsletter details. If you contact Margy or join the newsletter, the service processes your email address and the information you submit. Newsletter signup is separate from your Margy account.
  • Consent records. Your analytics choice, consent version, and update time are saved in a first-party cookie for up to 12 months so Margy can honour your choice.

Purposes and legal bases

  • Providing the beta. Margy processes account and workspace data to save, synchronize, display, export, and delete the features you request. Legal basis: performance of the beta service (Article 6(1)(b) GDPR).
  • Security and reliability. Margy uses authentication, rate limits, audit records, redacted logs, and error diagnostics to prevent misuse and maintain the beta. Legal basis: legitimate interests (Article 6(1)(f) GDPR).
  • Support and enquiries. Margy uses information you send to answer requests and resolve problems. Legal basis: pre-contractual or contractual steps and legitimate interests (Article 6(1)(b) and (f) GDPR).
  • Optional communications. Margy sends the newsletter only after your separate signup and sends push reminders only after browser permission and subscription. Legal basis: consent (Article 6(1)(a) GDPR).
  • Analytics. After consent, Google Analytics 4 measures visits to the public landing page. Analytics stays off on internal and authenticated routes, and Microsoft Clarity is not configured. Legal basis: consent (Article 6(1)(a) GDPR).

Data retention

Account and synchronized workspace data remain until you delete them or close the account. Public recipe snapshots remain until revoked or the account is deleted. Device-local records and photo bytes remain until you remove them, clear site data, or delete them during the account flow on that device. Push subscriptions and Connected Agent grants remain until revoked, expired, or deleted with the account. Newsletter data remains until unsubscribe or a valid deletion request. Support messages remain only while needed to answer the request and meet applicable obligations. Consent preferences last up to 12 months. Redacted diagnostics follow the configured Sentry free-plan retention; without a Sentry data source name, Margy sends none. Provider backups and security logs may age out after the live account is deleted under provider retention schedules and legal requirements.

Processors and other recipients

Margy uses providers only for the functions described below:

  • Supabase. Supabase provides authentication, database synchronization, row-level access controls, push scheduling, and server functions for the authenticated beta.
  • Google Analytics 4. After consent, Google Ireland Limited receives public landing page views, device or session information, and traffic sources. Margy does not load Google Analytics on internal or authenticated routes.
  • Sentry. When configured, Sentry receives redacted error and technical diagnostics. Margy excludes recipe content, notes, email addresses, tokens, cookies, authorization headers, and complete Model Context Protocol payloads from intended diagnostic context.
  • Web Push infrastructure. Your browser's push service receives a subscription endpoint and encrypted delivery data when you enable push reminders.
  • EmailOctopus. The newsletter provider receives your signup email and list status when you subscribe.
  • Connected Agent clients. Clients that you authorize receive the synchronized data permitted by their grant. Their operators may process exported data under their own terms.

International transfers

Supabase, Google Analytics, Sentry, EmailOctopus, browser push providers, and Connected Agent operators may process data outside the European Economic Area. Where GDPR transfer rules apply, the relevant provider's contractual safeguards and transfer mechanisms govern that processing. Google Analytics receives only consented public landing analytics; Microsoft Clarity is not configured.

Your rights

Under the GDPR, you may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests. You may withdraw consent without affecting earlier lawful processing. Use account export and deletion where available or email the controller. You may also complain to the Garante per la Protezione dei Dati Personali or your local supervisory authority.

Exporting, deleting, and managing your choices

Use account settings to export a portable copy of supported account data or begin permanent deletion. Deletion requires immediate reauthentication: password accounts enter their password and OAuth accounts sign in again with their provider. Revoke Connected Agent grants, public recipe links, push permission, or newsletter subscription from their respective controls. Local photos and browser data belong to the device, so clear them on each device you used.

Last updated: July 25, 2026