In the event of discrepancies, the German version is authoritative.

Controller

The controller responsible for processing personal data on this website is:

JITIS – Jakob IT und Informationssicherheit
Owner: Jonas Jakob
Karl-Stieler-Straße 18
93051 Regensburg
Germany

Telephone: +49 941 99227246
Email: info@jitis.io
Website: jitis.io

You may contact Jonas Jakob directly with privacy questions and to exercise your rights.

Overview

This notice covers our website, enquiries, callback requests, contract withdrawals, newsletters and job applications. Personal data include, for example, contact details, IP addresses and identifiers.

We process data under Article 6(1) GDPR: point (b) for contracts, point (c) for legal obligations, point (f) for legitimate interests and point (a) where consent is given. Access to devices is governed by section 25 TDDDG.

Hosting, delivery and server logs

We use Cloudflare for content delivery, website operations with Workers, the D1 database, and media and caches in R2. Media are delivered through media.jitis.io, among other channels. The EU jurisdiction is configured for R2; other Cloudflare processing may take place outside the EU. Payload is used to manage content and forms.

Cloudflare processes IP addresses, requested addresses, timestamps, browser and connection data. Error output may contain data relating to the relevant operation. We need this processing for delivery, troubleshooting and abuse prevention. The legal basis is Article 6(1)(f) GDPR, reflecting our interest in secure and accessible operations; point (b) additionally applies to contractual services. The technical recipient is Cloudflare, Inc., USA. We explain the contracting entities under “Recipients and processors”.

We delete our own operational and security logs no later than seven days after creation. In security incidents, necessary extracts are retained until the investigation and required legal proceedings are concluded. We no longer request Cloudflare network error reports; stored browser instructions may remain effective for seven days after last receipt.

For selecting settings, we determine the country from a country header through our own endpoint, without GPS location tracking. The dialogue also appears if the country is unknown. API responses containing personal data and the newsletter confirmation page include instructions against caching; stored data relating to the relevant operation remain unaffected.

Consent management and local storage

You can change your selection at any time using “Cookie settings” in the footer. The dialogue offers Necessary, Analytics, Marketing and Functional, as well as acceptance or rejection of all optional categories. It names Google Analytics 4 for analytics and Google Ads conversion measurement with Conversion Linker for marketing, both through Google Tag Manager; the provider is Google Ireland Limited. “Functional” currently has no separate service and only enables Google's signals for functionality and personalisation storage when Tag Manager is loaded because of analytics or marketing. This category alone does not load Tag Manager.

We store your selection locally in your browser under cookieConsent, including categories, decision time, information version and, where available, country. Restoring it does not change the original time. Without automatic expiry checks, the selection remains until changed or deleted by you or your browser. Necessary settings management is based on section 25(2), point 2 TDDDG and Article 6(1)(c) in conjunction with Article 7 GDPR, supplemented by our interest in reliable settings management under point (f).

Consent without categories or a matching information version does not activate optional services. We ask again; analytics, marketing and functional remain blocked until you decide. Stored refusals remain effective.

We ask again without preselecting optional categories. If saving a new decision fails, we remove the previously stored selection so that old consent does not remain effective.

Withdrawal of consent

You may withdraw your consent at any time with effect for the future. Withdrawal does not affect the lawfulness of processing based on consent before its withdrawal.

When you deselect a category, we set its Google consent signals to denied and stop further collection based on consent to that category. All open tabs of this website adopt the change; we also recheck the stored selection when you return to a tab. When analytics or marketing consent is withdrawn, the respective tab reloads if Tag Manager has already loaded. If you deselect only Functional, the signals are updated without reloading.

On every decision, when adopting changed categories from another tab and on page load, we clear accessible first-party identifiers according to the rejected categories:

Without analytics consent, cookies whose names begin with _ga.
Without analytics consent, the cookie _gid.
Without analytics consent, cookies whose names begin with _gat.
Without analytics consent, the cookie _clck from earlier Clarity visits.
Without analytics consent, the cookie _clsk from earlier Clarity visits.
Without marketing consent, cookies and local storage identifiers whose names begin with _gcl.
If analytics or marketing is rejected, cookies whose names begin with _gac.
If analytics or marketing is rejected, the cookie MUID, where accessible as a first-party cookie.

