ملحق معالجة البيانات — Kite API
تخطَّ إلى المحتوى
Kiteالمنصة
الباقات

هذا المستند القانوني منشور باللغة الإنجليزية. لا تتوفر ترجمة عربية معتمدة بعد.

Kite API Data Processing Addendum

Last updated: November 17, 2026

This Data Processing Addendum (DPA) forms part of the Kite API Terms of Use, or of another signed agreement for the API (the Agreement), between Kite and the customer organization (Customer). Kite is the entity that is the contracting party under the Agreement: Founderproof, Inc., a Delaware corporation, or, where an Order Form names it, Kite Technologies Company, a company registered in the Kingdom of Saudi Arabia (Unified National Number 7055368950). This DPA applies where Kite processes Customer Personal Data on Customer's behalf while providing the API and developer platform (the Services). It takes effect when Customer accepts the Agreement and needs no separate signature.

Capitalised terms not defined here have the meanings in the Agreement. Data Protection Law means the Saudi Personal Data Protection Law and its Implementing Regulations, including the Regulation on Personal Data Transfer outside the Kingdom (together, the PDPL), and, where they apply to Customer Personal Data, the EU and UK General Data Protection Regulation (GDPR) and any other data-protection law that applies to the processing. Personal Data Breach means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.

1. Roles

1.1 Customer Personal Data. For personal data that Customer or its users submit to or generate in the Services (account and team member details, and request metadata such as IP addresses, user agents and request parameters in request logs) and that Kite processes to provide the Services to Customer (Customer Personal Data), Customer is the controller and Kite is the processor.

1.2 Kite's own purposes. Kite is an independent controller, not a processor, when it uses Customer's account, billing and usage information for its own purposes: billing and collecting fees, keeping accounting and tax records, preventing fraud and abuse, securing its systems, meeting its legal obligations, and understanding how the Services are used. Kite's privacy policy describes that processing.

1.3 Kite Data is not Customer Personal Data. Listing and market data returned by the API is collected and published by Kite as an independent controller, under the Agreement's data terms. This DPA does not cover it. Customer is an independent controller of any personal data it keeps from API responses (for example, an advertiser's name on a licensed listing, or a phone number returned under the listings:contact scope) and must have its own lawful basis to use it, as section 8 of the Terms of Use sets out.

2. Processing details

Subject matterProviding the Services under the Agreement
DurationThe term of the Agreement, plus the deletion periods in section 9
Nature and purposeAuthenticating API calls; metering and billing; request logs and usage analytics shown to Customer; security, abuse prevention and support
Data subjectsCustomer's staff and team members; persons whose IP addresses reach the API from Customer's systems
Categories of dataNames, work email addresses, organization roles; IP addresses, user agents, request identifiers and parameters, timestamps
Special categoriesNone expected. Customer must not send sensitive personal data in API requests.
FrequencyContinuous, for as long as Customer uses the Services

3. Kite's obligations

Kite will:

  • process Customer Personal Data only on Customer's documented instructions, which are the Agreement and Customer's settings in the Services (for example, request-log retention and the "Store request details" setting), unless the law requires otherwise, in which case Kite will tell Customer first where the law allows it. Kite will tell Customer if, in its opinion, an instruction breaks Data Protection Law;
  • ensure that people authorized to process the data are bound by confidentiality;
  • implement the security measures in section 6;
  • help Customer respond to data subject requests (access, correction, deletion, and the other rights under Data Protection Law), taking into account the nature of the processing. Most requests can be met directly in the portal; Kite will pass on to Customer any request it receives that is about Customer Personal Data, and will not answer it itself unless Customer asks it to;
  • help Customer, with the information available to Kite, with data protection impact assessments and consultations with regulators where they relate to the Services;
  • notify Customer of a Personal Data Breach as section 7 sets out;
  • make available the information necessary to demonstrate compliance with this DPA (section 8).

4. Customer's obligations

Customer is responsible for the lawfulness of the Customer Personal Data it provides, for having a lawful basis for the processing, for giving any required notices to its team members, and for configuring the Services (request-log retention, request detail storage, IP allowlists, team roles) to suit its needs.

5. Subprocessors

5.1 Customer authorizes Kite to engage the subprocessors listed at platform.kite.sa/legal/subprocessors, which shows what each one does, the data it processes and where.

5.2 Kite will give at least 30 days' notice of a new subprocessor by updating that page and notifying Customer's organization owners by email or in the portal changelog. Customer may object on reasonable data-protection grounds within that period. The parties will discuss the objection in good faith; if it can't be resolved, Customer may terminate the affected Services and receive a pro-rata refund of prepaid fees for them.

5.3 Kite imposes data-protection terms on each subprocessor that are no less protective than this DPA, to the extent appropriate to the service it provides, and remains responsible for its subprocessors' performance of those obligations.

6. Security

