Privacy

Privacy Policy

Last Updated: October 25, 2026

Privacy Policy

Last updated: October 25, 2026

This Privacy Policy explains how OMNIX COMMERCE PTE. LTD. (“Omnix”, “we”, “us”, “our”), a company registered in Singapore, collects, uses, stores, and shares information when a merchant (“you”, “Merchant”) installs and uses Flunnel (the “App”), an AI landing-page builder for Shopify, and when a Merchant’s customers (“Customers”) interact with landing pages, sign-up forms, deals and offers created with the App, and when anyone visits our website or writes to us through it (Section 2.9).

By installing or using the App, you agree to this Privacy Policy.

1. Our role (controller vs. processor)

  • For Merchant account and store data, we act as a data controller to the extent we operate the App.

  • For Customer personal data that flows through the App (for example, email addresses submitted through a sign-up form, the sign-ups the App saves as Shopify customers, or the pseudonymous visit and order records kept for your reports and tests), the Merchant is the data controller and we act as a data processor acting on the Merchant’s instructions. The Merchant is responsible for having a lawful basis and a compliant privacy policy for collecting their Customers’ data.

  • For Roadmap posts (Section 2.8), we act as a data controller: we decide how the Roadmap shows them.

2. Information we collect

2.1 Information from your Shopify store

When you install the App via Shopify OAuth, we receive and store information necessary to operate the App, including:

  • Store identifiers and settings: your myshopify.com domain, and your store’s time zone and currency, so that reports count your store’s own days.

  • Your store’s Shopify session: the access scopes you granted and the access and refresh tokens used to call the Shopify Admin API on your behalf. The App uses Shopify’s offline access tokens, which carry no staff member’s name or email address, so the App stores none.

The App requests the following access scopes and uses them only for the stated purpose:

  • write_online_store_pages: Create, update, and delete the Online Store pages of the landing pages you publish.

  • write_themes: Write, update, and remove the App’s own theme files (their names contain flunnel) in your published theme so published pages render. When you publish a page as your store’s home page, password page or page of all collections, the App replaces that theme template (templates/index.*, templates/password.* or templates/collection.*) with the page, keeps the theme’s own file in its database, and puts that file back when the page leaves the role. The App also reads a few of your theme’s settings files (such as config/settings_data.json and templates/product.json) to match your theme’s look and to see whether the App’s theme blocks are turned on; it changes no other theme file.

  • write_files: Upload media (images and video) used by your pages to your store’s Shopify file storage.

  • write_app_proxy: Expose the public storefront endpoints used by the sign-up forms and by page, deal and A/B test measurement.

  • write_pixels, read_pixels: Install and manage the App’s web pixel.

  • read_customer_events: Let the App’s web pixel receive storefront events (page views, add to cart, checkout started, checkout completed, and the App’s own deal and click events) for your reports and tests.

  • read_orders, read_all_orders: Verify an order attributed to an A/B test and read its subtotal; record each order’s ID, sales channel, amounts, and the lines a deal put in it for your deal and offer reports; and read your past orders to recommend deals (read_all_orders lets that read go back further than 60 days). For deal recommendations the App reads each order’s customer ID only to group one customer’s orders while the recommendation is computed, and never stores it. The App never requests a Customer’s name, email address, phone number, or shipping or billing address from an order.

  • write_orders: Add the tag Flunnel Bundles to the orders a Flunnel deal sold.

  • write_checkout_extensions_apis: Show your one-click offer after payment, before the thank-you page, and, when a buyer accepts it, add the offered product to that buyer’s order through Shopify’s post-purchase changeset.

  • write_discounts: Create and remove the welcome discount codes your sign-up forms hand out and the discounts your deals use.

  • read_products: Show and keep up to date the product names, images, prices and stock your pages and deals display, and, under Kits & transfer, read your products (their variants, media, custom data, collections and theme template) when you export them, the products a file names when you import it, and the products whose handle, SKU or title matches a kit’s products when you install a kit.

  • read_customers: Check whether a sign-up’s email address already belongs to a Shopify customer (and that customer’s email marketing state) before saving the sign-up, and read the customer ID on orders as described above.

  • read_legal_policies: Read your store’s shipping and refund policies to write the store facts in your email programme.

  • write_products: Point a product at the page you publish as that product’s own page, apply product text you approve, and store a deal’s rule on its product; and, when you import a product file under Kits & transfer, create or update its products (their variants, media, custom data and the definitions it needs, theme template and manual collections), and put back a theme template the import changed when you undo the import.

  • read_locales: Read your store’s published languages for deal wording and page translation.

  • read_locations: Read your store’s locations (their names and IDs) so that a product file’s stock columns match them, when you import a product file or export products under Kits & transfer.

  • write_inventory: Set a variant’s available quantity from a product file’s stock columns when you import it (an existing variant only at locations where it is already stocked), read which locations stock your existing variants that the file names when you import a file, and read the quantities when you export products with stock per location under Kits & transfer.

  • write_publications: Publish the products you import to, or remove them from, the sales channels the file sets (a new product that is not a draft or archived, whose row names no channel and does not mark it unpublished, goes on your Online Store and Point of Sale); read your store’s sales channels when you import a product file or filter an export by channel, and each product’s sales channels when you export products with them, under Kits & transfer.