Clearing takes account of the path prefixes of the page being viewed and domain variants. We cannot remove cookies on third-party domains or without JavaScript access, particularly HttpOnly cookies, from the page. The information under “Former services” also applies to older pages that remain open.

We store your selection only in your browser; this does not automatically notify us of a withdrawal. When you withdraw a category, we remove the accessible identifiers for that category in your browser; this does not erase data already transferred to Google. Google deletes GA4 user and event data in its monthly deletion cycle after the configured two-month retention period expires; aggregated reports and Google Ads data are separate. We can attribute transferred data to you only through browser identifiers or, following a form enquiry, through its record and transaction identifiers. If you would like earlier erasure, an informal message to info@jitis.io is sufficient; insofar as we can attribute the data to you, we then arrange erasure with the provider.

The language follows the page path; we do not set a language cookie. Font files are delivered with the website.

Analytics and marketing

Google Tag Manager and consent

Before you consent, we do not load any Google scripts. We load Google Tag Manager GTM-P3WWWPZX only if you allow analytics or marketing, including through a stored selection. GA4 tags start only with analytics consent; Ads conversion tags only with marketing consent for advertising storage and advertising data use, and Conversion Linker only with marketing consent. Without consent to the respective category, its analytics or advertising tags do not start, including for measurement signals without cookies.

The legal basis is Article 6(1)(a) GDPR and, for device access, section 25(1) TDDDG. When scripts are retrieved, Google receives your IP address and browser data.

Google Analytics 4

We use GA4 G-4PVG1NMK7X to analyse reach and website usage. Enhanced measurement records page views including history changes, scrolling, outbound clicks and downloads; enabled video measurement applies to suitable embedded videos. Search terms may be transferred from the URL parameters q, s, search, query or keyword. Form interactions are not measured automatically.

After a contact or project form has been successfully stored, we send a success event with analytics consent; GA4 processes it as generate_lead with event, transaction and form attribution and as a key event. We also make further contact, appointment and action clicks and form starts available to the local measurement interface.

Google processes page addresses, referrers, campaigns, usage times, device/browser characteristics and pseudonymous user/session identifiers; granular location/device data are enabled worldwide. According to Google, GA4 does not store IP addresses. Analytics is based on your consent under Article 6(1)(a) GDPR and section 25(1) TDDDG. Technical recipients are Google companies, including Google LLC, USA.

Google Signals and user-provided data, including automatic detection of contact details, are disabled. Automatic form measurement is turned off, including for contact, project and withdrawal forms; our handling of them remains unaffected. GA4 remains linked to Google Ads. Sharing analytics data for advertising purposes depends on your marketing consent.

Further information: Enhanced measurement.

Google Ads and attribution of enquiries

With your marketing consent, we use Google Ads 16898247270 to measure advertising performance: successfully stored lead forms with a transaction identifier, and clicks on telephone and email links. A click confirms neither a conversation nor the sending of an email. We have not configured a dedicated Ads conversion tag for appointment bookings.

Conversion Linker starts only with your marketing consent. It stores ad click information from the landing address in first-party cookies and local storage. URL passthrough is disabled; measurement identifiers are not linked with the former company domain. For links to other addresses under jitis.io, Conversion Linker may append identifiers to the destination address. Enhanced conversions and the use of user-provided contact details are not enabled.

We store UTM campaign information, the landing page and a shortened referring address under jitisLeadAttribution in session storage only with analytics or marketing consent, and Google click identifiers only with marketing consent. Entries beginning with jitisLeadSuccess prevent duplicate form success reports. When both categories are deselected, we remove this attribution data; when marketing is deselected, we remove the click identifiers. Session storage generally ends with the tab session but may persist through browser restoration.

Permitted campaign data may be stored with contact enquiries. We independently add handling context such as the service and location. Our event function does not pass names, email addresses or message text as such; record identifiers remain linkable. Its URL sanitisation does not automatically apply to Google scripts. The legal bases for advertising measurement are Article 6(1)(a) GDPR and section 25(1) TDDDG. Recipients are Google and, for information stored alongside enquiries, our form and email service providers.

