Data we process

• Account data: email address, verification timestamps, and session state used to sign you in.
• Profile data: display name plus optional social links you publish on your author profile.
• User content: recipes, uploaded sample images, image metadata, and camera EXIF data you submit.
• Security data: magic-link request details, session metadata, IP address, and user agent used to protect the app.
• Optional analytics: Google Analytics page-view data only after you grant analytics consent.

Why we use it

OM Recipes uses account and security data to deliver passwordless login, maintain sessions, protect the public sign-in flow, and let authors manage profiles and uploads. User content is stored so recipes and image samples can be displayed publicly. Optional analytics helps measure traffic only when you allow it.

Third-party processors

• Netlify for application hosting and platform runtime.
• Neon/Postgres through Netlify DB for application data storage.
• Oracle Cloud Infrastructure for email delivery, object storage, and image-processing functions.
• Google Analytics 4 for optional traffic analytics when consent is granted.

Your controls

• Review and update your public author-profile fields from your profile page.
• Request a downloadable export of your account data and available uploaded originals.
• Request account deletion, which removes your first-party account data and user-owned content from the app.
• Change your analytics-consent preference at any time from the footer control.