Provider-specific terms

Provider and notices

The provider is Timo Fitzner, individual provider established in Greece, postal address Irinis 104, 15341 Agia Paraskevi, Greece. The service is Screen Self-Service for Jira. Support, privacy, security and contractual notices can be sent to tfitzner90@gmail.com. Customers with portal access may also use the support portal. No automatic administrator access to a customer's Jira site is included.

Agreement and attachments

The intended base is the unmodified Bonterms Standard End User Agreement, Version 1.0, offered through Atlassian. These Provider-Specific Terms identify the additions and variations for this free beta. They do not select the standard agreement in the Marketplace or assert that a customer has agreed.

The Data Processing Addendum, version BETA-DPA-2026-10-30.2, is an attachment for processing on the customer's behalf. The Support policy, version BETA-SUPPORT-2026-10-30.2, states the support offered during the beta. The Security statement describes safeguards and their limits. The Privacy Notice explains provider-controlled correspondence and website processing separately.

The applicable customer, order/effective date and exact attachment versions must be identifiable in the agreement record before customer use. A later website edit does not silently replace an adopted contract or expand processing instructions. Mandatory law and any applicable transfer clauses take priority within their scope.

Free beta period and price

The beta is for the customer's controlled internal evaluation of the documented capabilities. For the evaluation-period provision in section 18 of the base agreement, the designated period begins with the customer's first installation and continues until either party ends beta participation. The customer may stop using and uninstall the app. The provider may end participation under the base agreement and will communicate the end of the beta or a proposed paid offer through the agreed contact route.

There is no app fee, per-user charge or automatic paid conversion during this beta. A later paid subscription requires separate information and agreement through the applicable subscription process. Jira and other Atlassian subscriptions are separate from this app offer.

Beta support

The beta includes the published Support policy: Monday–Friday, 10:00–18:00 Europe/Athens, with a target first response within two working days. This expressly varies section 18's exclusion of Support to the extent necessary to provide that policy. The target is not a guaranteed fix time, an availability SLA or 24/7 cover. Other beta provisions of the base agreement are unchanged, subject to mandatory law.

The provider currently operates the beta personally, without a designated deputy. Planned absence is communicated in advance where practicable. An absence notice does not extend statutory privacy or incident deadlines. Confidential support access, attachments containing customer data and any live intervention require a separately agreed purpose, method, permissions and duration.

Supported scope and customer control

The supported scope and bounds are described in Getting started. The customer chooses installations, enabled projects, Jira roles, group restrictions and approval policy. The app checks current authority, configuration dependencies and applicable field rules. New configuration requires another Jira administrator; unsupported or unverified changes remain blocked.

Use a dedicated test project before an operational project. Jira changes can have partial or uncertain outcomes and may conflict with changes by other administrators. The service does not promise atomic Jira transactions, automatic rollback or universal field visibility.

The customer remains responsible for its Jira configuration, authorised instructions and copies it exports. An encrypted history backup restores readable app records, not Jira configuration or past approval authority. The provider cannot recover a forgotten backup passphrase. Disabling or uninstalling does not undo Jira screens or schemes already created.

Data, termination and changes

The customer retains control over its workspace data. Return/deletion instructions, protected work, platform lifecycle and separate copies are handled under the DPA. Provider-controlled support copies are reviewed no later than 90 days after case closure for continuing necessity; this is a review point, not a promise that every copy is erased automatically on day 90.

Customer data is not used for advertising or AI-model training. No external app backend, advertising integration or additional analytics dataset is introduced by these terms. Any material change to the service, data recipients or agreed terms follows the applicable notice and agreement process; it is not authorised solely by updating a page.

Applicable law and courts

For section 19.2(b) of the base agreement, the governing law is the law of Greece and the courts are the competent courts of Athens, Greece. Mandatory statutory protections and jurisdiction rules remain unaffected.

Document version: BETA-2026-10-30.2, 30 October 2026. The effective date is the date of the customer's applicable agreement/order; provider preparation or publication alone does not create a customer agreement.