Skip to content

Social App Privacy Page

Privacy Policy — Olde NOLA Cookery Social Monitoring App

Privacy Policy — Olde NOLA Cookery Social Monitoring App

Effective date: [2026-05-12]
Operator: Olde Nola Restaurant Group (operating Olde Nola Cookery, Mambo’s, Oceana Grill, Hideout, Tipsy Trumpet, and Bobby Hebert’s Cajun Cannon)
Contact: contactus@nolacookery.com

This privacy policy describes how the Olde NOLA Cookery — Social Monitoring application (“the App”) collects, uses, stores, and protects information obtained through the Meta Graph API (Facebook Pages and Instagram Business accounts). The App is operated solely by the owner of Olde Nola Restaurant Group for the internal purpose of monitoring engagement across the six restaurants’ owned social media accounts.

1. Scope of this policy

This policy applies only to the Olde NOLA Cookery — Social Monitoring application registered with Meta for Developers. It does not describe the privacy practices of the public-facing nolacookery.com website, the restaurants’ point-of-sale systems, reservation systems, or any other Olde Nola Group services. Those are governed separately.

2. Who uses the App

The App is a first-party, internal-use tool. The only authorized user is the business owner of Olde Nola Restaurant Group. The App is not offered to the public, is not distributed to third parties, and is not used by any party other than the owner.

3. What information the App accesses

When the owner authenticates the App through Facebook Login, the App accesses the following categories of information from the Meta Graph API, limited to the six Facebook Pages and six Instagram Business accounts owned and operated by Olde Nola Restaurant Group:

  • Page identifiers and metadata — Facebook Page IDs, names, categories, follower counts (via pages_show_list, pages_read_engagement).
  • Business asset list — the list of Pages and Instagram Business accounts contained in the owner’s Meta Business Portfolio (via business_management).
  • Webhook subscription state — whether each owned Page is subscribed to the App’s webhook endpoint for engagement events (via pages_manage_metadata).
  • Instagram account metadata — Instagram Business account username, name, profile picture URL, and media object metadata (media ID, media type, timestamp, permalink) for the six owned accounts (via instagram_basic).
  • Instagram insights — aggregated account-level and media-level metrics including reach, impressions, profile visits, follower growth, saves, and post-level performance counts for the six owned accounts (via instagram_manage_insights).

The App does not access:

  • Direct messages (DMs) or message content
  • Comment text bodies
  • Information about users other than the authenticated owner
  • Information about individual followers, commenters, or visitors beyond aggregated counts
  • Payment information
  • Information from any account not owned by Olde Nola Restaurant Group

4. How the information is used

Information accessed by the App is used exclusively to produce internal performance reports delivered to the business owner. Specifically:

  • A daily digest summarizing engagement and performance across the six restaurants.
  • A weekly digest summarizing trends across the six restaurants.
  • Ad-hoc internal queries by the owner to monitor account health.

Information is not used for:

  • Advertising or ad targeting
  • Marketing communications to customers or followers
  • Public publication, posting, or replying on any social media account
  • Resale or licensing to third parties
  • Building profiles of individuals other than the business owner
  • Training of third-party machine learning models

5. How the information is stored

  • Information retrieved from the Meta Graph API is stored locally on hardware controlled by the business owner.
  • Access tokens are stored in encrypted form in a credentials directory restricted to the owner’s user account on that hardware.
  • Cached digest data is retained for no more than 90 days and then automatically deleted.
  • No information is uploaded to public-facing servers, third-party hosting providers, or cloud-based analytics services as part of the App’s operation.

6. How the information is shared

The App does not share information with third parties. The information is accessed only by the business owner. The App makes no API calls to any service other than Meta, and exposes no public-facing API of its own.

7. User rights and contact

Because the App processes only information about Olde Nola Restaurant Group’s own owned accounts, and is operated only by the business owner, this policy does not create user-facing data subject rights of the type described in consumer-facing privacy regulations. The business owner may at any time:

  • Revoke the App’s access via Meta Business Suite → Business Settings → Integrations.
  • Delete all locally stored data by removing the App’s data directory.
  • Contact Meta to request deletion of any data Meta retains.

For questions about this policy, contact contactus@nolacookery.com.

8. Changes to this policy

Material changes to this policy will be reflected by updating the Effective date above and republishing at the same URL (https://www.nolacookery.com/social-app-privacy/). The current version of this policy is always the version published at that URL.

9. Compliance with Meta Platform Terms

The App is operated in compliance with the Meta Platform Terms and the Meta Developer Policies. The App does not request, store, or use any Meta Platform data in a manner inconsistent with those terms.

This document is the privacy policy for the Olde NOLA Cookery — Social Monitoring application registered with Meta for Developers. It is not the privacy policy for the public-facing nolacookery.com website or for any restaurant point-of-sale, reservation, or alarm-notification system operated by Olde Nola Restaurant Group.

Skip to content