Terms of Service
Effective: 8 November 2026 · Version 2026-11-08.1
Read together with the privacy policy, Data Processing Agreement and subprocessor list.
1. Provider, scope and eligibility
eu/jev is operated by Bevelites GmbH, Schleißheimer Str. 188, App. 520, 80797 München, Germany, Amtsgericht München, HRB 303590, represented by Razvan-Ion Radulescu. Contact: ali.raza@bevel.software. These terms govern the website, playground, accounts and decision API at eu-jev.com, including requests still sent to the earlier address jev.bevel.software.
You must be at least 18 and legally able to enter this agreement. If acting for an organisation, you must be authorised to bind it. Personal and work email addresses are welcome. Applicable consumer rights remain unaffected. By signing up after being shown these terms, or expressly accepting them, you agree to them. The privacy policy explains processing and is not a request for blanket consent.
2. What the service provides
The API evaluates supplied context against questions and criteria to return choices, probabilities or scores. The public playground makes real inference requests. Outputs are model predictions: they may be inaccurate, biased or unsuitable for your purpose. Evaluate them in your own application and provide appropriate human review.
Jev-style request support does not promise identical token counts, outputs, accuracy, limits or latency to another provider. eu/jev is not affiliated with TypeSafe AI. The application, database and model execution are hosted in Germany. The subprocessor list distinguishes this API processing from separate DNS, Google sign-in, account-email, payment and request-form services, which can involve international processing.
3. Accounts, access and API credentials
You may sign in with email and password where enabled, or choose Google. Email signup requires mailbox verification; recovery links expire and can only be used once. Keep your password, email account, Google account if used, sessions and API keys secure. You may use keys through authorised staff and applications acting for you, but must not publish them or bypass access controls. Notify us promptly of suspected compromise. You are responsible for activity you authorise and for reasonable credential security, subject to mandatory law.
Access is limited. Applications are reviewed as capacity opens. Submitting the external request form does not guarantee access, create an account or start billing. We may apply technical rate, concurrency, input-size and credit limits. Existing access is not a guarantee of uninterrupted capacity.
4. Credits, pricing and extra usage
Newly admitted accounts receive €5 in promotional API credits. The current input-token rate is €37 per billion tokens; output tokens are free. The service meters the model’s packed input, which can include instructions, criteria and model formatting. Token accounting can differ from other providers. Request costs and credit movements appear in your usage history.
A new account joining through a valid referral receives an additional €3 in API credits, and the inviter receives €3. The bonus applies to the first 5 verified new accounts admitted through each inviter’s link, for up to €15 earned by inviting. Each new account can receive one joining bonus and have one referrer. Credits are awarded when the account is created after verification, subject to normal admission. A click, an unverified signup or a waitlist application does not reserve a bonus or a place. Existing accounts do not qualify for a joining bonus. Once an inviter’s bonuses have been claimed, their link can still lead to ordinary signup with the standard starting credit. Self-referrals and creating additional accounts to claim referral rewards are not permitted. Referral credits have the same non-transferable, non-cash status as other promotional credits.
There is no automatic subscription, auto-renewal, stored-card charge or automatic conversion from free to paid use. Where card payment is enabled, you can voluntarily add prepaid API credit in whole-euro amounts between €5 and €500 through our payment provider Stripe. The net amount, applicable VAT and total are shown on Stripe’s checkout page before you confirm each payment, and Stripe sends the invoice. Purchased credit is added to your balance once Stripe confirms the payment and is consumed at the published input-token rate alongside promotional credit. When credits are insufficient, requests are blocked until you add credit or apply for extra usage through the linked form. Promotional credits have no cash value and cannot be transferred or redeemed for cash.
Purchased credit is a prepayment for use of the API by the account or Team workspace it was bought for and cannot be transferred to another account or workspace. If we discontinue the service, we will refund unused purchased credit. Consumers have the statutory right of withdrawal; a consumer who uses purchased credit before the withdrawal period ends asks us to begin performance early and owes payment for credit already used, while unused credit remains refundable within that period. These terms do not remove any mandatory refund or withdrawal right. Larger or bespoke arrangements require a separate express agreement showing price, taxes, payment and cancellation before you commit. Pricing changes apply prospectively after notice; they do not reprice completed requests.
5. Plans and Team workspaces
eu/jev is offered as three plans. Individual is a personal account that pays the usage price in section 4. Team is a shared workspace for an organisation, with a monthly seat fee in addition to the same usage price. Enterprise covers dedicated infrastructure, availability commitments and additional data-protection terms, and exists only under a separate written agreement that states its price and scope; nothing on the website commits us to Enterprise terms until that agreement is concluded.
Any signed-in user can create a Team workspace and becomes its owner. By creating a workspace, inviting members, adding credit or accepting the DPA for it, an owner confirms authority to bind the organisation that uses the workspace; that organisation is the customer for the workspace. Members act for the organisation within their role. Owners manage billing, the DPA, members, roles, keys and deletion; admins manage members other than owners and keys; members use the workspace’s keys and see its usage. A workspace always keeps at least one owner. Invitations are sent by email, expire after seven days and can only be accepted by signing in with the invited address.
Workspace API keys and the workspace balance belong to the workspace, not to the member who created or funded them, and keep working when that member leaves. Leaving a workspace or being removed ends access to its keys, balance, usage and agreements immediately. The person’s own account, keys and credits are unaffected and are never used to pay for the workspace.
The Team seat fee is €10 per member per month, owners and admins included. Each paid seat includes €5 of usage credit, which is added to the workspace’s balance when the seat fee is deducted, can be used only for usage of that workspace, does not expire while the workspace exists, and is not refundable or payable in cash. The fee is deducted from the workspace’s prepaid balance on the workspace’s billing day: the day of the month on which it was created, or the last day of a shorter month. A member who joins during a billing period is charged the remaining part of that period when joining and receives the same part of the included credit; joining is refused while the balance cannot cover that amount. No part of the fee is refunded when a member leaves or is removed during a period. Pending invitations are free. If the balance cannot cover the seats on the billing day, the workspace’s API keys are paused until the balance is topped up, and owners are notified by email. Seat fees and usage are shown separately in the workspace’s billing history. Seat fees and usage are deducted from credit already purchased, including any VAT charged at checkout; there are no stored-card or automatic card charges. Monthly invoicing can be arranged on request by separate agreement.
Owners can delete a workspace. Its keys, members and invitations are then removed, and any remaining balance ends with it; contact us before deleting a workspace if unused purchased credit should be refunded under section 4. Usage and payment records are kept for accounting as described in the privacy policy.
6. Permitted use and safeguards
You may automate calls to the API and integrate the results into your own products, including commercial products for your customers. Respect documented limits and applicable law. Do not attack the service, evade safeguards, extract other customers’ data, distribute malware, infringe rights or use compromised credentials.
Supply only data necessary for your purpose, with a valid legal basis and required notices. Do not submit passwords, secrets, payment-card details, special-category data under Article 9 GDPR, criminal-offence data under Article 10, or data for a high-risk use unless we have first agreed the additional safeguards in writing. Do not use predictions alone for decisions with legal or similarly significant effects unless the applicable law permits that processing and all required safeguards, including human intervention where required, are in place.
For personal data processed on behalf of a business or other controller, conclude the DPA before sending that data. A processor customer must have its controller’s authorisation. Use synthetic or non-personal examples in the anonymous playground.
7. Your content, service rights and feedback
You retain rights in your submitted content. You grant only the permissions necessary to receive, transmit and process it and return results according to your instructions and the DPA. We do not obtain an unrestricted right to publish, distribute, sell or train on your inputs or outputs. We claim no ownership in your outputs; their legal protectability and any third-party rights remain subject to applicable law.
Our branding and service software remain ours or our licensors’. Open-source components retain their own licences. These terms do not override rights those licences or mandatory law give you. You may use the service as described above without suggesting endorsement. We may use voluntarily supplied product feedback to improve the service; feedback is not permission to reuse personal data or confidential API content.
8. Privacy and operational monitoring
The privacy policy explains account, usage, security, agreement and contact records. Internal usage analysis uses request metadata, not prompt or response content. The application does not persist API content in its database or application logs and does not use it to train models. Transient token and intermediate-computation caches can remain in worker memory across requests; they are not immediately erased on completion.
The DPA governs customer personal data processed on instructions and takes precedence over conflicting service terms for that processing. It does not replace our controller obligations for account administration or reduce any person’s GDPR rights. Our subprocessor list distinguishes API processing from separate account and contact services.
9. Availability, changes and support
The Individual and Team plans have no contractual uptime percentage, latency guarantee or service-credit SLA. Such commitments exist only where separately agreed in writing, such as in an Enterprise agreement. Maintenance, failures and capacity limits can affect availability. Contact ali.raza@bevel.software for support; no fixed support response time is promised.
We will give reasonable advance notice of material service or API changes where practicable, explaining their effect and any migration steps. Urgent security or legal changes may take effect sooner. Mandatory rights concerning digital services remain unaffected.
10. Suspension, termination and data
You may stop using the service at any time and request account closure at ali.raza@bevel.software. We may restrict access where reasonably necessary to prevent misuse, protect security or comply with law. Where practicable we will explain the reason and allow you to remedy it. For discontinuation unrelated to misuse, we will give reasonable advance notice.
On closure, keys and sessions are revoked and personal data is deleted or returned under the DPA and privacy policy, subject to specific legal retention duties. We cannot return historical prompts or outputs that were not stored; retain results you need. Termination does not permit indefinite retention or displace data-subject rights, accrued payment rights or mandatory consumer remedies.
11. Liability
We remain liable without limitation for intent and gross negligence, injury to life, body or health, fraudulent concealment, an expressly assumed guarantee, and liability that cannot lawfully be limited, including applicable product-liability obligations. For ordinary negligence affecting an essential contractual obligation, liability is limited to damage typical of this agreement and reasonably foreseeable when it was concluded. Any further exclusion applies only to the extent permitted by law.
Nothing here limits a data subject’s compensation rights under Article 82 GDPR, powers of supervisory authorities, or mandatory consumer rights. There is no blanket indemnity for every consequence of using the service and no zero-fee liability cap that overrides those rights.
12. Changes to these terms
Material changes will be communicated with their proposed effective date and explanation. Where agreement is legally required, we will seek express acceptance; silence alone is not consent. A DPA already concluded is not silently replaced by editing this website. Statutory rights to reject changes or end the service remain available.
13. Governing law, disputes and contact
German law applies, excluding the UN Convention on Contracts for the International Sale of Goods. If you are a consumer, this does not remove mandatory protections of the law of your habitual residence or your legally available courts. For merchants and other parties for whom a jurisdiction agreement is legally permitted, Munich is the agreed venue. Mandatory jurisdictions remain unaffected.
You can contact ali.raza@bevel.software to seek an amicable resolution. No compulsory US arbitration, class-action waiver or obsolete EU Online Dispute Resolution platform is imposed. Statutory rights to complain to a supervisory authority or bring proceedings are unaffected. If a clause is invalid, the remaining agreement and applicable statutory rules continue to apply.