Project Intelligence Framework
by BI DEVELOPMENT

Privacy Policy

Last updated 13 November 2026

This notice explains how BI Development handles personal data for Project Intelligence Framework, including temporary project-content processing and the separate account and support activities.

1 Who is responsible

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.

This notice explains personal data processed by BI Development for website visitors, business contacts and Service users. Your organisation controls its project data; BI Development processes content on its behalf under the DPA, including when content is handled only temporarily. For questions about your employer's project data, contact that organisation first. We will assist it where appropriate.

2 How the Service handles data

Project Intelligence Framework runs in your own Claude and connects to your organisation's Microsoft 365. Your own Claude connection may read mail, calendar, Teams and files. The BID server delivers plugin instructions, checks licences and performs certain connector actions. Customer files and outputs are held in the customer's systems; content used in Claude is also subject to that customer's Anthropic service and settings. We do not claim that all processing remains within Microsoft 365 or the EU.

The BID server transiently processes report mail sent from your mailbox through Microsoft Graph to your own PM address and text it formats into a document. These are not retained as a project-content store; document text is deleted as soon as the document is issued. Project facts such as codes, dates and statuses may pass through to determine next actions and are not stored. These facts can still be personal data if linked to a person. The BID server does not routinely read the contents of your selected OneDrive or SharePoint folder.

3 Data we receive and sources

From Microsoft sign-in we receive your work email, Microsoft Entra user and tenant identifiers and connector authorisation tokens. We store the tokens encrypted. We hold licence status, the permitted report recipient address, chosen OneDrive or SharePoint folder link and identifiers, and monthly call counts needed for your licence limits.

From you and Stripe we receive purchase work emails, order and subscription identifiers, subscription status and paid period, and relevant business billing or transaction records. Card details are entered with Stripe and do not reach BI Development. For accepted offers we also process customer contact and invoice details directly.

We process technical metadata such as request times, errors and event types to operate and secure the Service. Logging must exclude project-content bodies and secrets. Support enquiries include contact details, questions, messages and any attachments you choose to send. The website assistant receives the questions you enter and necessary interaction metadata. Avoid passwords, tokens, licence keys, unnecessary third party data and sensitive personal information in these channels.

4 Controller purposes and legal bases

We use work-account identifiers, licence and usage data to provide access, administer subscriptions, prevent licence misuse and communicate about the Service. Where you are personally the contracting business customer, processing necessary for your contract or requested pre-contract steps relies on GDPR Article 6(1)(b). Where your organisation is the customer, our basis for processing its representatives' details is Article 6(1)(f): our and the organisation's legitimate interests in managing that business relationship. We assess necessity and balance these interests against individual rights.

Support administration and business enquiries rely on the same distinction. Technical security, fraud prevention, essential service operation and proportionate evidence of contract acceptance rely on Article 6(1)(f), for our legitimate interests in keeping the Service secure and demonstrating contractual obligations. Mandatory tax, accounting and regulatory records rely on Article 6(1)(c) under applicable law. Establishing, exercising or defending legal claims may rely on Article 6(1)(f) and applicable retention obligations.

We do not sell personal data, use it for advertising or use it to train models. That commitment concerns our processing and contracted instructions; your own Claude plan is subject to your agreement and settings. We do not rely on blanket consent obtained by accepting Terms. If a future optional feature requires consent, we will seek it separately and explain withdrawal.

For project content processed on behalf of your organisation, it determines the purposes, lawful basis and any special-category condition. Our processing is governed by its instructions and the DPA rather than a separate controller purpose for that content.

5 Microsoft permissions and controls

The BID connector requests delegated Files.ReadWrite to save formatted documents in your selected folder, Mail.Send to send reports from your mailbox to your own address, User.Read for profile identification and offline_access to maintain the authorised connection. These permission scopes are technically broader than a single-folder or self-only description; the Service must enforce its narrower action rules. They do not themselves confer access to another user's account.

You or your organisation can disconnect the connector and revoke Microsoft permissions. We delete or render stored connector tokens unusable without undue delay on disconnection or licence end. Withdrawal of permissions prevents actions depending on them. Your organisation controls its Microsoft 365 and Claude access and retention separately.

6 Recipients and AI assistance

Microsoft provides Azure hosting and Entra authentication for BI Development. The BID workload is hosted in Azure North Europe, Ireland. Relevant Microsoft entities and onward vendors may process data under the applicable contracts. Our staff and authorised support personnel access only what their duties require.

Anthropic PBC, United States, provides the API used for our supervised AI support and website assistant. Support messages and attachments and website questions are submitted for that purpose. Anthropic processes the relevant data under the applicable commercial agreement and DPA; any retention or onward processing depends on those contracted terms and settings. We do not store the website questions in a BI Development question archive; this does not promise zero retention by the API provider. Ask for human review of an AI support answer at support@bidevelopment.ro.

