Privacy policy
Last updated: 16 October 2026.
In short
This page explains what happens to personal data on engager.marlonjesus.com: the product page, the G4A Engager console, and the chat window when a website embeds it from this server. The product page sets no cookies, runs no scripts, has no analytics and loads nothing from other websites. G4A Engager sends nothing to its maker or to anyone else; data goes to another service only when one is connected on purpose, as described below.
Who is responsible
Dr. Jesus del Valle
Sonatenweg 10
13158 Berlin
Germany
Email: yeysus@gmail.com
When you open a page
To deliver a page, your browser necessarily sends the server your IP address and the usual details of the request: the address of the page, the time, and the name and version of your browser. The web server uses them only to send you the page and writes no access log. The application behind it logs requests without your IP address or browser details. These technical logs stay on the server and are read only to find and fix faults.
Legal basis: Art. 6(1)(f) GDPR, the legitimate interest in delivering this website securely and keeping it working.
Hosting
The server is rented from Contabo GmbH, Aschauer Straße 32a, 81549 München, Germany, and stands in a data centre in the European Union. Contabo processes this data on my behalf under a data processing agreement (Art. 28 GDPR).
The console: your account
If you have an account, the following is stored: your email address, your name, your password only as an argon2id hash (never the password itself), your language, an optional profile picture and the time of your last sign-in; for each organization you belong to, your role and display name. Two-factor authentication is optional; its secret is stored encrypted.
Signing in sets one cookie, g4a_session: HttpOnly, Secure, SameSite=Lax, valid for 30 days or until you sign out. It is strictly necessary to keep you signed in (§ 25(2) no. 2 TDDDG). For each sign-in the server keeps a hash of the session token, when it started and was last used, the IP address and the browser’s user-agent text. You can see these sessions in your profile and end them. They are not yet deleted automatically after they expire.
To slow down password guessing, sign-in attempts are counted per IP address and per email address in temporary memory for 5 minutes (sign-up and password reset: 1 hour). After 5 wrong two-factor codes the account pauses for 15 minutes and you get an email about it.
What is done in an organization (who, which action, on which record, when, and from which IP address) is written to a tamper-evident audit log. It is kept for 3 years by default; the organization can change that period.
The console saves a few settings in your browser’s storage: the colour theme (g4a.theme), the language (g4a.locale), whether the inbox sidebar is open (g4a.inbox.sidebar) and the last phone line used (g4a.phone.lastLine); unsent reply drafts are kept in session storage until the tab is closed. None of this leaves your device.
The system sends you emails it needs to: invitations (the link is valid for 7 days), password resets (valid for 1 hour), a notice when two-factor sign-in was paused, and notifications such as a visitor’s offline message. They go out through the mail server configured for this deployment; if that is an email provider’s server, the provider processes them as well. If browser push notifications are switched on and you allow them, their text goes through your browser maker’s push service.
Legal basis: Art. 6(1)(b) GDPR, providing the account you asked for; Art. 6(1)(f) GDPR for the security measures (the legitimate interest in protecting accounts and data).
The chat window on other websites
Organizations that use G4A Engager can embed its chat window on their own websites from this server. Each organization decides how it is set up there, for example whether it asks for your consent before recording visits; its own privacy policy tells you about that. This is what the software processes:
- In your browser: no cookies. A signed visitor token (
g4a_<site>) is kept in local storage when recording visits is allowed, otherwise only in session storage until the tab is closed. Your consent choice is saved on the website (g4a_<site>_consent), and which messages you have already seen is kept for the visit in session storage. - Consent and Do Not Track: when the website asks for consent and you have not given it, or when your browser sends Do Not Track or Global Privacy Control (respected unless the organization turns that off), no pages, device details, referrer or campaign data are recorded. The chat still works. Your browser’s language is recorded either way.
- When visits may be recorded: the pages you open (only their address without query string, apart from campaign parameters such as
utm_*; the part after # is never sent), page titles, time on page and scroll depth; where you came from (website and path only); browser, operating system and device type, read from the user-agent text; and, if a location database is installed on this server, an approximate location (city level, about 1 km) looked up locally from your IP address. The IP address itself is stored at most shortened (the last part removed). - Abuse protection: a keyed, one-way hash of your IP address is stored to block abuse; automatic blocks last 1 hour, a ban by the team 7 days. Request counters keyed by IP address are kept in temporary memory for up to 1 hour. Before a first chat, your browser solves a small computing puzzle; nothing about you is stored for it.
- The chat: what you write and send, and your name or email address if you give them. By default, closed conversations are kept for 2 years, recorded page views for 180 days, and visitors who never chatted for 395 days after their last visit; the organization can change these periods.
- Voice and video: calls, video and screen sharing start only after you accept, and run through this server’s own media and relay servers. Live sessions are never recorded. Phone calls are transcribed into the conversation; the audio is recorded only if the line records calls and you agreed on that call.
- AI: if an AI model is configured, for this deployment or by an organization for itself, the text of a conversation and matching help articles are sent to that model’s provider to write answers, suggestions, translations or summaries. Which provider is the choice of whoever configured it. AI outputs are kept for 1 year by default.
- Email: campaign emails go only to addresses that confirmed their subscription (double opt-in), and each has an unsubscribe link. Opening and clicking are not tracked unless the organization switches that on; then this server counts them. If an organization connects its mailbox, emails you send it are kept as conversations.
- Other connections: data goes to messengers, webhooks, a CRM or other systems only when an organization connects them, and only to those.
If you want a copy of your data or want it erased, contact the organization whose website you used; it can export and erase it in G4A Engager. You can also write to me.
Your rights
You have the right to:
- know what data about you is processed (Art. 15 GDPR),
- have it corrected (Art. 16) or deleted (Art. 17),
- have its processing restricted (Art. 18),
- receive it in a portable format (Art. 20),
- object to its processing (Art. 21).
An email to yeysus@gmail.com is enough. You can also complain to a data protection authority, for example the one responsible here: Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59–61, 10555 Berlin, datenschutz-berlin.de.