Data Processing Agreement
This agreement governs BI Development’s processing of business customer personal data for Project Intelligence Framework and is accepted with the Terms of Use.
1 Parties and incorporation
This Data Processing Agreement (DPA), including Annexes 1 to 4, forms an annex to the Terms of Use for Project Intelligence Framework (Terms). The Customer is the business or organisation identified in the accepted order or offer. BI Development is the service provider identified below. The DPA takes effect when the Customer accepts the Terms electronically, or when an accepted offer incorporates them. No separate signature is required.
Brand Identity Development S.R.L. ("BI Development"), Strada Tuberozelor 102, Complex MRS Country, Sat Păulești, Comuna Păulești, Prahova County, Romania; Trade Register no. J2015000188290; CUI 34076453; EUID ROONRC.J2015000188290. Contact: support@bidevelopment.ro.
GDPR means Regulation (EU) 2016/679. Personal data, processing, controller, processor, personal data breach and supervisory authority have their GDPR meanings. Customer Personal Data means personal data processed by BI Development on behalf of the Customer in delivering the Service, including temporary processing and relevant support content.
2 Roles and scope
The Customer is controller of Customer Personal Data and BI Development is processor. If the Customer acts as processor for another controller, it confirms authority to appoint BI Development as a further processor and to give the instructions in this DPA. References to the Customer's controller obligations apply accordingly through that chain.
BI Development is a separate controller for account administration, licensing, billing records, service security and its own business correspondence, as explained in the Privacy Policy. Roles follow the purpose of each operation; a support ticket may include both business correspondence and Customer Personal Data. Customer content submitted for troubleshooting remains protected by this DPA for that processing.
The Customer's own Claude and Microsoft 365 services are procured under its own contracts. They are not appointed by BI Development merely because the Customer connects them. BI Development remains responsible for vendors it actually engages to perform its own processing. Payment providers do not receive project content under this DPA.
3 Instructions and lawful processing
The Customer instructs BI Development to perform only the operations in Annex 1, including transfers permitted under clause 8. Instructions comprise this DPA, the accepted order, configuration choices and authorised requests through the Service or support@bidevelopment.ro. BI Development shall not sell Customer Personal Data, use it for advertising, train models on it or repurpose it for its own product development.
BI Development shall process Customer Personal Data only on documented instructions, unless required by Union or Member State law to which it is subject. It shall inform the Customer of that legal requirement before processing unless that law prohibits notice on important grounds of public interest. It shall immediately inform the Customer if, in its opinion, an instruction infringes applicable data protection law and may pause the affected operation while the parties resolve the issue.
The Customer shall establish the lawful basis, provide required notices, respect employee and third party rights, minimise submitted data and ensure lawful instructions and permissions. These duties do not reduce BI Development's own obligations. The Service is not intended for sensitive or criminal offence data; any necessary processing of such data requires prior written agreement on safeguards and the Customer's applicable legal condition.
4 Confidentiality and security
BI Development shall ensure that persons authorised to process Customer Personal Data are bound by confidentiality or an appropriate statutory obligation and access data only as needed. It shall implement and maintain the measures in Annex 2 and security appropriate to risk, taking account of the state of the art, implementation costs and the nature, scope, context and purposes of processing. Measures may evolve without materially reducing protection.
5 Assistance and accountability
Taking account of the nature of processing and information available to it, BI Development shall assist the Customer with data subject requests through appropriate technical and organisational measures, and with security, breach response, data protection impact assessments and prior consultation under GDPR Articles 32 to 36. It shall promptly forward requests concerning Customer Personal Data and shall not substantively answer them except on instruction or as legally required. It shall preserve relevant information and provide timely assistance so the Customer can meet applicable deadlines.
BI Development shall maintain the records required for its processor activities and cooperate with competent supervisory authorities. It shall provide information necessary to demonstrate compliance with this DPA. Routine assistance is included in the Service; any genuinely exceptional additional services require a separately agreed scope and fee, without delaying legally required cooperation.
6 Personal data breaches
BI Development shall notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data. It shall aim to provide initial notice within 24 hours of awareness; this operational target does not postpone the duty to notify without undue delay. Notice goes to the Customer's registered administrative email, with another available channel used if needed.
As available, notice shall describe the incident, affected data and persons, approximate numbers, likely consequences, containment and remediation and a contact for follow-up. BI Development shall send phased updates rather than delay initial notice, investigate, mitigate harm, preserve relevant evidence and cooperate with the Customer. It shall not notify data subjects or authorities on the Customer's behalf without instruction, unless legally required. The Customer retains responsibility for its own notification decisions and statutory deadlines.
7 Subprocessors
Subject to Annex 3 and clause 8, the Customer gives general written authorisation to the identified subprocessors for the stated purposes. BI Development shall bind each subprocessor to equivalent applicable data protection obligations, including sufficient security guarantees, before access and remains fully liable to the Customer for performance of those obligations.
BI Development shall email the Customer's registered administrative contact at least 30 days before adding or replacing a subprocessor, stating its legal identity, function, location and transfer safeguards. The Customer may object during that period on reasonable data protection grounds. The parties shall seek a reasonable alternative. If none is available, the Customer may terminate the affected Service before the change, with a refund of unused prepaid fees for the terminated portion. BI Development shall not disclose the Customer's data to the disputed new vendor before resolution or termination. Updating a website list alone is not sufficient notice.
8 International transfers
Primary BID server hosting is Microsoft Azure North Europe, Ireland. EEA hosting does not exclude access or onward transfers outside the EEA. BI Development shall identify relevant recipients, countries and the legal mechanism, and make that information available to the Customer before an affected transfer. It shall not initiate or permit a restricted transfer without valid safeguards and the Customer's documented instructions.
Where a valid adequacy decision applies, it may be used only within its scope. For the EU-US Data Privacy Framework (DPF), BI Development shall verify and document the particular US recipient's active certification, covered entity and relevant data coverage before reliance and monitor continued eligibility. A vendor brand name is not proof of coverage.
Where appropriate and applicable, BI Development shall execute the unmodified Commission Implementing Decision (EU) 2021/914 Standard Contractual Clauses (SCCs), select the correct module, complete all required annexes and options, assess destination-country laws and practices and implement necessary supplementary measures. Module Three is ordinarily relevant to BI Development's processor-to-subprocessor transfer; Module Two is ordinarily relevant to its separate controller-to-processor transfer. Other routes require their own analysis.
This DPA is not itself an executed set of SCCs. BI Development shall provide copies or relevant extracts of applicable safeguards on request, with only justified confidential information redacted. If safeguards cease to be effective, it shall suspend the affected transfer until a lawful solution is in place or terminate the affected processing and return or delete the data. Access by non-EEA customers, and any UK or Swiss law requirements, shall be assessed separately where applicable.
9 Return and deletion
During the Service, project content is handled transiently as described in Annex 1. On expiry or termination, processing access shall cease and stored connector tokens shall be deleted or rendered unusable without undue delay. At the Customer's choice, BI Development shall return any remaining Customer Personal Data in a reasonably usable format and delete its copies, or delete it, within 90 days. The Customer should request return before termination or promptly afterwards. This period is an outer limit, not permission to retain transient content for 90 days.
Project data held in the Customer's Microsoft 365 or Claude is controlled through its own providers and is not deleted by BI Development. Any residual backup copies within BI Development's control shall be isolated from operational use and deleted within the same 90-day outer limit. No project-content backup is authorised by this DPA. If Union or Member State law requires retention, BI Development shall identify the requirement, restrict the data to that purpose and delete it when the requirement ends. It shall confirm completion on request.
10 Audits
BI Development shall allow and contribute to audits, including inspections, by the Customer or an independent auditor it mandates, and make all information necessary to demonstrate compliance available. Relevant independent reports and remote evidence may be reviewed first, without removing inspection rights. Ordinarily the Customer shall give 15 working days' notice and use confidentiality protections that preserve statutory rights and protect other customers.
An annual routine review is the normal planning basis; additional audits remain available following an incident, reasonable compliance concerns or a competent authority's request. Urgent audits shall not be delayed by routine notice. Each party bears its own internal costs unless otherwise agreed; fees shall not prevent exercise of statutory audit rights. Confirmed deficiencies shall be remedied promptly.
11 Priority and liability
This DPA prevails over conflicting Terms for data protection matters. Applicable executed SCCs prevail over this DPA in their field. The Terms govern inter-party liability to the extent lawful; no limitation restricts data subject rights, supervisory powers, mandatory GDPR liability or obligations under SCCs. Romanian law and the jurisdiction provision in the Terms govern this DPA, subject to mandatory data protection law. Clauses requiring continued protection survive until processing ends and deletion is complete.
Annex 1 Processing particulars
Subject and purpose: enabling the Customer's licensed Project Manager to use Project Intelligence Framework with the Customer's own Claude and Microsoft 365, including temporary formatting of requested documents and sending reports to that PM; relevant troubleshooting only on request. The Service is licensed per PM and work account.
Duration and frequency: on demand during the subscription, including recurring report actions configured by the Customer; only necessary residual processing during return or deletion under clause 9. A request is processed for the time needed to complete it; document text is deleted as soon as the document is issued and report content is not retained as a content store. Failed requests must also be cleared when abandoned.
Nature of operations: receipt, access, transient use, formatting, transformation, transmission to Microsoft Graph, writing requested documents to the selected OneDrive or SharePoint folder, and deletion. The BID server does not routinely read the contents of that folder. The Customer's Claude connection may access mail, calendar, Teams transcripts and files separately under the Customer's contracts.
Data subjects: authorised users; the Customer's employees, contractors, project participants, customers, suppliers, meeting attendees and correspondents whose data appears in submitted content.
Data categories: names, business contact details, roles, meeting participation, communications, project assignments, dates, statuses, identifiers and personal data contained in report mail, document text or troubleshooting material submitted to BI Development. Codes and project facts may remain personal data where linkable to a person; removal of names alone does not establish anonymity.
Special categories and criminal offence data: not intended or authorised by default. Incidental receipt must be minimised and handled securely; further use requires the assessment and agreement in clause 3. The Customer remains responsible for third party rights and any necessary Article 9 or 10 condition.
Instructions and contacts: the Customer's authorised administrator is the contact identified in its order or account. BI Development's data protection, incident and instruction contact is support@bidevelopment.ro. The Customer shall keep its contact current.
Annex 2 Required technical and organisational measures
The following are contractual minimum measures for processing under this DPA. They describe obligations, not a claim of an independent certification.
- Access and isolation: unique staff identities, access limited to duties, multifactor authentication for privileged access, prompt revocation, separation of customer authorisations and protection against cross-tenant access.
- Tokens and secrets: encrypt stored Microsoft tokens; restrict key and secret access; keep secrets out of source code, logs and support material; revoke or render tokens unusable on disconnection or licence end; review access regularly.
- Transport and storage: encrypted network transport using current secure protocols; encrypted persistent storage for Customer Personal Data; appropriate key management; Azure North Europe for the BID workload, subject to documented vendor access and transfers.
- Data minimisation: process only content needed for a requested action; do not log message bodies, document text, tokens or full Graph payloads; prevent content capture in tracing, crash reports, queues and temporary files; clear transient content after success or failure.
- Permissions and actions: request only justified delegated Microsoft permissions; validate the authorised tenant and account; enforce report recipient equality with the PM's authorised address on the server; protect against arbitrary recipients, unauthorised file access and malicious instructions in source content.
- Secure operations: controlled deployments, supported components, vulnerability and dependency review, risk-based patching, security logging without project content, monitoring and incident handling; restricted support access subject to confidentiality.
- Resilience and verification: maintain recovery arrangements for essential service configuration without backing up transient project content; test restoration and deletion; periodically assess effectiveness of security controls and remediate findings according to risk.
- Personnel and suppliers: confidentiality, security and AI literacy training appropriate to duties; vendor due diligence and contracts; documented request, incident and deletion procedures; evidence of compliance and periodic review.
Annex 3 Subprocessors and other recipients
Microsoft Azure and Microsoft Entra ID: hosting, connector authentication and infrastructure operated for BI Development. BID hosting location is North Europe, Ireland. Relevant data includes transient content on Azure and identifiers, tokens and operational metadata as required for each service. Microsoft group contracting and processing entities, support locations and onward subprocessors shall be identified to the Customer before their access is authorised. Clause 8 applies to any restricted access or transfer.
Anthropic PBC, United States: API-based support and website assistant used by BI Development. For support submitted on the Customer's instructions, data is limited to necessary messages, attachments and troubleshooting content. General website questions and BI Development's own support administration are addressed in the Privacy Policy as controller processing. No routine flow of project content to BI Development's Anthropic API is authorised merely by this listing. Any such flow requires prior scope review, notice and lawful safeguards.
Conditional authorisation: vendor names describe the service providers currently identified. BI Development shall supply the exact relevant legal entities, countries and effective transfer safeguards before access to Customer Personal Data and obtain any authorisation required by clause 7 for a new entity. No unverified SCC execution, DPF certification or zero-retention arrangement is represented by this annex.
Stripe is a payment and billing recipient outside the project-data processing chain. Its exact entity and role depend on the contracted product and transaction; project data must not be sent to Stripe. Customer-procured Microsoft 365 and Claude are separate recipients under the Customer's contracts, not BI Development-appointed subprocessors for those contracts.
BI Development shall maintain the current list with this DPA and email changes under clause 7. Detailed vendor and safeguard information and copies of relevant safeguards may be requested at support@bidevelopment.ro.
Annex 4 Transfer implementation record
Before a restricted transfer, BI Development shall record the exporter and importer legal names and contacts, roles, countries, purposes, data categories, data subjects, frequency, duration, onward recipients and applicable security measures. Annexes 1 and 2 provide the service-level description; each vendor record shall add the destination-specific particulars.
For SCC reliance, the record shall identify the signed agreement, correct module, selected options, competent supervisory authority, governing law, courts and completed SCC Annexes I, II and, where relevant, III; it shall retain the transfer impact assessment and supplementary safeguards. For DPF reliance, the record shall retain dated evidence of active certification and scope and the applicable adequacy decision. No transfer is enabled solely by an entry saying SCC or DPF.
The Customer may obtain the relevant record and safeguards under clause 8. BI Development shall review them following material vendor, legal or architectural changes and suspend affected transfers when lawful safeguards cannot be maintained.