Google cookies and retention

GA4 uses cookies beginning with _ga to distinguish users and sessions. Google specifies two years by default; Chromium limits cookies to a maximum of 400 days. New visits may renew the cookie lifetime.
Advertising measurement uses cookies beginning with _gcl. Google specifies 90 days from setting these conversion cookies; setting them again may renew the period.
With marketing consent and browser support, Google and DoubleClick cookies may be used or set, including on Google domains. New visits may renew cookie lifetimes. Cookie lifetimes are separate from server-side retention.

Local Conversion Linker storage has no automatic expiry; a cookie lifetime does not limit it. We remove accessible linker identifiers from local storage if marketing consent is absent or withdrawn, on every page load and every decision.

Google specifies Ads report availability of 37 months for hourly/daily/weekly figures and eleven years for monthly/quarterly/annual figures, and three years for reach and frequency. These are reporting periods, not blanket raw-data erasure periods. According to Google, security and billing data may be needed longer. Ads retention, Erasure limitations.

Disabling Google Signals and user-provided data does not immediately erase data already collected. According to Google, the shorter GA4 period applies to existing Signals data, and the configured user retention period applies to user-provided data.

We retain GA4 user and event data for two months, without extending the period through new activity. According to Google, it deletes expired data monthly. Aggregated standard reports, cookies and Google Ads data follow separate rules.

Details: GA4 retention, GA4 cookies, advertising cookies, Google cookie lifetimes.

Former services

Newly loaded pages no longer include Microsoft Clarity, Ahrefs Web Analytics or Google reCAPTCHA Enterprise. This does not stop scripts already running in previously opened older tabs or erase data already transferred. Please reload or close such pages; older pages may also not yet support adopting changed consent. Information on recipients, retention and international transfers continues to apply to remaining personal data from earlier use.

We have deleted the Microsoft Clarity and Ahrefs projects and thereby initiated deletion of the data stored there; we have deactivated the reCAPTCHA key. Data processed by providers as independent controllers remain subject to their retention periods.

Microsoft Clarity

Until 13 October 2026, we used Microsoft Clarity with analytics consent for session recordings and heatmaps. Data collected included mouse movements, clicks, scrolling, page structure, visible content, and performance and error data; available GA4 user and session identifiers were passed on to link the analyses. The bases were Article 6(1)(a) GDPR and section 25(1) TDDDG.

Microsoft processes Clarity data as an independent controller. The Clarity terms also permit service improvement and user profiles including advertising. Processing in the USA is possible. According to Microsoft, regular recordings are retained for 30 days, and tagged or favourited sessions and click and heatmap data for nine months from collection; subsequent deletion includes backups. We remove remaining Clarity cookies if analytics consent is absent:

The cookie _clck for recognition and settings storage had a configured lifetime of 365 days.
According to Microsoft, the cookie _clsk for linking page views into a session lasts one day from writing or updating.

Earlier Clarity visits may also leave the session and upload token _cltk in session storage. Our consent cleanup does not remove this entry. Its duration depends on the tab session and possible browser restoration.

Details: Clarity data processing, Cookies, Retention.

Ahrefs Web Analytics

Until October 2026, we used Ahrefs Web Analytics with analytics consent. The recipient was Ahrefs Pte. Ltd., Singapore. Data collected included page views, full page addresses, referrers, page titles, language, screen dimensions and pixel density, link clicks with destination addresses and key states, form submission events with the form destination, and script errors and stack traces. The bases were Article 6(1)(a) GDPR and, for relevant device access, section 25(1) TDDDG.

According to Ahrefs, the service uses no cookies, discards raw IP addresses after processing and generates pseudonymous identifiers that change daily. The provider mentions country/city inference, browser data, aggregated studies, product improvement and US storage. We have initiated deletion of stored project data by deleting the project; the provider's retention criteria apply to data it processes as an independent controller. Singapore is not covered by the EU-US Data Privacy Framework.

Details: Ahrefs Web Analytics, Privacy policy.

