Privacy notice

How we process data in the current portal and in tracker features when activated later.

1. Controller and contact

The controller is mywerk system GmbH, Potsdamer Str. 81, 14542 Werder (Havel), Germany, represented by Robert Bastubbe. Send privacy requests by post or through the contact form below. This notice covers ZEIGBIKE. External sign-in providers have additional notices for their own processing.

2. Account, verification and preorders

We process name, email, language, a password hash where used, account status, confirmation times and versions of terms/privacy notices. Preorders store product, plan, quoted price, status and dates. This supports your account, request and evidence of agreements (GDPR Art. 6(1)(b)); security relies on our legitimate interest in protecting the service (Art. 6(1)(f)). Required details are necessary for an account. Acknowledging this notice is not blanket consent to other uses.

3. Operation and email codes

Requests process IP address, requested URL, time and technical browser/server information for secure delivery and error detection. The hosting provider processes operational data. The app uses short-lived derived IP/email identifiers against abuse. Verification codes last ten minutes and are stored only as keyed hashes; expired flows are purged during subsequent authentication activity and hourly. The configured mail server sends messages; the recipient’s email provider receives the address and message. Registration does not subscribe to marketing emails.

4. Apple and Google (optional)

Only when you choose this method are you redirected to Apple or Google. We receive a stable provider identifier and verified email, possibly an Apple relay address. We do not receive the provider password or request contacts, calendars or files. The identifier enables your chosen sign-in (GDPR Art. 6(1)(b)). The provider may process data outside the EU; consult its privacy notice and transfer safeguards. Email sign-in remains an alternative.

5. Location and vehicle data

An empty customer account collects no bike locations, routes or sensor readings. A later explicitly activated tracking service may process device IDs, GPS/Wi-Fi/mobile location, movement, altitude, rides, alerts and available CAN data. Its scope, legal basis and retention will be explained before activation. Registration does not authorize third parties, police links or AgentLink. Health analysis or training is not automatically included in this account.

6. Cookies, web app, maps and push

Essential session cookies secure sign-in and forms; a signed-in session expires after eight hours without renewal. An OAuth security cookie lasts ten minutes. The web app caches public interface assets, not private account pages. We use no advertising trackers or additional analytics cookies; see “Site statistics” for usage measurement. External map tiles expose the IP address to the map provider; empty customer accounts load no maps. Push needs separate browser permission and a delivery endpoint. New accounts without a tracker do not yet receive real device alerts.

7. Recipients and retention

Authorized staff and necessary hosting/IT and email providers have access for operation and support; authorities only where legally required or through a lawful transfer you request. We do not sell data. Account data lasts for the account lifetime, then is deleted or restricted unless law or necessary legal claims require retention. Preorder requests remain until handled or withdrawn. Confirmation evidence is kept only as needed for proof and claims. Abuse counters are purged on subsequent activity after their 24-hour window. Operational logs and backups follow operational deletion rules.

8. Your rights

Under GDPR conditions you have rights of access, correction, erasure, restriction, portability and objection to processing based on legitimate interests. You may withdraw voluntary consent for the future at any time. Contact us below; proportionate identity verification may be required to protect your account. You may complain to a data protection authority, particularly where you live; in Brandenburg, the state commissioner for data protection and access to information. The current portal makes no automated decisions with legal or similarly significant effects.

9. Protection against automated abuse

Before sending an email code, we check forms for abuse and limit sending frequency. When Cloudflare Turnstile is enabled, a security widget from Cloudflare, Inc., USA, is loaded. Cloudflare processes IP addresses and browser and device signals to detect automated requests. Our server verifies the result before sending; we do not send names, passwords or email addresses to Turnstile. The legal basis is our legitimate interest in protecting accounts, recipients and infrastructure (GDPR Art. 6(1)(f)). Processing outside the EU is possible; the linked Turnstile privacy notice explains Cloudflare's processing. Contact support if you experience technical problems. Our form proofs expire after 20 minutes; anonymous daily failure counts without IP addresses or account links are retained for 30 days.

10. Optional bike profile and photos

Enabled accounts can create a bike profile with name, model, drive, optional frame number and their own photos. We process this information to provide the account feature you choose (GDPR Art. 6(1)(b)). Main photos are cropped, cut out and slightly adjusted for brightness on our server; they are not sent to an external AI image service. The original view is re-encoded and reduced in size if needed, without background editing. Stored views contain no GPS or camera metadata; the temporary upload is deleted after processing. Photos are accessible in the portal only to the associated signed-in account. Upload only images you have the necessary rights to, preferably without other people or addresses. You choose the original or processed view and may remove the photos at any time. Unselected previews are purged after seven days. Bike profiles and selected images remain stored for the account feature; account deletion and backups follow the general retention notice. A bike profile does not activate tracking. The optional component archive stores detail photos with a category and optional position, label, date and notes. These photos are re-encoded for display and reduced to a maximum of 4096 pixels on the longest side, without background removal or colour enhancement. GPS and camera metadata and temporary uploads are removed. Component photos are stored independently of the main photo until deleted and are excluded from the seven-day preview cleanup. The same access, account-deletion and backup rules apply to this archive. Model and licence plate can be stored for eScooters and speed pedelecs. For photos categorised as licence plate or frame number, local text recognition on our server attempts to read the number. Images are not sent to an external OCR service. The suggestion is stored with the photo and can be corrected or discarded. Vehicle details are changed only after your explicit confirmation. Deleting the photo also deletes its recognition suggestion; a previously confirmed number remains independently editable in the vehicle details.

