الانتقال إلى المحتوى
auto.happyin.app
الحلول
  • معارض السيارات المستعملة
  • الأسواق الإلكترونية
  • الوكلاء المعتمدون
  • المزادات والتأجير
  • الأساطيل ومشاركة السيارات
  • كل القطاعات
التقنية
API
  • API
  • التكاملات
الأسعارالأمانالمدونةالأسئلة الشائعة
AR
  • EnglishEN
  • EspañolES
  • DeutschDE
  • العربية✓
لوحة التحكم30 صورة مجانًا
القائمة
الحلولمعارض السيارات المستعملةالأسواق الإلكترونيةالوكلاء المعتمدونالمزادات والتأجيرالأساطيل ومشاركة السياراتكل القطاعاتالتقنيةAPIالتكاملاتالأسعارالأمانالمدونةالأسئلة الشائعةلوحة التحكم
  • English
  • Español
  • Deutsch
  • العربية

ملحق معالجة البيانات

النص الإنجليزي أدناه ترجمة للاطلاع فقط، والترجمة العربية قيد المراجعة القانونية ولم تُعتمد بعد. الأصل الصربي هو المعتمد: Tekst na srpskom.

Revision: 4 November 2026. In force from 4 November 2026. This is a translation provided for convenience. The Serbian text is legally binding and prevails in case of any discrepancy.

This Data Processing Addendum (DPA) is part of the contract for the auto.happyin.app service between the Customer under the accepted Order and Anastasiia Butova PR Beograd, a Serbian sole proprietor, MB 68595398, PIB 115737200, address: Trg Nikole Pašića 5, Floor 1, 11000 Belgrade (Stari Grad), Serbia (Processor, we).

An online purchase of a plan on auto.happyin.app is made from our online reseller Paddle as Merchant of Record (Terms of Service, section 6.10) and is an accepted Order for the purposes of this DPA, which applies between the Customer and us. Paddle does not receive photos or other Customer Personal Data and is not a sub-processor; it processes payment data as an independent controller. An order under our invoice paid by SEPA or SWIFT is also an accepted Order.

Personal data and incidents: privacy@auto.happyin.app. Support: support@auto.happyin.app.

1. Scope and roles

1.1 Customer Personal Data means personal data in Input Photos, Outputs, the Customer’s materials, their metadata and other content that we process on the Customer’s instructions. The Customer is the controller. If the Customer itself processes the data on behalf of another controller, we are a sub-processor, and the Customer must have the right to appoint us.

1.2 This DPA meets the requirements of Article 45 of the Serbian Law on Personal Data Protection (ZZPL) and, where applicable, Article 28 of the GDPR and the UK GDPR. Its safeguards apply even if the GDPR does not apply to us directly.

1.3 For business contacts, invoices, accounts and our own security we are an independent controller (Privacy Policy). This does not entitle us to use the Customer’s content for other purposes.

1.4 This DPA applies to a company’s free pilot and to an installation on the Customer’s servers, to the extent that we obtain access to data (section 14). An individual’s pilot is governed by the Privacy Policy (section 2).

1.5 This DPA applies when a company instructs us to process personal data. Photos that an individual uploads for themselves are governed by the Privacy Policy.

2. Details of processing and duration

2.1 The subject matter, purposes, operations, data, data subjects, locations and periods are in Annex 1. The sole purpose is to provide the agreed image-processing service.

2.2 Processing lasts for the term of the contract and afterwards for as long as is needed for return, deletion or retention required by law (section 10). Data may not be processed outside the locations in Annex 1 or by sub-processors not listed in Annex 3.

3. Customer’s obligations

3.1 The Customer determines the legal basis, informs the people concerned and does not knowingly upload special categories of data or data on criminal convictions without separate agreement.

3.2 The service does not perform biometric identification and does not create biometric templates. People may not be identified from photos. If unexpected sensitive data appear in the materials, the parties jointly restrict their processing or delete them.

3.3 From the files we deliver we remove unnecessary EXIF data and device and location data, but we keep the AI marking required by law.

4. Instructions and prohibitions