Google reCAPTCHA Enterprise

Until October 2026, we used Google reCAPTCHA Enterprise to prevent abuse of contact, project and withdrawal forms. On a submission attempt, verification tokens, site keys, expected actions, available IP/browser details and technical risk signals were processed; according to Google, the security cookie _GRECAPTCHA was set.

Our processing was based on Article 6(1)(f) GDPR, reflecting our interest in protection against automated attacks; strictly necessary device access was based on section 25(2), point 2 TDDDG. Google Cloud EMEA Limited, Ireland, processed customer data as a processor; processing in the USA is possible. For Cloud service data, Google specifies mostly up to 180 days, or longer for specific security incidents or legal obligations. This is not a uniform period for reCAPTCHA customer data or its cookie. Details: reCAPTCHA data processing, Cloud retention.

Contact, forms and job applications

Contact and project enquiries

We process your contact details, message and, depending on the form, enquiry type as a business or private individual, company for business enquiries, telephone number, project type, needs, scope, budget, timeframe and source page. Data are stored in our database and sent internally by email; some project selections appear only in the internal message. For the project form, we also store the IP address and browser identifier truncated to a maximum of 500 characters in the database; the internal email does not contain these two details. We remove them after 14 days in the daily deletion run.

The project form stores the draft needed to resume the form under salesFunnelState in session storage for the tab session, even without analytics or marketing consent. It contains the step, project selections, budget, seats, needs, timeframe, name, enquiry type, company where applicable, email, telephone and message. Forms with an automatically preselected project scenario may create a draft containing the form state and empty input fields before you enter anything; your input is subsequently added so that you can resume the form. We erase it after successful submission and do not write it again. A company name is not required for private enquiries. There is no separate expiry check; for unfinished enquiries, the tab session and possible browser restoration determine its duration.

Article 6(1)(b) GDPR applies to initiating and handling contracts; point (f), reflecting our interest in appropriate handling, applies to other contacts and business contact persons. Storage strictly necessary for requested form functions is based on section 25(2), point 2 TDDDG. Acknowledging the privacy notice is not consent to advertising.

Electronic withdrawal form

For the withdrawal function, we process your name, contract reference, any part of the contract specified, email address, statement and receipt time, as well as your IP address and browser identifier truncated to a maximum of 500 characters. The IP address and browser identifier are removed after 14 days in the daily deletion run. We also store check signals for a completed hidden field, a check that was too fast or missing, an exceeded rate limit, maintenance mode and fallback storage, as well as delivery statuses for the acknowledgement of receipt and internal notification.

We accept valid withdrawal submissions even when anomalies, an exceeded rate limit or maintenance mode apply; these circumstances do not cause rejection. We personally review anomalies. If regular storage fails, direct fallback storage in the database is attempted. If this also fails, we attempt an internal emergency email with your details and display a notice asking you to send your withdrawal by email to info@jitis.io.

Acknowledgements of receipt and internal notifications are processed through a persistent queue with separate delivery statuses. For submissions without anomalies, we attempt delivery immediately; submissions with anomalies are handled through the regular run every ten minutes. Delivery failures trigger retries at increasing intervals of up to 24 hours between attempts; after eight failed attempts, delivery is marked as failed and an internal alert email is attempted. To prevent abusive confirmation emails, we limit acknowledgements to three per address in 24 hours; further acknowledgements are deferred by one hour at a time, not discarded. This does not guarantee delivery within 24 hours; your stored statement is unaffected by delivery failures or deferrals. The system reports permanently failed acknowledgements internally. We personally follow up these and any overdue acknowledgements and use another delivery method where necessary.

Insofar as section 356a BGB applies to the respective contract, we process the necessary details for the statutory online withdrawal function under Article 6(1)(c) GDPR. Further contract reversal is based on point (b), and necessary legal evidence on point (f). Withdrawal is also possible by an unambiguous statement emailed to info@jitis.io or sent by letter; we point out the email alternative at every step. See the withdrawal information.

Job applications

