SparkleCloud Data Processing Agreement
Version: v1.0 · 18 November 2026
This agreement forms part of the SparkleCloud subscription between the organisation identified in the accepted order (Customer) and Brightness Subscriptions B.V. (Processor), Graftermeerstraat 22c, 2131 AC Hoofddorp, Netherlands, Chamber of Commerce number 81921985. It applies when Processor handles personal data on Customer’s behalf. Customer acts as controller or as an authorised processor for another controller. The parties may accept this agreement electronically by reference to its title, version and date in the order.
1. Instructions and duties
Processor processes personal data only on Customer’s documented instructions, including for transfers. The order, this agreement, authorised platform settings and connections, and authorised support requests can document instructions. If EU or Member State law requires processing, Processor informs Customer beforehand unless that law prohibits notice on important public interest grounds. Processor immediately tells Customer if it believes an instruction infringes applicable EU or Member State data protection law and may suspend that instruction pending resolution.
Customer ensures its instructions are lawful and manages its legal bases, notices, permissions and integrations. Processor does not use customer personal data for its own advertising, sell it or use it to train general-purpose AI models of its own. Its own subscription administration and billing are covered by the SparkleCloud Privacy Notice.
2. Processing schedule
Item | Scope |
|---|---|
Subject and duration | Provision of the selected SparkleCloud modules during the subscription and the applicable return, deletion and backup periods |
Nature and purpose | Hosting, storage, access, transmission, support, maintenance, backup, export and deletion. AI processing, transcription and integration exchanges where enabled |
People | Customer staff and users, customers, prospects, suppliers, applicants, contacts and other individuals whose data Customer includes |
Personal data | Contact details, identifiers, permissions, usage records, CRM records, business documents, communications, recordings, transcripts and AI inputs and outputs, as applicable |
Sensitive data | Special-category data, criminal offence data and high-risk data about children or vulnerable people require prior written agreement covering scope and safeguards |
Locations | Default hosting in the Netherlands. Brightness’s India team has no access to SparkleCloud production data, content, logs or support tickets. Additional locations for external processing must be documented and subject to section 4 |
3. Security and confidentiality
Processor implements appropriate measures under Article 32 GDPR. Access is limited to authorised persons bound by confidentiality. Measures include access controls and least privilege, MFA for privileged access, encryption in transit and protection of stored data, logging and monitoring, backups and recovery, separation of production and development, and incident response. Processor periodically reviews security and tests relevant measures. Routine support access requires documented authorisation. Necessary emergency access is limited, logged and reported without undue delay. Any higher security commitments in the order or agreed security schedule apply.
4. Subprocessors and customer integrations
Customer gives general written authorisation for the subprocessors identified in the SparkleCloud register supplied at contracting. Processor informs Customer by email or in the customer environment at least 30 days before adding or replacing a subprocessor. Customer may object for documented data protection reasons within 15 days. The parties seek a reasonable solution. If they cannot resolve a material objection, Customer may end the affected service before the change takes effect.
Processor imposes the same applicable data protection obligations on each subprocessor by written contract and remains responsible to Customer for its performance. Choosing a model in SparkleCloud does not change these duties where Processor engages the provider. If Customer operates its own model or contracts directly with a third-party service and instructs SparkleCloud to connect to it, Customer governs that direct relationship. The actual roles depend on how the service is contracted and operated. Processor complies with Chapter V GDPR for transfers it makes, including by using an adequacy decision or applicable safeguards such as EU standard contractual clauses, with additional measures where required.
Register to attach before use
[Insert the authorised SparkleCloud register or a dated link. Confirm any AI provider, gateway, transcription, infrastructure or support vendor engaged by Processor, with function, processing location and relevant transfer safeguards. Record an empty register explicitly if verified.]
5. Assistance and incidents
Processor uses appropriate measures to help Customer answer data subject requests and, taking account of the processing and available information, assists with Articles 32 to 36 GDPR. Processor forwards requests it receives about customer personal data and follows Customer’s instructions, subject to legal obligations. Processor notifies Customer without undue delay after becoming aware of a personal data breach and aims to send an initial notice within 24 hours. It provides available details about scope, affected data and people, likely consequences, mitigation and a point of contact, with updates as information becomes available. Send privacy and security notices to support@sparklecloud.ai.
6. End of service
At the end of processing, Customer chooses whether Processor returns or deletes the personal data. Self-service export is available during the active, paid subscription. Proposed support process for confirmation before use: Customer may give a return instruction before expiry or request a standard copy from support during the first 30 calendar days after the subscription ends. Processor verifies the requester and delivers the copy securely. Processor deletes active copies within 30 calendar days of the end date, subject to completing a timely return request, an applicable statutory retrieval period or legally required retention.
Processor deletes backup copies on expiry of the protected backup cycle. Proposed maximum for confirmation before use: 90 days after termination, as in the Brightness model. Residual backups are isolated and accessed only when required for recovery. If data is restored, the deletion instruction is reapplied. Where law requires retention, Processor isolates the data and retains it solely for that purpose until the obligation ends. Processor confirms deletion on request.
7. Evidence, audits and legal terms
Processor makes information necessary to demonstrate Article 28 compliance available to Customer and allows and contributes to audits, including inspections, by Customer or its appointed auditor. The parties protect confidentiality, other customers’ information and service security when arranging audits. Reasonable notice applies where possible, with urgency and regulatory requirements taken into account.
This agreement takes priority for personal data processing. Liability, law and jurisdiction follow the subscription agreement to the extent permitted by mandatory law. This agreement does not limit data subjects’ statutory rights or supervisory authorities’ powers.