11. Optional AI inventory

When you select “AI inventory”, we send the selected component photos without GPS or camera metadata to the OpenAI API to identify the component, visible product markings, manufacturer and model. Photos in the licence plate and frame number categories are excluded. We do not include contact details, OBU identifiers or photo notes; personal information visible within the photo may still be transmitted. Use is optional and requires a valid Plus contract for the OBU assigned to this bike. Suggestions are not technical inspections, measurements or maintenance approvals. Only your review and confirmation marks them as inventory; unknown details remain blank. Unconfirmed component suggestions are removed with the source photo. Confirmed inventory entries and bike-model suggestions belong to the bike and survive deletion of individual evidence photos; deleting the bike or account removes them. Combined recognition uses suitable detail photos and the main photo of the same bike. We also send the motor manufacturer and motor model or generation entered in your bike profile as product-search hints; motor serial numbers, frame numbers and licence plates are not included as profile data. The bike recognition processes all eligible processed photos in batches. OpenAI web search may compare public product information, manufacturer manuals and original equipment lists. Technical specifications and maintenance notes include provenance and source links where available and remain reviewable suggestions. Model identification and changes to bike details require your confirmation; stock equipment does not prove the currently fitted components. Device assignment, request time and token usage are retained for usage limits for up to 30 days; account deletion removes these too. Daily cost totals without account or device references are retained for cost control. We disable OpenAI response storage (store=false). According to OpenAI, API data is not used for training by default; security logs may still be retained for up to 30 days and longer in justified exceptions. Processing outside the EU is possible. Details: https://developers.openai.com/api/docs/guides/your-data . Local background removal and local number recognition remain separate.

Maintenance overview and service records

If you use the maintenance overview, we store service dates, selected maintenance tasks, odometer and operating-hour readings, and notes with the component or bike. We use these to calculate upcoming service indicators from the saved intervals. This information is not sent to OpenAI for identification. Service records remain independently of component photos until you delete the record, component, bike or account. You can replace or clear current usage readings; they are deleted with the bike or account at the latest.

Crash detection and emergency contacts

For optional crash detection we store your phone number, emergency contacts’ names and numbers, and settings per bike. Inform contacts before adding them. You can change the information or clear it after disabling the feature. The prepared flow starts with a push request. Without confirmed cancellation an AI assistant is intended to call you first, in your last selected portal language, ask whether you are OK and confirm an all-clear again. Without an unambiguous all-clear, contacts are called in order; when they explicitly take responsibility they may receive your callback number, event time and available last location. This requires the configured telephony and AI service to process numbers, conversation audio and temporary speech recognition. The portal stores no call recordings or full transcripts. Crash alerts, call states and conversation decisions are retained for up to 30 days and then deleted by the background service. Contacts remain until changed or the bike/account is deleted. The push notification notice applies. Telephony, emergency transfer and a call center are not connected yet; no calls or data transfers currently take place through them. Specific providers and their processing will be added before activation.

Site statistics

To improve content and usability, our own server counts successful page deliveries and transitions between predefined sections. Only daily totals by section, language, broad device class and source domain or internal source section are stored, for at most 90 days; cleanup runs hourly. The statistics contain no IP addresses, complete browser identifiers, visitor or account identifiers, bike IDs, search terms or full URLs. Browser identifiers are evaluated temporarily only to classify devices and recognizable bots. Referrers contribute only external hostnames or known internal sections; paths, URL parameters and fragments are not retained. No personal visit histories, additional cookies or browser storage entries are created. Admin visits, sharing links and technical endpoints are excluded. Requests carrying Do Not Track or Global Privacy Control signals are excluded. These statistics are not shared with external analytics services.

Optional ZEIGBIKE email updates

You can subscribe to development, compatibility and launch updates independently of an account. Processing is based on consent (GDPR Art. 6(1)(a)). Apple or Google sign-in does not subscribe you automatically. We store email, language, status, consent wording and version, and request, confirmation and withdrawal timestamps. Newsletters are enabled only after confirmation using the emailed link, valid for 48 hours. Unconfirmed list entries are then removed by hourly cleanup. Turnstile and delivery limits protect this form too. Our mail engine and existing mail server handle delivery; delivery metadata appears in the administrative mail log. We do not track opens or individual link clicks. Images are embedded in emails. Withdraw consent at any time using the unsubscribe link in each email or account settings for the same email address. Messages already handed off cannot be recalled. Your account and bikes remain intact. To defend potential claims, we retain consent and withdrawal evidence under legitimate interests (GDPR Art. 6(1)(f)) for at most three years after withdrawal, then delete the list entry and evidence. Completed outbox records are deleted after 90 days.

Google · Privacy notice ↗ · Apple · Privacy notice ↗ · Cloudflare Turnstile · Privacy notice ↗