OpsiviaOpsivia

Opsivia Privacy Policy

Last updated: 25 October 2026

We handle personal information in accordance with the Australian Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).

1. What we collect

  • Account information: name, email, organization details. Your sign-in credentials, including your password, are handled directly by Supabase Auth, our authentication provider; Opsivia's own application database does not store your password in a readable form.
  • Business data you input: inventory records, staff details (name, contact info, pay rates, rostered hours), sales records, invoicing/client data, and content of any documents or photos you upload for AI-assisted processing — for example photos or PDFs of supplier invoices, sales statements, floor-plan sketches, menu items, and free-text business-setup descriptions.
  • Subscription billing information: your Opsivia subscription is billed via Stripe, through our development platform Lovable's billing gateway (see section 3); we store a reference to your Stripe customer ID for that subscription, but not full payment card details.
  • Online payments (Stripe Connect) information: if your Organization accepts online card payments from its customers, we collect and hold a broader set of information described in section 4 below, not only a customer ID.
  • Staff push-notification tokens: if a staff member installs the Opsivia mobile app and allows notifications, we hold a device push-notification token used to send shift-related alerts to that device.
  • Usage data: log data, device/browser information, and analytics to help us improve the Service.

2. How we use it

  • To provide and operate the Service, including the features you've configured for your Organization.
  • To process AI-assisted features (for example extracting line items from an uploaded photo or PDF of a supplier invoice or sales statement, reading a floor-plan sketch, importing menu items from a photo or PDF, or generating a business-setup suggestion from a free-text description) — these requests are sent to Anthropic, our AI model provider, as described in section 3 below.
  • To send staff shift-related push notifications to a staff member's mobile device, where that staff member has installed the mobile app and allowed notifications.
  • To send transactional emails (account verification, password resets, billing notices, roster notifications) and, where relevant, product updates.
  • To bill you for your subscription via Stripe.
  • If your Organization accepts online card payments, to create and administer a connected Stripe account for your business and to process, refund, and resolve disputes on the resulting Transactions, as described in section 4 below and in our Merchant Payments Terms.

3. Who we share it with

