Skip to content
Ominity Assistant

Your business, understood. Create content, uncover insights, and take action with AI. Discover the assistant

OminityOminity

Content & commerce

Content managementManage content for every experience.Content models & blueprintsBlueprints, components, and custom types.CommerceProducts, orders, and connected channels.SubscriptionsBuild recurring business.BookingsSessions, services, and eligibility.

AI & business logic

Ominity AssistantUnderstand your data and act on it.AI generation & translationPrepare content and translations.Visual automationsConnected events, conditions, and actions.Business rulesExpress the criteria behind decisions.Custom fieldsExtend your business records.Traceability & audit trailsEvery action, decision, and outcome.DashboardsCharts, KPIs, comparisons, and shared views.

Make it yours

ExtensionsOfficial modules and custom integrations.Media & storageIncluded capacity or your own S3 storage.Mobile appYour business on the go.Headless APIYour frontend. Your stack.MCP serverBuild and configure with AI.
Explore all 29 platform features

By team

Marketing teamsCampaigns, content, and languages.AgenciesDistinct client experiences.Commerce teamsProducts, customers, and workflows.SaaS foundersIdentity, customers, and subscriptions.DevelopersYour stack and your integration.

By project

Marketing websitesPages built around your brand.Complex websitesStructured, connected information.WebshopsA headless purchase experience.Subscription businessesServices and recurring relationships.Web & mobile applicationsInterfaces with business context.

At scale

Enterprise teamsActions, decisions, and audit trails.Product storiesSee the implementation decisions.All solutionsFind the project you have in mind.
Explore solutions

Start building

QuickstartMake the first connection.APIContent and commerce operations.Integration SDKsTypeScript, PHP, Next.js, and Laravel.Starter templatesStart with the Next.js storefront.

Context & capabilities

Authentication & accessWho is acting and what can they do?Customer contextMake the selected business explicit.MCP serverConnect compatible AI tools.Custom extensionsYour project-specific capabilities.

Explore

Developer documentationBrowse the integration guides.Developer toolkitChoose your starting point.Plan an integrationGive each part a clear responsibility.
Meet the developer toolkit
Case Studies

Learn

Developer docsIntegration guides and architecture.Platform guidesPractical steps for real work.GlossaryClear definitions in context.

Explore

RoadmapPlanned features and platform directions.Platform notesIdeas for your next project.Case studiesProduct stories and project highlights.All resourcesFind a useful next step.

Work with us

Become a partnerIntroduce your implementation craft.Find a partnerIntegration and extension development.CareersBring your craft to the conversation.Contact the teamTell us what you have in mind.
Explore resources
Pricing

Cookie Policy

Cookies, local storage, and similar technologies on Ominity websites, services, and apps.

Version 1.0 · Effective 11 October 2026
Privacy PolicyCookie PolicyTerms & Conditions
On this page
01Who we are and what this Policy covers02Cookies and similar technologies03Categories and purposes04Information and consent05Changing or withdrawing your choice06Server-side measurement07Mobile and desktop apps08Retention and device controls09Personal data and your rights10Changes and contact

1. Who we are and what this Policy covers

Ominity is operated by Connexeon BV, trading under the brands Ominity and Wizzou, with registered office at Emiel Banningstraat 47 / 5, 2000 Antwerp, Belgium. Our enterprise number is 0867.496.536 and VAT number is BE0867496536. Contact us at [email protected].

This Policy covers cookies and similar technologies on Provider-operated Ominity websites and services and in official applications for iOS, Android, macOS, Windows, and Linux, where available. Coverage of a platform does not mean that an app for it has already been released.

Read this alongside the Ominity Privacy Policy. Customer-operated websites, webshops, portals, and instances can use different technologies. Their operators are responsible for their own notices and consent controls.

2. Cookies and similar technologies

Cookies are small pieces of information stored by a browser. Session cookies expire with the relevant session; persistent cookies remain until their configured expiry or deletion.

Similar technologies include local storage, session storage, webview storage, tags, pixels, SDK identifiers, and other methods of storing or accessing device information. Applicable rules continue to apply when a mechanism is described as cookieless or server-side.

Technology can be operated by Connexeon or a service provider. Device-storage duration is distinct from retention of data already transmitted to a server. Clearing a cookie does not erase an account, invoice, or previously collected server record.

3. Categories and purposes

Categories depend on the service, instance, platform, and enabled features. This explanation does not mean that every category is active on every service.

CategoryPurposeChoice and duration
Necessary sessions and securityMaintain requested authenticated access, route a connection, and protect the service against misuseConsent is not required only where the legal necessity exception applies. Storage lasts for the session or limited period necessary for the requested function.
Consent choicesRemember acceptance or rejection of optional purposesDuration must be proportionate to respecting and recording your choice. A material change can require an earlier new choice.
Interface preferencesRemember selected presentation or functionality preferencesA preference necessary for an explicit request can fall within the necessity exception. Other preference storage requires consent where applicable.
Analytics and diagnosticsMeasure visits, interactions, referrals, conversions, errors, or performanceOptional measurement and corresponding device access require prior consent where applicable. Necessary fault or security investigation is assessed separately.
Advertising and marketingAttribute advertising conversions or support marketing audiencesUsed only with the required consent. Applicable consent information identifies enabled purposes, recipients, and lifespans.
App and instance connection storageRemember instance addresses, local preferences, and requested sign-in informationDuration depends on the platform and requested function. Removing local information does not erase server-side accounts.

Necessary technologies are limited to providing a communication or service you explicitly request and are not repurposed for advertising. Exemption from device-storage consent does not remove the need for a lawful basis for personal-data processing.

