Terms of Service

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: juan@bevel.software. These terms govern the website, playground, accounts and decision API at 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 Google accounts are welcome; using one does not waive consumer rights. 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 and request-form services, which can involve international processing.

3. Accounts, access and API credentials

Sign-in uses Google; we do not issue an account password. Keep your Google account, 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 US$42 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.

There is no automatic subscription, credit-card collection, auto-renewal or automatic conversion from free to paid use in the current service. When credits are insufficient, requests are blocked and you can apply for extra usage through the linked form. Promotional credits have no cash value and cannot be transferred or redeemed for cash.

Any paid arrangement requires a separate express agreement showing price, taxes, payment, cancellation and any statutory withdrawal information before you commit. These terms do not authorise a future payment or remove any mandatory refund or withdrawal right. Pricing changes apply prospectively after notice; they do not reprice completed requests.

5. 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.

6. 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.

7. 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.

8. Availability, changes and support

The current service has no contractual uptime percentage, latency guarantee or service-credit SLA unless separately agreed in writing. Maintenance, failures and capacity limits can affect availability. Contact juan@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.

9. Suspension, termination and data

You may stop using the service at any time and request account closure at juan@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.

10. 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.

11. 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.

12. 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 juan@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.