We share data with the following service providers as necessary to operate the platform:

  • Supabase, provisioned and managed through Lovable Cloud (database, authentication, file storage, and the server-side functions that process Stripe Connect and other backend operations)
  • Lovable: in addition to providing the Lovable Cloud infrastructure described above, Lovable is the development platform we use to build and edit the application, and also routes our subscription-billing calls to Stripe through its own billing gateway (see below); Lovable's infrastructure can access the data described in this policy to the extent necessary to provide that hosting and gateway role.
  • Hostinger International Ltd (hosting of the server that runs Opsivia's web application and backend logic — see below)
  • Anthropic (AI model provider for the AI-assisted features described in section 2 — see below)
  • Expo (push-notification delivery to the Opsivia mobile app — see below)
  • Cloudflare (bot/abuse-prevention check shown on public order and table-booking forms — see below)
  • Stripe (subscription billing, routed through Lovable's gateway described above, and, for businesses that accept online card payments, connected-account and payment processing — see section 4)
  • Xero (optional accounting sync, only for a business that connects its own Xero account — see below)
  • Zeller (in-person card-terminal payments, currently offered only to a small, invited set of businesses as a pilot — see below)
  • Resend (transactional email delivery)

Hostinger International Ltd, located in Cyprus, supplies the virtual server on which Opsivia's web application and backend logic run. Hostinger's role is infrastructure hosting: the application code, and the personal information that passes through it while the application is running, is processed on Hostinger's server, but Hostinger is not a party we separately send personal information to for its own use.

Anthropic provides the AI model behind our AI-assisted features. When you use one of those features, we send Anthropic the specific document, photo, or text you submitted for that feature (for example a photo or PDF of an invoice, sales statement, floor-plan sketch, or menu, or a free-text business-setup description) together with an instruction describing what to extract or generate, and Anthropic returns its response. Opsivia does not automatically attach customer-order, payment, roster or payroll database records to an AI request. However, Anthropic receives any information contained in the document, photo or text you choose to submit for one of these features — so if, for example, a photo you upload happens to show a customer's name or other personal information, Anthropic receives that too. You should avoid including personal information in a submission that is unnecessary for the feature. We rely on Anthropic's own published terms and data-processing documentation for how it handles that information; we do not independently verify, and this policy does not claim, how Anthropic anonymises, retains, or otherwise processes it, or whether it is used to improve Anthropic's models.

Cloudflare provides a bot/abuse-prevention check (Turnstile) shown on our public online-ordering and table-booking forms. This happens in two parts. First, the Turnstile widget running in your browser communicates directly with Cloudflare to produce a response token; Cloudflare's own documentation states that, as part of this, it processes client-side signals including your IP address, TLS fingerprint, User-Agent header, and the site key and origin of the page you are on. Second, once your request reaches our server, our server sends that response token, your IP address where our systems can determine one, and the name of the action you completed (for example placing an order or booking a table) to Cloudflare's verification service, before completing your order or booking. Turnstile does not receive the contents of the form itself (for example your order items or booking details) through this integration.

Xero is an optional accounting connector a business may choose to connect its own Xero organisation to. If your Organization connects Xero, we send Xero your Organization's approved invoices (as drafts) so they can be reconciled in your Organization's own books — this includes customer names and email addresses, invoice line items, amounts, tax information, and the identifiers Xero needs to match and avoid duplicating an invoice. We also exchange the OAuth account information and Xero organisation identifier needed to maintain that connection. We do not send Xero information for an Organization that has not connected its own Xero account.

Zeller provides in-person card-terminal payment processing. This is currently offered only as a pilot to a small, specifically invited set of businesses, with a capped transaction amount. For a business using this pilot, we exchange the payment amount, our own payment reference, the terminal's identifiers, and the transaction's status with Zeller through its terminal SDK.

Expo operates the push-notification delivery service used by the Opsivia mobile app. If a staff member installs the mobile app and allows notifications, we send Expo that device's push-notification token together with the notification's fixed title and body text (for example a prompt to confirm or clock out of a shift) so Expo can deliver it to the device. Expo does not receive your customers' order or payment information.

These providers may store or process data outside Australia, including in the United States. Before relying on an overseas provider, it is our policy to take reasonable steps appropriate to the circumstances, consistent with OAIC guidance on Australian Privacy Principle 8 — which may include assessing whether the provider is subject to a law or binding scheme that upholds protections substantially similar to the APPs, and otherwise seeking appropriate contractual arrangements (such as confidentiality, security and use-limitation obligations). Your use of the Service does not, by itself, remove our own accountability under Australian Privacy Principle 8 for how an overseas recipient subsequently handles your information; where APP 8.2 applies, we will usually remain accountable if the overseas recipient mishandles it.

We do not sell your data or your staff's/customers' personal information to third parties.

4. Online card payments (Stripe Connect)

If your Organization enables online card payments through Opsivia, your Organization's Stripe Connect integration involves exchanging a wider range of information with Stripe than a simple customer-ID reference. This section describes that information; our Merchant Payments Terms also describe how it is used.

We collect, hold or receive from Stripe:

  • business representative, beneficial-owner and identity-verification information your Organization submits to Stripe as part of connecting a Stripe account (for example the names, contact details and identity-verification information of people who own or control the business);
  • the connected-account identifier and its onboarding and account status (for example whether card payments and payouts are active, and what verification, if any, Stripe still requires);
  • your customers' identity, contact and order information collected at checkout (for example name, email, delivery address and what was ordered);
  • checkout-session, payment-intent, refund, fee, payout and dispute information for each Transaction (for example amounts, status, the platform fee charged, and payout timing);
  • webhook delivery records and other payment-security records Stripe sends us to confirm and reconcile Transactions; and
  • risk, verification and account-status information Stripe provides back to us about a connected account.

We share the information above with Stripe to create and administer your Organization's connected account and to process Transactions (payments, refunds, transfer reversals and disputes) on it. Stripe may, in turn, share connected-account, risk, payment and verification information back to us.

Stripe processes this information under its own privacy and services agreements, and may do so outside Australia, including in the United States. The cross-border protections described in section 3 apply to this sharing as well.

Merchant Payments Terms acceptance records (which Business Administrator accepted which version of the Merchant Payments Terms, and when) are retained as described in section 7 below.

5. Data of your staff and customers

If you input personal information about your staff (for rostering) or your customers (for invoicing/sales records), you are responsible for ensuring you have the right to do so and, where required, that affected individuals are aware of how their information is being used. We process this data solely to provide the Service to you.

Table bookings. When you book a table online, the venue you book with collects your name, phone number and email address, your group size, the date and time you choose, and any notes you add. The venue uses this information to manage your booking and to email you about it. The venue is the collector of this information; Opsivia hosts it on the venue's behalf.

6. Data security

We use industry-standard measures including encryption in transit and at rest, role-based access controls, and tenant data isolation (each Organization's data is logically separated). No system is perfectly secure, and we encourage strong, unique passwords.

7. Data retention

We retain your data for as long as your account is active. On cancellation, we retain your data for 30 days to allow reactivation; after that period, operational data may be deleted, unless you request earlier deletion.

We retain data for longer than that, including after cancellation or a deletion request, to the extent reasonably necessary for payment, transaction, tax, fraud-prevention, dispute, security, audit or other legal obligations. This includes Transaction and payout records connected to online card payments, and Merchant Payments Terms acceptance records, which we may retain after your Organization's account is cancelled for these purposes.

8. Your rights

Under the Privacy Act, you may request access to, or correction of, personal information we hold about you, subject to legal exceptions (for example, information we must retain under section 7 above). You may also request deletion of personal information we hold about you, subject to the same exceptions. Contact us at info@opsivia.com.au to make a request or to raise a complaint; we will respond within a reasonable time.

9. Cookies

We use essential cookies/local storage to keep you logged in and remember your preferences. We do not use third-party advertising cookies.

10. Changes to this policy

We may update this policy from time to time. Material changes will be notified via email or in-app notice.

11. Contact

For privacy questions or complaints: info@opsivia.com.au. If unresolved, you may contact the Office of the Australian Information Commissioner (oaic.gov.au).