4.1 We process Customer Personal Data only on the Customer’s documented instructions — the contract, its annexes, the settings and the jobs submitted — including as regards transfers of data, unless the law requires otherwise.

4.2 If an instruction appears to us unlawful, we inform the Customer immediately and suspend its execution.

4.3 If the law requires us to disclose data, we tell the Customer in advance where this is permitted, disclose the minimum and challenge unlawful requests.

4.4 We do not use Customer Personal Data or the Customer’s photos, Outputs and materials to train models, for advertising, for sale or for any other purposes of our own. We require the same of sub-processors. A quality check of the ordered job is permitted.

5. Confidentiality

Only authorised persons who need the data for the service and who are bound by confidentiality, including after the contract ends, have access to the data. Access is reviewed and withdrawn when no longer needed.

6. Security

6.1 We apply the measures required by Article 50 ZZPL and, where applicable, Article 32 GDPR. The minimum list is in Annex 2.

6.2 Customer Personal Data are encrypted in transit and at rest, including backups (Annex 2).

6.3 We hold no certificates or external auditors’ reports. The measures may change, but the level of protection is not lowered. This does not displace obligations under the Serbian information security law.

7. Sub-processors

7.1 The Customer gives general written authorisation for the sub-processors in Annex 3. We engage only sub-processors that provide sufficient guarantees of data protection (Article 45 ZZPL, Article 28(1) and (4) GDPR). A provider without a completed row is not approved.

7.2 We give notice of adding or replacing a sub-processor at least 30 days in advance: name, functions, countries and information on the transfer of data. During that period the Customer may object on reasonable data-protection grounds. We address the concerns or offer a reasonable alternative. If there is no solution, the Customer may, before the change takes effect, stop using the affected part of the service and receive a refund of unused prepayment for it. While the objection is unresolved, we do not use the disputed sub-processor for that Customer’s data without its express consent.

7.3 A written contract with the same data-protection obligations has been concluded with each sub-processor. We are responsible to the Customer for the sub-processor.

7.4 An external AI service or support tool without a row in Annex 3 does not receive Customer Personal Data.

8. Assistance

8.1 We forward requests from individuals concerning Customer Personal Data to the Customer without delay and help to answer within the statutory time.

8.2 We assist the Customer with security, breaches, the impact assessment (DPIA), prior consultation and the assessment of data transfers.

8.3 Free of charge: standard documentation, one security questionnaire per year, help with requests from individuals and with a breach caused by us. Other substantial assistance is at an agreed reasonable rate. A payment dispute does not delay assistance required by law.

9. Security breaches

9.1 We notify the Customer of a breach of the security of Customer Personal Data without undue delay and no later than 48 hours after becoming aware of it. We do not wait for the investigation to end.

9.2 The notification states what is known: what happened and when, which data and how many people are affected, the consequences, the measures taken and a contact. We then send updates and help to remedy the consequences.

9.3 The Customer, as controller, notifies the supervisory authority and individuals; we assist. Our 48 hours do not replace the statutory periods, including the 72 hours under the ZZPL and the GDPR.

10. Deletion and return

10.1 Ordinary period. Input Photos, Outputs and working copies are deleted 90 days after each file is uploaded or created, unless an exception under clause 10.5 or clause 10.3a applies. When a batch reaches 90 days, its files are no longer made available. The same applies to failed, cancelled and incomplete jobs. The Customer may delete a batch earlier — in the Dashboard or under clause 10.2. Brand files — clause 10.6.

10.2 Early deletion. We carry out an instruction to delete usually within five business days and in any event no later than 30 days and no later than the ordinary period. Deletion of a batch in the Dashboard or through the API, and deletion of the account of the Customer’s last member (together with the organisation, its batches and brand files), are carried out automatically: files leave the storage usually within minutes, and for a large organisation within a few hours. If a deletion request is made while photos are being processed, the request is registered and carried out automatically once the job finishes or is cancelled.

10.3 End of contract. At the Customer’s choice, we return the data and then delete it, or simply delete it, within 30 days after the contract ends, unless the ordinary period expires earlier. On request we confirm deletion.

