Privacy Policy

Ominity is operated by Connexeon BV, trading under the brands Ominity and Wizzou, with registered office at Emiel Banningstraat 47 / 5, 2000 Antwerp, Belgium.

• Enterprise number: 0867.496.536.
• VAT number: BE0867496536.
• Privacy contact: [email protected]. Please include “Privacy” in the subject.

This Policy explains what personal data is processed, why it is processed, who receives it, how long it is kept, and how you can exercise your rights. Personal data means information relating to an identified or identifiable person.

This Policy applies to the Ominity marketing website and Provider-operated account, identity, administration, API, billing, support, and related services. It also applies to official Ominity mobile and desktop applications for iOS, Android, macOS, Windows, and Linux, wherever we make them available.

Coverage of an operating system does not imply that an application for it has already been released. The same privacy principles apply to Free and paid plans.

The apps can connect to different Ominity instances, including customer-managed or third-party-managed instances. Those instances can have different operators. This Policy covers Connexeon's processing; the relevant organisation's notice covers its processing of its own users, customers, visitors, and tenant records. A separately branded Wizzou or Onetagger service has its own applicable notice unless it expressly refers to this Policy.

3.1 Where Connexeon is a controller

We act as a controller when we determine why and how personal data is processed for our own account administration, subscriptions, billing, security, support administration, recruitment, business communications, and lawful marketing activities.

An organisation may invite you to its instance and supply your name, email address, membership, and role. We may process that information to administer our direct service relationship where applicable. This does not make all tenant data our own controller data.

3.2 Where we process data for a customer

An organisation using Ominity usually controls the data it places in its instance and the purposes of its website, webshop, customer portal, bookings, analytics, and other business workflows. Where we host or access that data to supply the agreed Service, we generally act as processor under a data processing agreement and the organisation's lawful instructions.

If the organisation is itself a processor, we may be its subprocessor. Actual roles depend on the activity, not simply the name used in a contract.

If your question concerns an organisation's content, customer record, visitor tracking, booking, or payment workflow, contact that organisation first. We will help it fulfil its duties where required. You can also contact us if you do not know which operator is responsible.

For customer-managed deployments, tenant content can remain on infrastructure that Connexeon does not operate or receive. We may nevertheless receive licensing, feature-usage, support, or security information, or access data where authorised for support.

Data depends on the features you use and the service operator. We do not assert that every category below is collected from every user.

Tenant content can include files, content and translations, customer memberships, orders, products, subscriptions, bookings, eligibility data, affiliate records, forms, visitor events, and other custom fields. The organisation chooses what to collect and must provide the relevant notice. For example, a driver's licence date used by a booking operator is that operator's tenant data, not information every Ominity app user must provide to Connexeon.

We obtain data directly from you, through your use of the Service, from your organisation or its authorised users, from enabled identity and payment providers, and from publicly available business information where reasonably necessary for an enquiry or business relationship. Where legally required, we provide notice when data is received indirectly.

We use the appropriate legal basis for each purpose. Contract necessity applies only where processing is objectively necessary for a contract with the person concerned; an employee's use of an employer's subscription is not automatically a contract with that employee.

We assess the necessity and impact of legitimate-interest processing and can explain our balancing approach on request. We do not use a single blanket consent to justify all processing. Necessary service messages are distinct from promotional emails.

Where data is necessary to create an account, authenticate, issue an invoice, or fulfil a legal duty, we identify that requirement. Not providing it can prevent the relevant function. Optional marketing, analytics, or notification choices do not prevent core service access.

6.1 Connecting to an instance

The app is an administration companion for an existing, active Ominity instance. It does not offer account creation. You enter the instance address, which may be a dedicated Ominity subdomain such as tenant.ominity.com or the organisation's configured custom domain.

The app opens the instance's OAuth authorisation page. You sign in there with an existing Ominity administrator account and approve the app's requested access. The resulting authorisation allows the app to establish an authenticated session. Access remains subject to the instance operator, your administrator permissions, and the granted authorisation. Signing into one instance does not itself authorise access to another.

