1. Acceptance of Terms
By accessing and using exployt ("the Service"), you accept and agree to be bound by these Terms of Service. If you do not agree, please do not use the Service.
2. Description of Service
exployt is a multi-AI orchestration platform that allows users to manage and monitor multiple AI agents working on software development projects.
3. User Accounts
- You must provide accurate information when creating an account
- You are responsible for maintaining the security of your account
- You must be at least 18 years old to use the Service
- You are responsible for all activity under your account
4. Acceptable Use
You agree not to:
- Use the Service for any illegal, harmful, or immoral purpose, or in a way that harms others
- Attempt to gain unauthorized access to the Service
- Interfere with or disrupt the Service
- Reverse engineer or decompile the software
- Use the Service to develop competing products
5. Subscriptions and Payments
- Private, non-commercial use of the Service by an individual is free of charge and does not require a paid subscription (see § 6). Commercial use requires an appropriate commercial subscription, except where you are covered by the transitional free-commercial period for individuals (see § 6), a discretionary Free Commercial grant (see § 13.4), or another free arrangement we may offer from time to time
- Payment-provider payments, such as subscription charges and User Budget top-ups where offered, are processed by Stripe
- Subscriptions renew automatically unless cancelled
- Payment-provider refunds for subscription charges are handled according to Stripe's policies; project-license credits and refunds are handled under § 13.1 through § 14 and § 20
- We reserve the right to change pricing with 30 days notice
6. Free Private Use and Transitional Free Commercial Use for Individuals
- Private use is free. Private, non-commercial use of the Service by an individual is free of charge and does not require a payment method. Every account automatically receives this free non-commercial access on registration; no trial, expiry, or card is involved. This is our current offering and not a perpetual guarantee — we may change it with reasonable notice, but any change will not retroactively charge you for prior free private use.
- Transitional free commercial use for individuals. As a time-limited promotion, commercial use of the Service by an individual (Professional scope, as defined in Sections 12 and 13) is also free of charge until 1 September 2026. This transitional grant is applied automatically to every new account on registration. After that date, commercial use by an individual requires a Professional (or higher) subscription, while private, non-commercial use by an individual remains free.
- The transitional free-commercial period applies to individuals only (Professional scope); commercial use by a company or other organisation always requires the applicable Company or Enterprise subscription and is not covered by this promotion.
- We may additionally offer an optional trial of a paid tier. Any such trial is not a guaranteed entitlement; whether one is available, its duration, and its conditions are defined on the Pricing page and may be changed or withdrawn at our reasonable discretion. Where such a trial requires a payment method, that is stated at checkout, it is limited to one per person, creating multiple accounts to obtain additional trials is prohibited, we use device identification and risk assessment to enforce the one-trial-per-person policy, and after the trial period the subscription converts to a paid plan unless cancelled. If trial abuse is detected, we reserve the right to revoke the trial without notice and to permanently suspend the account, person, or company involved.
7. Intellectual Property
The exployt platform, including its software, user interface, website content, documentation, and other original materials, is protected by copyright and owned by exployt Software GmbH. Your code and projects remain your property.
8. Termination
We may terminate or suspend your account for violations of these terms. You may delete your account at any time through the account settings.
9. Disclaimer
The Service is provided "as is" without warranties of any kind. We do not guarantee uninterrupted or error-free service.
To the maximum extent permitted by applicable law, exployt Software GmbH is not liable for any damage of any kind — direct or indirect, material or immaterial — arising from the use of, or the inability to use, the software or any output it produces. Where mandatory law (in particular consumer-protection law) does not permit such an exclusion, our liability is limited to the minimum extent that law allows. Detailed limitations of liability are set out in our separate Liability Disclaimer.
9.1 Service Availability, Support and SLA
Support requests sent to office@exployt.ai or through product support/feedback forms receive an initial response within 24 hours. exployt cloud is needed for account creation, login/account management, billing, payment, subscription/license validation, Marketplace cloud actions, and fresh entitlement checks. Ordinary desktop project work is local-first: the desktop app keeps a signed entitlement snapshot with a maximum 72-hour grace window, so transient server outages do not immediately remove access to subscription-locked features.
If an exployt cloud outage occurs, our operational commitment is to restore the account/subscription service before that 72-hour grace window expires. The Service remains provided "as is" and without service credits unless a separate written enterprise agreement says otherwise. When a product support, feedback or bug-report flow can include diagnostic data, the flow shows you what will be sent, asks for confirmation, and submits only the data you approve.
9.2 Security, Enterprise Use and Certifications
Security and compliance information is published on the Trust & Security page, /llms.txt, /trust.txt, /security.txt, and /faq-security.txt so that human reviewers and AI systems can find the same answers.
As of July 8, 2026, exployt does not claim ISO 27001 certification, SOC 2 Type I, SOC 2 Type II, or an equivalent external security certification or audit report. We are preparing the control documentation, risk assessment, access-review evidence, incident-response evidence, vendor review, and management-review material needed for an ISO 27001 or SOC 2 readiness/audit process.
9.3 DPA, Subprocessors and Data Residency
Business and enterprise customers can request a Data Processing Agreement (DPA) by contacting office@exployt.ai. We are preparing a public DPA package and will publish it when it is ready. The DPA is intended to document controller/processor roles, confidentiality, technical and organizational measures, subprocessor use, deletion/return after termination, and cross-border transfer safeguards.
The primary production web service is hosted on Microsoft Azure in the West Europe region (Netherlands). Current service providers for the public website and account service include Microsoft Azure, Stripe, Resend, MaxMind offline geolocation data, and optional Google Analytics 4 / Microsoft Clarity website analytics where enabled and consented where required. Customer-selected AI providers, Git services, tools, plugins, connectors, OpenRouter, and local Ollama models used by the desktop app are chosen or configured by you and are not exployt cloud subprocessors for local project content.
9.4 Data Export, Deletion and Exit
Local project files, source code, local project databases, local AI-provider API keys, local credentials, and local agent history remain under your control on your machine during ordinary desktop-app operation. The project database is a SQLite database stored under the project's .exployt folder; when local database encryption is not enabled, it can be inspected or exported with ordinary SQLite-compatible tools. exployt also provides export/import flows for workflows, settings sets, and many configuration assets such as agent/workflow settings.
Project content leaves that local boundary only through explicit user actions: you select a cloud AI provider or external tool and send task context to it, you publish selected files and metadata as a Marketplace item for sharing or sale, or you submit a support/bug report after preview and confirmation. The Terms do not restrict you from using your own local project data with other software. For cloud account data, billing data, support records, and other personal data processed by exployt, you may request access, deletion, restriction, or portability under the Privacy Policy and applicable law. Some records must be retained for legal, tax, accounting, fraud-prevention, dispute, or security reasons.
10. Governing Law and Dispute Resolution
These terms are governed by the laws of the Republic of Austria, excluding its conflict-of-laws rules and excluding the United Nations Convention on Contracts for the International Sale of Goods (CISG).
For business-to-business (B2B) disputes, the exclusive jurisdiction is the courts of the company's registered seat in Graz, Austria. For business-to-consumer (B2C) relationships, mandatory provisions of the consumer's country of habitual residence are not derogated from, and the consumer retains the right to bring proceedings in the courts of their place of residence to the extent permitted by EU and Austrian consumer-protection law.
European consumers may submit complaints via the EU Online Dispute Resolution platform at https://ec.europa.eu/consumers/odr. Our point-of-contact email for ODR purposes is office@exployt.ai. We are not obligated to participate in any alternative dispute resolution procedure outside the ODR platform.
11. Subscription Compliance
11.1 Subscription Scope
Your exployt subscription defines the permitted scope of use:
- Non-commercial subscriptions permit use for personal, educational, and other non-revenue-generating projects only. A project that generates revenue is never covered by a non-commercial subscription, even where that project is also educational in nature.
- Professional subscriptions permit commercial use exclusively by a single natural person, such as a freelancer or sole proprietor. Use by or on behalf of a company or other organisation is not permitted under this subscription tier.
- Company and Enterprise subscriptions permit commercial use by company entities and other organisations.
11.2 Incidental Compliance Signals
For non-commercial subscriptions only, the AI agents that work on your behalf carry a single one-sentence instruction (not more than one sentence): if, while carrying out the work you have assigned them, they happen to notice clear signs that the project is being used commercially, they record one compliance flag through a simple internal API call. That is the entire mechanism.
There is no project scanning, no separate analysis pass, and no use of your paid AI budget to inspect or evaluate your project. Nothing is read or processed beyond the work you have already asked the agent to do — the agent merely reports an incidental observation. No source code, file content, or project details are transmitted to exployt servers or any other third party; only a non-descriptive project identifier and a compliance indicator (a flag count) are recorded. Commercial subscriptions are not subject to this monitoring at all.
11.3 Automated Market Verification
exployt reserves the right to conduct automated, AI-assisted research to verify whether software developed using exployt is publicly distributed, offered for sale, or commercially marketed. This verification is limited to publicly available information (app stores, public websites, software registries, corporate registrations) and does not involve accessing user systems, accounts, or private data.
11.4 Project Integrity and Re-Identification
To enforce project-level licenses fairly, exployt may maintain non-descriptive technical integrity values for a project and may use them, together with the public-information market verification described in § 11.3, to recognise a project that has been renamed, copied, or published. These values contain no source code, file content, or personal data beyond a non-descriptive project identifier and integrity checksums. Their sole purpose is license enforcement and fraud prevention.
11.5 Compliance Notifications
Users whose projects are flagged by the compliance system will be notified via in-app notifications. These notifications identify the affected project, explain the detected concern, and provide guidance for resolving the situation, such as upgrading the relevant subscription or project tier, correcting the project classification, or settling project-license amounts through the User Budget where applicable.
11.6 Consequences of Non-Compliance
Use of exployt for purposes exceeding the subscription scope does not grant the user distribution rights for software developed with exployt. exployt reserves the right to take appropriate measures in cases of confirmed subscription violations, including but not limited to: requiring subscription upgrades, restricting service access, or pursuing legal remedies.
11.7 Transparency
The compliance signal described in § 11.2 is an incidental observation by the AI agent, not a dedicated analysis of your project. No human reviews your source code or project content. Flagging is advisory and subject to manual review by exployt administrators before any action is taken. False positives may occur; users can disregard compliance notifications if they believe them to be in error.
12. Subscription Types and Terminology
This Section defines the terminology these Terms use for subscriptions. The actual subscription tiers we currently offer — together with their prices, monetary thresholds, and seat counts — are listed on the Pricing page and may be updated per Section 17.
Commercial vs. non-commercial. Every subscription is either non-commercial or commercial. Non-commercial covers personal, educational, hobby, and other non-revenue-generating use, as set out in Section 13. Commercial covers any use that generates revenue or takes place within a company or other organisation, as set out in Section 13.
Who the subscription is for. A Professional subscription is for a single natural person acting commercially, such as a freelancer or sole proprietor. A Company (Business) or Enterprise subscription is for a company or other organisation; where such subscriptions are offered in more than one tier, the tier that applies depends on the thresholds listed on the Pricing page.
If the commercial rights to a project need to move to another person, company, client, or other legal entity, the project ownership-transfer rules in § 16 apply. Any project-level upgrade, downgrade, retroactive licensing, or budget settlement is handled under § 13.1 through § 14, not by a separate three-month transfer fee.
Lifetime subscriptions, where offered, are exceptional and time-bound. We may from time to time run a Lifetime campaign on selected tiers. We make no commitment to repeat any past Lifetime campaign or to launch new ones in the future, and we may modify or discontinue a Lifetime offering at our sole discretion at any time before purchase. Only purchases completed during an active Lifetime campaign window grant lifetime rights. Subscribers who acquired a Lifetime entitlement during a prior campaign keep the rights granted at the time of their purchase, regardless of whether future campaigns occur.
13. License Scope and Commercial Use
Private, non-commercial use of the Service by an individual is free of charge and licensed for non-commercial use only. Commercial use is permitted only while you hold a commercial subscription appropriate to your activity, as described in Section 12 — except during the transitional free-commercial period for individuals set out in § 6, which permits commercial use by an individual (Professional scope) free of charge until 1 September 2026.
Your intellectual property in your own work is preserved at all times. The license restriction in this Section applies only to commercial-exploitation activities; it does not transfer ownership of any code, data, or content you produce with the Service.
Without limitation, the following activities constitute commercial use and require an appropriate Commercial subscription:
- Distributing, selling, or licensing software, services, or content produced wholly or in part with the Service for a fee, royalty, or other consideration;
- Operating a paid app, SaaS product, in-app purchase flow, advertising-supported service, or paid game produced wholly or in part with the Service;
- Using the Service in the course of providing paid consulting, paid contract development, commissioned work, or paid managed-service work for a third party — this is commercial even where there is only a single client;
- Any use of the Service inside a company, government body, or other organisation — including internal tooling, process optimisation, and personal-assistant use — regardless of whether that particular use directly generates revenue;
- Use of the Service by a freelancer or sole proprietor in the course of their paid work;
- Generating outputs intended for resale or for inclusion in a commercially distributed product.
The following activities are not commercial use and do not require a Commercial subscription:
- Personal, educational, research, prototyping, and free-and-non-monetized open-source projects;
- Internal experimentation, learning, and free demonstrations that do not generate revenue;
- Unpaid contributions to free, non-monetized open-source projects.
13.1 Per-Project Licensing
Each project you create with the Service is assigned a unique, server-issued project identifier and is licensed independently. A project is licensed per period of thirty (30) days, counted from your account creation date; opening a project at any point within such a period requires a license for that whole period at the tier appropriate to the project's declared use. If the subscription you already hold for that period is equal to or higher than the project's required tier, no additional fee is due for that project in that period; a lower-tier subscription does not reduce the project fee. Authoritative time, usage records, and identity are determined solely by exployt's servers; the local project database is a cache only.
13.2 Project Classification
When you create a project you must classify it as non-commercial or commercial, and, where commercial, whether the rights holder is an individual (Professional) or a company or other organisation, and for such organisations the applicable tier as listed on the Pricing page. You confirm that you are authorised to make this classification on behalf of the rights holder. The terminology and scope of Sections 12 and 13 apply to this classification. A company project is always commercial, including purely internal use.
13.3 Multiple Accounts and Cost Sharing
More than one account may open the same project. The account designated as project owner must hold the project's required tier active in order to open it; a collaborating account may open the project with any active subscription, and any resulting license amounts accrue against that account. An account without an active subscription cannot open the project. Project-license amounts are settled exclusively from a User Budget (§ 20); the Service does not bill those amounts directly to a payment provider. A payment provider is used only to top up a User Budget. Where the owner sees all project license information, a non-owner account sees only its own amounts.
The intent of this clause is consistent with industry-standard developer-tool licenses (such as Unity or JetBrains), which distinguish non-commercial from commercial use: a non-commercial subscription lets you build, learn, and experiment, while a commercial subscription is required once your activity generates revenue or is conducted within a company or other organisation. The project-level rules above apply that same distinction to each project, so ownership, classification, shared access, and later tier changes remain auditable and consistent.
13.4 Free Commercial (Discretionary Hardship Grant)
In legitimate cases where someone genuinely cannot afford a subscription but for whom exployt could create real value, we may grant that person Free Commercial access to the Service. Free Commercial is not an entitlement, is not guaranteed, is granted case by case (see the Free Commercial tab on the Pricing page), and we may limit, suspend, or end it at any time at our reasonable discretion.
Free Commercial is free, personal, revocable permission to use the Service commercially during the granted period. It is not a licence: the recipient acquires no licence rights and gains no ownership of or title to any licence, and we do not restrict what the recipient builds during Free Commercial. Your own work stays yours: a recipient retains full ownership of and all rights to any software, content, or work they create using the Service during the Free Commercial period, exactly as elsewhere in these Terms; nothing in this Section affects ownership of a recipient's own work.
Our commitment not to pursue you. Free Commercial is a voluntary act of goodwill and we knowingly accept the risk it carries. Accordingly, for use of the Service during the Free Commercial period we will not charge any fee and will not assert, demand, or enforce any licensing claim against the recipient. This is a binding waiver of those claims for the Free Commercial period (a forbearance, not the grant of a licence), subject only to the fraud exception below.
Fairness, not obligation. Because no licence was acquired, a recipient does not become legally clean for commercial use merely because we do not pursue it; the clean footing remains an appropriate commercial licence. We therefore invite — but never require — a recipient who later comes to comfortably afford it (for example because exployt helped them earn well) to voluntarily pay the fair retroactive fee under § 15 (Self-Cure), simply because it is fair. This is an appeal to fairness, not a contractual claim; declining is not a breach, and we acquire no legal right to that payment.
The single exception — fraud. The commitment above does not apply where Free Commercial was obtained by deliberate, materially false misrepresentation — for example, someone who could plainly afford a normal subscription and knowingly and dishonestly misrepresented their situation to obtain free commercial access. In such a clearly evidenced case of bad-faith deception the grant is void from the outset, and for use during and after the Free Commercial period we reserve the same rights and remedies available against any other user — including ending Free Commercial immediately and, where the recipient does not take the retroactive Self-Cure under § 15, enforcing the appropriate commercial licence fee and pursuing other legal remedies. We apply this exception narrowly and only on clear evidence of intentional deception.
Relationship to § 14. This Section prevails over § 14 for the Free Commercial period: outside the fraud exception, we do not assert the retroactive licensing fee for that period, although a recipient may always choose to settle it voluntarily under § 15.
14. Retroactive Licensing Fees and Project Tier Changes
If you have used the Service for commercial activity (as defined in Section 13) without holding the appropriate commercial subscription tier, you owe a retroactive licensing fee. The fee is calculated only over the periods during which a subscription of any kind was actually running on your account — including a non-commercial subscription or an active free trial — and equals, for each such period, the difference between the fee that would have been due for the appropriate commercial tier and the fee you actually paid for that period.
Why we count subscription time rather than guessing when your work became commercial. When a project quietly grows from a private experiment into a commercial product, there is rarely a single visible moment when that happens. We can see when a commercial outcome appears in the world (an app launches, a paid product ships); we cannot see, from our records alone, when the work that produced it genuinely became commercial in your mind. Rather than guess, we anchor the fee to something objective and recorded: the time during which you actually held a subscription. What matters is whether a subscription was running — not how active you were in the app. Periods in which no subscription was running at all (a fully cancelled account, with no trial and no paid plan) are not charged, because during those periods you held no licence from us. This keeps the rule objective on both sides and applies uniformly to everyone.
Example. You hold a non-commercial subscription and use exployt privately for six months while you build a side project. In month seven you publish that project as a paid app. Your retroactive fee covers the months in which a subscription was running, charged at the Professional rate (or the higher tier appropriate to your situation) that applied in each of those months, minus the non-commercial fees you already paid for the same months. If your subscription had lapsed entirely for, say, two of those months, those two months are not charged. The fee is capped at thirty-six (36) months counted backwards from today. You can settle it the same day, in one click, through the in-app upgrade flow — see § 15 Self-Cure and Automatic License Grant for the customer-friendly relief valve we have built into this rule.
The retroactive fee is calculated period by period, using the price of the applicable commercial tier as it stood in each period (the actual historical rates, not merely the current or most recent price), less any subscription fees you already paid to the company for the same periods. Only periods in which a subscription was running on your account are included; periods with no active subscription are excluded. This calculation is implemented in the company's billing system and is shown to you transparently in the upgrade flow before any payment is taken. The retroactive period is contractually capped at thirty-six (36) months counting backwards from the current date.
Separate project-license calculation. The preceding paragraphs address account-level unauthorized commercial use. Project-level licensing is calculated under § 13.1; for those project-license amounts, a lower-tier subscription does not reduce the project fee unless the subscription for that period is equal to or higher than the project's required tier.
Project tier changes. Increasing a project's tier applies the higher tier retroactively to every prior period in which the project was opened by any account, subject to the same thirty-six (36) month cap. Decreasing a project's tier may produce a surplus; any surplus is refunded as User-Budget credit only (never cash), apportioned to each account that originally paid, in proportion to its payments. Each individual budget payment may be reversed within fourteen (14) days; after that window it is final.
The retroactive fee is set as a contractual lump-sum measure of damages on a license-analogy basis, in line with established intellectual-property practice. Where mandatory consumer-protection law applies, statutory consumer-protection rules prevail to the extent the contractual measure would otherwise be invalid.
15. Self-Cure and Automatic License Grant
You may cure any prior unauthorized commercial use at any time by paying the retroactive licensing fee described in Section 14. Upon successful payment, the company is contractually bound to immediately grant you the corresponding Commercial license retroactively from the start of the calculated period. The company may not withhold the retroactive license after payment.
Project-license amounts remain subject to the project-level rules in § 13.1 through § 14. This Section does not create direct payment-provider billing for project-license amounts; where those amounts are due, they are settled through the User Budget as described in § 13.3 and § 20.
The cure is implemented in the in-app and in-account upgrade flow: selecting a higher tier triggers a transparent quote covering both the retroactive remainder and ongoing recurring fees, and on successful payment the retroactive license is recorded in the user's licensing audit trail.
First-time good-faith cure: A user who cures their non-compliance within three (3) months of receiving the first compliance notification from the company is, beyond payment of the retroactive fee itself, released from any further claim by the company in respect of the cured period (including any claim for injunction or additional damages). This carve-out applies once per user account.
16. Hardware Binding and Seat Transfer
Each Commercial subscription grants the right to use the Service on one active hardware device at a time ("one seat = one active hardware"). A single user account may hold multiple seats by purchasing multiple subscriptions; each seat is independent and is bound, while active, to one specific device.
Switching devices. You may transfer any seat to a new device at any time by using the "Sign out this device" action in your Account area, which releases the current hardware binding and allows the next device to claim the seat. There is no limit on how often you may switch devices — only the rule that at any moment exactly one device per seat is active.
Online and offline operation. Hardware binding is verified by the Service on each application launch when online. When you are offline, the Service continues to operate for a limited grace period using a short-lived, server-issued unlock token cached on the device. After the grace period expires, the Service stops working until you reconnect and the unlock token is refreshed online. It does not silently downgrade to a lower scope — access is simply paused until the next successful online check.
Account sharing — and changes of the rights-holder. Sharing the login credentials of a user account with other persons is not, by itself, a separate violation of this Section, provided the one-active-hardware-per-seat rule is respected at all times. The rule is enforced both technically (only one device per seat may run the Service at a moment) and contractually.
Project ownership and rights-holder changes. If the commercial rights to a project developed with the Service need to belong to a different person, company, client, buyer, or other legal entity, this is not treated as a hardware-seat transfer. It is a project ownership transfer under this Section.
The prospective project owner must be an account that has previously opened the project and must satisfy the applicable project-level licensing rules before the transfer can take effect. A non-commercial-to-non-commercial project transfer is permitted under this Section. A transfer that makes the project commercial, moves it to a company, or increases the required tier is blocked until the necessary project-level upgrade and budget settlement have been completed under § 14. No separate one-time three-month transfer fee applies under this Section.
The intent is straightforward: who runs the Service on a device is a hardware-seat question; who owns or commercially exploits a project is a project-licensing question.
17. Tier Threshold Changes and Material Updates
Tier criteria (such as annual gross revenue thresholds, employee counts, or other reasonable factors used to assign a user or entity to a tier) are listed on the Pricing page. The company may update these criteria at its reasonable discretion in response to market conditions, product evolution, or changes to its cost base.
Material changes — defined as price increases greater than ten percent (10%), tightening of tier thresholds that would push existing users into a higher tier, or removal of features to which an existing user is currently entitled — trigger a thirty (30) day advance notification sent to the affected users' registered email addresses. During the notification window, affected users may cancel the affected subscription without penalty and retain the previously granted rights through the end of the already-paid billing period.
Non-material changes — such as cosmetic edits, clarifications, the addition of new tiers that do not affect existing tiers, or price adjustments at or below the rate of consumer-price inflation — become effective on publication.
Where Austrian or EU consumer-protection law (notably § 6 KSchG and § 25c KSchG) provides for stricter notification, opt-out, or termination rights than this Section, those statutory rules prevail.
18. Recruitment Reward Programme
We may operate a recruitment reward programme that lets you earn a bonus when a person you invite signs up and pays for a subscription. Participation is optional and open to all account holders unless we have notified you otherwise. This section sets the rules; the current bonus amount, eligibility criteria, and any campaign-specific conditions are published on our Rewards page and may be adjusted by us at any time at our reasonable discretion, without amending these Terms.
Which referral counts. A person you invite may open several different affiliate links or promo codes before they sign up. Attribution is decided by the most recent eligible affiliate link or promo code that was opened before the recruited user creates their account: each newer link supersedes any earlier one, and the one active at the moment of account creation is permanently locked in as the attributed referrer for that account. Links opened after the account has been created do not change the attribution.
How the bonus accrues.
- The bonus is calculated as the Reward Percentage (published on the Rewards page) applied to the value of one month of the recruited user's plan — that is, the standard monthly subscription fee for that plan. This applies regardless of how the recruited user pays: where the recruited user buys an annual plan or a one-time lifetime licence, the bonus is still calculated on the equivalent one-month fee for that plan, and never on the total amount the recruited user pays.
- The bonus is credited to your User Budget (described in § 20) only after both of the following have occurred:
- the recruited user's payment to our payment provider has cleared, and
- the statutory refund / withdrawal period applicable to that payment has expired.
Until both conditions are met, the bonus is shown as pending in your account and is not yet usable or payable.
One bonus per recruited customer. The recruitment bonus can be earned only once for each customer you recruit. For this purpose the combination of you (the recruiting account) and the recruited customer counts as a single, one-time entitlement, irrespective of how many user seats, licences, or separate subscriptions that recruited customer purchases. In particular, where the recruited customer is a company or other organisation that buys multiple seats, the bonus is calculated on one month of a single plan’s monthly fee, once — it is not paid per seat and is not multiplied by the number of seats. This entitlement is also one-time for the entire lifetime of the relationship between your account and that recruited customer: once a bonus for that customer has accrued (or has been rejected or clawed back under the refund or anti-abuse rules), no further recruitment bonus arises from any later purchase, plan upgrade, additional seat, or renewal by the same recruited customer, whether it happens days, weeks, months, or years later.
One bonus per company domain. Where you recruit multiple users who share the same corporate email domain (for example, alice@example.com and bob@example.com), you are entitled to one recruitment bonus from that domain only. The first recruited user from that domain whose payment clears and whose refund window expires earns the bonus; subsequent recruits from the same domain do not generate an additional bonus. Free, public email providers (such as gmail.com, outlook.com, yahoo.com and similar) are exempt from this rule — each user on a free-email domain is treated as an independent recruit.
Same-company referrals excluded. Referring your own colleagues, co-workers, or other members of the same company or organisation — identified by a matching corporate email domain between your account and the recruited account — does not constitute an eligible recruitment and no bonus is paid. This rule exists to prevent abuse where, instead of purchasing additional seats directly, employees refer their colleagues to obtain a discount through the recruitment bonus. We may also investigate and reject referrals that circumvent this rule through the use of alternative email addresses or other means.
Refunds and reversals. If the recruited user obtains a refund or successfully exercises a chargeback after the bonus has been credited, the corresponding bonus is automatically reversed from your User Budget. If your User Budget balance is insufficient at the time of reversal, the reversal is recorded as a negative balance and is offset against your next eligible bonuses or payouts.
Anti-abuse. We may reject, suspend, or claw back bonuses where, at our reasonable assessment, recruitment activity shows signs of fraud or abuse — examples include but are not limited to recruiting yourself through a different identity, recruiting colleagues from your own company through alternative email addresses, using stolen payment instruments, coordinating sign-ups designed to be refunded after the bonus is paid, and material misrepresentation in the recruitment flow. We will not suspend or claw back bonuses arbitrarily; we will document our reasons internally and explain them on request.
Tax treatment. The bonus is a benefit that may be taxable in your country of residence. You are responsible for declaring it according to your local tax rules. See § 21 Tax Treatment of Payouts for our general approach and disclosures.
Programme changes and ending. We may modify, pause, or terminate the recruitment reward programme at any time at our reasonable discretion. Bonuses that have already been credited to your User Budget remain yours subject to the rules above; bonuses that are still pending at the time of a programme change are processed under the rules in effect at the time the bonus accrued.
From time to time we may issue promo codes as part of the recruitment reward programme described above. When someone redeems a valid promo code, they receive a one-time free month and are linked to the code's owner as their recruit, so any recruitment reward arising from a later paid subscription is governed by this Section 18 — including its refund, chargeback, and anti-abuse reversal rules.
Who receives codes. Shareable promo codes are issued only to paying commercial subscribers — not to free, trial, or private non-commercial plans — and only after the payment they come from is no longer refundable. Each code is locked until that refund window has passed and carries the issuing subscriber's own plan tier. The number of codes per paid invoice is set by us and may be zero (programme paused). Codes are shown on your Account page, which is also where they are redeemed.
Who may redeem. A promo code may be redeemed once per account, and only by a genuinely new customer: an account that has never redeemed a promo code before and has never held a paid subscription (a free trial does not count). It cannot be redeemed by the code's owner, by anyone sharing the owner's company (corporate email domain), or by an account whose company has already redeemed a code — each company may redeem only once in total. Redeeming grants one free month at the issuing subscriber's plan tier and does not itself generate any new codes.
Company checks and review. Where an attempted redemption comes from a corporate email domain already associated with a paying customer or a prior redemption, we may warn you that it appears to breach these rules and, if you proceed, flag the grant for review (automated and, where needed, manual). We reserve the right to cancel a free month granted in breach of these rules.
A redeemed code is honoured. Once you successfully redeem a valid code, the free month is yours. The discretionary terms below concern the programme — the issuing and continued availability of codes — and do not take away a free month you have already validly redeemed.
Discretionary, and only while available. The promo-code programme is offered at our reasonable discretion and creates no binding entitlement: we are not obliged to issue codes, codes are offered only while available, and we may change, pause, or end the programme at any time. Codes are non-transferable for resale, and abuse — including self-redemption, automated or bulk redemption, or other circumvention — may void the grant under the anti-abuse rules above.
19. Marketplace Income Share
If you choose to offer your own products or services through the exployt Marketplace, this section defines how revenue from those sales is split, when your share is credited, and what you are responsible for. The marketplace itself, your eligibility to sell, and the categories of products we accept are governed by the separate Marketplace Publisher Terms (linked from the Marketplace page); this section covers only the economic and payout-relevant rules.
Marketplace uploads. Publishing a Marketplace item is a deliberate upload: the files and metadata you choose for that item are transmitted so the item can be reviewed, hosted, shared, sold and delivered to buyers. If the item contains source code, connector packages, integration modules or reusable project assets, you decide what to include; we recommend removing secrets and private customer data, minimizing the package, and using obfuscation where appropriate. exployt can support obfuscation-oriented publishing workflows, but you remain responsible for what you choose to publish.
Service Fee. exployt retains a Marketplace Service Fee from each completed sale. The current percentage and any product-category-specific variations are published in the in-app Marketplace and may be adjusted by us at any time at our reasonable discretion, without amending these Terms. The remaining amount, after the Service Fee and after any payment-provider transaction fees, is your share.
When your share is credited. Your share is credited to your User Budget (described in § 20) only after both of the following have occurred:
- the buyer's payment to our payment provider has cleared, and
- the statutory refund / withdrawal period applicable to the buyer's purchase has expired.
Until both conditions are met, your share is shown as pending in your account and is not yet usable or payable.
Refunds and reversals. If a buyer obtains a refund or successfully exercises a chargeback after your share has been credited, the corresponding amount is automatically reversed from your User Budget. If your balance is insufficient at the time of reversal, the reversal is recorded as a negative balance and is offset against your next eligible credits or payouts. The Service Fee for the affected transaction may also be subject to reversal, but payment-provider fees that we have already incurred on the original sale are not refunded to you; we pass through only the actual amount we recover.
Your responsibilities as a seller.
- You are the contracting party to the buyer for what you sell. You are responsible for the legality, accuracy, and fitness-for-purpose of your product, for fulfilment, for buyer support, and for your own warranty and consumer-protection obligations under applicable law.
- You must keep the identity and tax data in your seller profile (legal name, address, tax identification number, IBAN, country of tax residence) accurate and current. We may suspend payouts until missing or invalid data is provided.
Reporting to tax authorities. As an operator of an EU digital platform that facilitates the sale of goods and services, we are required by EU and Austrian law (notably the EU DAC7 directive as transposed into Austrian law) to report your identifying data and payout totals to the Austrian Federal Ministry of Finance on an annual basis. A de-minimis exemption applies to small-scale sellers of goods: if, in a reporting period, you complete fewer than 30 sales of goods and receive no more than €2,000 in total for them, you generally do not have to be reported for that activity. (These are the current statutory values for the sale-of-goods category; they can change, and the values in force at the time apply.) The Federal Ministry of Finance shares reportable information with the tax authority of your country of tax residence. The data we report, the legal basis, and your rights in relation to that reporting are described in § 21 Tax Treatment of Payouts and in our Privacy Policy.
Anti-abuse. We may reject, suspend, or claw back marketplace credits where, at our reasonable assessment, the activity shows signs of fraud or abuse — for example, fake transactions designed to round-trip funds, use of stolen payment instruments by a buyer in collusion with a seller, or material misrepresentation in the product listing. We will document our reasons internally and explain them to you on request.
Programme changes and ending. We may modify, pause, or terminate the Marketplace or any product category at any time at our reasonable discretion, with reasonable advance notice where commercially practicable. Credits that have already been credited to your User Budget remain yours subject to the rules above; pending credits at the time of a programme change are processed under the rules in effect at the time of the underlying sale.
20. User Budget and Payouts
Earnings you generate through the recruitment reward programme (§ 18) or the marketplace (§ 19), once they meet the release conditions in those sections, are credited to your User Budget. The User Budget is a record of how much money we owe you and is held by us — it is not a separate payment account in your name. You may use your User Budget to pay for exployt services (subscription extensions, marketplace purchases, and other paid features) or request a payout to an external channel.
Supported payout channels. The payout channels we currently offer are listed on your Account page. We choose the channels we support based on cost, geographic coverage, reliability, and compliance. We are not obligated to offer any specific channel (such as a particular bank-transfer network, e-money wallet, or third-party service) and may add, change, or remove channels at our reasonable discretion. Where a channel becomes unavailable, we will try, but do not guarantee, to give reasonable advance notice and to suggest an alternative.
Payout SLA. Once you submit a payout request through a supported channel, we will process the request within fourteen (14) days, subject to (a) successful identity-verification and anti-fraud checks (we may need to ask you for additional documents before processing the first payout to a given channel) and (b) the payout channel's own clearing time, which is outside our control.
Minimum payout amount. A minimum payout threshold may apply, shown on the Account page. The minimum exists so that small payouts do not get eaten by fixed transaction fees; it is not a way to keep funds you have earned.
Deductions. From each payout we deduct:
- the transaction fees charged by the payment provider for that specific transfer;
- any currency-conversion fees or spread where the payout currency differs from the currency in which your User Budget is held; and
- any taxes we are required by applicable law to withhold at source — for ordinary commissions and marketplace earnings paid to recipients inside the EU there is normally no income-tax withholding by us, but we reserve this clause for cases where law makes us a withholding agent (for example, certain cross-border or treaty-driven situations).
The applicable rates, fees, and the channel-specific deduction structure are shown on the Account page before you confirm a payout. Rates may change without amending these Terms.
Currency. Your User Budget is held in a single base currency, which we will tell you on the Account page. Where conversion is required (incoming credits in a different currency, or payout in a different currency), the rate applied is the one in effect at the time of the conversion transaction and is shown to you in the breakdown.
No interest, no escrow. Funds held in your User Budget do not earn interest. The User Budget is not a payment account, e-money account, or escrow account within the meaning of EU payment-services regulation; it is a closed-loop record between you and exployt Software GmbH.
Disputed or reversed credits. If a credit to your User Budget is later reversed under § 18 or § 19 (refund, chargeback, anti-abuse claw-back) and your balance becomes negative, you may not initiate a new payout until the balance returns to positive through new credits or by a one-time top-up payment, if we offer one.
Account closure. If you close your exployt account while your User Budget has a positive balance, we will pay out the balance to a supported channel of your choice, subject to the same SLA, deductions, and identity-verification rules as any other payout, and after any open reversal risk windows from § 18 and § 19 have expired.
21. Tax Treatment of Payouts
This section explains how Austrian tax law treats payouts from your User Budget to you, so you can make informed decisions. It is provided for information only. It is not legal or tax advice, it does not create a tax-advisory relationship between you and exployt Software GmbH, and the figures and rules quoted below may change without notice and may differ in your country of tax residence. You are responsible for your own tax compliance. Please consult a qualified tax advisor in your jurisdiction before acting on anything stated here.
Who declares what.
- Earnings paid to you under § 18 or § 19 are, in general, your taxable income. You declare them to your own tax authority according to the rules of your country of tax residence.
- For ordinary commercial commissions and marketplace earnings paid to recipients inside the EU, Austrian law generally does not require exployt Software GmbH to withhold income tax at source. We pay you the gross amount minus the § 20 deductions only. (These statements are subject to change and to your specific circumstances — see the disclaimer at the start of this section.)
Austrian Section 109a EStG payor-notification.
- Austrian income-tax law (§ 109a EStG) may require Austrian payors to notify the tax authority about certain enumerated payment categories. Official Austrian guidance currently allows the notification to be omitted only if both the total paid to the recipient in the calendar year is not more than €900 and each individual covered payment is not more than €450. If either limit is exceeded and the payout falls into a covered category, reporting may be required. (Checked against BMF/USP and RIS guidance on 25 August 2026; for information only, without warranty, current law at the time applies.)
- Whether a given payout falls within the enumerated categories of § 109a EStG (such as supervisory-board members, insurance agents, free-service employees, or licence-fee recipients) depends on the legal characterisation of the payout. We document our categorisation internally and, where § 109a EStG applies, we file the annual report electronically by the end of February of the following year via ELDA, as required by Austrian law.
EU DAC7 platform reporting (marketplace).
- For payouts under § 19 Marketplace Income Share, exployt Software GmbH is an operator of an EU digital platform within the meaning of EU Directive 2021/514 ("DAC7"), as transposed into Austrian law via the Digitales Plattform-Meldepflichts-Gesetz (DPMG). This obliges us to report your identifying data and payout totals to the Austrian Federal Ministry of Finance (BMF) on an annual basis (currently the report is due by 31 January of the year following the reporting year — date may change). A de-minimis exemption applies to small-scale sellers of goods: a seller who completes fewer than 30 sales of goods and receives no more than €2,000 in total for them in the reporting period is generally not reportable for that activity (current statutory values for the sale-of-goods category; subject to change — the values in force at the time apply).
- The Federal Ministry of Finance shares this information with the tax authority of your country of tax residence under the DAC7 exchange mechanism. The categories of data we transmit (legal name, address, tax identification number, IBAN, country of tax residence, quarterly transaction count and total consideration) and your data-protection rights in relation to that reporting are described in our Privacy Policy.
VAT on what you sell (marketplace).
- If you sell on the exployt Marketplace and you are an Austrian taxable person whose annual turnover exceeds the Kleinunternehmer threshold (currently approximately €55,000 gross per calendar year following the 2025 reform of § 6 Abs. 1 Z 27 UStG — exact threshold and tolerance rule for the current year may differ; see BMF official guidance), you must invoice the buyer with the applicable VAT rate (in Austria, the standard rate is 20% at the time of writing). Below the threshold you may invoice without VAT under the Kleinunternehmer regulation.
- exployt Software GmbH is not below the Kleinunternehmer threshold. Our § 20 deductions for exployt's own service fees are subject to AT VAT (currently 20% at the time of writing) charged to you. Where you are VAT-registered in another EU member state and provide your VAT ID, B2B reverse-charge rules may apply.
- For cross-border B2C sales facilitated by the Marketplace, the e-commerce VAT package (deemed-supplier rule under Art. 14a of the EU VAT Directive) may apply once thresholds are exceeded. The mechanics are implemented in the Marketplace pricing and invoicing flow.
Retention of tax records. Tax-relevant records that we generate or hold in connection with your payouts (identity data, transaction records, invoices, payout breakdowns) are retained for seven (7) years in line with § 132 of the Austrian Federal Tax Code (BAO), and longer where law requires it for specific records or ongoing proceedings. Where DAC7/DPMG reporting applies, the reporting dataset follows the DPMG retention and deletion rule, currently deletion ten (10) years after the relevant reporting period. (Checked against RIS BAO and RIS DPMG on 25 August 2026; for information only, without warranty.)
Your tax-data fields. When you initiate your first payout, we collect from you: legal name, primary address, tax identification number (TIN) of your country of tax residence, your VAT identification number if you have one, your IBAN (or other supported payout identifier), your date of birth (for natural persons), and your country of tax residence. We use this data strictly to execute the payout and to meet our payor-side reporting obligations described above. The data-protection mechanics are in our Privacy Policy.
Global closing disclaimer (please re-read). Everything in this Section 21 is provided for information only. We have researched the figures and rules with reasonable care, but we make no warranty as to their accuracy, completeness, or current validity. Tax law changes. Your situation may differ. Nothing in this Section creates a tax-advisory relationship, and exployt Software GmbH accepts no liability for any consequence of your reliance on this information. Please consult a qualified tax advisor in your jurisdiction before making tax-relevant decisions.
Official source basis. The tax figures above were checked on 25 August 2026 against Austrian BMF/USP guidance on § 109a EStG, the RIS text of the § 109a regulation, RIS DPMG §§ 5, 14 and 15, RIS BAO § 132, and BMF guidance on Austrian income-tax and VAT thresholds. This source note does not reduce the no-warranty disclaimer in this Section.
22. User Connections & Direct Messaging
User-to-user direct messages, message requests, and connection requests are optional peer interactions between account holders. exployt does not moderate, monitor, pre-screen, verify, arbitrate, or mediate these interactions and does not operate a complaints or moderation desk for user-to-user conversations.
You use these features at your own risk. Other users may send spam, scams, fraudulent requests, harassment, unlawful, offensive, misleading, or otherwise abusive content. To the maximum extent permitted by applicable law, exployt Software GmbH is not liable for another user's conduct, message content, connection request, failure to respond, or any decision you make based on a user-to-user interaction.
You are responsible for deciding whom you contact, whom you connect with, what you share, and whether you trust anything you receive. Be cautious before sharing personal, business, technical, financial, or security-relevant information with another user.
Your controls are limited to the tools provided in the product: you can show or ignore a message request, ignore a user so their current and future messages are hidden from you, decline a connection request, accept a connection request, or remove an existing connection at any time. Ignoring, declining, removing, or accepting a connection is your own decision and does not create a duty for exployt to investigate or act against another user.
By sending a direct message, sending a connection request, accepting a connection request, or continuing a direct-message exchange, you accept this User Connections & Direct Messaging section as part of the Terms of Service.