10.3a Customer switching to another provider. On a switching notice under section 18 of the Terms of Service, the Customer may export retained Input Photos, Outputs, brand files, and job and account data. The retrieval period starts when the transition period under section 18 of the Terms of Service ends and lasts at least 30 days; from the switching notice until the retrieval period ends, files are not deleted under clause 10.1. After it ends, we delete the data under clause 10.3. This excludes data deleted before the notice and our internal security records.

10.4 Backups — Annex 1. While a copy exists, it is isolated and not used. After restoration from a copy, deletions are applied again.

10.5 Exceptions. We keep data longer only where the law, a lawful preservation instruction or a mandatory change of provider requires it; the parties record the reason, the data and the period. This is not permission to keep data indefinitely or to train models.

10.6 Brand files (licence plates, overlays such as a logo, own scenes) are kept until the Customer deletes them or its organisation is deleted; they are not deleted by age. A deleted file is removed from the storage, and a failed deletion is repeated automatically. The copy made for a batch is deleted together with the batch under clause 10.1. Other materials are kept beyond the duration of the job only on an instruction stating a purpose and a period.

10.7 Payment and accounting records (invoices, Orders, payments) are not covered by section 10. We keep them as a controller under the Serbian tax law: five years from the end of the year, ten years for electronic invoices in the SEF, and longer only for the duration of a tax inspection or dispute (Privacy Policy, section 7). They contain no Customer photos.

11. Information and audit

11.1 We provide the information necessary to demonstrate compliance with this DPA and allow audits by the Customer or an independent auditor.

11.2 Verification usually starts with documents and questionnaires. A scheduled audit is on 30 days’ notice, during business hours, no more than once in 12 months. An additional or on-site audit is possible where reasonably necessary: after an incident, on signs of a breach, at the request of an authority. This does not limit the powers of the supervisory authority.

11.3 An audit protects the data of other customers. A scheduled audit is at the Customer’s expense. We hold no ISO/IEC 27001 or SOC 2 certificates.

12. Locations and transfers of data

12.1 We process data only in the countries in Annex 1 and subject to section 7.

12.2 Serbia. The basis for transfers is under Articles 63–65 ZZPL. To the EU/EEA — under Article 64(2) (parties to Council of Europe Convention No. 108). To recipients in the United States — on the basis that applies to each recipient (for example the EU–US Data Privacy Framework only for a recipient certified under that framework, or the standard clauses of the Serbian Commissioner), stated in Annex 3. The EU SCCs are not treated as clauses of the Serbian Commissioner.

12.3 GDPR. There is no adequacy decision for Serbia.

Scenario A. Where the GDPR applies to the Customer’s processing, the GDPR does not apply directly to our processing, and the data are transferred to us or made accessible to us in Serbia (including remotely), the unmodified standard contractual clauses under Decision (EU) 2021/914 (SCCs) apply: Module 2 where the Customer is a controller, Module 3 where the Customer is a processor (clause 1.1). The Customer is the exporter and we are the importer. The SCCs are incorporated into this DPA by reference and are concluded by acceptance of an Order, including an online purchase, without a separate signature. Selections (Annex 4 A): Clause 7 applies; Clause 9(a) — Option 2, notice of thirty (30) days; the optional wording of Clause 11(a) does not apply; the supervisory authority — under Clause 13(a); Clause 17 — Option 2, and if the law of the exporter’s country does not allow third-party beneficiary rights or the exporter is not established in the EU — the law of Ireland; Clause 18(b) — the courts of the State whose law governs the SCCs. Annexes I–III to the SCCs are Annexes 1–3 to this DPA; the Customer’s details are taken from the account or the Order. The SCCs prevail over this DPA and the Terms of Service in Scenario A.

Scenario B. If the GDPR applies directly to our processing under Article 3(2) GDPR, we comply with the GDPR directly, including Chapter V GDPR for onward transfers. Before the Customer’s personal data are transferred or made accessible to us, the parties assess that transfer under Chapter V GDPR and the current guidance of the EDPB and the European Commission and agree the applicable safeguard in writing; if the European Commission adopts standard contractual clauses for importers subject to the GDPR, the parties use them. Until a safeguard is agreed, the transfer does not take place.