Authentication and service requests are directed to the selected instance and, where required for the relevant function, Provider-operated account, identity, or licensing services. Processing roles depend on which organisation operates the instance.

6.2 Local storage and authentication

The app can store instance addresses, selected preferences, session information, and tokens needed to maintain a sign-in. Storage and security controls depend on the operating system and the application version; this Policy does not promise identical hardware-backed storage on every platform.

Use the sign-out controls to end your app session. Other sessions or independently issued credentials may need to be revoked separately through the relevant account or instance controls. Uninstalling the app does not delete server-side accounts, revoke every independently issued token, or cancel a subscription. Some operating systems can retain secure-storage items or backups after uninstall.

6.3 Push notifications

The app uses Apple Push Notification service (APNs) for iOS push notifications and Google Firebase Cloud Messaging (FCM) for Android push notifications. No additional notification delivery platform is used.

Where notifications are enabled, processing involves the registration and routing information needed to deliver them, including a push registration token and its association with the relevant instance or account. Apple or Google, as applicable, handles the token, notification payload, and technical information needed for delivery through its service. These identifiers support delivery to an installation; they do not grant permission to access the Ominity instance. FCM is identified here for push delivery; this does not imply that other Firebase features, such as advertising or analytics, are enabled.

We minimise sensitive information in notification payloads, and the operating system may display previews on a locked device according to your settings. You can disable notification permission in system settings and, where available, the app's notification preferences.

6.4 Files and device permissions

When supported, selecting or uploading a file gives the chosen instance access to that selected file and its associated metadata. A system file picker need not imply unrestricted access to your photo library or filesystem.

Device permissions, such as camera, microphone, photo-library, location, or biometric access, are relevant only where a feature actually requests them. The purpose must be explained when access is requested. Running the app does not by itself authorise access to those device resources; permissions can be managed through the operating system.

6.5 Diagnostics and Sentry

We use Sentry for app diagnostics and error reporting to identify faults, investigate crashes, and improve reliability. Depending on the app version and diagnostic configuration, reports can include error messages, stack traces, event timestamps, app and operating-system versions, device characteristics, and technical context about the events leading to a fault. URLs, instance addresses, request context, and identifiers can appear where included in the report; diagnostic records can therefore contain personal data and are not assumed to be anonymous.

Diagnostic handling is limited to information reasonably necessary for the relevant reliability or security purpose and the applicable legal basis. Where an external Sentry service receives a report, Sentry processes the transmitted diagnostic information for that function. Necessary fault investigation is distinguished from optional usage analytics. Any device-storage access or optional tracking requiring consent remains subject to the relevant consent rules and the Cookie Policy. Naming Sentry does not imply that every Sentry feature, including session replay, is enabled.

You can contact [email protected] with questions about diagnostic handling or to exercise applicable privacy rights. Information you independently submit in a support report is also processed to investigate your request.

Using the assistant or automatic translation can send the prompt, content, relevant context, and associated metadata to the selected AI or translation provider. Requests should include only information needed for the operation. Your organisation controls enabled features and must have a lawful basis to submit third-party personal data.

Ominity currently uses direct APIs from OpenAI, DeepL, and Anthropic for enabled AI or translation features. Their processing is governed by the applicable business/API service arrangements and data-protection requirements. Primary hosting in Belgium does not mean that external AI or translation processing takes place exclusively in the EU. Consumer chatbot terms are not treated as the terms governing our API use.

Our authority to process tenant data is limited to the agreed service and the organisation's lawful instructions. Acceptance of the Terms does not authorise Connexeon to use tenant content or personal data to train general-purpose models for unrelated purposes. Any additional use requires a lawful basis and appropriate information. External providers' handling depends on the relevant API arrangements; enabling an AI feature is not a guarantee of zero provider-side retention.

Assistant proposals can be recorded with approvals, rejections, results, and execution history. Some tasks require approval; separately configured automations can run under the organisation's permission rules. AI-generated outputs and translations can be inaccurate and should be reviewed.