We process contact details, qualifications, professional history and voluntarily submitted documents to decide whether to establish an employment relationship under section 26(1) and (8) BDSG in conjunction with Article 88 GDPR; necessary legal defence is based on Article 6(1)(f) GDPR.

We initially store new registrations with express consent as unconfirmed: email address, optional name, language, source path, request time, consent flag, consent text version, status, IP address and browser identifier truncated to a maximum of 300 characters. We store only the version identifier of the consent text, not the text itself. We keep one record per email address; no immutable event history is created. Authorised administrators can change or delete records after signing in.

You receive a neutral confirmation email with a link valid for 72 hours. Only the confirmation button, not opening the link, activates your registration. We store the confirmation time and active status and trigger the welcome email. You can normally request a new confirmation email after ten minutes, or potentially earlier if sending fails. Resubscribing after unsubscription also requires this procedure. Regular campaign sending is disabled.

Registration and sending based on consent rely on Article 6(1)(a) GDPR and section 7 UWG. You may withdraw through the unsubscribe link or by contacting us. Unsubscription changes the status and reduces the record to the suppression and defence evidence described below. We maintain necessary consent evidence under Article 6(1)(c) in conjunction with Article 7(1) GDPR. Necessary suppression and defence records are based on Article 6(1)(f) GDPR; our interest is preventing unlawful mailings and defending specific claims.

We mark earlier newsletter addresses without provable consent as unsubscribed and exclude them from sending. We do not send re-opt-in emails. You may initiate a new registration yourself through the confirmation procedure. Suppression records follow the stated evidentiary retention period.

Recipient selection for regular campaigns includes only active subscribers with confirmation evidence.

Protection against abuse

Contact, project and newsletter forms use a hidden check field and a minimum completion time of three seconds. Only a check value containing the version, elapsed time and whether the hidden field was completed is transmitted; the field's text is not transmitted. We additionally limit submissions using the IP address supplied by Cloudflare: contact and project forms to ten each, and newsletter registrations to five per ten minutes. The limit applies per server instance in memory; rate-limit data are not stored persistently. Where rejections are logged, the protection entry contains only the reason, not an IP address. Separate storage of metadata in accepted records is described above.

Our form protection uses no additional third-party services and sets no cookies. It is based on Article 6(1)(f) GDPR, reflecting our interest in secure transmission and abuse prevention; insofar as strictly necessary device access occurs, it is based on section 25(2), point 2 TDDDG. We do not use reCAPTCHA. For withdrawals, the checks serve only as handling indicators; exceeding the limit of ten submissions per IP address in ten minutes does not cause rejection there.

Email and telephone

We process contact details, messages and necessary conversation content under Article 6(1)(b) GDPR for contractual contacts, point (f) for our interest in responding to other communications, and point (c) for statutory documentation obligations. We send website emails through Microsoft 365 with support@jitis.io as the technical sender. Microsoft processes sender, recipient, content and delivery data. Mailboxes follow the retention period for the relevant matter.

Appointment booking through Microsoft

We link to Bookings on outlook.office.com without embedding it. Microsoft and we process the appointment/contact data entered to organise appointments. Article 6(1)(b) GDPR applies to our contractual contacts; otherwise, point (f) applies, reflecting our organisational interest. Microsoft's Privacy Statement applies to its own processing. You can also arrange appointments by email or telephone.

External links and social networks

We link to TeamViewer downloads, the separate customer portal portal.jitis.io, and Facebook, Instagram and LinkedIn. Opening a link generates connection data at the destination provider. A TeamViewer download does not start remote support; this is governed by the agreed engagement. The Google Maps address appears in structured business data. We do not embed social or map modules.

Recipients and processors

Active recipients are Cloudflare for hosting, database, media and operational security, Google for tag management and measurement, and Microsoft for email and appointment booking. Recipients of personal data from former services also include Microsoft for Clarity, Ahrefs for web analytics and Google Cloud for reCAPTCHA. Authorities and legal advisers receive data where required by legal obligations or necessary pursuit of legal claims. Payload is management software; its use alone does not make it an additional data recipient.

