This agreement is between Web Ninja FZCO (“Glideworth”, a free zone company in Dubai, United Arab Emirates, registered address Unit 001-46348, Building A1, Dubai Digital Park, Dubai Silicon Oasis, Dubai, United Arab Emirates) and the customer who uses the service as described above (“the customer”). It forms part of the terms of service. It applies to the UK GDPR, the EU GDPR and laws that implement them (“Data Protection Law”). Terms such as “personal data”, “controller”, “processor” and “data subject” have their meaning in that law.

1. Subject matter and duration

Glideworth processes personal data for the customer to provide the hosted service described in the terms. The details are in Annex I. This agreement lasts as long as Glideworth processes that data, which includes the period before deleted data ages out of backups.

2. Instructions

Glideworth will process the personal data only on the customer’s documented instructions. The terms, this agreement, and the customer’s use of the service’s features (including the API, MCP server, export and deletion) are the customer’s instructions. If Glideworth believes an instruction breaches Data Protection Law it will tell the customer. If the law requires Glideworth to process the data otherwise, it will say so first unless the law forbids it.

3. Confidentiality

Glideworth makes sure that people allowed to process the data are bound by confidentiality. Staff cannot see the contents of a workspace except through a support grant the customer creates (Annex II).

4. Security

Glideworth takes the measures in Annex II, which are meant to meet Article 32 of the GDPR. Glideworth may change them if the protection is not reduced.

5. Sub-processors

The customer gives general authorisation for Glideworth to use the sub-processors on the sub-processor list. Glideworth will:

  • keep that list up to date and give the customer at least 30 days’ notice of a new or replacement sub-processor, so the customer can object on reasonable data protection grounds;
  • if the customer objects and the parties cannot agree, allow the customer to stop using the service for the affected data and receive a refund of prepaid fees for the unused period;
  • put terms on each sub-processor that give the same level of protection as this agreement; and
  • remain responsible to the customer for each sub-processor’s performance.

6. International transfers

Glideworth plans to store customer data in the European Union (Germany). Glideworth is based in the United Arab Emirates, and its staff may reach that data from there, only for support and operations and only under the access controls in Annex II. The EU has not made an adequacy decision for the UAE, and Glideworth does not rely on an adequacy decision from the UK for it.

To the extent the customer’s use of the service is a transfer that needs a safeguard under Chapter V of the GDPR or the UK GDPR, the parties agree the following, and they apply only to that extent:

  • EU. The standard contractual clauses in Commission Implementing Decision (EU) 2021/914, Module Two (controller to processor), are incorporated. Clause 7 (docking clause) does not apply. Under Clause 9(a) Option 2 applies, with the notice period in section 5. The optional language in Clause 11(a) does not apply. Under Clause 13 the competent authority is the one for the customer’s establishment. Under Clauses 17 and 18 the law and courts are those of the EU Member State where the customer is established, or if that law does not allow third-party beneficiary rights, those of Ireland. Annex I of this agreement is Annex I.B of the clauses, Annex II is their Annex II and Annex III is their Annex III. The parties and the competent authority are as described above.
  • UK. The UK International Data Transfer Addendum to those clauses, issued by the Information Commissioner under section 119A of the Data Protection Act 2018, is incorporated, with the details above. In its Table 4, the exporter (the customer) may end the Addendum if the Information Commissioner issues a revised one.
  • The Commission has said that those clauses cover transfers to importers who are not subject to the GDPR. If they do not apply because Glideworth is itself subject to the GDPR for this processing, the rest of this agreement still applies in full.

7. Helping the customer

Taking account of the nature of the processing, Glideworth will:

  • help the customer answer data subject requests. The customer can use the in-app export and deletion tools and the personal-data download directly. Glideworth will pass on any request it receives about the customer’s data and will not answer it itself except to say it was passed on;
  • help the customer meet its obligations about security, breach notification, data protection impact assessments and prior consultation, so far as it relates to the processing and the information Glideworth has.

8. Personal data breaches

Glideworth will tell the customer without undue delay, and aims to do so within 48 hours, after becoming aware of a personal data breach affecting the customer’s data, with the information it then has: what happened, the data and people affected, likely consequences, and what has been done. It will give further information as it learns it.

9. Deletion and return