Stripe receives payment and transaction data. Its legal entity and controller or processor role depend on the particular Stripe product and purpose. Where acting as independent controller, including for its own payment compliance or a verified merchant-of-record transaction, its privacy notice applies to that processing. It is not a subprocessor for customer project content. See https://stripe.com/privacy for its notice and the checkout for the actual merchant identity.

Your own Microsoft 365 and Claude suppliers operate under your organisation's contracts. Professional advisers and competent authorities may receive limited information where necessary for legal duties or claims, subject to confidentiality and legal restrictions. We do not disclose project content to payment services.

7 Locations and transfers

Azure hosting in Ireland does not establish that all vendor processing or remote access occurs within the EEA. Anthropic API use and vendor support or onward processing may involve the United States or other countries. Before a restricted transfer, we must identify the actual recipient, countries and applicable safeguard.

Where applicable, transfers use a valid adequacy decision or executed SCCs under Commission Decision (EU) 2021/914, with appropriate assessment and supplementary safeguards. DPF reliance is limited to a verified active US entity and covered data under the applicable adequacy decision. This notice does not assert that every named vendor is DPF-certified or that SCCs have been executed for every account. Transfers lacking a valid mechanism must be suspended until regularised.

Contact support@bidevelopment.ro for the relevant destination information and a copy of applicable safeguards, with justified confidential information protected. The DPA governs transfers of Customer Personal Data; your own provider contracts govern transfers arising from your direct use of Claude or Microsoft 365.

8 Retention

Transient report and document content is used only for the requested action and is not retained as project content; document text is deleted when the document is issued. Failed or abandoned jobs must also clear temporary content. Project facts passing through the BID server are not stored.

Connector tokens are retained while the authorised connection and licence remain active and deleted or rendered unusable without undue delay on disconnection or licence end. Account, licence, folder-reference and usage records are kept during the licence and deleted within 90 days after it ends, unless a specific legal retention duty or necessary legal claim requires a limited subset longer.

Technical logs are retained only as needed for operation, security and incident investigation, with a maximum of 90 days unless particular entries are necessary for a documented incident or legal claim. Support correspondence is retained while needed to resolve the request and support the active licence and deleted within 90 days after licence end; for non-customers, within 90 days after closure, subject to necessary legal exceptions.

Invoices, accounting records and necessary transaction evidence are retained for the period required by applicable Romanian law. Contract acceptance and dispute records are kept for the applicable limitation period and any pending claim. We retain only the necessary subset, restrict access and delete it when the duty or claim ends. You may request the applicable category-specific retention criterion and legal requirement from us. A legal hold does not justify keeping all account data indefinitely.

Residual copies within our control must follow the same 90-day deletion outer limit where no longer retention is legally necessary. We do not maintain backups of transient project content. Data held in your organisation's own Microsoft 365 or Claude follows its own retention arrangements and is not erased by cancelling this licence.

9 Your rights

Where applicable, you may request access, correction, deletion, restriction of processing and portability of data processed automatically on consent or contract. You may object to processing based on legitimate interests for reasons relating to your situation; we will assess the request under the GDPR. If we ever rely on consent, you may withdraw it at any time without affecting prior lawful processing. These rights have legal conditions and exceptions.

Send requests to support@bidevelopment.ro. We may ask for proportionate identity verification. We normally respond within one month; if an extension of up to two further months is permitted because of complexity or number of requests, we will explain it within the first month. Requests concerning project content controlled by your organisation will be forwarded or directed to it, with our assistance under the DPA.

You may complain to ANSPDCP, the Romanian supervisory authority, at https://www.dataprotection.ro, or to the authority where you habitually reside, work or believe an infringement occurred. You do not have to contact us first. Judicial remedies remain available.

10 Required information and automated operations

Work identifiers, licence and payment-status information and relevant permissions are needed to provide the Service. Without them, we cannot activate or operate the affected features. Support details beyond what is necessary are optional. Data may be received indirectly from your organisation, Microsoft and Stripe as described above; the categories and purposes are the same.

Licence checks, call limits and payment-status controls operate automatically. We do not use the Service to make solely automated decisions about individuals producing legal or similarly significant effects. If you believe an access decision is wrong, request human review at support@bidevelopment.ro. AI-generated project drafts require review by the authorised user.

11 Cookies and similar technologies

The BI Development website is intended to operate without cookies for advertising or analytics. The connector uses only technologies necessary for sign-in and requested functions. Stripe checkout, Claude and Microsoft services may use their own technologies under their notices. Any non-essential storage or tracking added to our own site will require a separate assessment, clear information and consent where legally required before activation.

12 Updates and contact

We publish changes with a new date and notify licence holders in advance of significant changes. A notice update does not itself change an existing lawful basis or authorise a new purpose. Contact support@bidevelopment.ro for all privacy questions and to obtain current supplier, transfer and retention information.