12.4 In Scenario A, if the SCCs are not sufficient for a specific transfer, the parties apply another lawful mechanism. If protection cannot be ensured, the transfer is suspended.

12.5 In Scenario A, for a transfer from the United Kingdom the UK Addendum to the SCCs (UK Addendum) also applies, with the details in Annex 4 B.

13. Requirements of other countries

If the law of another country requires special terms for processors, the parties put them in place before processing begins. In any event we do not sell Customer Personal Data, do not disclose them for behavioural advertising, do not use them outside the purpose of the contract and do not combine them with other data. If we cannot comply, we will tell the Customer.

14. Processing on the Customer’s servers

The environment and the access we need are stated in the Order and Annex 1. Without permission we do not export photos, enable telemetry containing personal data or copy data into support tools. Remote access is limited and logged. The Customer is responsible for its own systems, and we for our own work.

15. Precedence and liability

On matters of personal data this DPA prevails over the Terms of Service and the Order; the SCCs and the UK Addendum prevail by their own rules. Liability is governed by the Terms of Service; their limitations apply only to companies and do not limit the rights of data subjects, the powers of authorities or the obligations under the SCCs.

16. Governing law and disputes

The law of Serbia, the courts of Belgrade, subject to mandatory rules. The SCCs and the UK Addendum retain their own rules on law, courts and supervisory authority. Data subjects’ rights to choose a court are preserved.

Annex 1 — Details of processing

A. Description

Parameter Description
Subject matter Processing of car photographs and the Customer’s materials for the ordered editing service
Purpose Background replacement, shadows, licence-plate processing, changes to the view through the windows in interior shots, identification of car characteristics, delivery of Outputs, support
Operations Receipt, transmission, storage, automatic transformation, troubleshooting, delivery, export, deletion
Frequency When jobs are submitted and for support during the contract
Data subjects Car owners, the Customer’s staff, photographers, passers-by and other people in the materials
Data Images and reflections of people; licence plates and VINs where they are personal data; EXIF and GPS; location indicators; Customer and job identifiers; personal data in backgrounds and in materials for support
Special categories Not requested; biometric identification and profiling are prohibited
Retention period 90 days after each file is uploaded or created (section 10); the Customer may delete earlier
Brand files Until the Customer deletes them or the organisation is deleted (clause 10.6)
Cloud or Customer’s servers Stated in the Order before processing begins

B. Where the data are processed

The cloud service stores Customer Personal Data in the EU: photos, Outputs, brand files and backups in Frankfurt (Germany), job and account records in the API database in the EU jurisdiction. Photo processing is planned in the EU. But not only in the EU: requests are served by the global network of the API hosting — including photos sent in a single synchronous API call and brand files on their way to the storage — and administration is carried out from Serbia. The providers are in Annex 3.

Processing of Customer Personal Data on the production service has not started and the photo storage on it is not yet in use. Before it starts we will complete Annexes 1–3, publish them here and notify Customers under clause 7.2.

Component Where
Storage of photos, Outputs and brand files Germany (Frankfurt)
Photo processing (GPU) EU; country and provider before processing begins
API database (jobs and accounts) EU
Receipt of photos in a synchronous API call and of brand files Global network; countries — Annex 3
Administration and support Serbia (us)

Transfers. To EU countries — under Article 64(2) ZZPL. To recipients in the United States and in the global network — under clause 12.2; the basis is stated in Annex 3 before processing begins.

Backups. Photos, Outputs and brand files are not copied: the copy in the storage is the only one. The API database is copied every night to the storage in Frankfurt. The backup service can write a copy but cannot read or delete it; the 30-day deletion lock can be lifted only by an authorised administrator; after 35 days the copy is deleted automatically. Copies are encrypted before upload (X25519 and AES-256-GCM), and the key is kept separately. The database provider keeps its own recovery history for no more than 30 days. A deleted record therefore disappears from all copies within 35 days at the latest. At present the API database holds no Customer Personal Data — only our records as a controller (Privacy Policy, sections 5–7).

For an installation on the Customer’s servers, the processing locations and access are stated separately.

