Privacy

What is not collected here

• No cookies, no tracking, no analytics tools.
• If you choose “Light” or “Dark” in the page header, your browser remembers that choice (local storage, entry jico_darstellung). It never leaves your device and is not sent to us; “Match system” deletes the entry. It is stored only on your explicit click — no consent is required for this under § 25 (2) no. 2 TDDDG.
• No forms that take in data — with the one exception of the newsletter sign-up below. Other enquiries go through the linked e-mail addresses, straight from your own mail program.
• No embedded third-party content (no maps, no videos, no remotely loaded fonts) — the newsletter form, too, is a plain HTML form without any loaded script; only when you submit it does the sign-up go to the provider, whose confirmation page opens in a new tab while this page stays open.

Server logs

The website and the customer portal are hosted by Cloudflare. When you open these pages, Cloudflare, as our hosting provider, processes technically necessary access data (IP address, time, page requested) in order to deliver and secure the service (Art. 6 (1) (f) GDPR). No evaluation beyond that takes place.

Newsletter sign-up

• What: an email address — no name, no company. Optionally, if ticked, which topics interest you (hosted solution, local installation), so that we only send you what fits. Without a tick we store nothing about it. Choosing “Register interest” in the “Hosted” section signs you up for the newsletter and marks the topic hosted solution. We also store the language version of the page you signed up on (German for Germany, German for Switzerland or English), so that the newsletter reaches you in your language.
• How: through an external newsletter service with double opt-in — the sign-up only takes effect once you click the confirmation link. The address passes from the form through our web server (Cloudflare, see above) directly to the service; we do not store it along the way.
• Withdrawal: every email carries an unsubscribe link with which consent can be withdrawn at any time without giving reasons (Art. 7 (3) GDPR).
• Legal basis: consent (Art. 6 (1) (a) GDPR).
• Separate from the portal: this applies regardless of whether the sign-up comes from an existing customer or a prospect — the sign-up is technically and legally separate from the licence and the customer account in the portal.

Provider: Brevo GmbH, Köpenicker Str. 126, 10179 Berlin, Germany (a Brevo group company, parent: Brevo SAS, Paris) — as processor (Art. 28 GDPR); the data processing agreement is part of Brevo's terms of service. Which further sub-processors Brevo uses is listed there. Some are located outside the EU, including the US; transfers rely on the European Commission's standard contractual clauses and, for the US, where applicable on the EU-US Data Privacy Framework.

Retention: the email address remains stored until consent is withdrawn; proof of the consent itself (time of confirmation) is kept by the provider for a short time beyond that as evidence.

JiCo on LinkedIn and WhatsApp

Next to the newsletter, the website links to our company page on LinkedIn and our WhatsApp channel. It is an ordinary link: opening the website transfers nothing to LinkedIn, and there are no embedded buttons or counters. Only if you click the link do you go to LinkedIn (LinkedIn Ireland Unlimited Company, Dublin), where their privacy policy applies.

The same applies to our WhatsApp channel: the website only links to it. Following the channel happens in WhatsApp (WhatsApp Ireland Limited, Dublin); as channel operator we do not see the phone numbers of followers.

Account and sign-in

• Email address and customer number — for the sign-in by link and the assignment to the contract. Retention: as long as the customer relationship exists. If you delete your account (a message to us is enough), we replace your address and those of your team members throughout the portal with a pseudonym, delete sign-in links, access and quota, and block your licences; invoice records remain, without the address, for the statutory retention period. We also remove the remote-access tunnel; we archive the contact in sevDesk (the invoices stay linked to it) and delete your customer record at Stripe.
• Sign-in links and sign-in codes, as a checksum only — a link is valid for 15 minutes and once; the code belonging to a link tolerates at most five failed attempts, which are counted. Retention: until used or expired, then deleted.
• Self-registration — email address, version of the accepted trial terms and time of consent, as proof that, and to which version, consent was given. The account is only created once the link in the confirmation email is redeemed. Retention: the record is only ever appended to and is not deleted automatically; if you delete your account, it remains with a pseudonym instead of the address.
• Team members — the member's email address, the account they belong to, the address of the person who invited them, and the time of the invitation, of the first sign-in and, where applicable, of the removal. Reason: several sign-ins per account need an assignment, and who invited whom must remain traceable. Retention: removal ends access, the entry itself remains (after an account deletion, with pseudonyms instead of addresses); a new invitation of the same address overwrites it.