The following scopes are optional. The App asks for each one only when you use the feature that needs it:

  • read_online_store_navigation: Check, for the Get started guide, whether a live page is linked in your store menu.

  • write_customers: Save sign-ups as Shopify customers who accept email marketing (see Section 2.3).

  • read_reports: Read your store’s own aggregated figures from Shopify (such as total sales, average order value and sessions) for the App’s analytics screens, once you click “Show store figures” (see Section 2.6).

2.2 Information you provide to the App

  • Email platform connection. You may connect your Klaviyo account through Klaviyo’s own sign-in (OAuth); you do not give the App an API key. The App stores the connection’s tokens server-side, uses them only to build and run the email programme you set up and to add your sign-ups to your lists, and deletes them when you disconnect under Integrations. It also keeps your Klaviyo account’s ID and name, saved when you connect, and the account’s default sender email, which an email programme build reads from Klaviyo and keeps in that build’s record. Disconnecting or uninstalling keeps these (a reconnect replaces the ID and name), and shop data erasure (Section 6) deletes them. (AI content generation runs on the App’s own system API keys; you do not provide AI provider credentials.)

  • Google Analytics connection. You may enter your GA4 measurement ID and a Measurement Protocol API secret under Integrations. The App stores the measurement ID and an encrypted copy of the secret (only its last four characters are ever shown), uses them only to send the clicks on the page elements you track to your own GA4 property, and deletes both when you remove them or uninstall the App.

  • Page content and briefs. Product details, offers, target persona, copy instructions, design preferences, generated pages, translations, email content, templates, custom code you add to a page or to your store, and version history that you create in the App.

  • Billing and credit records. Your subscription plan and AI credit balance and usage. Payments are processed entirely by Shopify Billing; we never receive or store your payment card or bank details.

  • Your answer after a plan change. After you downgrade or switch to Free, the App may ask one optional question about why. If you answer, it stores the reason you picked from a fixed list, the two plans and the time; it asks for no text and no personal details. We use the answers only to understand why stores change plans and to improve the App.

  • Plan picks. When you pick a plan on Plans & pricing, the App records the plan you picked, the plan the page suggested (if it suggested one) and the time. It records the pick before any Shopify approval page, so a pick counts even if you never approve the charge. It holds no personal details. We use these records to learn which plans stores choose, and to check that an answer about a downgrade (above) follows a downgrade you picked. They are kept while the App is installed and deleted with the rest of your store’s data at shop data erasure (Section 6).

  • Product files. When you import or export products under Kits & transfer, the App keeps the file on that import’s or export’s row in your import and export history: a compressed copy of each file you export or import, so you can download it again, and, for an import, a plain-text copy that the import’s check and run read and, when the file moves a kit between stores, that kit. The history keeps the compressed copies of your store’s latest 100 files: when you export products, the App removes the older ones, and their rows stay. The plain-text copy and the kit are kept until shop data erasure. When you upload a new file before running an earlier checked one, the App removes the earlier one’s files. Shop data erasure (Section 6) deletes them all.

2.3 Customer (buyer) information collected through sign-up forms

The App’s sign-up forms (the pop-up on a landing page and the storefront-wide pop-up) accept a sign-up only while your store has Klaviyo connected. When a Customer submits one, the App receives:

  • The Customer’s email address.

  • The landing page handle the form was submitted from (none for the storefront-wide pop-up).

  • The pop-up’s reading of the Customer’s privacy choice (written to one debug log line, without the address) and its bot check fields; neither is saved in the database.

