Back to Venview

Privacy Policy

Last updated: 16 October 2026

1. Who We Are

Venview (“we”, “us”, “our”) is operated by Venview AS (organisation number 938 650 802, registered in the Foretaksregisteret, head office in Oslo). We operate a restaurant operations platform — reservation management and AI workflow features, together with the optional modules a restaurant subscribes to, such as marketing, back-office and labour scheduling, point of sale, and inventory. This Privacy Policy explains how we collect, use, store, and share personal data in connection with the Service, and it applies to every module: where a module is described below, that description applies only if the restaurant has subscribed to it.

For the purposes of the GDPR, we act as a data controller for account and billing data (the restaurant operator’s own details), and as a data processor for the data a restaurant uploads to or generates within the Service about other people — its guests, and its staff. For that data the restaurant is the controller and we process it on their instructions.

2. This Website (venview.app)

This section covers the marketing website venview.app: its product and price pages, blog, founder pages and demo-booking pages (/demo/ and /en/demo/), and the measurement of visits that lead to signing up and subscribing. The rest of this policy covers the Venview platform.

Hosting and cookies. The website is hosted by Cloudflare. As the host, Cloudflare processes the technical data of each page request, such as your IP address. The website sets one cookie of its own, vv_consent, which only remembers your choices below and lasts 12 months. Google Analytics and the Meta pixel load only after you accept them in the consent bar, and the cookies they can set are described below.

Booking a demo (Google Calendar). The demo pages embed Google Calendar’s appointment booking page, which Google provides. It loads only after you accept in the consent bar or press “Show calendar”; you can also open the calendar in a new tab instead. When it loads, Google may set the cookie NID in your browser. On its cookie page (policies.google.com/technologies/cookies) Google says that NID is used to remember preferences and other information, and that “Each ‘NID’ cookie expires 6 months from a user’s last use”. Google also says that the NID cookie can be used to show ads in Google services for signed-out users, and that depending on your cookie choices you may have the cookie ‘_Secure-ENID’ instead, which lasts for 13 months. If you book a demo, the details you enter in Google’s booking form are received by Google and by us.

Google Analytics (Google tag). The website uses a Google tag with Google Analytics 4 (measurement ID G-G6SSHKYB5Z) to measure visits and use of the website, and what our ads lead to. It loads only after you accept it in the consent bar. Until then Google’s consent signals for analytics and advertising are set to denied; when you accept they are set to granted. The tag measures page visits, including visits to our price and product pages, and these events: a visit to the demo page, an opening of the demo calendar, signing up for an account, and subscribing (with the order value in NOK and a transaction ID). On its cookie page (policies.google.com/technologies/cookies) Google says: “‘_ga’, the main cookie used by Google Analytics, enables the service to distinguish one visitor from another and lasts for 2 years”.

Your choice. Your choice in the consent bar is stored in the cookie vv_consent on venview.app and its subdomains, so one choice covers venview.app and my.venview.app. It holds only your choices (calendar, Google Analytics, Meta pixel), lasts 12 months, and is sent to our own sites with your page requests, not to Google or Meta. You can change it at any time with the “Tracking preferences” link in the footer. If you withdraw a choice, the page reloads without the calendar, the Google tag or the pixel, and we remove the Google Analytics and Meta cookies from venview.app where we can. Cookies that Google has set for its calendar stay in your browser until they expire or you delete them.

Meta pixel. The website uses the Meta pixel. It loads only after you accept it in the consent bar. It counts visits to the website, including the price, product and demo pages, openings of the demo calendar, signups and subscriptions. With the pixel settings we use, Meta also receives details about the page you view, such as its title and description and, where the page shows them, products and prices. Meta processes data in the United States. For that transfer we rely on the EU Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework (see International Transfers below).