At the end of the service, or when the customer asks, the customer can export a complete copy and delete the workspace in the app. On deletion the live database is deleted at once, and encrypted backups age out within a further 35 days. If the customer asks Glideworth to delete it, Glideworth does so within 30 days. Glideworth keeps only what the law requires, such as billing and accounting records, and a minimal record that the workspace existed. A workspace that is read-only after a lapse is deleted on the timetable in the privacy policy, section 7, with warning emails 30 and 7 days before, so the customer should export what it needs before then.

10. Information and audits

Glideworth will give the customer the information needed to show compliance with Article 28, including a reasonable written description of its security measures, and will allow and contribute to audits (including inspections) by the customer or an auditor it appoints, on reasonable notice, no more than once a year unless there has been a breach, during working hours, subject to confidentiality and without exposing other customers’ data. The customer pays its own costs, and Glideworth’s reasonable costs beyond a first request. Glideworth holds no security certification at the date of this document and does not claim any.

11. Liability and order of precedence

Liability under this agreement is subject to the limits in the terms, to the extent the law allows. Nothing in this agreement or the terms limits the rights of data subjects, or any liability to them that the law does not allow to be limited. If this agreement conflicts with the terms on the processing of personal data, this agreement prevails.

12. Law

This agreement is governed by the laws applicable in the Emirate of Dubai and the federal laws of the United Arab Emirates, subject to anything Data Protection Law requires, and to the choices of law in section 6 for the standard contractual clauses.

Annex I: Details of the processing

Item Details
Controller The customer
Processor Web Ninja FZCO, Unit 001-46348, Building A1, Dubai Digital Park, Dubai Silicon Oasis, Dubai, United Arab Emirates
Subject matter Hosting and operating a personal financial planning workspace, its API and its MCP server
Nature of processing Storing, retrieving, calculating, displaying, backing up, exporting and deleting data, as the customer directs
Purpose To provide the service to the customer
Duration The life of the workspace, plus the backup period in section 9
Categories of data subjects The customer’s own clients, household members and other individuals about whom the customer enters data
Types of personal data Names, ages or dates of birth, family and household structure, income, spending, assets, accounts, pensions and tax details, plans, assumptions, notes and any data the customer chooses to enter. Account data of the customer’s users: email, name, sign-in and security records
Special category data Not intended. The customer must not enter it
Frequency Continuous, for the life of the workspace
Location European Union (Germany planned). See sub-processors. Glideworth staff may reach it from the United Arab Emirates, as section 6 says

Annex II: Security measures

These are the measures the hosted service is designed to have. Each is to be confirmed as implemented before the hosted service opens.

  • In transit and at rest. TLS for all traffic. Encrypted data volume. Backups encrypted per workspace with their own key (AES-256-GCM). The service is not end-to-end encrypted: Glideworth’s servers can read the workspace.
  • Separation. Each workspace is a separate database file. Credentials carry the workspace identity, and tests check that one workspace cannot read another.
  • Authentication. Passwords stored as salted scrypt hashes. Tokens, API keys and recovery codes stored as hashes. Two-factor sign-in (planned). Sign-in throttling and bot checks. Password re-entry for sensitive actions. Session lists and revocation. New-device alerts.
  • Access. Operator console on a private interface only, with mandatory two-factor sign-in. It does not show workspace contents. Time-limited, customer-created, read-only support grants are the only route to contents, and each view is logged and notified to the customer. This applies to staff wherever they are, including in the United Arab Emirates.
  • Least data in logs. An allowed-field logging rule. No financial values, request bodies, query strings, cookies, tokens or error text in logs or error reports, enforced by an automated test.
  • Backups and recovery. Changed workspaces are backed up every 15 minutes. Every backup is kept for 48 hours, then the newest each day for 30 days. Restore is tested regularly. Targets of 15 minutes for data loss and 15 minutes to restore one workspace are objectives, not guarantees.
  • Deletion. Workspace deletion removes the live database and the workspace’s backups age out within 35 days.
  • Audit trail. Account security events and per-workspace data changes are recorded.
  • Network and host. Firewall, hardened host, TLS with strict transport security, security headers.
  • Incident handling. A written incident process and a security contact (security@glideworth.com).
  • Not done. Application-level encryption of live databases. Third-party security certifications.

Annex III: Sub-processors

See the sub-processor list, which is incorporated into this agreement. It is currently a list of proposed providers. It will be final before the hosted service accepts sign-ups.