Privacy policy
Last updated: 26 October 2026
1. Controller
Thomas Gewinner
Bachstraße 23
55569 Monzingen
Germany
Phone: 0151-27081898
Email: info@carnotify.de
2. Purpose and basic principle of the service
CarNotify allows registered vehicle owners to create a QR code for a vehicle. People who scan this QR code can send a message to the owner. The public scan page does not display the owner's name, address, phone number, email address, license plate or other stored vehicle data.
3. Web hosting
This website is hosted by:
Einzelunternehmen Tom Gewiese
Tom Gewiese
Obernaglbach 2
94259 Kirchberg im Wald
Germany
Email (no support): vertrieb@skrime.eu
Abuse email (no support): mail@threatoff.eu
Phone (no support): +49 160 92595136
Technically required data is processed during hosting in order to deliver the website and to ensure stability and security. Where the hosting provider processes personal data on our behalf, this processing must be arranged in accordance with the GDPR requirements for processors.
4. Server log files
When the website is accessed, server log files may process information such as IP address, date and time, requested resource, transferred data volume, referrer, browser/operating-system information and HTTP status code. This processing serves the secure and stable operation of the website and the detection and prevention of technical attacks. The legal basis is Art. 6(1)(f) GDPR. The specific retention period of hosting logs depends on the hosting provider's server configuration.
5. Registration and user account
Registration currently requires name, street and house number, postal code, city, country, phone number, email address and password, as well as the data of the first vehicle. These details are required to provide the user account, vehicle assignment and service functions. The legal basis is Art. 6(1)(b) GDPR. Passwords are stored only as password hashes and cannot be read in plain text.
6. Vehicle data
Stored vehicle data includes license plate, make, model and color. These details are processed in the protected user and administration areas and are not shown on the public QR scan page. Personal and vehicle details are additionally encrypted in the database by the application. A vehicle owner may optionally store a driver name and driver email address for a specific vehicle. These are encrypted and can be changed or removed by the account owner. The driver must be informed and agree before their contact details are entered; the account owner is responsible for ensuring a valid legal basis.
7. Email verification
A temporary random verification token is created to verify an email address. Only a hash of this token is stored in the database. After successful verification the token is discarded.
8. QR codes and public scan pages
The QR code contains only a URL with a randomly generated public token. Personal owner or vehicle data is not written into the QR code. The QR code can be disabled or renewed in the user area; renewing it invalidates the previous token.
9. Contacting a vehicle owner
A person scanning the code may choose a notification reason and optionally enter a short message and voluntary reply contact. These details are used to create the email to the vehicle owner. After a successful send, the timestamp, notification reason, optional message, voluntary reply contact and delivery status are also stored in the protected notification history of the relevant vehicle owner. The application additionally stores whether and when a history entry has been marked as read so that the unread counter can be provided. Message and reply contact are encrypted in the database. These history details are not visible on the public QR scan page and are not shown to other vehicle owners. To limit abuse, the application also processes a keyed hash derived from the IP address. The plain IP address is not stored in the application's contact-attempt table and is not copied into the notification history. Rate-limit data is removed from the application after no more than 30 days.
10. Email delivery
If an optional driver email is saved for a vehicle, QR notifications are additionally sent to the driver in a separate email. The owner continues to receive their own alert. The driver does not receive access to the owner’s account or notification history. The application stores the separate delivery result for each notification. An identical owner and driver address is not emailed twice.
Transactional emails, especially verification, password reset, QR code delivery and owner notifications, are sent via the configured SMTP service at gewinner-cloud.de. Recipient address, sender information and the relevant message content are processed for this purpose. Where the email is required to provide the account or a requested function, the legal basis is Art. 6(1)(b) GDPR.
10a. Optional Android app and Firebase Cloud Messaging
If a user installs the optional CarNotify Android app and allows push notifications, the app can register the device for Firebase Cloud Messaging (FCM). For this purpose CarNotify processes an opaque FCM registration token, an app-specific random device identifier, device/model designation, app version, activation status and the last connection time. These details are linked to the signed-in CarNotify account so that vehicle notifications can be delivered to the selected device. The user can disable push notifications or remove registered devices in the profile at any time.
FCM is provided by Google. When push is enabled, device and message-delivery metadata required for the service is transmitted to Google/Firebase. The notification content can contain the selected notification reason, the vehicle license plate and, if provided, a shortened message preview. CarNotify uses FCM only for requested transactional vehicle notifications, not for advertising. The legal basis for providing this optional function is Art. 6(1)(b) GDPR; where consent or device-access rules are additionally required, the corresponding Android permission and applicable requirements must be observed.
10a. Optionale Android-App und Firebase Cloud Messaging
Installiert ein Nutzer die optionale CarNotify-Android-App und erlaubt Push-Benachrichtigungen, kann die App das Gerät für Firebase Cloud Messaging (FCM) registrieren. CarNotify verarbeitet dafür einen nicht sprechenden FCM-Registrierungstoken, eine app-eigene zufällige Gerätekennung, Geräte-/Modellbezeichnung, App-Version, Aktivstatus und den Zeitpunkt der letzten Verbindung. Diese Angaben werden dem angemeldeten CarNotify-Konto zugeordnet, damit Fahrzeugmeldungen an das ausgewählte Gerät zugestellt werden können. Push kann im Profil jederzeit deaktiviert und registrierte Geräte können dort entfernt werden.
FCM wird von Google bereitgestellt. Bei aktivierter Push-Funktion werden die für die Zustellung erforderlichen Geräte- und Zustellmetadaten an Google/Firebase übertragen. Der Inhalt einer Push-Benachrichtigung kann den gewählten Meldegrund, das Kennzeichen des betroffenen Fahrzeugs und – falls eingegeben – eine gekürzte Nachrichtenvorschau enthalten. CarNotify nutzt FCM ausschließlich für angeforderte transaktionale Fahrzeugmeldungen und nicht für Werbung. Rechtsgrundlage für die Bereitstellung dieser optionalen Funktion ist Art. 6 Abs. 1 lit. b DSGVO; soweit zusätzlich eine Einwilligung oder Vorgaben zum Zugriff auf das Endgerät einschlägig sind, sind die Android-Berechtigung und die jeweils anwendbaren Anforderungen zu beachten.
10b. Public contact form / Öffentliches Kontaktformular
Visitors may contact CarNotify's operator by providing a name, email address, topic, subject and message. This information is sent directly to info@carnotify.de using the configured SMTP service. It is not stored in a separate contact-form database table. For abuse prevention, the application stores pseudonymised technical request counters and message fingerprints; Google reCAPTCHA is also used. Email correspondence may be stored in the operator's email mailbox until the request is handled and any applicable retention duties are fulfilled. Please do not submit passwords or sensitive account data.
11. Google reCAPTCHA
Google reCAPTCHA is used for functions that are particularly vulnerable to abuse, currently including registration, resending a verification email, password reset, public operator contact requests and notifying a vehicle owner. reCAPTCHA is used solely for security, fraud prevention and abuse prevention.
On pages containing these protected forms, reCAPTCHA is loaded regardless of the cookie-notice acknowledgement. Data such as IP address, browser, device and interaction information may be processed and the _GRECAPTCHA cookie may be set. CarNotify uses the recaptcha.net domain recommended by Google for reCAPTCHA integrations. The application treats reCAPTCHA as a security component required for the protected forms. The legal assessment of the applicable basis, including the requirements of § 25 TDDDG, remains the responsibility of the website operator.
According to Google's current reCAPTCHA information, Google has classified itself as a processor for reCAPTCHA customer data since 2 April 2026. Responsibility for providing information and integrating the service lawfully remains with the website operator.
12. Cookies, language preference and “stay signed in”
CarNotify uses a technically necessary session cookie so that login, session management and CSRF protection work. A notice cookie stores that the privacy/cookie notice has already been acknowledged. A language preference cookie stores the selected German/English language so that it does not have to be chosen again on every visit.
In a normal web browser, if the user chooses “Stay signed in”, a persistent authentication cookie valid for up to 30 days is set. In the CarNotify Android app, persistent sign-in is activated automatically so the user does not have to sign in again regularly. The app login is renewed during use for up to 365 days at a time and is revoked when the user logs out. The browser/app stores a random token; the database stores only a cryptographic hash of the secret token part. Tokens are rotated when used. A new login may still be required after a password or email change, account/security revocation, reinstalling the app or clearing app data.
Google reCAPTCHA is not switched on or off through the cookie settings. It is always loaded on the protected registration, verification/reset and vehicle-owner contact forms. The “Cookie settings” page in the footer explains which required functions are used.
13. Local QR code generation
The QR matrix is generated in the logged-in user's browser using a JavaScript library hosted locally on this web server. The QR content is not sent to an external QR generator or external CDN. The generated QR image is then stored on the own web server so it can be displayed again, printed and sent as an email attachment.
For the optional CSV vehicle import, the uploaded file is processed on the server only to validate and preview the import. Vehicle values kept for the confirmation step are stored encrypted in the user session and are discarded after confirmation or automatically after about 30 minutes. After confirmation, imported vehicle data is stored in the regular encrypted vehicle records. QR codes for imported vehicles are generated locally in the browser and stored on the own web server without using an external QR service.
14. Carli website assistant
The Carli assistant answers questions using a locally maintained CarNotify knowledge catalogue. No external AI or chatbot provider is contacted for this function. The complete chat history is not stored on the server. If Carli cannot answer a question with sufficient confidence, the submitted question text, selected website language, number of identical requests and timestamps are stored in an internal administration list so that the knowledge catalogue can be improved. No name, account/user ID or plain IP address is added to this assistant entry. Please do not enter personal, confidential or sensitive information into the assistant. Unanswered-question entries are automatically removed after no more than 90 days. The legal basis for this limited processing is Art. 6(1)(f) GDPR, based on the legitimate interest in improving the help function and avoiding incorrect automated answers.
14a. Support tickets
Signed-in users can open support tickets. We store account linkage, category, status, timestamps and conversation history. Subjects and messages are encrypted in the database and are only visible to the account owner and authorized administrators. Notification emails may be sent without the actual message text. Tickets remain available in the dashboard even when email delivery fails. Do not include passwords or highly sensitive data. Records remain until account deletion or separate removal, subject to reviewing appropriate retention periods. Art. 6(1)(b) GDPR applies where tickets concern providing the service.
14b. Voluntary reviews and homepage testimonials
Registered users can voluntarily submit one review with a 1–6-star rating, a self-selected public display name and a review text. Display name and review text are encrypted in storage; submission and moderation dates, review status and consent time are also stored. Publication only takes place after the user has explicitly agreed and an administrator has approved the review. Approved reviews appear on the publicly accessible homepage with the chosen display name, star rating and review text. Account names, email addresses and vehicle information are not used for publication. Edited reviews require renewed approval. Users can edit or remove their reviews in the dashboard at any time; deletion also removes the public review. Reviews are deleted upon deletion of the user account. The legal basis for voluntary public display is consent under Art. 6(1)(a) GDPR, withdrawable at any time with effect for the future.
15. Legal bases at a glance
- Art. 6(1)(b) GDPR: registration, account management, vehicle management, QR code functionality and necessary transactional emails.
- Art. 6(1)(f) GDPR: secure provision of the website, server logs and technical abuse protection, including reCAPTCHA where this legal basis is applicable.
- For storage of or access to information on the user's device, the requirements of § 25 TDDDG must additionally be observed. The website operator must verify whether the exception for a strictly necessary function under § 25(2) TDDDG applies to the specific reCAPTCHA implementation.
16. Recipients of data
Recipients of personal data may include the hosting provider, the SMTP/email service and Google as reCAPTCHA provider, in each case only where required for the relevant function. The application does not provide for disclosure for advertising purposes.
17. Transfers to third countries
When external service providers are used, processing outside the European Union or European Economic Area cannot always be ruled out. Where a third-country transfer takes place, the requirements of Chapter V GDPR must be observed, in particular an adequacy decision or appropriate safeguards.
18. Retention periods
- Account data: generally until account deletion or for as long as required for the service.
- Vehicle data and QR images: generally until deletion of the vehicle or account.
- Email verification token: normally no more than 24 hours.
- Password reset token: normally no more than 60 minutes.
- Vehicle notification history including read status: generally until deletion of the vehicle or account. For older notifications sent before the history feature was introduced, only still-available send timestamps may be imported; the original reason and content cannot be reconstructed retrospectively.
- Temporary CSV import preview: normally no more than about 30 minutes or until the import is confirmed.
- Application rate-limit/abuse-protection data: no more than 30 days.
- Questions Carli could not answer: no more than 90 days; no complete chat history is stored on the server.
- Session cookie: normally until the browser session ends.
- Language preference cookie: up to 12 months.
- Persistent “stay signed in” token: in the web browser up to 30 days; in the Android app up to 365 days at a time and renewed during use; removed earlier on logout or security revocation.
- Privacy/cookie notice cookie: up to 180 days.
Statutory retention obligations and technically necessary backup cycles remain unaffected where applicable.
19. Data security
The application uses prepared SQL statements, password hashing, CSRF protection, protected sessions, random QR tokens, access controls, rate limits, encrypted sensitive data and hashed persistent-login tokens. Production operation must use HTTPS only. Server, PHP, database and libraries must be kept up to date.
20. Data subject rights
Subject to the statutory requirements, data subjects have rights including access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21). Where processing is based on consent, that consent may be withdrawn at any time for the future under Art. 7(3) GDPR.
21. Right to lodge a complaint
You have the right to lodge a complaint with a data protection supervisory authority. For the controller's place of establishment, the following authority may in particular be relevant:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-Pfalz
Hintere Bleiche 34
55116 Mainz
Phone: +49 (0) 6131 8920-0
Email: poststelle@datenschutz.rlp.de
22. Account deletion
Registered users can delete their account in the user area. The account, related vehicle records and stored QR images are removed from the production system and the related QR codes stop working. Statutory retention duties and technically necessary backups remain unaffected where applicable.
23. Changes to this privacy policy
This privacy policy will be updated when functions, service providers, technical processes or the legal situation change.