Our active contracting entities are Cloudflare, Inc., USA, for hosting, Workers, D1 and R2, Google Ireland Limited, Ireland, for Analytics, Ads and Tag Manager, and Microsoft Ireland Operations Limited, Ireland, for Microsoft 365 including Bookings. For Cloudflare, Analytics, Tag Manager and Microsoft 365 including Bookings, the agreed processing terms under Article 28 GDPR apply. Google Ads is generally governed by terms between independent controllers; enhanced conversions are not enabled. Google Cloud EMEA Limited, Ireland, was the processor for the former reCAPTCHA service; Microsoft Ireland Operations Limited, Ireland, was the contracting entity for Clarity, and Microsoft processes Clarity data as an independent controller.

Transfers to third countries

Google, Cloudflare and Microsoft may process data in the USA. Transfers to actively certified recipients covered by the EU-US Data Privacy Framework are based on Article 45 GDPR. Google LLC and Microsoft Corporation are actively certified; Cloudflare, Inc. is active with recertification under review. The entries also cover non-HR data.

Transfers without an adequacy decision require appropriate safeguards under Article 46 GDPR; analytics consent does not replace them. The information under “Former services” applies to personal data remaining at Ahrefs. You may obtain information about applicable safeguards and, where relevant, a copy through our contact details.

Retention

Automatic deletion runs for the website database are scheduled daily at 02:17 UTC. They process due records in limited batches; they pause during a maintenance write restriction. Expiry of a retention period and the actual deletion run may therefore occur at different times. The queue for withdrawal acknowledgements continues during this restriction.

Contact and contract records

We delete enquiries that do not lead to a contract no later than six months after handling is completed, or earlier if their purpose ceases. Statutory retention and evidence for specific legal disputes follow the separate rules.

In the website database, we delete contact and project enquiries regardless of their outcome six calendar months after receipt in the daily run; we keep contract records outside the website database.

We retain commercial and business correspondence subject to statutory retention for six years, accounting vouchers for eight, and books, inventories and financial statements for ten years. Periods begin at the end of the year of receipt, dispatch or creation, respectively; for tax-related financial statements, preparation under section 147(4) AO is decisive, while adoption applies under section 257(5) HGB. Section 257 HGB additionally applies where we qualify as a merchant. Under our reasoned policy, we generally retain other necessary contract evidence for three years from the end of the year in which contract administration is completed; statutory limitation periods start under their own conditions. Emails, including sent messages, follow the period for the relevant matter. Statutory extensions and specific legal disputes may require longer retention; processing is then restricted to the evidentiary purpose.

Technical metadata

We remove IP addresses and browser identifiers from form, withdrawal and newsletter records after 14 days in the daily run; the period runs from collection, or from the last confirmation request for newsletters. If that time is missing, the deletion run uses the record's last modification time. We clear operational email and export copies under the same 14-day period. New internal project enquiry emails do not contain these details. In documented abuse or legal cases, only necessary information is retained separately until final resolution; other data follow their own periods.

We delete unconfirmed newsletter registrations in the daily run once the last request is more than 30 days old, even if the confirmation email could not be delivered. Suppression evidence from earlier unsubscriptions is not deleted in this process, and its period remains unchanged. We do not send automatic reminder emails.

If the confirmation request time is missing after a delivery failure, the deletion run uses the record's last modification time.

During a subscription, we keep one record per email address containing an optional name, language, source path, consent text version and the times of registration, confirmation request and confirmation. After unsubscription, we retain only the email address, status, language, consent flag, consent text version, the times of registration, confirmation and unsubscription, and the unsubscribe link identifier as suppression and defence evidence. This reduction takes place immediately when the unsubscribe link is used, or otherwise in the next daily run. We delete this evidence in the daily run after three years have elapsed from the end of the year of unsubscription; deletion is suspended while a resubscription is pending. Further unsubscribe requests after unsubscription do not extend the retention period. In the daily run, once the last request is more than 30 days old, we reduce an unconfirmed resubscription to this evidence without changing the retention period; if the person unsubscribes again during this time, the period starts anew. After an unconfirmed resubscription, language and text version come from the latest registration. A confirmed resubscription replaces the evidence; we do not retain earlier subscription periods. Following the transition, we retain earlier addresses without confirmation evidence only as suppression evidence; if no unsubscription time is recorded, the period starts with the transition. We delete the evidence earlier if its purpose ceases sooner; we retain evidence needed for specific legal disputes separately until those disputes are concluded.