Licences

• Licences (identifier, scope, term, licence file) — so that you can find them again. The licence file carries the customer number, the machine code (a checksum of the device identifier, not a computer name) and the public installation key of your JiCo installation — no name, no address. Retention: term plus ten years, then deleted.
• Licence requests (by email to lizenz@getjico.com or directly from JiCo) — sender address, the verified request block and what is read from it (customer number, scope, partner, machine code), the result of the sender check (DKIM/SPF), status and, where applicable, the reason for rejection. No subject, no message text, no attachments. Retention: until decided, then one year, then deleted. The email itself is forwarded to our support mailbox.
• Blocks — licence identifier, reason (such as a second dunning notice for an invoice, or a withdrawal by you) and since when, so that the licence is put on the signed block list. Retention: until lifted.
• Expiry reminders — an email to the account address 10, 7, 3 and 1 day(s) before a licence expires and on the day of expiry itself; only which reminder has already been sent for which licence is stored. Blocked accounts are not reminded.

Invoicing and payment

• Billing address — company, street, postcode, town, country and VAT ID, maintained by you in the “Account” area; paying customers provide it before the first invoice. It is passed, together with the customer number, to our invoicing software sevDesk. Retention: as long as the customer relationship exists; after an account deletion ten years (statutory retention of invoices), then deleted.
• Orders and invoice references — seats, term, currency, amount, tax case, order status, and the identifier and number of the invoice in sevDesk. The invoice itself is created in sevDesk; the portal fetches the PDF fresh from there when you open it and does not store it. Retention: the retention period for invoices.
• Queries to sevDesk — per query the time, type, invoice or customer concerned, result, and payment and dunning status, no response text. Retention: 400 days.
• Invoice emails — the invoice arrives by email with a link to the “Invoices” area of the portal; the portal also announces by email when purchased seats are activated.

Paying by card or SEPA direct debit (Stripe)

Every order results in an invoice in sevDesk. Stripe is only a payment method for an invoice that already exists — alongside bank transfer.

• What the portal passes to Stripe: email address, customer identifier, invoice number, gross amount and currency, and the order identifier.
• What Stripe collects itself: the payment details. Stripe does not issue an invoice; the portal does not ask for a billing address or VAT ID through Stripe.
• What the portal stores about it: no payment details — only that, and when, the invoice was paid. From the earlier purchase flow (payment first at Stripe), the Stripe session identifier, seats, term, currency, net and gross amount and payment status remain per purchase. Retention: the retention period for invoices.
• Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).
• Stripe's role: by its own account controller and/or processor depending on the activity; details in Stripe's privacy policy.

Suggest a feature and report an issue

In the "Suggest a feature" section you can send us a wish or feedback; in the "Report an issue" section, likewise a problem. The same applies to both:

• What is passed on: the title and text of your wish and, optionally, the place in JiCo you came from. We create an entry from it in our non-public task tracking at GitHub (GitHub Inc., USA) — without your e-mail address, company or customer number. The portal replaces e-mail addresses in the text before sending.
• What the portal stores about it: only that your account reported a wish and under which number — so that we can get back to you with questions.
• Confirmation by e-mail: you receive a thank-you e-mail at your sign-in address with the number, title and text of your suggestion, without a link. The portal does not store the e-mail.
• Please do not enter: content from Jira or Confluence, or names or addresses of people.
• Legal basis: legitimate interest in developing the product (Art. 6 (1) (f) GDPR).
• Retention: until the wish is implemented or rejected, then as long as we keep our development records.

Remote access (only if you switch it on)

If you explicitly switch on remote access in the JiCo panel, you can reach your local JiCo installation while away.