With that address the App does the following:

  • Stores a welcome code record (only when your store offers a welcome discount). The App stores the Customer’s email address (lowercased) with the discount code it handed out, the code’s Shopify discount ID, the percentage, the expiry date (none for a storefront-wide pop-up code), the sign-up date, and which form it came from. The record ensures that one email address holds at most one live code, gives the same code back on a repeat sign-up, and backs the sign-up list in your Settings. Retention is described in Section 6.

  • Hands the address to your Klaviyo account (through your connection): it adds the Customer to your welcome list (and to the list you chose for landing-page sign-ups), and writes to the Customer’s Klaviyo profile the welcome code with its expiry and, where your page has sign-up wording, that wording. For the storefront-wide pop-up it also records a sign-up event.

  • Saves the address as a Shopify customer (only while you have granted the optional write_customers scope): a new address becomes a Shopify customer subscribed to email marketing at the single opt-in level, with the time of the sign-up as the moment of consent, tagged flunnel and popup. For an address Shopify already knows, the App changes the marketing state to subscribed only from “not subscribed” or “unsubscribed”, and adds the same tags. You manage these customers in your Shopify admin like any other.

  • Identifies the browser to Klaviyo on Flunnel landing pages, only after a successful sign-up and only when the Customer has allowed both marketing and analytics through Shopify’s customer privacy settings: the page then loads your Klaviyo account’s on-site script, which sets Klaviyo’s own cookie on your storefront. A visitor who never signs up is never identified.

  • Limits repeated sign-ups: the Customer’s network address is held in the server’s memory for up to 10 minutes to cap sign-ups per address and per store. It is never written to the database; a log line carries only a hash of it.

The App writes every use of a Customer’s address (the welcome code record read or written, the hand-off to Klaviyo, the save as a Shopify customer) to its access log as a keyed hash, never the address itself (see Section 7). The sign-up path writes no Customer email address into the App’s server logs.

The pop-ups also keep functional markers in the Customer’s browser storage (whether the pop-up was already submitted or dismissed, and whether the visitor arrived from one of your emails). These markers stay in the browser and are sent nowhere.

2.4 Visitor and order data collected for your reports and tests

The App measures how visitors move through your pages, deals, post-purchase offers and A/B tests so it can report what works. For this purpose the App collects:

  • First-party cookies on your storefront, set only after the visitor allows analytics through Shopify’s customer privacy settings: _flunnel_experiments (the variant a visitor was assigned in a page test, 365 days), _flunnel_visitor_id (a randomly generated pseudonymous identifier, 365 days), _flunnel_session_id (a randomly generated session identifier, 30 minutes from the last view of a tested page), _flunnel_time_on_page (a short-lived engagement handoff, 30 minutes), and _flunnel_arms (the version of a deal or offer test the visitor was assigned, 365 days). These cookies are scoped to your storefront. Apart from the Klaviyo identification described in Section 2.3, the App’s code sets no third-party or cross-site tracking cookies.

  • Storefront events through a Shopify web pixel: page views of Flunnel pages and of product and collection pages, add to cart, checkout started (the lines a deal put in the cart), checkout completed (the order ID), the App’s deal box events, and clicks on the page elements you chose to track. Each event comes with Shopify’s pixel client ID. The App does not store that ID: it stores a keyed hash of it (the first 16 bytes of an HMAC over your store and the client ID), which names no one.

  • Records the App keeps from those events and from Shopify’s order webhooks, none of which holds a name, email address, phone number, postal address or IP address:

    • A/B test sessions: the random visitor and session identifiers, device type (derived from the browser), traffic source (the referring site), UTM parameters, page view and add-to-cart counts, time on page, and when the visitor reached checkout.

    • A/B test orders: the Shopify order ID and its subtotal (amount and currency), used to verify the order and report revenue per variant.

    • Deal and page visits: the keyed browser hash per deal or page and store day, the deal’s surfaces and tiers, and the orders such a browser completed.

    • Deal order ledger: every order’s ID, sales channel, amounts, the lines a deal put in it, and their refunds. Shopify’s order webhooks deliver to the App only a fixed list of order and line fields, with no customer field.

    • Post-purchase offer records: the checkout’s reference ID (a pseudonymous ID from Shopify), the offer shown, accepted or declined, and the accepted product and amount.

    • Element click counts: one count per tracked element and store day, with no visitor identifier.

    • Event IDs: kept briefly so that a repeated event is counted once.

