Who we are
PRENIO provides restaurant websites, growth services and reservation software. For enquiries and our own website, PRENIO acts as controller. When a restaurant uses PRENIO to manage reservations, that restaurant normally controls its guest data and PRENIO processes it on the restaurant’s instructions. Meta advertising data that a restaurant chooses to connect is processed on the restaurant’s behalf to provide the reporting it asked for (see “Meta (Facebook) advertising data” below).
Information we process
Depending on how you use our services, this may include contact details, restaurant and account information, booking details, guest preferences you choose to provide, consent choices, device and security logs, and communications with us. If a restaurant chooses to connect Meta, it also includes the Meta advertising data described in “Meta (Facebook) advertising data”.
Why we use it
We use data to provide and secure the service, fulfil reservations, respond to enquiries, manage accounts, prevent abuse, meet legal duties and—only where there is a valid basis—measure or improve our services and send marketing.
Sharing and retention
Data is shared only with the relevant restaurant, authorised service providers and authorities where legally required. We retain information only as long as needed for the stated purpose, contractual duties, security and applicable law. Meta advertising data is kept while the restaurant keeps Meta connected and for 365 days after a disconnect, after which it is deleted automatically, unless the restaurant deletes it earlier.
Your rights
Depending on applicable law, you may request access, correction, deletion, restriction, portability or object to processing. You can withdraw consent at any time without affecting earlier lawful processing. Contact hello@prenio.net.
Meta (Facebook) advertising data
Connecting Meta is optional. A restaurant owner or an authorised manager can connect the restaurant’s own Meta business assets to PRENIO. PRENIO’s access is read-only. PRENIO does not create, edit, pause or delete campaigns, ad sets or ads; does not change budgets or bids; has no access to billing, invoices or payment methods; and does not publish or edit content on the restaurant’s Facebook Page.
What the restaurant authorises. In the Meta dialog the restaurant chooses its Business Portfolio, its Facebook Page and its ad account, and grants PRENIO read-only permissions to list those assets and to read advertising performance for the selected ad account.
What we store.
- the Meta user ID of the person who connected, the permissions granted, and an encrypted access token (the token is never shown to anyone, including PRENIO staff);
- the names and IDs of the Business Portfolios, Facebook Pages and ad accounts made available to PRENIO in the Meta dialog (with basic details such as the Page category and the ad account’s status and currency), and which ones the restaurant selected;
- daily advertising performance metrics for the selected ad account. They may be stored at account, campaign, ad set and ad level, and include amount spent, impressions, reach, clicks and link clicks, results and conversions reported by Meta (and their value, where Meta provides it), and derived metrics such as CTR, CPC, CPM and frequency, together with campaign, ad set and ad names and IDs.
We do not store Page posts, comments, messages, followers’ personal data, audience lists or payment information.
How we use it.
- to show the restaurant its own advertising performance in its PRENIO dashboard;
- for PRENIO Marketing Intelligence reporting: authorised PRENIO staff use the stored metrics to prepare reporting and recommendations for that same restaurant. Access is restricted by role, and linking, syncing and deletion are recorded in an audit log.
Each restaurant’s Meta data is kept separate. We never use one restaurant’s Meta data for another restaurant, never combine restaurants’ data into shared audiences or benchmarks, never use it for PRENIO’s own advertising, and never sell it.
Disconnecting. In PRENIO, go to Settings → Integrations → Meta → Disconnect and confirm. Disconnecting stops all future syncing, asks Meta to revoke PRENIO’s access where supported, and removes the stored access credentials and the asset selection. Meta advertising data already stored is retained for 365 days after the disconnect and then deleted automatically, unless the restaurant reconnects or deletes it earlier. Once the data is deleted, we keep only a minimal record that a connection existed and was disconnected (dates and internal IDs, with no metrics, no token and no Meta account details) and our audit log, for security and accountability.
Deleting Meta data earlier.
- In PRENIO: Settings → Integrations → Meta → Delete Meta data. This permanently deletes the Meta advertising data PRENIO stored for the restaurant, immediately. If Meta is still connected, it first disconnects Meta (which also asks Meta to revoke PRENIO’s access). It does not change any ads, campaigns, budgets or settings in the restaurant’s Meta accounts.
- By email: write to hello@prenio.net with the subject “Meta data deletion” and the name of the restaurant. We confirm when deletion is complete. Records we must keep by law (for example invoices) are not affected.
Removing PRENIO in Meta. You can also remove PRENIO directly from your Meta account at any time:
- Facebook: Settings & privacy → Settings → Business integrations → PRENIO → Remove.
- Meta Business Suite: Business settings → Integrations → Connected apps → PRENIO → Remove.
This stops PRENIO’s access immediately, but it does not by itself delete data PRENIO already stored or start the 365-day period. To have that data deleted, also disconnect Meta in PRENIO, use Delete Meta data, or email us as described above.
Retention. Meta advertising data is kept while Meta stays connected in PRENIO and for 365 days after a disconnect in PRENIO, unless it is deleted earlier with Delete Meta data or by email request. The 365 days run in full from the disconnect, or from when PRENIO scheduled the deletion if that is later.