Privacy Policy
Information on the processing of personal data on the website xictraq.com and when using the platform.
Last updated: November 2026
1. Controller
Controller within the meaning of the General Data Protection Regulation (GDPR):
XICTRON — Lennart Harmes
Glockruthenallee 16
31185 Söhlde, Germany
Phone: +49 (0) 5123 9579000
E-Mail: mail@xictraq.com
2. Hosting and Data Center
The website xictraq.com, the platform and all associated databases are hosted in data centers within the European Union (locations Nuremberg, Falkenstein and Helsinki). Data processing agreements pursuant to Art. 28 GDPR are in place with the hosting processors (named in section 10). No personal data is transferred to third countries outside the EEA in the hosting layer; individual processors expressly listed in section 10 (in particular Anthropic for the optional AI chat assistant and the AI visibility feature) process data in the USA on the basis of the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR).
3. Server Log Files
When this website, the customer area, the status pages or the interface at api.xictraq.com are accessed, the web server automatically stores an entry in its access log: the full IP address of the requesting device, date and time, the request method and the requested address including any parameters it contains, the HTTP status code, the amount of data transferred, the referring page (referrer) and the browser identifier (user agent), from which the browser type and version and the operating system can be seen. If an error occurs during a request, the web server's error log also records the IP address and the request. In addition, our application writes an entry containing the full IP address to its own error log in certain cases: in the event of a failed or unverifiable check of an access key or signature, a rejected registration (together with the email address entered) and a detected manipulation attempt against the AI chat assistant (together with the beginning of the message and the identifier of the conversation and, if you are signed in, of your account). This data is used exclusively for system security and error analysis and is not merged with other data sources. The following storage periods apply: the web server's access logs are rotated daily and deleted automatically after ten days. The web server's error logs, by contrast, are rotated not by time but by size; when an entry is deleted therefore depends on how quickly the file grows with new entries. Because comparatively few entries arise there, entries can remain in them for several months. The same applies to the access logs of rarely accessed addresses, such as little-used subdomains: without new requests their file is not rotated, so entries there can also remain for several months. Our application's error log is started anew each day; each daily file is deleted automatically after 14 days. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in trouble-free and secure operation).
4. Cookieless Visitor Statistics
For audience measurement we use XICTRAQ® on xictraq.com, our own cookie-free analytics system. On each page view the following is processed: the page visited and the referring page (referrer), campaign parameters, the approximate time on page, screen and window size, the device class derived from them, browser and operating-system category including version, and — where the browser states them on its own — form factor, device family and manufacturer, the approximate location (country, region, city, postal code and coordinates, derived from the IP address), the internet provider including its network number (ASN), the selected language, and the date and time of the visit; if a JavaScript error occurs on the page, also its message and location in the code, with email addresses in it and access values in contained URLs (such as token= or key=) made unrecognisable. Collection is carried out entirely without cookies, without fingerprinting and without transfer to third parties.
For audience measurement no cookies are set and no information is stored in or read from the browser; consent under § 25(1) TDDDG is therefore not required for this. To distinguish visits, a pseudonymous daily identifier is formed from the IP address and a daily key (salt). The daily key is a random value generated anew each day and deleted once the day is over; after that, the daily identifier can no longer be attributed to an IP address in the visitor statistics. The IP address is used only to form this identifier, for approximate geographic classification, to determine the internet provider, to detect automated access and, for at most one minute, to limit the number of requests, and is not stored in the visitor statistics; the web server's access log (section 3) also contains these requests with the full IP address. If you talk to our AI chat assistant, it stores the IP address of the conversation (section 9b). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in the statistical evaluation of website usage). Additionally, for click and scroll heatmaps on xictraq.com the individual clicks (position, element type and visible text of the clicked element) and the scroll depth are captured, pseudonymously via the daily identifier — see section 8b for details. Session recording is disabled by default on xictraq.com and only runs after active consent given via the cookie consent banner (see section 8b-r for details).
5. Registration and User Account
To use the paid and free functionality of the platform, it is necessary to create a user account. We process: name, email address, password (stored as a secure hash, never in plain text), selected plan, language preference, timestamps of registration and last login. For business customers, additionally the company name, billing address and VAT identification number. Legal basis: Art. 6 para. 1 lit. b GDPR (contract performance or pre-contractual measures). The data is deleted as soon as it is no longer required for contract performance and no statutory retention obligations (in particular §§ 147 AO, 257 HGB) exist. In the account area we log sign-ins and sign-in attempts as well as actions that change something or download data (such as settings, websites, invoice and data exports), each with the time, the requested path, the submitted details (with passwords and access keys redacted), the result, the IP address and the browser identifier (account log). Failed sign-ins and rejected registrations are recorded together with the email address entered. The purpose is to make account changes traceable and to detect misuse, the legal basis is Art. 6(1)(f) GDPR; the entries are deleted after twelve months.
Sign-in with Google: if you choose this sign-in, we redirect you to Google. After your consent there, Google sends us an identifier of your Google account, your email address together with whether Google has verified it, and your name. We store the provider, this identifier and the email address to assign the sign-in to your user account; when a new account is created, we take over name and email address into the user account. The privacy notice of the provider applies to the sign-in with the provider itself. The legal basis is Art. 6(1)(b) GDPR. The link can be removed in the account settings.
Referral programme: if someone registers through the referral link of a customer, we store the link between both user accounts, the email address of the referred account, the state of the referral with the time it took effect, and the identifiers of the discounts we create for it with the payment provider Stripe. The legal basis is Art. 6(1)(b) GDPR.
5b. Security notices to business domains (outreach)
When our public security index detects concrete technical issues on a German business domain (e.g. expired SSL certificate, missing security headers, GDPR-relevant pre-consent trackers, mixed content), we send a one-time factual notice with the specific findings to the contact address listed in that domain's imprint. For this purpose we process only data the recipient has themselves published in their public imprint (address, responsible party, e-mail) plus the technical scan results for the domain. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in security and compliance information in the B2B context) in conjunction with § 7(2)(3) UWG (presumed interest of the recipient in an immediate technical finding regarding their own domain). Maximum three messages per domain, minimum 90-day cooldown between messages. Every message contains a one-click unsubscribe link (RFC 8058); revocation takes effect immediately and permanently at e-mail and domain level. The message contains an image element loaded on open (open-tracking) — for the message we record only the first open timestamp, no IP address and no repeated opens; like every request, loading the image element appears in the web server's access log (section 3); revocation any time via the unsubscribe link. Recipients of outreach messages are not XICTRAQ® customers; their data is processed separately from customer data and, after unsubscribe, kept on a suppression list so that further sending is technically excluded.
6. Monitoring and Check Data
As part of using the platform, the websites specified by the customer are automatically checked by our monitoring agents from the DACH region. In the course of these checks, technical data about the respective website is collected (URLs, HTTP headers, response times, SSL certificate metadata, DNS records, detected third-party scripts, cookies found, accessibility and SEO evaluations, screenshots of the website). This data is assigned to the respective customer account and stored there until the customer deletes it or terminates their account; monitoring raw data and screenshots are deleted automatically at the latest once the periods stated in section 11 have expired, with the exception of the baseline capture stated there.
Insofar as the websites monitored by the customer contain personal data of third parties (e.g. visitors to the customer's website, names visible in the imprint), such processing is carried out by us on behalf of the customer pursuant to Art. 28 GDPR. In this respect, the customer is the controller and we are the processor. The arrangements required by Art. 28(3) GDPR are contained directly in Annex E1 (data processing) of our Terms and become binding upon contract conclusion; no separate written DPA is required.
We evaluate technical measurements without personal reference (such as availability, response times and certificate, DNS and header findings) in aggregated form that allows no conclusions about individual customers or websites, including after the contract has ended, for statistics and benchmarks. We do not use data that we process on behalf of our customers for this purpose.
7. Cookieless Analytics on Customer Websites
If the customer embeds our tracking script (“t.js”) on their own website, visitor data of that website is also processed using the procedure described in section 4. Processing is carried out exclusively on behalf of the customer. The customer is obliged to make the processing transparent to visitors on their own website (own privacy policy) and to verify the legal basis of its use on their website.
8. Payment Processing (Stripe)
For paid plans we use the payment service provider Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland. Payment data (credit card, SEPA direct debit) is processed directly on Stripe's servers; XICTRAQ® has no access to full payment details. We only receive payment status, billing period and an invoice ID. Legal basis: Art. 6 para. 1 lit. b GDPR (contract performance). Further information can be found in Stripe's privacy policy.
8a. Passkeys (WebAuthn)
You may optionally log in with a Passkey (WebAuthn / FIDO2) instead of a password. The cryptographic private key stays exclusively on your device or hardware token and is never transmitted to us. On our servers we store only the public key, a credential ID, the signature counter of the authenticator, the model identifier of the authenticator (AAGUID, from which we display the provider, such as a password manager), the transports reported by the device (such as internal, USB, NFC), the times of registration and last use, and a display name so you can distinguish multiple Passkeys. We do not collect any biometric data. You can revoke any Passkey registration individually in your account area at any time. Legal basis: Art. 6 para. 1 lit. b GDPR (contract performance / authentication) and our legitimate interest in account security pursuant to Art. 6 para. 1 lit. f GDPR.
8b. Click and Scroll Heatmaps
Customers may optionally enable click and scroll heatmaps on their own websites. Each click is stored individually: the position on the page (as a percentage of page width and height), window and page size, device class, host name, URL path including query parameters (values that grant access or name a person are replaced by *), the type of the clicked element and its visible text (at most 100 characters), and flags for repeated and ineffective clicks. Scroll depth is stored per page view as a percentage. Each click carries the pseudonymous daily identifier of the visit (section 4); the identifier itself contains neither a name nor an IP address, and no cookies are set for this. The captured visible text may contain information that the page itself displays, such as the name of a signed-in customer, unless the area is masked. Email addresses in the click text are made unrecognisable before storage, except addresses of the website's own domain, such as a contact address. Form inputs and passwords are not captured; the heatmap does not record the session (see section 8b-r for that). Activation is performed by the customer, who is responsible for informing visitors in their own privacy notice. Legal basis: Art. 6 para. 1 lit. f GDPR (legitimate interest in usability optimisation); where consent is required under TDDDG, Art. 6 para. 1 lit. a GDPR.
8b-r. Session Recording
On xictraq.com we run session recording only when you actively enable the "Session recording" category in our cookie consent banner. Default is off; without consent no recording takes place. With consent given we record session activity (DOM mutations, mouse, scroll and click movements, page interactions and timestamps) pseudonymously: each recording carries the daily identifier of the visit (section 4); the identifier itself contains neither a name nor an IP address, and no third-party cookie is set. The recording may contain information that the page itself displays, such as the name of a signed-in customer, unless the area is masked. Input fields and content marked as sensitive — passwords and text fields in particular — are masked automatically in the browser before upload (maskAllInputs); credit-card and IBAN patterns are redacted. We use the open-source library rrweb, served from our own domain — no external script hosts, no third-party cookies. Recordings are stored on servers in the EU for no longer than 90 days and then deleted automatically. Revocation: at any time with future effect via the cookie settings link in the footer; already stored recordings will be deleted on request pursuant to Art. 17 GDPR. For the duration of the session an identifier for the recording is stored in your browser (sessionStorage); it is deleted when the tab is closed. Legal basis: Art. 6(1)(a) GDPR (consent) in conjunction with § 25(1) TDDDG.
8c. API Access and API Keys
Users may create their own API keys in the account area to use the XICTRAQ® API programmatically (e.g. export, integrations, custom dashboards). Each key is stored only as a hash; the plaintext is shown only once at creation. We log API calls (endpoint, HTTP status, timestamp and client IP) to detect abuse and enforce rate limits; storage only takes place as long as it is necessary for these purposes. Legal basis: Art. 6(1)(b) and (f) GDPR. You can revoke all keys instantly at any time.
8d. Status Page Subscriptions
If a customer operates a public status page, its end-users can subscribe there to incident notifications by email. For this purpose we store the email address, the subscribed status page and a randomly generated confirmation and unsubscribe token (double opt-in). Processing is carried out on behalf of the status page operator pursuant to Art. 28 GDPR; the legal basis towards the subscriber is their consent pursuant to Art. 6(1)(a) GDPR. Every notification email contains a personalised unsubscribe link. After unsubscription, all data stored for subscription management is deleted without undue delay.
8e. Free Online Check Tools
On our website you can have a domain checked without registering. For the free website check, which checks a website as a whole (including availability, SSL, security headers, data protection and SEO), we store for each check the address you entered, the result, the duration of the check as well as your IP address and the country derived from it, browser identification, referring page and preferred language. The purpose is abuse prevention, enforcement of usage limits and operational statistics; the legal basis is Art. 6(1)(f) GDPR. After 90 days at the latest we remove the IP address, browser identification, referring page and language from these entries; the remaining row without personal reference is kept for operational statistics. The individual check tools at /tools (including SSL check, security score, PageSpeed, Open Graph tags, email authentication and accessibility) keep no such log: they process the request in memory and in some cases keep the result for a domain in the cache for up to one hour, without any reference to the caller; like every request, the call is recorded in the web server's access log (section 3), for tools that pass the input in the address including the input.
Customers on the agency plan can embed the website check as a component in their own website. If you check a domain via such an embedded component, we record, in addition to the details in the previous paragraph, for the operating customer which address was checked, which page the call came from and which country it originated in. In this additional record your IP address does not appear in plain text but only as a salted hash used solely for recognising repeat requests. This processing is carried out on behalf of the embedding customer pursuant to Art. 28 GDPR.
8f. Shop API Connection (Shopware 6)
Customers can connect a Shopware 6 shop via its Admin API. For this we store the credentials of an integration created by the customer (the secret only in encrypted form) and the address of the API. Once a day we read the shop's version number through it. If the customer also switches on the order status, we request once a day, for the purchases captured by the tracker in the last 30 days, the order number and the status of the order, payment and delivery. For the order status we do not request names, addresses, email addresses or order line items. The status appears only in the customer's own order log, not via share links. We delete it together with the purchase events after the retention period of the plan, and immediately when the customer switches off the fetch or disconnects the shop. Processing is carried out on behalf of the customer pursuant to Art. 28 GDPR.
In addition, the customer can switch on the order import. Only while this switch is on do we use the same integration to fetch the shop's entire existing order history once and then, on an ongoing basis, new and changed orders, including orders entered in the shop's administration, for example after an order by telephone. For each order we fetch: order number, time of the order and of its last change, gross and net amount, tax, shipping costs, currency, payment and shipping method, the status of the order, payment and delivery, the sales channel as a technical identifier, whether the order was created in the Shopware Administration (only this flag is stored, not the user who created it), the line items with product number, name, variant, quantity, unit price and line total, as well as the first and last name, company and customer number of the person ordering. We do not fetch the email address, billing and shipping address, telephone number, the comment of the person ordering, VAT ID, or campaign, affiliate and deep-link codes. The role required in Shopware technically makes further details readable, for example the email address of the person ordering; we do not request them. Shopware only delivers the additional details of a line item as a whole; of these we keep the product number and variant attributes and discard the rest. We store the name, company and customer number only if the customer's plan includes the identification of customers. If a purchase captured by the tracker exists for an order, we assign the order to that purchase instead of counting it twice; the remaining orders count in the customer's e-commerce reports without reference to a visit. This processing, too, is carried out on behalf of the customer pursuant to Art. 28 GDPR; as the controller, the customer informs the people ordering from them in their own privacy policy.
We delete the imported orders, line items and details of the person ordering after the retention period of the plan (section 11), when the customer removes the website from XICTRAQ®, and immediately when the customer switches off the order import or disconnects the shop. Irrespective of this, we remove the first and last name, company and customer number of the person ordering with the daily automatic deletion as soon as the order is 365 days old; the remaining order data is not affected. For orders that are already more than 365 days old when fetched, we do not store these details. The name, company and customer number of the person ordering appear only in the customer's own area, not via share links.
8g. Storage in Your Browser (Technically Required)
Independently of audience measurement (section 4), which stores nothing in your browser, the website and the customer area keep individual items in your browser's storage (localStorage or sessionStorage) to provide functions you request: your choice in the cookie settings; the selected colour scheme and your accessibility settings; the state of the AI chat (session identifier, window size and position, your consent to the chat, whether a notice was closed); briefly cached public platform status data for the lifetime of the tab; after a registration from a quote, the noted checkout destination, for at most 14 days and deleted after sign-in; the destination after signing in with an external provider (currently Google); the state of the demo access. In the customer area this also includes: your sign-in (access identifier, until you sign out), views, sort orders, dashboard layouts and notes, the progress of the security assistant and the widget configurator, and notices and introductions already seen. If you open a shared dashboard link and rearrange its cards, that arrangement is also remembered in your browser. These items serve no measurement, are not passed to third parties and are not evaluated by us; apart from the access identifier, which accompanies each request to our API, they do not leave your browser. The legal basis is § 25(2) no. 2 TDDDG; processing is based on Art. 6(1)(b) GDPR or, for display settings, Art. 6(1)(f) GDPR. You can delete these items at any time via your browser settings.
9. Transactional Emails and Notifications
As a registered user you receive transactional emails that are necessary for providing our Service (registration confirmation, password reset, monitoring alerts, weekly/monthly reports, invoices, contract information). Legal basis: Art. 6 para. 1 lit. b GDPR. Alert notifications can be deactivated or adjusted in scope and channel (email, browser push, Slack, Discord, Telegram, Microsoft Teams, webhook) at any time in your account settings. Transactional emails without advertising character will still be delivered after deactivation, insofar as this is indispensable for contract performance.
Dispatch log: for the emails our system sends, including those to recipients without an account such as subscribers to status notifications, we store the recipient address, the subject, the type of email derived from it, the dispatch result (with the error message in case of a failure), the message ID, the file names of attachments and the content of the email. Links containing access values, for example for confirming, resetting or unsubscribing, are made unrecognisable before storage. The log serves as proof that an email was sent and for troubleshooting delivery problems; only our administrators can view it. Legal basis: Art. 6 para. 1 lit. f GDPR; our legitimate interest is email delivery that can be verified. If your account is deleted, we also remove the entries for the email addresses of your account, except emails that must be retained as business letters; the periods otherwise are set out in section 11. The legal basis for retaining these business letters is Art. 6 para. 1 lit. c GDPR in conjunction with § 257 HGB and § 147 AO.
Browser notifications (web push): if you switch on browser push in the notification settings, your browser asks for your permission. If you grant it, the push service of your browser vendor assigns a delivery address for this device. For your account we store this delivery address, the two keys we use to encrypt the content for your device, the browser identifier (user agent), the intended types (alerts, reports, chat, incidents), the time of registration and of the last successful delivery, and the number of consecutive failed deliveries; we also renew the times and the counter whenever you open the customer area on this device. We hand every notification (title, short text, link into the customer area, for chat replies their first 120 characters) to this push service in encrypted form; only your browser can read it. The push service learns the delivery address, our public sender key together with a contact address of ours, the time and the size of the message. It is operated by your browser vendor, not by us, and may be located outside the European Union. Legal basis is your consent (Art. 6 para. 1 lit. a GDPR), which you give via the browser prompt. You can withdraw it at any time by switching off browser push in the settings or by revoking the permission in your browser. When you switch it off we delete the registration immediately; if the push service reports the delivery address as expired or delivery fails ten times in a row, we delete it at that attempt; all registrations are removed with your account.
9a. Contact Form
If you write to us via the contact form, we process your name, your email address and your message in order to answer your enquiry. We forward these details by email to our mailbox and add the IP address and the browser identifier (user agent) of your device as well as the language of the page, so that we can recognise abusive submissions. To reject a duplicate submission of the same message, we keep a hash value of the email address and message for ten minutes, not the details themselves. The forwarded email is recorded in the dispatch log (section 9) and deleted there after 90 days. Legal basis: Art. 6 para. 1 lit. b GDPR insofar as your enquiry aims at the conclusion or performance of a contract, otherwise Art. 6 para. 1 lit. f GDPR; our legitimate interest is answering your enquiry. Providing the details is voluntary; without name, email address and message we cannot accept the enquiry.
9b. AI Chat Assistant (Anthropic)
We provide an AI-powered chat assistant for product consultation, documentation help and configuration support. For response generation we use the language-model API of Anthropic, PBC, San Francisco, USA. The following data is transmitted to Anthropic:
- content of your chat messages;
- prior chat history of the current conversation (max 30 messages);
- current page URL / section (e.g. "/app/websites/[ID]") for contextual responses;
- for authenticated users: current plan, number of websites, selected website data (status, score, alerts) — when the assistant actively queries these to answer your question;
- for authenticated users: the entries in the assistant's memory (Settings → AI memory), at most 40 per conversation.
A data processing agreement under Art. 28 GDPR is in place with Anthropic. Transfer to the USA is based on the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR). Anthropic contractually guarantees that API data is not used to train AI models ("Zero Data Retention" for API calls). Processing is exclusively for response generation. Legal basis for authenticated users: Art. 6(1)(b) GDPR (performance of the XICTRAQ® service contract); for visitors who are not signed in: Art. 6(1)(a) GDPR (consent, which you give by confirming the notice in the chat window; we store the time of consent with the conversation).
Storage: Chat transcripts are stored in our EU-hosted database and deleted automatically: conversations without a login 30 days after the last message, conversations of logged-in users after twelve months. For each conversation we also store the IP address and the browser identifier of the device it was started from; without sign-in, the IP address binds the conversation to that device so it can only be continued from there. Both are deleted together with the conversation after these periods; the legal basis is Art. 6(1)(f) GDPR. Authenticated users can remove their conversations themselves at any time: individually in the chat archive ("Delete conversation for good") or all at once ("Delete all"). The "Clear history" button, by contrast, only ends the current conversation and moves it to the archive; it is then deleted within the periods stated above. Entries in the assistant's memory remain stored until you delete them under Settings → AI memory or delete your account; deleting a conversation does not remove them. Requests for full deletion are handled in accordance with Art. 12(3) GDPR.
IP address and link to visitor statistics: For each conversation we store the IP address and the browser identifier (user agent) of your device together with the chat transcript; both are deleted with the conversation after the periods stated above. The IP address is used to protect conversations without a login from access by others and to enforce usage limits against abuse. On the day of the conversation we also use it to form the daily identifier of the visitor statistics (section 4) and thereby link the conversation to the page views of the same visit on xictraq.com (including pages visited, origin, approximate location and device), so that our team can put the request into context. Once the day is over, this link is no longer possible because the daily key has then been deleted. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in protection against abuse and in advice tailored to the visit).
Access and handoff to staff: Staff members of the XICTRAQ® team can view conversations and take over an ongoing conversation to reply in person. If you explicitly ask for a staff member or agree to a handoff offered by the assistant, the conversation is handed over to a staff member. While a staff member handles the conversation, your messages are not transmitted to the AI service provider. If the staff member hands the conversation back to the assistant, the assistant receives the previous history as usual (at most 30 messages), including the staff member's replies.
Voice input: If you use the microphone in the chat, we send the recording (at most 8 MB, at most 90 seconds are evaluated) to our server. There a speech recognition model running on our own server converts it into text; the recording itself is not passed to any third party, including the language-model provider named above. The recording and its converted version exist on the server only as working files for the duration of the conversion and are deleted afterwards; if a file is left behind after an interruption, we remove it within two days at the latest. We place the recognised text in your input field; only when you send it is it processed like any chat message. The legal basis is the same as for the chat.
10. Recipients and Processors
To deliver the Service, we engage carefully selected data processors with whom we have concluded agreements pursuant to Art. 28 GDPR:
- Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany — hosting of the platform, databases, email delivery and all server infrastructure in data centers within the EU;
- Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland — payment processing (credit card, SEPA Direct Debit, EU VAT);
- Anthropic, PBC, 548 Market Street, PMB 90375, San Francisco, CA 94104, USA — AI response generation in the optional chat assistant and in the AI visibility/share-of-model analysis (details see section 9b), and texts in the customer area: summaries in reports, drafts for incident notices on status pages and descriptions of detected competitor changes; for these, the respective metrics and findings are sent to Anthropic in aggregated form, no data on individual visitors; transfer to the USA based on the EU Standard Contractual Clauses pursuant to Art. 46(2)(c) GDPR; Anthropic contractually does not use API data for training purposes (Zero Data Retention).
Third-party services optionally configured by the customer in the user account (e.g. Slack, Microsoft Teams, Discord, Telegram, generic webhooks) for forwarding alerts are not processors of the Provider. Transmission to these services takes place solely at the customer's instruction; the customer is responsible for the data protection assessment of these third-party services.
No personal data is passed on to third parties beyond this unless we are legally obliged to do so.
11. Storage Period
We store personal data only for as long as necessary for the agreed purposes (Art. 5(1)(e) GDPR). Monitoring and analytics raw data are deleted automatically and irrevocably after a period that depends on the booked plan. Monitoring raw data (including availability, SSL and security checks and screenshots): Free 7 days, Starter 30 days, Business 90 days, Agency 180 days. The exception is the most recent capture of the visual change detection per website: it serves as the baseline for the next check and is kept until a newer one replaces it or the website is removed. Analytics data: Free 30 days, Starter 90 days; on the Business and Agency plans no plan-dependent period applies and the data remain stored for as long as one of these plans is booked; after a switch to a plan with a period, that period applies after a run-off of up to 30 days. Upper limits apply irrespective of the plan: session recordings are stored for no longer than 90 days (section 8b-r), assignments of visits to customer accounts of the customer's website are deleted once they have not been confirmed by a new visit for twelve months, and section 8f applies to the name, company and customer number from the order import. The “Extended data retention” add-on extends the period for monitoring raw data to 24 months and removes the period for analytics data. Independently of that, all personal data are removed within the framework of our deletion concept after the contract ends; the period for this is set out in § E12(4) of our Terms. As proof of the deletion we keep the name, email address and plan of the deleted account for twelve months; after that these details are removed from the record. Invoices of a deleted account remain restricted with name, address and VAT ID until the end of the statutory retention period of eight years after the end of the year of issue (§ 147 AO, § 14b UStG) and are anonymised afterwards. Quotes sent to a deleted account likewise remain restricted until the end of the retention period of six years after the end of the year in which they were sent or accepted (§ 257 HGB, § 147 AO) and are anonymised afterwards. Invoicing and tax-relevant data are retained in accordance with the statutory retention periods under §§ 147 AO, 257 HGB and deleted after these periods have expired. Separate periods apply to data not tied to a contract: entries from the free website check lose their personal reference after 90 days (section 8e), unconfirmed subscriptions to status notifications are deleted after 30 days, the account log after twelve months (changes made by the operator to an account's plan, discount, trial, payment method and invoices after eight years, like the related invoices), the dispatch log of our emails likewise after twelve months (after 90 days for recipient addresses with no associated account; emails that are business letters, i.e. those on invoices, payments, payment reminders, subscriptions and quotes as well as notices of suspension or on the contract, after six years from the end of the year of dispatch, also after an account deletion), team invitations that were not accepted after 90 days, the web server's access logs after ten days, its error logs and the access logs of rarely accessed addresses with their size-based rotation, before which several months can pass, and the application's error log after 14 days (section 3).
11a. Obligation to Provide Data and Automated Decision-Making
The provision of your personal data is neither legally nor contractually required; however, it is necessary for the conclusion and performance of the contract. Without the information required for a given function, the corresponding part of the service cannot be provided.
No decision based solely on automated processing — including profiling — within the meaning of Art. 22 GDPR takes place.
12. Your Rights as a Data Subject
Under the GDPR, you have the following rights regarding your personal data:
- Right of access (Art. 15 GDPR)
- Right to rectification (Art. 16 GDPR)
- Right to erasure (Art. 17 GDPR)
- Right to restriction of processing (Art. 18 GDPR)
- Right to data portability (Art. 20 GDPR)
- Right to object to processing based on legitimate interests (Art. 21 GDPR)
- Right to withdraw consent (Art. 7 para. 3 GDPR)
To exercise your rights, a simple email to mail@xictraq.com is sufficient. To prevent misuse, we may request suitable proof of identity.
13. Right to Lodge a Complaint
You have the right to lodge a complaint with a data protection supervisory authority pursuant to Art. 77 GDPR. The authority responsible for XICTRAQ® / XICTRON is the State Commissioner for Data Protection of Lower Saxony, Prinzenstraße 5, 30159 Hannover, Germany (lfd.niedersachsen.de). You may also contact the supervisory authority of your habitual residence or your place of work.
14. SSL/TLS Encryption
This site and the platform use SSL/TLS encryption for security reasons and to protect the transmission of confidential content. You can recognise an encrypted connection by the fact that the browser's address bar displays “https://” and by the lock icon in your browser bar.
15. Changes to this Privacy Policy
We update this privacy policy whenever changes arise for legal or operational reasons. The current version can always be found on this page. Logged-in customers are additionally informed of material changes by email.