If you turn on tracking for a page element, the page also reports that click to the analytics or advertising tags you have installed on your storefront, under your own accounts. The App itself keeps only the click count and, when you connect Google Analytics, sends each such click to your GA4 property: the event and parameters you chose, the page’s title and section and a random event ID, with no visitor identifier, no IP address and advertising consent denied.

Consent. The App’s web pixel is registered under Shopify’s analytics consent category with sale of data disabled. In regions where consent is required, Shopify withholds the pixel until the visitor grants analytics consent, and Shopify’s consent management applies automatically.

Content your published pages load from other providers. These requests come from the visitor’s browser on every view, before any consent choice, and like any web request they give the provider the visitor’s IP address, browser user agent and your store’s web address:

  • Fonts: a published page, and a deal box styled with a font of its own, load their fonts from Google Fonts (fonts.googleapis.com, fonts.gstatic.com).

  • Icons: a page that shows icons loads the Font Awesome icon set from your store’s own Shopify domain; only if that copy is missing does it fall back to cdnjs, run by Cloudflare (cdnjs.cloudflare.com).

  • Styles: a page whose styles the App could not prepare when it was last published, or that has not been published again since the App began preparing them (September 2026), loads Tailwind’s style compiler from jsDelivr (cdn.jsdelivr.net).

  • Videos: a Video element loads YouTube’s player from its privacy-enhanced host (youtube-nocookie.com) or Vimeo’s player with do-not-track (dnt=1) when the visitor scrolls near it. Those providers’ own terms govern any cookies or storage their players use.

  • Your own media links: an image or video you add from another web address loads from that address.

2.5 Email platform checks

When you build or check your email programme, the App reads recent “Placed Order” events from your connected Klaviyo account to confirm which store feeds it. Those events can carry a Customer’s name and address. The App keeps only your store’s web address from them and stores nothing else; each such read is written to the access log with its count.

2.6 Store analytics

To show your store’s own figures beside the App’s reports, the App reads aggregated store reports from Shopify through Shopify’s ShopifyQL API (shopifyqlQuery, with the read_reports scope). Shopify grants that API only to apps approved for protected customer data at Level 2, which covers Customer names, addresses, phone numbers and email addresses. The App reads aggregate figures only (such as totals per day), never an individual Customer’s name, phone number or address, and stores none of them.

2.7 What we do not collect

  • We do not collect or process payment card or financial account data.

  • We do not request Customer names, phone numbers, or shipping or billing addresses from Shopify, and we do not store them. The only Customer contact detail the App stores is the email address of a sign-up that received a welcome code (Section 2.3).

  • We do not track visitors across sites.

2.8 Roadmap posts

If your store uses the Roadmap inside the App, we keep what it posts there: feature requests (a title, details and up to 3 pictures), comments and replies (up to 1,000 characters and up to 2 pictures each), and your votes, follows and reports. The App re-encodes each picture, which removes its camera and location data. We use these to run the Roadmap and to plan the App.

Other stores that use the App see your comments, replies and approved pictures, under “Store” and a short code, or under your store’s name if you choose to show it. Your requests, votes, follows and reports are seen only by your store and our team; other stores see only how many there are: an item’s votes, the stores that asked for it, and its followers. When our team approves a request, it becomes an item that every store sees, without your store’s name. Our team sees your store’s name and plan. The writer of a comment is not told who reported it.

Do not post personal data about your Customers or anyone else. If a post holds it, we hide or delete it. If your data appears in a Roadmap post, write to hello@flunnel.ai and we will remove it.

2.9 Our website

When you write to us through the form at flunnel.ai/contact-us, we receive the name, email address, phone number and message you enter, and we use them only to answer you. The website runs on a hosted website builder (the website’s host), which receives the form and counts visits with its own site analytics. The website also loads a stylesheet from unpkg (unpkg.com). Apart from that analytics, the website runs no tag manager and no tracking pixel.

3. How we use information