Signing up and subscribing. You sign up and pay for a subscription on my.venview.app, and Stripe handles the payment. When you sign up and when you subscribe, we count these two events in Google Analytics and the Meta pixel in your browser. So that a sale is still counted when a browser blocks the tag, our server can also send the same event to Google Analytics and to Meta after Stripe confirms the payment. These events can contain the type of event, the time, the order value and currency (NOK), a transaction ID, the page address, and identifiers that let Google and Meta match the event to an earlier visit: the identifiers in the Google and Meta cookies and, in the server copy, your IP address, your browser type and a hashed form of your email address (converted so that it cannot be read back). We send these events only for the choices you have accepted in the consent bar; Google Analytics and the Meta pixel are separate choices. If you declined or withdrew a choice, that service receives nothing, neither from your browser nor from our server. Card details are handled by Stripe; we never receive them and never send them to Google or Meta.

3. Data We Collect

Account data: name, email address, sign-in provider and account identifier (Google or Microsoft), restaurant name, timezone, and subscription details provided during sign-up.

Guest data: reservation details, guest names, contact details, and any notes you store in the Service about your guests.

Email content: when you connect an email inbox, we access inbound emails in order to process reservation requests. We store message content only as required to operate the AI workflow features.

Usage data: log data including IP addresses, browser type, pages visited, and actions taken within the Service, for security and performance purposes.

Payment data: billing information is processed by our payment provider (Stripe). We do not store full card numbers.

Staff and scheduling data (labour and back-office modules): for each shift you record, the work email address of the staff member, their role, the shift start and end times, the hourly rate you enter, and any note you add. Staff members are identified by the email address you invite them with; we do not hold their home address, national identity number, or bank details. For this data your restaurant is the controller and we are the processor.

Staff activity records: wherever the Service records an action taken inside your account, it also records which staff account took it — for example who opened or closed an order or a till shift, who moved stock, who entered an expense or a shift, who changed a guest record, and who sent a campaign. A till close additionally records the cash counted and the difference found. These records exist so you can reconcile a till and audit a change; they are staff personal data on the same basis as the scheduling data above, and they arise in every module rather than in one.

Sales and order data (point-of-sale module): orders, order lines, discounts and the reason you give for them, cover counts, the payment method recorded for an order (for example “card” or “cash” — we never receive or store card numbers), receipt numbers, and the free-text label or note you put on an order. An order linked to a reservation is also linked to that guest’s record. If you import sales reports from a connected mailbox, we store the sending address, subject and file name of the imported message together with a sample of its rows.

Supplier and expense data (back-office and inventory modules): supplier or vendor names as you type them on an expense entry, plus amounts and dates. These are normally business details, but a supplier name you type may be a person’s name. Ingredient and stock records themselves hold no personal data.

4. How We Use Your Data

5. Legal Basis for Processing (GDPR)

6. Sub-processors and Data Sharing

We do not sell your personal data. We share it only with the sub-processors we engage to operate the Service, and with legal authorities when required by applicable law or court order. Our current sub-processors are:

For the measurement on our own website and when you sign up and subscribe (section 2), we share the data described there with Google (Google Analytics) and Meta, only after you accept the matching choice in the consent bar.

Sub-processors are contractually bound to protect personal data. Under our API agreements with Google and Anthropic, your data is not used to train their models. We maintain an up-to-date sub-processor list and will give notice of changes.

Google API Services Limited Use

When you connect a Gmail mailbox, our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically, we use Gmail data only to provide and improve the user-facing reservation features you have enabled (reading inbound reservation emails and drafting and sending replies from your mailbox). We do not transfer or sell Gmail data for advertising, we do not use it to train or improve generalised AI/ML models, and we do not allow humans to read it except where you direct us to, where you give specific consent, where required for security or to comply with applicable law, or on data that has been aggregated and anonymised for internal operations.

7. Data Retention

We retain account data for the duration of your subscription and for up to 12 months thereafter for audit and legal purposes. Guest and reservation data is retained for 24 months from the date of the reservation, or for the duration of your subscription, whichever is longer. Email content is retained for 12 months. You may request earlier deletion at any time.

