This document has not been translated yet and is shown in English.
Scope: this policy covers the website amarbaro.com only. The AMARBARO Android
applications each have their own policy: ABCam,
ABSend, ABDoc.
Last updated: 6 November 2026
This site is server-rendered, not static: it has accounts and logged-in, moderated blog comments, and it may show advertising served by Google AdSense, described below. Apart from the Google advertising scripts and the Cloudflare Web Analytics script, it loads no third-party resources: no external fonts, no embedded video.
We count page views with Cloudflare Web Analytics, which is cookieless and described below. The only other personal data processed is the server log described below, generated for every visit to keep the site secure, and whatever you choose to put in an email if you write to us.
Tomi Alexandru
Knullwald
Germany
Email: privacy@amarbaro.com
There is no statutory obligation to appoint a Data Protection Officer for this site (Art. 37 GDPR, § 38 BDSG), and none has been appointed.
This site writes its own request log to its database (not a Caddy access log file): one row per page you request, so we can see traffic, errors and abuse patterns without needing shell access to the server. A row can contain:
| Field | Example |
|---|---|
| IP address | 203.0.113.7 |
| Date and time of the request | 2026-09-02T14:03:11Z |
| Requested path and HTTP method | GET /impressum/ |
| HTTP status code | 200 |
| How long the request took | 12 milliseconds |
| Referrer, if your browser sends one | https://example.org/ |
| User agent string | Mozilla/5.0 (…) Firefox/141.0 |
| The account you were signed in as, if any | an internal account id, not shown here |
Stylesheets, scripts, images and this site's own internal endpoints are not logged: a crawler that fetches one page shows up once, not once per file that page also loads.
Purpose and legal basis. Delivering the site, keeping it stable, and detecting attacks and abuse. The legal basis is Art. 6 (1) (f) GDPR, our legitimate interest in operating a functioning and secure website. An IP address is personal data, which is why it is listed here even though we do not use this log to reconstruct what an anonymous visitor looked at.
When you are signed in. A request made while you are logged in also records which account made it. We use that link for two purposes: security (for example, recognising when an account is being used in an unexpected pattern) and your customer profile, where we can see which pages you visited while signed in, so we can support you and understand how customers use the site. The legal basis for both is Art. 6 (1) (f) GDPR. That is the one respect in which this log identifies you: an anonymous visit does not link to anyone, a signed-in request links to your account, and the profile never reaches further back than the retention period below. This activity is included when you request a copy of your data. It is never joined with the analytics described below.
Retention. Rows are kept for 30 days by default (configurable by us in the admin) and deleted automatically by a daily job once past that window. They are not merged with any data source beyond the account link described above, and are not used to build a cross-session profile of a visitor who is not signed in.
You can create an account at /account/signup. It is optional: browsing this site,
reading the blog and viewing the portfolio never require one.
What we store. Your name, your email address, a bcrypt hash of your password (never the password itself), and the time the account was verified. Legal basis: Art. 6 (1) (b) GDPR, performance of the contract you asked for by signing up.
Verification. We email a one-time link to confirm you control the address. Until you click it, the account cannot sign in. An unclicked link expires after 24 hours.
Retention. We keep account data for as long as the account exists. You can download a
copy of it, or delete the account entirely, from /account/profile at any time. Deletion
anonymises your personal data while keeping records the law requires us to retain, consistent
with the erasure right described under Your rights below.
One account, several surfaces. The same account signs you in here, lets you comment on the blog, and covers anything bought through the shop. We do not keep a separate account per surface.
Buying something in the shop requires the account described above: there is no guest checkout, because what an order grants (a licence, credit, or a prepaid code) has to belong to somebody.
What we store. The order itself (what you bought, the price, the currency) and the payment reference our payment processor gives it. We never see or store your card number, bank details or any other payment credential: those go directly to the processor's hosted payment page, not through our server.
Payment processing. Checkout is handled by Paysipa, our payment processor, under a data processing agreement (Art. 28 GDPR). Paysipa tells us, via a signed, verified notification, whether a payment succeeded, which is how an order is confirmed as paid; it does not tell us how you paid.
What a paid order writes. Confirmation grants exactly what you paid for: a licence
entry, a credit top-up, or a prepaid code, recorded against your account so /account
can show it back to you. Legal basis: Art. 6 (1) (b) GDPR, performance of the purchase
contract.
Retention. Order records are kept for as long as Swiss and German commercial and tax law require records of a sale to be kept, which is longer than the account itself. Deleting your account anonymises the personal data on past orders (the same way it anonymises the rest of your account, described above) but does not delete the transaction record itself, consistent with the erasure right described under Your rights below.
You can comment on a blog post while signed in. There is no anonymous form: a comment is tied to your account, not to a name typed into a box.
What we store. The comment text, which account posted it, the time it was posted, and the time it was reviewed. Legal basis: Art. 6 (1) (b) GDPR, performance of the contract you asked for by posting a comment.
Moderation. A new comment is held and shown to nobody, including its author, until we review and approve it.
Retention. A comment is kept for as long as the account that posted it exists. Deleting the account removes the comments posted under it along with everything else the erasure right covers, described under Your rights below.
You can ask for a quote on "Software on request" at /shop/request. It does not require an
account: this is a pre-sale enquiry, not a purchase.
What we store. Your name, your email address, and the description of what you are asking about, attached to your customer record. Legal basis: Art. 6 (1) (b) GDPR, steps taken at your request before entering into a contract.
Retention. We keep it as part of your customer record until you ask us to delete it (see Your rights below) or the record is otherwise cleared out.
The site is served from a virtual server rented from Contabo GmbH, Aschauer Straße 32a, 81549 München, Germany. Contabo processes the log data described above on our behalf as a processor under Art. 28 GDPR, under a data processing agreement. The servers are located in the European Union.
The site itself sets no cookies. Google AdSense, when it runs, may set cookies or use similar
identifiers; see Advertising (Google AdSense) below. The site stores one value in your
browser's localStorage:
| Key | Value | Purpose |
|---|---|---|
amarbaro-theme |
"dark" or "light" |
Remembers whether you chose the dark or light appearance. |
This value never leaves your browser. It is strictly necessary in the sense of § 25 (2) no. 2 TDDDG, because it provides the display setting you explicitly asked for. You can delete it at any time through your browser's site-data settings; the site will then follow your operating system's dark/light preference again.
Pages on this site may show ads delivered by Google AdSense, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland ("Google"). To deliver ads, measure them and prevent fraud, Google processes your IP address, browser and device data, and the page you are reading, and may read or store cookies or similar identifiers on your device.
Consent. Visitors in the EU, the EEA, the UK and Switzerland first see a consent dialog. It is Google's own consent management platform, certified under the IAB Transparency and Consent Framework. Google only uses cookies for personalised ads after you agree. If you decline, Google may still show non-personalised ads, which are chosen by the page content, and may still use cookies or identifiers for frequency capping, aggregate reporting and fraud prevention. You can change or withdraw your choice at any time through the privacy and cookie settings link the dialog leaves on the page.
Legal basis: Art. 6 (1) (a) GDPR and § 25 (1) TDDDG (your consent) for personalised ads and for storing or reading information on your device; Art. 6 (1) (f) GDPR (our legitimate interest in financing the site) for non-personalised ads. Google may process data in the United States; Google LLC is certified under the EU-US Data Privacy Framework. Details: How Google uses information from sites that use its services and Google's privacy policy. You can also turn off personalised ads for your Google account at adssettings.google.com.
We use Cloudflare Web Analytics, provided by Cloudflare, Inc., which also delivers this
site. A small script from static.cloudflareinsights.com loads with each page and reports
the page view to Cloudflare. It runs for every visitor, without a consent step.
It sets no cookie and stores nothing on your device. It reports aggregate page and
performance data such as the page URL, referrer, country, browser and device type. Our
dashboard shows totals, not individuals. Cloudflare receives your IP address as part of
delivering the request. Legal basis: Art. 6 (1) (f) GDPR, our legitimate interest in
understanding how the site is used. You can object at any time by writing to
privacy@amarbaro.com, and blocking the script in your browser stops it.
If you write to support@amarbaro.com, bugs@amarbaro.com or privacy@amarbaro.com, we
process your email address, your message and any information you choose to include, for the
sole purpose of answering you. The legal basis is Art. 6 (1) (b) GDPR where your message
concerns a contract or pre-contractual steps, otherwise Art. 6 (1) (f) GDPR — our
legitimate interest in responding to enquiries. We keep correspondence for as long as it is
needed to handle the matter and to comply with statutory retention periods, then delete it.
Our mailboxes are hosted by Purelymail LLC (United States), which acts as a processor. Transfers to the United States are covered by the EU Standard Contractual Clauses. Email is inherently not confidential in transit unless both ends use encryption; please do not send us sensitive personal data by unencrypted email.
Under the GDPR you have the right to:
To exercise any of these, email privacy@amarbaro.com. For a visit where you were not
signed in, our server log contains no identifier that lets us connect an IP address to you,
so for an access request about that data we may be unable to identify you within the
meaning of Art. 11 (2) GDPR. For a request made while you were signed in, the log row is
linked to your account, and we can locate it the same way as the rest of your account data.
You also have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR), in the EU member state of your residence, place of work, or of the alleged infringement.
The whole site is served over HTTPS with certificates from Let's Encrypt. Plain HTTP requests are redirected to HTTPS.
We update this policy when the site changes in a way that affects it: on 4 September 2026, when the consent-gated analytics described above was added, on 15 September 2026, when accounts, blog comments and the server-side request log described above replaced the earlier Caddy access log description, on 17 September 2026, when signed-in activity became part of your customer profile, and on 3 November 2026, when Cloudflare Web Analytics replaced the consent-gated counter. The date at the top always reflects the current version.
Language note. This Datenschutzerklärung is published in English and in German. Where German law requires German-language information, the German version governs.
Without your consent, no analytics data is stored or sent. Only after you consent do we store a random visitor identifier in your browser's local storage and a session identifier in session storage. On each page view, we send the page path, referrer (host and path), screen size, time zone, language, and a hash of browser and device characteristics (client hints, screen, time zone, language). Our server adds a shortened IP address and browser user-agent. These records are pseudonymous personal data.
The purpose is to count visits and see which pages are used so we can improve the site. Our legal basis is your consent under Article 6(1)(a) GDPR and § 25(1) TDDDG. Data is processed solely on our own server in the EU, with no recipients other than our EU hosting provider. We keep the data for 90 days so we can compare months and seasonal trends, after which it is deleted automatically.
You can withdraw your consent at any time for the future via “Cookie settings” in the footer. When you withdraw, the identifiers are deleted from your browser and sending stops. Withdrawal does not affect the lawfulness of processing carried out before it. You have the right to access, rectification, erasure, restriction of processing, data portability, and objection, as well as the right to lodge a complaint with your local data protection authority.