First-party analytics are not automatically exempt from consent. A diagnostic feature is not necessary merely because it is useful. Optional tracking remains optional inside apps as well as websites.

4. Information and consent

Where optional technologies are deployed, prior informed consent is required before activation. The applicable service-specific consent information identifies the technologies, purposes, recipients, and storage lifespans and supplements this Policy. It must describe the actual configuration rather than a generic supplier configuration.

Consent is an active choice. Continuing to browse, accepting the Terms, or signing into an account does not authorise optional tracking. Optional purposes are not preselected. An interface offering acceptance must also provide a clear refusal and a way to manage choices.

Refusing optional tracking does not prevent basic access. Blocking storage necessary for a requested authenticated service can prevent that function from working.

Choices can be browser-, device-, site-, or instance-specific. Consent on Wizzou's website is not assumed to authorise tracking on Ominity or a connected customer's instance.

5. Changing or withdrawing your choice

Use the consent or privacy controls presented by the relevant website or app to change your choice where optional technologies are enabled. You may also contact [email protected] to withdraw consent or request help identifying the relevant controls. Identify the service and, where relevant, your account or instance; do not send your password.

Withdrawal stops future processing based on that consent without making earlier lawful processing unlawful. Optional first-party identifiers are removed or disabled where technically possible. Third-party cookies or device storage may also need removal through browser or operating-system controls.

New purposes or materially different recipients require a new choice where applicable. Updating this Policy does not itself provide consent.

6. Server-side measurement

Where enabled, server-side measurement can send an event to a configured endpoint and then forward it to a relevant recipient. This does not remove consent requirements for the underlying collection, device access, or marketing purpose.

A first-party domain, proxy, or hashed identifier does not automatically make personal data anonymous. Consent signals must be respected across the collection and forwarding chain. Necessary operational logs are distinguished from optional analytics and advertising.

This Policy does not assume that a measurement provider used on a separately operated Wizzou website is also active on Ominity.

7. Mobile and desktop apps

Apps can use browser or webview sessions and local storage to connect to selected instances. Authentication and connection information supports the requested access. Storage behaviour differs by operating system, app version, and instance operator.

A customer-managed instance can load its own content and technologies. Connecting does not grant blanket consent to its optional tracking. Its operator must provide the appropriate notice and choices.

iOS push notifications use Apple Push Notification service (APNs); Android push notifications use Google Firebase Cloud Messaging (FCM). The token and related delivery information are described in the Privacy Policy. Naming FCM for push delivery does not imply that other Firebase analytics or advertising features are enabled.

Notification permission controls notification delivery; it is not consent to optional analytics, advertising, microphone use, or unrelated device access. Other permissions must be explained and requested for the relevant function.

Clearing app or webview data can remove preferences or sign you out. Some operating systems retain secure-storage items or backups after uninstall. Uninstalling does not cancel a subscription or request server-side account deletion.

The app uses Sentry for diagnostics and error reporting as described in the Privacy Policy. Diagnostic information can include app and device details, error records, and technical event context. This is distinguished from optional advertising or usage tracking; any optional storage or tracking requiring consent remains subject to the choices described above. This statement does not assert that session replay or every other Sentry feature is enabled.

8. Retention and device controls

Device information is retained for the period appropriate to its disclosed function and configuration. Necessary storage expires or is removed when no longer needed. Optional storage is subject to its disclosed lifespan and withdrawal controls. Proportionate consent evidence can be retained separately where needed, without using that purpose to retain unrelated tracking data indefinitely.

Most browsers allow inspection, deletion, and blocking of cookies and website storage through privacy or site-data settings. Operating-system settings can provide app-storage, notification, and permission controls. Terminology and capabilities vary by platform.

Device controls supplement the service's consent choices. They do not automatically delete information already sent to a recipient. The Privacy Policy explains retention and rights for that information.

9. Personal data and your rights

The Privacy Policy explains our role, purposes, legal bases, recipients, international transfers, retention, and rights where a technology processes personal data. Optional tracking requiring consent is not justified solely by a general reference to legitimate interests.

Contact [email protected] to ask about a technology or exercise applicable access, correction, erasure, restriction, objection, or portability rights. Consent can be withdrawn at any time.

You may complain to the Belgian Gegevensbeschermingsautoriteit / Autorité de protection des données or another competent supervisory authority. See https://www.gegevensbeschermingsautoriteit.be/ or https://www.autoriteprotectiondonnees.be/.

10. Changes and contact

We update this Policy when relevant handling changes and show its version and effective date above. Changes requiring new consent are not activated solely on the basis of an earlier choice.

Questions about cookies, local storage, or tracking can be sent to [email protected].

What comes next?

OminityOminity

Your content.
Your commerce.
Your possibilities.

Platform

Platform overviewContent managementCommerceOminity AssistantSubscriptionsVisual automationsTraceability & audit trailsExtensionsAPI & integrationsMobile appPricing

Solutions

For marketing teamsFor agenciesFor developersFor commerce teamsFor SaaS foundersMarketing websitesMulti-channel webshopsWeb & mobile applications

Developers

Developer documentationAPIIntegration SDKsStarter templatesMCP serverCustom extensions

Work with us

CareersJoin the partner programFind an agency

Resources

RoadmapPlatform guidesGlossaryBlog postsCase studiesContact the teamMeet Wizzou
Instagram SoonYouTube SoonGitHubLinkedIn Soon
© 2026 Ominity. A product by Wizzou.
Privacy PolicyCookie PolicyTerms & Conditions

Let’s talk about
your next project.

Three quick questions to start the conversation.

What’s your name?
Where can we reach you?
What do you have in mind?
Your email app opens a draft at the final step. Nothing is sent automatically.Open your email draft