Ominity lets organisations create rules and automations, including eligibility, usage, or subscription logic. The organisation is responsible for disclosing any profiling or solely automated decision that affects its users and for satisfying applicable safeguards. For example, a tenant's automatic subscription upgrade is not automatically a Connexeon decision about every app user.

The Cookie Policy explains cookies, webview storage, pixels, tags, and similar technologies. Strictly necessary storage can support sign-in, security, or a service you explicitly request. Optional analytics and advertising technologies requiring consent are not activated merely because you keep browsing, accept the Terms, or use a server-side tagging setup.

You can change consent through the deployed cookie/privacy settings and control local storage through your browser or device. Blocking essential session storage can prevent sign-in. Refusing optional tracking does not remove access to the basic service.

Access is limited to those who need it for a disclosed purpose. Recipients can include:

• Authorised Connexeon personnel and bound service providers.
• Hosting, infrastructure, storage, security, and delivery providers.
• Identity, payment, email, support, AI, translation, and notification providers actually used.
• Analytics or advertising recipients enabled by the relevant consent and configuration.
• The organisation's administrators and other users allowed by its role and membership rules.
• Professional advisers and public authorities where legally necessary.
• A prospective or actual acquirer where necessary for a lawful business transaction, with confidentiality, minimisation, and appropriate safeguards.

Processors receive appropriate contractual instructions and safeguards. Independent providers, such as some payment providers or identity operators, have their own responsibilities and notices. A link to their notice does not remove our responsibility for the disclosure we make.

Information about service providers

The categories above describe the recipients relevant to the applicable service and enabled features. Personal data may be handled by contracted providers of encrypted backup storage, email delivery, support tooling, payments, and enabled AI or translation services, as applicable. These categories do not imply that every possible integration is enabled for every customer. OpenAI and Anthropic supply enabled AI processing, and DeepL supplies enabled translation, through direct APIs.

The suppliers confirmed for the following features are:

This identifies confirmed supplier brands, not a representation that every recipient or contracting legal entity has been individually listed. Infrastructure, encrypted backup-storage, and communication providers are described by their functions above. Supplier names alone do not establish EU-only processing. We do not publish individual support staff names or sensitive infrastructure configurations. Requests concerning actual recipients and applicable transfer safeguards can be sent to [email protected] and are handled in accordance with data-protection law.

Provider-operated Ominity instances and their databases currently run on servers owned and operated by Connexeon in Antwerp, Belgium. Provider-controlled hosting and backup storage remain within the European Union. Backups may be stored with external providers and are encrypted. Applicable recipient identification and transfer-disclosure duties remain in force; the supplier list above does not replace those duties. Production support personnel are currently located only within the EU. This does not establish that external email, AI, translation, push delivery, or diagnostics services process all data exclusively within the EU.

This describes the Provider's own hosting and backup storage. External AI, translation, support access, or enabled integrations need a separate location assessment and may involve processing outside the European Economic Area. Hosting the primary database in Belgium alone does not establish EU-only handling by every external supplier. Future infrastructure changes must respect the applicable contractual commitments and legal safeguards and are disclosed as required.

Where a transfer takes place, we use the mechanism applicable to the recipient and processing, such as an adequacy decision or standard contractual clauses with any necessary assessment and supplementary measures. A transfer to an entity relying on the EU-US Data Privacy Framework is treated as adequate only where that entity's valid certification and scope cover the transfer.

You may request information about actual processing locations or a copy of relevant transfer safeguards through [email protected]; confidential portions can be redacted where appropriate without concealing essential protections. A customer's independently chosen destination is subject to its own lawful-transfer responsibilities, alongside any duties applicable to us.

We keep personal data only as long as needed for the disclosed purpose and lawful obligations. Retention depends on the account, processing role, record type, security needs, and applicable claims or accounting requirements.

An unresolved invoice does not justify retaining all tenant content. A legal hold should be limited to relevant records. Data that has been effectively anonymised so that individuals are no longer identifiable is not retained as personal data; pseudonymisation alone is not anonymisation.

You can request deletion of a Connexeon-operated Ominity account by emailing [email protected] with the account email or identifier and the relevant instance. Do not send your password. We verify requests proportionately and explain any record we must retain and why.