Kite maintains technical and organizational measures appropriate to the risk, including: encryption in transit (TLS) and at rest; API keys stored only as hashes; role-based access for Customer's team; audit logging of security-relevant changes; access to production systems limited to the people who run the Services; and incident response procedures. The current measures are described on the security page. Kite may change them over time but will not materially reduce the overall protection of Customer Personal Data.

7. Personal Data Breaches

7.1 Kite will notify Customer without undue delay, and in any case within 72 hours, after becoming aware of a Personal Data Breach. The notice goes to Customer's organization owners by email.

7.2 The notice will describe, as far as Kite knows at the time, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Where Kite doesn't yet have all of it, it will send the information in stages as it becomes available.

7.3 Kite will take reasonable steps to contain the breach and limit its effects, and will give Customer the information it reasonably needs to meet its own duty to notify regulators or data subjects. Kite's notice is not an admission of fault or liability.

8. Audits

8.1 Once a year on written request, and also after a Personal Data Breach, Kite will answer Customer's reasonable security questionnaire and provide the documentation that reasonably demonstrates compliance with this DPA.

8.2 Kite does not currently hold a SOC 2 report or an ISO 27001 certification. If it obtains one, providing the current report or certificate will satisfy section 8.1 for the matters it covers.

8.3 Where the information under section 8.1 does not reasonably demonstrate compliance, or a regulator requires it, Customer may audit Kite's compliance with this DPA, itself or through an independent auditor bound by confidentiality. The audit needs at least 30 days' written notice and an agreed scope, takes place during business hours without disrupting the Services or exposing other customers' data, and is at Customer's cost. Kite's subprocessors are audited through the reports and certifications they publish.

9. Return and deletion

9.1 Request logs are deleted automatically after the retention period Customer sets (7, 30 or 90 days).

9.2 Within 90 days after the Agreement ends, Kite deletes the remaining Customer Personal Data, except:

  • billing, invoicing and payment records, and the usage records that support them, which Kite keeps for as long as tax and accounting law requires; and
  • audit records of security-relevant events, kept in restricted form for as long as needed for security and legal claims.

Data in backups is deleted as the backups expire. The retained data stays protected by this DPA for as long as Kite holds it, and is used only for the purposes it is kept for.

10. International transfers

10.1 Kite's subprocessors process data in the locations listed on the subprocessor page, some of them outside the Kingdom of Saudi Arabia. Customer authorizes those transfers.

10.2 Kite transfers Customer Personal Data outside the Kingdom only as the PDPL permits: to a country that the competent authority has found to have an adequate level of protection, or otherwise under the appropriate safeguards the Regulation on Personal Data Transfer outside the Kingdom provides for, such as standard contractual clauses issued by the Saudi Data and Artificial Intelligence Authority (SDAIA), or another ground that Regulation allows. Kite will carry out any transfer risk assessment the PDPL requires.

10.3 Where the GDPR applies to Customer Personal Data and it is transferred to a country without an adequacy decision, the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Module Two, controller to processor), with the UK International Data Transfer Addendum for UK data, are incorporated into this DPA by reference. Section 2 completes their annexes, section 6 describes the technical and organizational measures, the subprocessor page lists the subprocessors, and the optional clauses are not used. If those clauses conflict with this DPA, the clauses prevail.

11. General

11.1 If this DPA conflicts with the Agreement on the processing of Customer Personal Data, this DPA prevails. The Agreement's limitations and exclusions of liability apply to this DPA, as far as Data Protection Law allows.

11.2 This DPA is governed by the law, and subject to the courts, that govern the Agreement: under section 17 of the Terms of Use, the laws of the Kingdom of Saudi Arabia and the competent courts in Riyadh. This does not affect the governing law of the Standard Contractual Clauses where they apply.

11.3 Kite may update this DPA to reflect changes in Data Protection Law or in the Services, with notice under the Agreement. An update will not materially reduce the protection of Customer Personal Data.

11.4 This DPA is written in English. Where Kite publishes an Arabic version, the Arabic version prevails if the two conflict.

Contact: legal@kite.sa. Founderproof, Inc., 2810 N Church St STE 90880, Wilmington, DE 19802, USA.

Kite API

بيانات العقارات السعودية للمطوّرين.

المنتج
  • تغطية البيانات
  • الباقات
  • المستثمرون والمطورون
  • فحوصات التقييم
  • التقنية العقارية والتطبيقات
المطورون
  • البدء السريع
  • الأدلة
  • مرجع API
  • خادم MCP
  • مكتبة JavaScript (npm)
  • مكتبة Python (PyPI)
  • سجل التحديثات
  • حالة الخدمة
الشركة
  • kite.sa
  • المدونة
  • تواصل معنا
  • الأمان
الشؤون القانونية
  • الشروط
  • المصادر وحقوق البيانات
  • الخصوصية
  • ملحق معالجة البيانات
  • جهات المعالجة الفرعية
© Kite