We use the information described above to:

  • Authenticate the App and operate it within your Shopify admin.

  • Generate pages, translations, product text and email content using the App’s AI providers.

  • Publish, update, and remove pages and their supporting theme files.

  • Run your sign-up forms: hand out welcome codes, add sign-ups to your Klaviyo lists and flows, and save them as Shopify customers when you allow it.

  • Build and check the email programme in your connected Klaviyo account.

  • Measure your pages, deals, offers and A/B tests: assign visitors to variants, count visits and funnel milestones, attribute orders, and report aggregate results (conversion, revenue per variant, deal and offer revenue) to you. We use this data solely to provide these reports to you, never for our own marketing or advertising, and never to build cross-store or cross-site profiles.

  • Recommend deals from your store’s order history.

  • Run the Roadmap inside the App: show your store’s posts to other stores, review them, and plan the App from the requests and votes (Section 2.8).

  • Manage your subscription plan and AI credit balance (payment processing is handled by Shopify Billing).

  • Provide support, maintain security, debug issues, and improve the App.

  • Comply with legal obligations.

We do not sell personal information, and we do not use Customer data for our own marketing.

4. Third-party services and sub-processors

The App relies on the following service providers. Data is shared with them only as needed to provide the App:

  • Shopify: App platform, authentication, Admin API, web pixel, and webhooks. Data shared: store identifiers, access tokens, page and theme data, discount codes, and the sign-ups the App saves as Shopify customers.

  • Render (application hosting): Runs the App server. Data shared: all processed data in transit.

  • Supabase (database hosting): Stores App data. Data shared: store records, settings (including the encrypted system AI keys, your Klaviyo connection’s tokens and your Google Analytics connection’s encrypted API secret), briefs, generated pages and emails, welcome code records, the pseudonymous measurement records, the Roadmap’s posts and pictures (Section 2.8), and the access log.

  • Anthropic, OpenAI, and Google (AI providers): Generate page, translation, product and email content. Data shared: the content brief, page content and product context you submit, sent using the App’s own system API keys. No Customer or visitor records are sent to AI providers.

  • Klaviyo: Email list subscription, email flows and delivery, through your own Klaviyo account. Data shared: Customer email addresses, the sign-up’s profile properties (welcome code, its expiry, and your page’s sign-up wording), and generated email content.

  • Google Analytics (only when you connect your own GA4 property under Integrations, see Section 2.2): Receives, from the App’s server, the clicks on the page elements you track, as events in your own GA4 property, with no visitor identifier and no IP address, and with advertising consent sent as denied.

  • Google Fonts, cdnjs (Cloudflare), jsDelivr, YouTube and Vimeo (content providers of your published pages, see Section 2.4): Serve the fonts, the icon set, the style compiler and the video players your pages show. Data shared: each visitor’s IP address, browser user agent and your store’s web address, sent by the visitor’s browser when a page loads them. The App’s server sends them no Customer or visitor data.

  • Our website’s host (a hosted website builder, see Section 2.9): Hosts flunnel.ai, receives what you enter in its contact form, and counts visits with its own site analytics. Data shared: what you enter in the form, and each visitor’s IP address and browser user agent, sent by the visitor’s browser.

  • unpkg (a content provider of our website, see Section 2.9): Serves a stylesheet the website loads. Data shared: each visitor’s IP address, browser user agent and the website’s address, sent by the visitor’s browser.

When you connect your Klaviyo account, your use of Klaviyo is also governed by their terms and privacy policies.

5. Data sharing and disclosure

We do not share personal information except:

  • With the sub-processors listed above to provide the App.

  • With other stores that use the App: what your store posts on the Roadmap, as Section 2.8 describes.

  • To comply with law, legal process, or a lawful government request.

  • To protect the rights, property, or safety of us, our users, or the public.

  • In connection with a merger, acquisition, or sale of assets, subject to this Policy.