• Setup: JiCo sends the portal the licence identifier, the public installation key, the machine code and the local port, signed with the installation key. The portal then creates a tunnel with the hostname <licence identifier>-relais.getjico.com in our Cloudflare account and returns only the associated tunnel key to JiCo, without storing it. Stored are the licence identifier, tunnel identifier, hostname, time of provisioning and a secret that binds the sign-in to exactly this installation.
• Sign-in: whoever opens the hostname in a browser signs in with their portal account (/fern/anmelden). The portal issues a short-lived, signed sign-in token for this, which names the role (owner or member) but no email address; only the fact that a token was issued or refused is counted.
• Route of the traffic: all traffic to the relay hostname passes through Cloudflare. The encrypted connection ends at Cloudflare's edge and is forwarded from there through the tunnel to your JiCo installation; Cloudflare can therefore technically see the content of this traffic. That content is the calls from your AI client to JiCo and their responses, in the form redacted by JiCo, as well as the sign-in and approval pages.
• Protection rules: at Cloudflare's edge, rules let through only the paths JiCo serves there and limit sign-in attempts per IP address.
• Legal basis: performance of a contract (Art. 6 (1) (b) GDPR); the protection rules serve security (Art. 6 (1) (f) GDPR).

Update check (only on click)

When you click “Check for update” in JiCo, JiCo sends the portal the licence identifier, the public installation key, the machine code, platform and partner, signed with the installation key. The portal uses them to check the licence and names or delivers the latest released version. When a package is downloaded, the portal keeps, per licence, only which package was last downloaded and when (one row, overwritten by the next download), so that you can see under “Your licences” which installation is out of date and when its package expires. Beyond that, only the fact that a check, a download or a refusal took place is counted. JiCo never asks in the background.

Access for AI agents (only with your code)

An AI agent acting on your behalf can read your licence overview - but only if you start it yourself. The agent gives the portal an e-mail address; if it belongs to an account, the portal sends a 6-digit code there. Only when you give the agent this code does it receive a key.

• What is stored: the e-mail address, and code and key only as a checksum, with expiry, number of failed attempts and the time of redemption or revocation. No name of the agent, no IP address.
• What the agent sees: only the licence overview (identifier, scope, term, block flag) - not the licence file, no invoices, no packages. It cannot change anything or create an account.
• Limits: the code is valid for 15 minutes, once, and tolerates at most five failed attempts; the key is valid for 12 hours and can be revoked earlier. If the account is blocked or the team member removed, access ends immediately.
• Legal basis: performance of the contract at your request (Art. 6(1)(b) GDPR).
• Retention: the code is deleted after redemption or expiry, the key after expiry or revocation.

Operations and traceability

• Daily counters (such as the number of sign-ins, downloads, emails sent) — without personal reference, to assess operations. Retention: 400 days.
• Administration log — what a member of our staff does in the administration area (time, their address, action, customer or package concerned; when issuing a licence, also the request and licence identifiers and the term). It is only ever appended to; the one change: if you delete your account, we replace your address in it with a pseudonym. Retention: the record-keeping period for contracts.
• Error lines — on a technical error, the path, error type and message, with email addresses blacked out, never a sign-in link or form content.

What the portal does not collect

The portal itself stores no IP address, no browser type, no record of who downloaded what and when, no click paths and no referrer. Signing in needs no password and sets a technical session cookie (12 hours, HttpOnly) — no tracking, no third-party cookies. If you choose “Light” or “Dark” in the header, the portal sets a second cookie on that click, holding only this choice (jico_darstellung, 1 year, no personal data); “Match system” deletes it. If you choose a language in the header (DE · CH · EN) or open the portal via a link from the Swiss or English version of this website, the portal remembers the language in a third cookie (jico_sprache, 1 year, only the language code, no personal data). Without such a choice, the language follows your browser’s language setting; nothing is stored for that. No consent is required for any of the three cookies under § 25 (2) no. 2 TDDDG.

Legal bases

• Account, licences, invoicing and payment: performance of a contract or steps prior to entering into one (Art. 6 (1) (b) GDPR).
• Retention of invoice data: statutory retention obligations (Art. 6 (1) (c) GDPR).
• Registration record, administration log, inviters in teams, counters and error lines: our legitimate interest in proof, traceability and secure operation (Art. 6 (1) (f) GDPR).

Who processes on our behalf

• Cloudflare — hosting of the website and the portal: runtime, database, file storage in the EU jurisdiction, sending of portal emails, receipt of mail to lizenz@getjico.com and support@getjico.com, tunnel and protection rules for remote access; as a processor.
• sevDesk — our invoicing software for invoicing and dunning. Company, billing address, VAT ID, customer number and the invoice items go there — never content from Jira or Confluence.
• Stripe — payment by card or SEPA direct debit (see above).

Cloudflare and Stripe belong to groups of companies headquartered in the USA; processing of the data mentioned may therefore also take place in the USA.