Sales and order data is retained for at least five years from the date of the order, because Norwegian bookkeeping law requires it. After that it is removed or reduced to figures that identify no one.

Staff and scheduling data is retained for five years from the date of the shift, because a shift record is also a payroll and working-hours record you may have to produce. If you have set a longer retention period, that period applies instead. After that a shift is removed automatically. You can delete an individual shift at any time, and you can ask us to delete a former staff member’s records earlier.

Supplier and expense data follows the same five-year accounting rule, because an expense entry forms part of your books. It is then removed automatically.

Till shifts (the cash count that opens and closes a service) are removed on the same five-year rule as the orders they cover, once no order still refers to them.

Imported sales-report emails — the sender address, subject and file name we record when you import a report from a mailbox — are kept for at most 12 months, or for your retention period if you have set a shorter one. Your activity log also records that the import ran, and that entry can name the sender; log entries are removed on your configured retention period — 12 months unless you have set a different one — so a longer setting keeps the sender for that longer period. The orders the report created keep the five-year sales rule. The import record that groups those orders is part of that sales trail rather than of the 12-month rule, and it stores the file name, so a file named after a person keeps that name with the sales records. We remove that record, and the file name with it, five years after the import ran — or later if the orders it produced are still inside the five-year sales rule, because the record is what those orders are traced back to.

When your subscription ends, we keep your data only for the periods described above, and for any longer period the law requires.

Guest and reservation records, sales and order data, staff and scheduling records, till shifts, expense entries and imported-report metadata are now all removed automatically when their period ends. Account data and your configuration are removed when you ask us to, not on a timer. You can still ask us to delete a record earlier — for staff and supplier records that is a manual operation we carry out for you, because there is no self-service tool for them yet.

8. International Transfers

Our core infrastructure is hosted within the European Economic Area. Some sub-processors — including Anthropic, Stripe, Meta, Resend, Sentry, and Cloudflare — process data in the United States. Our AI features that read inbound email content or the public booking form's comment (either of which can include dietary/allergy information) run on Google Vertex AI within the European Economic Area; only our internal operations assistant may surface limited data to Anthropic in the United States. Where data is transferred outside the EEA, we rely on appropriate safeguards, including the EU Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework. You can request details of the safeguards in place for a specific transfer.

9. Security

We implement appropriate technical and organisational measures to protect your data against unauthorised access, alteration, disclosure, or destruction. These include encryption in transit (TLS), encrypted storage, access controls, and regular security reviews.

10. Your Rights

Under the GDPR and applicable privacy law, you have the right to:

If you are a guest of a restaurant, or a member of its staff, that restaurant is the controller of your data. Send your request to the restaurant; we help them answer it, and we act on their instruction.

To exercise any of these rights, contact us at privacy@venview.app. We will respond within 30 days. You also have the right to lodge a complaint with your national data protection authority.

11. Cookies and Tracking

We use a session cookie to keep you signed in. The operator dashboard does not use third-party advertising cookies. On a restaurant’s public booking page, a visitor who picks a language from the on-page switcher gets one first-party preference cookie (pb_lang) so the pages they visit next stay in that language; it stores only the language code, identifies no one, and is set only when the visitor chooses a language themselves. Where the restaurant has enabled a conversion-tracking or analytics tag (Meta Pixel, TikTok Pixel, Google Ads, or Google Analytics), that tag loads only after the visitor accepts it via the on-page consent banner; visitors who decline get no tag. That tracking is controlled by the restaurant as data controller. Cookies and tracking on the venview.app website, and the counting of signups and subscriptions, are described in section 2.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes via email or in-app notification at least 14 days before they take effect.

13. Contact

Venview AS, organisation number 938 650 802, Foretaksregisteret, Oslo, Norway.

For privacy enquiries, contact our data protection contact at privacy@venview.app.