Annex 2 — Security measures

Minimum measures for the cloud service (not an audit opinion):

  • Transmission: authenticated encrypted connection everywhere, with no unprotected fallback channels.
  • Storage and keys: restricted access to all copies; encryption at the providers — the API database with AES-256-GCM (keys held by the provider), the photo storage with AES-256 and a separate key per object; the nightly database copies are additionally encrypted by us (X25519 and AES-256-GCM), with the key kept separately.
  • Access: personal accounts, least privilege, strong authentication for administrators, timely withdrawal and review of access, separation of customers.
  • Logs: records of access and events without photo content or credentials, kept for a limited period.
  • Infrastructure: updates, configuration and vulnerability management, protection of external access points.
  • Recovery: a recovery plan, protected copies with a fixed expiry, recovery tests.
  • Deletion: verified deletion of all copies, deletions applied again after restoration.
  • Staff and providers: confidentiality, instructions, only approved sub-processors.
  • Incidents: a responsible person, a working communication channel, containment, preservation of evidence, timely notifications.
  • Built-in protection: data minimisation, removal of unnecessary EXIF data, no model training on customers’ data.

A record of the measures actually implemented is appended here before Customer Personal Data are processed on the production service.

Annex 3 — Sub-processors

Processing of Customer Personal Data on the production service has not started; therefore no sub-processor has yet processed those data. Before processing starts, we complete each row, including the approval date, and notify Customers under clause 7.2. A provider without a completed row is not approved (clause 7.1). The GPU photo-processing provider is not approved until its row is completed.

Legal entity name Function and data involved Countries of processing and access Transfer mechanism and authorisation
Cloudflare, Inc. Hosting of the API on Cloudflare Workers: receives in the request the Input Photos sent in a synchronous API call and the brand files that the Customer uploads, and writes them to the photo storage; keeps the account, usage and job records in the API database (Cloudflare D1) API database — European Union (Cloudflare’s EU jurisdiction); request handling — the countries of Cloudflare’s network as published by Cloudflare; support access — the countries in Cloudflare’s list of sub-processors (version of 1 October 2025) Under ZZPL — the EU–US Data Privacy Framework for the certified recipient (clause 12.2; certification — the Data Privacy Framework List); under the GDPR — also the EU SCCs under Cloudflare’s agreement; data-processing agreement — the Cloudflare Customer Data Processing Addendum, version 6.4 of 3 April 2026; approval date — the date this revision enters into force
Wasabi Technologies LLC, Boston, United States Storage of Input Photos, Outputs and brand files; encrypted nightly database backups (35 days) Storage — Frankfurt, Germany (eu-central-2); access by Wasabi, its affiliates and its sub-processors — the countries in Wasabi’s list of sub-processors (version of 22 January 2026) Under the GDPR — the EU SCCs under Wasabi’s agreement; under ZZPL — Article 64(2) ZZPL: the data are stored in Germany, a party to Council of Europe Convention No. 108; data-processing agreement — the Wasabi Data Processing Agreement, version of 29 December 2025, part of the Wasabi Customer Agreement; approval date — the date this revision enters into force
GPU photo-processing provider — not engaged Photo processing on the production service is not enabled — The provider will be named and approved, and Customers notified under clause 7.2, before photo processing begins

The photos of an ordinary batch do not pass through Cloudflare: they are uploaded to the storage and downloaded from it directly.

Providers that we use only as a controller are listed in the Privacy Policy. For example, Plus Five Five, Inc. (Resend) sends service emails and receives only email addresses and the text of the messages, without photos or other Customer Personal Data, so it is listed in section 5 of the Privacy Policy as the email sending service. The same applies to the shared support line, our team’s tool, and its encrypted backups: support tickets and enquiries are our records as a controller (Privacy Policy, sections 5 and 7), not Customer Personal Data. If such a provider begins to receive Customer Personal Data, it is first added here under clause 7.2.

Annex 4 — Terms on the transfer of data

A. EU SCCs — Scenario A

In Scenario A in clause 12.3, the unmodified text of the clauses under Decision (EU) 2021/914 applies; they are concluded by acceptance of an Order.