Contract withdrawals and job applications

We retain only parts of withdrawal statements and acknowledgements that qualify as business correspondence subject to statutory retention for six years from the end of the year of receipt or dispatch, respectively; refund vouchers are retained for eight years from the end of their creation year. Section 356a BGB does not itself establish a six-year retention period. We generally delete other necessary legal evidence three years after the end of the year in which reversal is completed, and purposeless additional data earlier; IP addresses and browser identifiers after 14 days.

Withdrawal statements are not deleted automatically; we clear them ourselves according to these periods. Only IP addresses and browser identifiers are removed automatically in the daily run.

We delete application documents no later than six months after receipt of the rejection or, where the procedure ends otherwise, after that documented event. If you are hired, we transfer only necessary documents. Evidence needed for specific legal disputes remains restricted until final resolution.

Other provider and storage periods

We delete our own copies of Ads reports no later than 90 days after creation. Provider reporting periods do not guarantee erasure of all personal raw data at that point. We restrict further retention to necessary billing, resolution of specific security incidents or statutory evidence until the relevant purpose ends or obligation expires.

Backups

We use Cloudflare D1 on the paid Workers plan with a recovery window of 30 days. We delete additional database backups managed by us after no more than 30 days. Backups are used exclusively for recovery; we reapply deletions already due before resuming regular use. In Microsoft 365, a recovery period of 14 days is configured for messages removed from the Deleted Items folder. Documents required by law or restricted for specific legal disputes follow their separate retention rules.

We delete personal data once the purpose and retention obligations cease to apply. Where further retention is justified, we restrict processing to the relevant purpose.

Your rights

Subject to the statutory requirements, you have the following rights:

Access and a copy under Article 15 GDPR.
Rectification and completion under Article 16 GDPR.
Erasure under Article 17 and restriction under Article 18 GDPR.
Information about recipients of rectifications, erasures or restrictions under Article 19 GDPR.
Data portability under Article 20 GDPR for automated processing based on consent or a contract.
Objection under Article 21 and withdrawal of consent under Article 7(3) GDPR with effect for the future.
A complaint under Article 77 GDPR, particularly to the supervisory authority where you live, work or where the alleged infringement occurred.

The competent authority for private-sector organisations in Bavaria is the Bavarian State Office for Data Protection Supervision (BayLDA):

Visitor address: Promenade 18, 91522 Ansbach, Germany
Postal address: Postfach 1349, 91504 Ansbach, Germany
Website and access to complaints: BayLDA

Right to object under Article 21 GDPR

You may object at any time, on grounds relating to your particular situation, to processing based on Article 6(1)(e) or (f) GDPR, including profiling based on those provisions. We will then cease processing unless we demonstrate compelling legitimate grounds overriding your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. You may object to direct marketing, including related profiling, at any time without giving a particular reason; your data will subsequently no longer be processed for those purposes.

Automated checks and provision of data

Our form protection automatically rejects contact, project and newsletter submissions if the hidden check field is completed, fewer than three seconds have elapsed, the check value is missing or invalid, or the respective rate limit is exceeded. Contract withdrawals are never rejected for these reasons. You can contact us at any time via info@jitis.io, request personal review, present your position and challenge the rejection.

You do not have to use our contact forms. The project form requires a name, email address, enquiry type as a business or private individual, acknowledgement of the privacy notice and project selections depending on the scenario, including required information on needs, scope and timeframe. For business enquiries, we require a company name; it is not required for private enquiries. Budget and telephone number are optional. The form is not submitted without the required information. Other forms mark their required fields.

Online withdrawals require a name, contract identification and an email address for confirmation; specifying a part of the contract is optional. Unambiguous statements through other channels remain possible. Without usable contact details, we generally cannot reply. Analytics, marketing and newsletters are voluntary and are not a prerequisite for contacting us.

Last updated

13 October 2026.

Privacy notice