Removing an instance from the app removes its local connection configuration; it is not necessarily a server-side account-deletion request. Signing out or uninstalling also does not delete the server-side account.

For an account controlled by your organisation or another instance operator, the request is handled with that operator as required. Removal of your access does not automatically erase another person's data, the organisation's invoices, or records it must lawfully retain. Where necessary, records can be reassigned, minimised, or anonymised rather than retained as an unnecessary full personal profile.

If you use several instances, identify whether the request concerns one tenant identity or a Provider-operated identity used across instances. We explain the effects before applying a deletion that would affect other access. An ownership transfer can be arranged where genuinely necessary, but deletion must not be obstructed through arbitrary administrative steps.

Deletion is distinct from cancellation of an organisation's subscription. We do not treat temporary suspension or freezing as completed account deletion. Necessary legal, fraud-prevention, or security retention is disclosed and limited; an indefinite exception is not used to keep all data.

Subject to the circumstances and applicable law, you may request access to your personal data, correction, erasure, restriction, and portability. You may object to processing based on legitimate interests. You may object to direct marketing at any time, including associated profiling, and that processing will stop.

Where processing is based on consent, you can withdraw it at any time as easily as it was given. Withdrawal does not make earlier lawful processing unlawful. If qualifying solely automated decisions are made, the applicable information and safeguards, including human intervention and contesting the decision, must be available.

Send requests to [email protected]. We may ask for proportionate information to verify identity or the scope of the request, especially where disclosure could affect others. We do not routinely require a full identity-document copy where a less intrusive method works.

We normally respond within one month. A lawful extension of up to two further months may apply for a complex or numerous request; we explain the extension within the initial month. Requests are normally free, subject only to the narrow legal exceptions for manifestly unfounded or excessive requests. We explain a refusal and available remedies.

For tenant data processed on an organisation's behalf, we forward or coordinate the request with that controller and assist it. That routing does not waive your rights.

We use measures appropriate to the processing risks and service scope, including controlled access, authentication, confidentiality, and documented operational security processes. We do not claim independent NIS2, CyFun, or ISO certification or CCB endorsement. This Policy does not promise continuous monitoring or a particular recovery objective unless separately agreed.

The Provider encrypts critical data and encrypts backups, including externally stored backups; Connexeon alone controls the backup encryption keys. This statement does not claim universal end-to-end encryption of all processing. Access to tenant data is limited to approved personnel with confidentiality duties and a legitimate need for access. Ordinary support access to an instance requires the requesting authorised customer's approval. Tenant isolation uses separate databases, containers, and credentials, and production facilities have physical access controls. Necessary incident handling or other lawfully authorised processing is distinguished from ordinary support access.

No internet service can promise absolute security. This is not a disclaimer of our legal duties. If a personal data breach requires notice to an affected organisation, supervisory authority, or individual, we provide the required notification under the applicable rules.

The Ominity administration service is intended for professional users and is not marketed as a service for children. We do not use this statement to deny rights to a minor whose data is actually processed.

Customers can operate their own lawful services for different audiences; they must assess the relevant children's-data, consent, and transparency obligations. Avoid submitting special-category or other sensitive data to Ominity or AI features unless the deployment, contractual arrangements, and lawful basis support it.

You can contact us at [email protected], but you do not have to contact us first before complaining to a supervisory authority.

In Belgium, the relevant authority is the Gegevensbeschermingsautoriteit / Autorité de protection des données, Drukpersstraat / Rue de la Presse 35, 1000 Brussels, Belgium. Information and complaint procedures are available at https://www.gegevensbeschermingsautoriteit.be/ and https://www.autoriteprotectiondonnees.be/.

You can also approach the competent supervisory authority in the country of your habitual residence, place of work, or alleged infringement, where applicable.

We update this Policy when processing changes and show its version and effective date. Material changes are communicated through a suitable channel before they apply where required. New consent is requested where necessary; a revised policy alone is not consent to a new optional purpose.

This Policy applies across the covered websites and released apps. Platform-specific notices and permission requests provide additional information about the features you use; they do not remove the rights described here.