Item Selection
Module Module 2 where the exporter is a controller; Module 3 where a processor
Clause 7 The docking clause applies
Clause 9(a) Option 2: general written authorisation, 30 days’ notice
Clause 11(a) The optional wording does not apply
Clause 13(a) and Annex I.C The supervisory authority is determined under this clause; the law of Ireland does not by itself make an Irish authority competent
Clause 17 Option 2: the law of the EU Member State where the exporter is established; if it does not allow third-party beneficiary rights or the exporter is not established in the EU — the law of Ireland
Clause 18(b) The courts of the State whose law governs the SCCs; data subjects’ rights to choose a court are preserved
Annex I.A Exporter — the Customer according to the account or Order details; importer — Anastasiia Butova PR Beograd (details above), privacy@auto.happyin.app
Annex I.B Annex 1 to the DPA
Annex II Annex 2 to the DPA
Annex III Annex 3 to the DPA

The start date is the date the Order is accepted; the date of the revision on the website is not that date.

B. UK Addendum

The Addendum approved by the ICO, or its approved replacement, applies. Table 1 — the parties from the Order and above; Table 2 — Module 2 or 3 and the selections from part A; Table 3 — Annexes 1–3; Table 4 — the right to end the Addendum belongs to both the exporter and the importer. The mandatory provisions are not changed; the law and courts are those of England and Wales.

Contents
  1. 1. Scope and roles
  2. 2. Details of processing and duration
  3. 3. Customer’s obligations
  4. 4. Instructions and prohibitions
  5. 5. Confidentiality
  6. 6. Security
  7. 7. Sub-processors
  8. 8. Assistance
  9. 9. Security breaches
  10. 10. Deletion and return
  11. 11. Information and audit
  12. 12. Locations and transfers of data
  13. 13. Requirements of other countries
  14. 14. Processing on the Customer’s servers
  15. 15. Precedence and liability
  16. 16. Governing law and disputes
  17. Annex 1 — Details of processing
  18. Annex 2 — Security measures
  19. Annex 3 — Sub-processors
  20. Annex 4 — Terms on the transfer of data
auto.happyin.app

تعالج نماذج الذكاء الاصطناعي الصور: فهي تستبدل الخلفية والمنظر عبر النوافذ والظل، ولوحة الأرقام وشريطة الهدية بظلها وانعكاسها على الطلاء وورق الهدايا فوق السيارة والإضاءة الاحتفالية إن طلبتم ذلك؛ ولا يُعاد رسم بقية السيارة، إلا في تصحيح هندسة الهيكل الخارجي (تشوّه العدسة واسعة الزاوية) إذا فعّلتموه للدفعة.

المنتجالحلولالتقنيةAPIالتكاملاتلوحة التحكمعلى خوادمكم
الشروطالأسعارالأمانالأسئلة الشائعة
للقراءةالمدونةمن نحن
اتصلوا بناsales@auto.happyin.appلنتحدث عن الإطلاق
© 2026 auto.happyin.appأمان البياناتالأسئلةالمستندات القانونيةسياسة الخصوصيةشروط الخدمةسياسة الاستردادإشعار ملفات تعريف الارتباطإعدادات الخصوصية

نستخدم ملفات تعريف الارتباط (الكوكيز) لتحسين تجربتكم. المزيد عن الكوكيز

إعدادات الكوكيز

اختاروا ما تسمحون به. يمكنكم تغيير اختياركم في أي وقت من «إعدادات الخصوصية».

  • تسجيل الدخول إلى لوحة التحكم، ولغة الموقع، والحماية من الروبوتات، ونموذج الدفع، واختياركم بشأن الكوكيز. لا يعمل الموقع بدونها.

  • إحصاءات الزيارات الخاصة بنا: الصفحات التي تُفتح والإجراءات التي تُنفَّذ، والدولة، ونوع الجهاز، وسرعة تحميل الصفحة، والموقع الذي جئتم منه ووسوم الحملات الخاصة به (utm)؛ وفي لوحة التحكم تُربط بحساب المؤسسة. لا تُشارك مع أي جهة.

اعرفوا المزيد