6. Data retention and deletion

  • While installed: we retain your store data for as long as the App is installed so it remains available to you, except where a shorter period is set below. Apart from A/B test sessions, which a daily job also deletes, the clean-ups below are not on a timer: each runs in the background when the App next does related work for your store (a sign-up, an incoming event, opening the related screen, or a restart of the App), so a record can stay past its period until that run.

  • Welcome code records: a landing-page code is deleted from its Shopify discount, and its record from our database, once it has expired; the clean-up runs with later sign-ups on your store. An older code that has a Shopify discount of its own (codes made before October 2026) goes, with its discount, 30 days after it expired. A storefront-wide pop-up code never expires, so its record is kept while the App is installed, until a Customer data erasure request or shop data erasure (below) deletes it.

  • A/B test sessions: an ended experiment is reported from an aggregated snapshot that contains no per-visitor records. Once the experiment has been ended for 30 days and its snapshot is saved, its raw per-visitor session records are permanently deleted by a job that runs daily for every store, or sooner when you open the A/B tests list. A/B test order records (order ID and subtotal) are kept to back the experiment’s revenue report for as long as you keep the experiment.

  • Deal and page visits: the keyed browser records are deleted after 90 days, together with the order links no remaining visit uses; the daily totals they leave behind hold no browser key.

  • Element click counts: deleted after 90 days.

  • Post-purchase offer request log: deleted after 400 days. Post-purchase offer records and the deal order ledger are kept while the App is installed.

  • Plan change answers: kept while the App is installed, through an uninstall and a reinstall, and deleted with the rest of your store’s data at shop/redact.

  • Roadmap posts: kept until your store or our team deletes them, or until shop data erasure. At shop/redact we delete your store’s Roadmap requests, comments, pictures, votes, follows, reports and short code. An item our team made from your request stays, without your store’s name. Where another store or our team replied to one of your comments, a “Comment deleted.” line with no words and no link to your store stays, so the replies keep their place.

  • Access log: deleted after 400 days (see Section 7).

  • On uninstall: we mark your store as uninstalled, delete your Shopify session and access tokens, and delete your Google Analytics connection (the measurement ID and the encrypted API secret). Your pages and other App data are retained temporarily so they can be restored if you reinstall.

  • Shop data erasure (shop/redact): approximately 48 hours after uninstall, in response to Shopify’s mandatory compliance webhook, we revoke your Klaviyo connection and permanently delete all of your store’s data from our database, including settings, the Klaviyo connection’s tokens, welcome code records, all measurement records, and the access log rows of your store.

  • Customer data requests (customers/data_request, customers/redact): we support Shopify’s mandatory customer data webhooks. On a data request, we find the records the App holds for that Customer (the welcome code record by email address; the A/B test order and its linked session, the deal and page visit links and visits, and the deal order ledger rows by the orders Shopify names) and provide them to you through support so you can fulfil the request. On a redact, we permanently delete those same records. The post-purchase offer records are kept, because their checkout reference ID names no one. Sign-ups held in your Klaviyo account and the Shopify customers the App saved for you are managed by you, as the controller, in Klaviyo and in your Shopify admin.

You may also contact us at hello@flunnel.ai to request access to or deletion of your data.

7. Data security

We implement reasonable technical and organizational measures to protect information, including:

  • Encryption in transit using TLS/HTTPS for the App’s admin and storefront endpoints.

  • Application-level encryption (AES-256-GCM) for the system AI keys and your GA4 API secret, the secret under a key of its own (ciphertext only; full keys and secrets are never returned to the browser).

  • Strict multi-tenant data isolation so each store can access only its own data.

  • Pseudonymization of measurement data (random visitor identifiers and keyed browser hashes; no direct identifiers stored).

  • An access log: each use of a Customer’s email address (a sign-up’s welcome code record, its hand-off to Klaviyo, its save as a Shopify customer, the Settings sign-up list, the expired-code clean-up), each order read that names customers, each read of your Klaviyo order events, and each customer data request or erasure Shopify sends is recorded with who acted, what was done, why, and when. Measurement events, order webhooks and the other clean-ups are not recorded in it. The log holds a keyed hash of an email address, never the address, cannot be changed once written, and is kept for 400 days.

  • Restricted access to production systems.

No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

8. International data transfers

The App is hosted on infrastructure located in Singapore (Render and Supabase), and data may be processed in other countries where our sub-processors operate. Where required, we rely on appropriate safeguards for international transfers.

9. Your rights

Depending on your location, you (and your Customers, via the Merchant as controller) may have rights to access, correct, delete, or restrict the processing of personal data, and to data portability. Requests can be made to hello@flunnel.ai. For Customer data, please direct requests to the relevant Merchant; we will assist the Merchant as their processor.

This Policy is intended to support compliance with applicable laws including the GDPR and CCPA/CPRA.

10. Children’s privacy

The App is intended for use by businesses and is not directed to children. We do not knowingly collect personal data from children.

11. Changes to this Policy

We may update this Privacy Policy from time to time. We will revise the “Last updated” date above and, where appropriate, provide additional notice. Continued use of the App after changes take effect constitutes acceptance of the updated Policy.

12. Contact us

If you have questions or requests regarding this Privacy Policy or your data, contact:

OMNIX COMMERCE PTE. LTD.
68 Circular Road, #02-01, Singapore 049422
UEN 202613421M
Email: hello@flunnel.ai
Website: https://flunnel.ai