Data controller
- Controller
- SIA Proecufiles
- Registration No.
- 50203764061
- Registered address
- Eduarda Smiļģa iela 32–19, Rīga, LV-1002, Latvia
- Privacy contact
- info@proecufiles.de
Data we process
The portal may process account details, business contact details where provided, account access data, login activity, order records, uploaded ECU/TCU files, order messages, revision requests, payment records, retained historical financial references, email notification records, activity logs and server logs.
Uploaded ECU/TCU files are handled as private order material. They are not intended for public access and are delivered through authorised account access.
Why we process data
- To create and manage customer accounts.
- To manage customer account access, support restrictions and order submission settings.
- To process ECU/TCU file orders, messages, revisions and authorised downloads.
- To retain direct-payment, receipt and reconciliation records required for accounting, audit and dispute handling.
- To send account, order, file and revision notifications.
- To protect the portal from abuse, fraud, unauthorised access and operational errors.
Files, messages and internal notes
Original files, modified files, revision files and attachments are stored privately. Customers can access their own authorised files through their account or verified guest-purchase access. Admins and assigned tuners can access files needed for their work.
Customer-visible order messages may be shown to the customer and staff. Internal notes are staff-only and must not be exposed to customers.
Guest file purchases
Fast Checkout processes your delivery email, selected file, agreed price, consent, payment status and protected access credentials without creating a portal account. Stripe processes payment details on its hosted checkout. We send the receipt and access code to your email; card details are not stored by this portal.
Protected guest download access lasts 30 days after payment confirmation. This access period does not delete financial records, which are retained where required for accounting, disputes and legal obligations. Keep your access code private. It is not included in the purchase URL, public pages or application logs.
Sharing and disclosure
Customer data is not sold. Data may be shared only where needed to operate the portal, deliver the service, maintain hosting or email infrastructure, comply with a valid legal obligation or protect SIA Proecufiles from abuse or fraud.
WhatsApp Business contact
WhatsApp contact links are standard external links. Merely viewing a ProECUFiles page does not load WhatsApp or Meta scripts and does not send data to WhatsApp. The interaction begins only when you choose to follow the link.
WhatsApp then processes the messages and attachments you choose to send, and SIA Proecufiles receives them through its WhatsApp Business account. You may use the protected customer portal instead when you need structured order tracking, payment records or protected download history.
Retention and requests
Data is kept only as long as reasonably needed for account operation, file-service delivery, accounting or tax records, fraud prevention, dispute handling, security monitoring and legal obligations. Exact category-specific retention periods still require a documented legal and operational retention schedule.
Data access, correction or deletion requests can be sent to info@proecufiles.de. Some records may need to be retained where legally or operationally required.
Optional site measurement
When enabled, optional first-party measurement starts only after permission. We store daily counts by event, broad channel, public page class, language and public product reference, not visitor records. A preference cookie lasts up to 180 days; a short-lived server session groups visits for 30 minutes. Change or withdraw permission in Measurement preferences in the public footer. DNT and Global Privacy Control signals disable collection. Aggregates use a rolling 90-day window with automatic daily cleanup. Verified payment records are separate operational records; they are not proof of a traffic source.